RPC API Matrix
This page is intended to be generatable from chains/<chain>/metadata.yaml via scripts/generate-rpc-matrix.ts. Until generated output is wired into CI, keep it aligned with the metadata files.
| Chain | Interface | Transport | Port | Status | Public exposure | Notes |
|---|---|---|---|---|---|---|
| Ethereum | JSON-RPC HTTP | HTTP | 8545 | Standard | Yes, behind an authenticated gateway | Standard execution RPC surface; see Ethereum JSON-RPC and Geth RPC ports. |
| Ethereum | JSON-RPC WebSocket | WebSocket | 8546 | Standard | Yes, behind an authenticated gateway | Subscription-capable execution RPC surface. |
| Ethereum | Beacon API | HTTP | 5052 | Standard-internal | No | Consensus client API; do not publish directly. See Beacon APIs. |
| Ethereum | Engine API | Authenticated HTTP/JWT | 8551 | Internal | No | Execution/consensus client coupling surface. See Execution APIs. |
| Sui | gRPC | gRPC | 9000 | Recommended | No by default | Preferred machine interface for full node data access; see Sui gRPC. |
| Sui | GraphQL RPC | HTTP | Chain deployment value | Recommended | Yes, through API gateway | Preferred app query surface; see Sui GraphQL RPC. |
| Sui | JSON-RPC | HTTP | Chain deployment value | Deprecated | Migration-only | Sui documents JSON-RPC as deprecated and directs users to migrate by 2026-07; see Sui API references. |
| Aptos | REST | HTTP | 8080 | Standard | No by default | Fullnode REST API; expose only through a controlled gateway. See Aptos REST overview. |
| Aptos | GraphQL | HTTP | Deployment-specific | Standard | Gateway only | Indexer-backed API for richer queries; see Aptos APIs. |
| Aptos | Transaction Stream | gRPC | 50051 | Standard | No | Streaming feed for processors/indexers. |
| Solana | JSON-RPC HTTP | HTTP | 8899 | Standard | No by default | Solana RPC HTTP methods; see Solana RPC and HTTP methods. |
| Solana | JSON-RPC WebSocket / PubSub | WebSocket | 8900 | Standard | No by default | Subscription interface; see Solana WebSocket methods. |
warning
Treat every public RPC endpoint as an Internet-facing application. Put authentication, quotas, request-size limits, method filtering, TLS, and observability in front of the node process; do not publish internal client, metrics, or P2P control surfaces.