What you get
- One node, both interfaces — JSON-RPC over HTTPS and native gRPC over HTTP/2, from a single Chainstack Sui node.
- Deep checkpoint retention — tens of millions of checkpoints of history for point lookups and backfills.
- Server reflection enabled on gRPC — explore services and call methods with grpcurl, no proto compilation needed.
x-tokenauthentication on gRPC; auth token or basic auth on JSON-RPC.
Endpoints
Find your endpoint and credentials on Chainstack — see View node access and credentials. Copy the full HTTPS endpoint (shown below asYOUR_CHAINSTACK_ENDPOINT) — it already carries your auth token.
| Interface | Endpoint | Authentication |
|---|---|---|
| JSON-RPC (HTTPS) | YOUR_CHAINSTACK_ENDPOINT | auth token or basic auth, built into the endpoint |
| gRPC | sui-mainnet.core.chainstack.com:443 | x-token metadata header |
sui-testnet.core.chainstack.com:443. The auth token and x-token are the node’s access credentials, not your Chainstack platform API key. For every authentication option, see Authentication methods available on Chainstack.
Checkpoint retention
A Sui full node serves a moving window of recent checkpoints rather than the full ledger from genesis. Query the current window withGetServiceInfo, which reports the tip (checkpointHeight) and the oldest checkpoint the node still holds (lowestAvailableCheckpoint):
lowestAvailableCheckpoint at runtime for the current floor. For reads older than the window, query an archival store.
Verify your endpoint
list output shows the node’s sui.rpc.v2 services — Sui tooling describes what each one is for.
The official Sui TypeScript SDK (
@mysten/sui) works here over a native gRPC transport — see the setup in Sui tooling. Its default gRPC-Web transport is not supported on Chainstack yet (HTTP 415), so browser apps should use JSON-RPC or proxy gRPC through a backend.Next steps
- Migrate Sui from JSON-RPC to gRPC — call-by-call method mapping and quickstart.
- Sui tooling — SDKs and per-language connection code.