List view
Proposed improvements in order to deploy **lite-rpc** on a larger scale based on these following requirements: - [rpcpool.com](http://rpcpool.com) operators: **securely managed stake identity** through a standalone quic proxy - access to stake identity is considered high-risk - multiple lite-rpc instances in the same region can not trivially share a stake identity - [rpcpool.com](http://rpcpool.com) operators: prefer **geyser over jsonrpc** connectivity - mango-feeds library can provide the necessary abstraction: [milestone](https://github.com/blockworks-foundation/mango-feeds/milestone/1) - mango traders: simplify integration into existing **rust stack** - json rpc is a good interface to integrate arbitrary languages, for rust based users a linkable library would be preferred - mango traders: allow low latency access to **all commitment status** - rpc blockSubscribe is limited to confirmed yet status *processed* is required for some use cases - geyser subscription provides block once processed by replay stage
No due date•3/4 issues closed