serve network data reliably.
RPC and indexing infrastructure should be treated as independently scalable services with explicit limits, health checks and failure boundaries.
RPC exposure
Bind administrative interfaces privately. Public endpoints should use rate limits, request-size limits, transport security and upstream protections appropriate to their traffic profile.
indexing pipeline
Track canonical chain state, reorg handling, ingestion lag and failed transformations. Consumers should be able to distinguish fresh indexed data from temporarily stale results.
capacity
Plan CPU, memory, storage and connection capacity separately for node execution, RPC serving and indexer workloads. High-volume public services should not compromise validator duties.
qualified configuration
Ports, process flags, retention settings and public service limits will be published with qualified releases rather than copied from development defaults.