gRPC¶
gRPC is the typed protobuf gateway to selected Koinos RPC services. Clients use generated protobuf interfaces, while the gateway forwards each request through RabbitMQ to the microservice that owns the method.
Dependencies and inputs¶
The service depends on RabbitMQ, the public gRPC service definitions, and each internal service required by an exposed method. The public schema contains a selected API surface; it does not expose every internal RPC used inside the node.
Outputs and interfaces¶
gRPC returns typed protobuf responses and gRPC status errors. Depending on the enabled services, its methods can query Chain, Block Store, Mempool, P2P, Transaction Store, Contract Meta Store, and Account History.
The gateway does not originate consensus decisions or maintain a second copy of chain state.
State and consistency¶
gRPC owns protocol and in-flight request state, not blockchain databases. A reachable gRPC endpoint can still report that its target service is unavailable or return data from an index that is catching up.
Client and server schemas must be compatible. Retrying a read is different from retrying a transaction or block submission after an uncertain timeout.
Public API operation
Transport security, exposure, message limits, and health checks belong in the public API node guide.