RP1’s native JSON-RPC server is not a thin alias for a CometBFT node. It includes custom handlers for status, transaction broadcast, retained transaction observation, block headers, validators, DAG data, and feature benchmarks.
Common methods
| Method | Use |
|---|---|
status |
Node and canonical application status. |
abci_query |
Query application state through the compatibility adapter. |
broadcast_tx_sync |
Submit a signed envelope and receive admission information. |
broadcast_tx_async |
Submit without waiting for admission completion. |
broadcast_tx_commit |
Request broadcast plus commit observation where the endpoint supports it. |
tx |
Observe a retained transaction by exact hash and retrieve raw evidence. |
block_header |
Read the complete current retained header without transaction bodies. |
block / block_results |
Read current retained block data under RP1’s current-only and completeness rules. |
WebSocket subscribe |
Receive supported event streams from the native RPC service. |
Canonical-head rule
status may expose an application head ahead of the complete retained consensus header after an application commit. Block-specific methods require a complete canonical retained header and must return an explicit unavailable error rather than fabricate a hash, app hash, timestamp, or empty transaction sidecar.
For a common-height cluster check, poll concurrent unqualified block_header responses. Do not request a header height derived from a status response and assume that it exists on every validator.
Cosmos client compatibility flows may call ABCIInfo through the adapter used around the native server; that compatibility method is not a separately registered native JSON-RPC handler. Native RPC callers should use the methods listed above, including abci_query.
Broadcast safety
Public RPC bodies and batches are bounded. A client should handle HTTP 413 or JSON-RPC errors as admission failures and never treat a truncated or oversized request as a valid prefix. Keep the exact signed envelope, hash, signer, account number, and timestamps in the client record.
WebSocket caution
Subscriptions are an observation convenience. They can disconnect, deliver duplicate notifications, or race with a query. Use the transaction hash and a committed query as the source of truth.