> For the complete documentation index, see [llms.txt](https://docs.triton.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.triton.one/chains/sui.md).

# SUI

### Overview

> **Deprecation notice:** Sui JSON-RPC is being sunset. Triton will continue to support it until the **end of October 2026**, after which it is removed from the Sui source code and node binaries and our endpoints will no longer serve it. Migrate to [gRPC](https://docs.triton.one/chains/sui/grpc) or [GraphQL](https://docs.triton.one/chains/sui/graphql) before then. See [JSON-RPC deprecation](https://claude.ai/chat/a683b0bb-ca5b-424e-9847-872ab66e0791#json-rpc-deprecation) below.

As one of the original validators on Sui, we provide full-service Sui data access. Our stack now spans full nodes (JSON-RPC and gRPC), GraphQL RPC, a long-term Archival Service, and Walrus and Seal support.

***

#### Service summary

<table><thead><tr><th>Stack</th><th width="376.76171875">Protocol &#x26; endpoint format</th><th>Data range</th><th>Reference</th></tr></thead><tbody><tr><td><strong>Mainnet — Full node</strong></td><td>JSON-RPC: <code>https://XXX.sui.rpcpool.com</code> gRPC: <code>XXX.sui.rpcpool.com:443</code></td><td>Recent (pruned by full node)</td><td><a href="https://docs.triton.one/chains/sui/grpc">gRPC</a></td></tr><tr><td><strong>Mainnet — GraphQL</strong></td><td>GraphQL: <code>https://XXX.sui.rpcpool.com/graphql</code></td><td>Latest 30 days</td><td><a href="https://docs.triton.one/chains/sui/graphql">GraphQL</a></td></tr><tr><td><strong>Mainnet — Archival Service</strong></td><td>gRPC: <code>archive.mainnet.sui.rpcpool.com:443</code></td><td>Full history (from genesis)</td><td><a href="https://docs.triton.one/chains/sui/archival-storage-and-services">Archival Storage and Services</a></td></tr><tr><td><strong>Testnet — Full node</strong></td><td>JSON-RPC: <code>https://XXX.sui.rpcpool.com</code> gRPC: <code>XXX.sui.rpcpool.com:443</code></td><td>Recent (pruned by full node)</td><td><a href="https://docs.triton.one/chains/sui/grpc">gRPC</a></td></tr></tbody></table>

> `XXX` is your unique endpoint slug, visible in the [client panel](https://customers.triton.one/), where you also find your token. GraphQL and the Archival Service are available on **Mainnet only**.

Authentication uses the `X-Token` header on all non-free endpoints (GraphQL also accepts the token in the URL). We also provide **free, rate-limited test endpoints** for gRPC and GraphQL that require no token — see the [gRPC](https://docs.triton.one/chains/sui/grpc) and [GraphQL](https://docs.triton.one/chains/sui/graphql) pages for details.

***

#### Choosing an interface

* **gRPC** — high-performance, low-latency point lookups and real-time checkpoint streaming. Best for indexers, exchanges, bots, and backend systems. Now generally available.
* **GraphQL** — flexible, composable queries that return exactly the fields you need across transactions, objects, events, and balances. Best for frontends, explorers, and dashboards. Serves the latest 30 days.
* **Archival Service** — long-term, consistent access to the full history of Sui mainnet from genesis, over the same gRPC `LedgerService` interface. Use it for any lookup older than the full node or GraphQL retention windows.
* **JSON-RPC** — deprecated. Supported through the end of October 2026 for backward compatibility only. See below.

***

#### Additional services

**Mainnet**

* Walrus — storage, publisher, and aggregator
* Seal — permissioned server

**Testnet**

* Walrus — storage, publisher, and aggregator
* Seal — open and permissioned server

***

#### JSON-RPC deprecation

Sui JSON-RPC is deprecated across the network and is currently in its **sunsetting period**. JSON-RPC has already been disabled on Sui Foundation mainnet full nodes, and upstream removal from the Sui source code and node binaries is scheduled for October 2026.

**Triton will continue to support JSON-RPC until the end of October 2026.** After that date, JSON-RPC is removed from the Sui source code and binaries, and our endpoints will no longer serve it.

To avoid disruption, migrate to one of the supported interfaces before then:

* Move backend systems, indexers, exchanges, and streaming workloads to [gRPC](https://docs.triton.one/chains/sui/grpc).
* Move frontends, explorers, dashboards, and flexible or filtered read workloads to [GraphQL](https://docs.triton.one/chains/sui/graphql).

For a method-by-method mapping from JSON-RPC and guidance on choosing between gRPC and GraphQL, see the official [JSON-RPC Migration Guide](https://docs.sui.io/develop/accessing-data/json-rpc-migration).

> **Note:** The Sui WebSocket API is officially deprecated and has been retired by Mysten Labs. Use gRPC checkpoint streaming for real-time updates.

***

#### Resources

* [gRPC](https://docs.triton.one/chains/sui/grpc)
* [GraphQL](https://docs.triton.one/chains/sui/graphql)
* [Archival Storage and Services](https://docs.triton.one/chains/sui/archival-storage-and-services)
* [Official: Access Sui Data](https://docs.sui.io/develop/accessing-data/data-serving)
* [Official: JSON-RPC Migration Guide](https://docs.sui.io/develop/accessing-data/json-rpc-migration)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.triton.one/chains/sui.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.