-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
C:rpcComponent: JSON RPC, gRPCComponent: JSON RPC, gRPCT:designType: Design work is neededType: Design work is needed
Milestone
Description
The Tendermint RPC endpoints evolved somewhat haphazardly and insufficient attention has been given to production concerns. We have strived to enable the default Tendermint RPC endpoints to be safe to expose over the public internet, though we in general don't recommend this. Certain endpoints leak information (#3055), while others still pose DoS vulnerabilities (#3076). Other issues suggesting the need for a larger rethink of the RPC design include:
- events: distinguish between internal consensus events and the block-level user events #3210
- Tendermint has four serialization protocols #608
- Improvements to Tendermint RPC #529
- Move
unsafe_*rpc commands to independent devops server #193
There's also questions around how mature Tendermint's indexer should be, and at what point we should just stream events out to an external indexer like postgres (#1161).
Opening this issue to track discussion around the RPC, and to solicit feedback from users on what they'd like to see here.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C:rpcComponent: JSON RPC, gRPCComponent: JSON RPC, gRPCT:designType: Design work is neededType: Design work is needed