You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SDK currently exposes the following REST endpoints as thin wrappers over tendermint:
GET /node_info
GET /syncing
GET /blocks/latest
GET /blocks/{height}
GET /validatorsets/latest
GET /validatorsets/{height}
In keeping with how we are marking all other non GRPC-gateway based REST endpoints as deprecated (#7686), we need to decide if these endpoints should also be considered deprecated, and if so, what alternative endpoints we communicate users to use instead for Stargate chains.
The options as I see them:
Leave endpoints as is (undeprecated), and continue supporting these endpoints for Stargate, not deprecating until we have a bigger aligned plan with tendermint's future use of grpc and/or grpc gateway
Mark as deprecated and write GRPC + GRPC services exposing the same functionality via standard Cosmos SDK grpc(+gateway) interfaces
Mark as deprecated and tell clients to query tendermint RPC directly for these queries
Would be good to hear from someone on the Tendermint side about this as well-- possibly @marbar3778 ?
The SDK currently exposes the following REST endpoints as thin wrappers over tendermint:
In keeping with how we are marking all other non GRPC-gateway based REST endpoints as deprecated (#7686), we need to decide if these endpoints should also be considered deprecated, and if so, what alternative endpoints we communicate users to use instead for Stargate chains.
The options as I see them:
Would be good to hear from someone on the Tendermint side about this as well-- possibly @marbar3778 ?
cc @amaurymartiny (see original comment here)
The text was updated successfully, but these errors were encountered: