Skip to content
This repository has been archived by the owner on Feb 23, 2022. It is now read-only.

light client: coordinate exposed API #163

Closed
tac0turtle opened this issue Sep 17, 2020 · 1 comment
Closed

light client: coordinate exposed API #163

tac0turtle opened this issue Sep 17, 2020 · 1 comment
Labels
C:light Component: Light client C: rpc Component: RPC

Comments

@tac0turtle
Copy link
Contributor

tac0turtle commented Sep 17, 2020

Light client implementations should coordinate exposed API's.

This way users will not have to implement the communication separately.

Currently, the go implementation shares the same API as the RPC layer. I believe this is a good approach and if its adopted as the light client spec API we should form an RPC API spec within this repo.

Things to note about this discussion:

  • Tendermint-go had a conversation around migrating to gRPC
    • This conversation may need to be moved into this repo if clients will share API's. Although we could keep the RPC layer as is and clients could add a layer like gRPC as a feature of their client if they see it necessary or useful.
@cmwaters
Copy link
Contributor

I think we can close this. The API's in term of the RPC endpoints are aligned and there aren't any conversations currently of changing that

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C:light Component: Light client C: rpc Component: RPC
Projects
None yet
Development

No branches or pull requests

2 participants