Open Samyoul opened 4 years ago
Hm, writing a spec for this seems both a bit early and a bit like busy work - ie this would be a natural part of the API documentation of the library itself, and it's probably too early to formalize it into a spec per se
You are probably right. We need somewhere to document the API, and on reflection in the spec may not be the correct place. I believe that some global document would be a better location than in the library directly as, although the lib exposes the API, the various Status clients are dependant on the API and each need to implement calls to the methods.
The compiled
status-go
binary exposes a number of endpoints that are consumed by desktop and mobile implementations of the Status app.API endpoints are specified in code her https://github.com/status-im/status-go/tree/develop/mobile
C bindings are generated here https://github.com/status-im/status-go/tree/develop/cmd/library