Chain Matrix
This matrix summarizes both developer-interface guides and the Kubernetes deployment guides now documented in the site.
| Chain | Category / VM | Node types covered | Primary developer interfaces / operator surface | Production runtime | Status |
|---|---|---|---|---|---|
| Ethereum | EVM | Execution full node, consensus beacon node, archive/trace profile | JSON-RPC HTTP, JSON-RPC WebSocket, Beacon API, Engine API | Docker, Kubernetes, Helm, Argo CD | Draft |
| Sei | Cosmos/EVM | Validator plus Horcrux signer overlays | P2P, RPC/API/gRPC, EVM HTTP/WS, Horcrux signer/cosigner | Kubernetes, Argo CD, Helm (charts/chain-templates) | Kubernetes reference pattern |
| Stable | Cosmos/EVM | Stablevisor validator plus Horcrux signer overlays | P2P, RPC/API/gRPC/gRPC-web, EVM RPC/WS, Prometheus, Horcrux | Kubernetes, Argo CD, Helm (charts/chain-templates) | Kubernetes reference pattern |
| Initia | Cosmos / MoveVM ecosystem | Active validator plus Horcrux signer overlays | P2P, RPC/API/gRPC, Horcrux signer/cosigner | Kubernetes, Argo CD, Helm (charts/chain-templates) | Kubernetes reference pattern |
| Walrus | Sui ecosystem storage | Storage node | Storage service, metrics, setup RPC/checkpoint dependencies | Kubernetes, Argo CD, Helm (charts/chain-templates) | Kubernetes reference pattern |
| Canton | Canton / Splice | Validator, participant, Postgres | Validator service, metrics, ingress/auth surfaces | Kubernetes, Argo CD multi-source Helm | Kubernetes reference pattern |
| Sui | MoveVM | Full node, API-serving full node, event/indexer-adjacent workloads | gRPC, GraphQL RPC, JSON-RPC migration path | Docker, Kubernetes, Helm, Argo CD | Draft |
| Aptos | MoveVM | Fullnode, indexer processor, GraphQL/API serving tier | REST, GraphQL indexer, Transaction Stream gRPC | Docker, Kubernetes, Helm, Argo CD | Draft |
| Solana | SVM | Validator/RPC node, private RPC node, WebSocket PubSub endpoint | JSON-RPC HTTP, WebSocket PubSub | Docker, Kubernetes, Helm, Argo CD | Draft |
note
Use this page to compare capabilities. Use each chain page for concrete manifests, flags, and runbooks because safe defaults differ by protocol.