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.
Testnet gRPC is
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
The Chainstack Sui node holds a window of checkpoints fromlowestAvailableCheckpoint to the tip, not the full ledger from genesis. GetServiceInfo reports both ends of the window — the tip (checkpointHeight) and the oldest checkpoint the node holds (lowestAvailableCheckpoint):
lowestAvailableCheckpointObjects is the matching floor for historical object versions. The floor can change, so read lowestAvailableCheckpoint at runtime instead of hard-coding it.
How the window applies to each interface:
- gRPC — checkpoints, transactions, and object versions older than the window return
NotFound. - GraphQL — point lookups share this floor, and filtered transaction and event queries keep a shorter window.
serviceConfig.availableRangereports each window — see How far back GraphQL history goes. - JSON-RPC — object versions older than the window return
VersionNotFound. On Mainnet, JSON-RPC also resolves older checkpoint and transaction lookups through the implicit archival fallback built into Sui’s JSON-RPC, which Sui’s deprecation timeline disconnects at the end of September 2026. Do not build on JSON-RPC reads belowlowestAvailableCheckpoint.
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 both its default gRPC-Web transport and a native gRPC transport — see the setup in Sui tooling. gRPC-Web is served over HTTPS on Mainnet and Testnet, so browser apps can use the SDK directly, no proxy required.Next steps
- Migrate Sui from JSON-RPC to gRPC — call-by-call method mapping and quickstart.
- Sui tooling — SDKs and per-language connection code.