Sui Starts JSON-RPC Shutdown, Forcing Apps Off Foundation Nodes

Sui Foundation JSON-RPC Shutdown Starts This Week

The immediate change applies to Sui Foundation mainnet full nodes. The official GraphQL documentation says the legacy interface is disabled during the week of July 27, while full decommission and code removal are planned for mid-October.

That timeline resolves an apparent conflict in earlier Sui material. A March Sui Foundation blog post described July 31 as a hard date for JSON-RPC deactivation; the current technical documentation distinguishes the Foundation-node shutdown from the later removal of JSON-RPC support from the software codebase.

For a user, the symptoms may look like a product outage: a wallet can show stale balances, a dashboard can fail to load transaction history, or a bot can stop before sending an order. None of those outcomes means Sui has stopped finalizing blocks. They mean the app’s chosen route to the chain needs to change.

The distinction resembles Polygon’s scheduled removal of certain public endpoints, which Daily Crypto Briefs covered in its guide to the Polygon Amoy and mainnet RPC deadlines. In both cases, the chain remains active while an old access URL becomes unusable.

The scope also depends on the provider. Ankr’s Sui notice says its independently operated JSON-RPC endpoints are not affected by the July public-good shutdown and will continue until the planned October software removal. Developers should not assume that exception applies to every provider or that it removes the need to migrate.

gRPC and GraphQL Replace Sui’s Legacy Data Calls

Sui’s replacement stack separates workloads that JSON-RPC handled through one interface. gRPC is aimed at applications that need continuous, low-latency data, such as a trading interface monitoring activity in real time. GraphQL RPC is built for wallets, explorers and dashboards that benefit from filtered and composed queries.

The GraphQL RPC guide says the service can query the network, submit transactions and simulate transactions. Its General-purpose Indexer is intended to make structured historical and frontend data easier to retrieve without requiring an application to stitch together multiple legacy calls.

Historical data is the operational edge case. Full nodes prune older information to stay efficient, while Sui’s Archival Store is designed to make point lookups for older transactions, objects and checkpoints available. A team that only checks a current wallet balance has a different migration job from an explorer that promises a complete account history.

Sui said its full stack, including gRPC, GraphQL RPC and the Archival Store, is generally available. The Foundation listed QuickNode, Ankr, BlockPi and ZAN as managed-service options when it announced the migration, although a provider’s feature set, limits and pricing can change.

That is why changing one URL is not always enough. Teams should validate read requests, transaction simulation, transaction submission, event subscriptions, historical queries and rate limits against the service they intend to use. A development endpoint that works in a test can still be too constrained for a production wallet or high-frequency application.

Sui Apps Need Endpoint Inventories Before October

The near-term task is to find every dependency. Developers should search source repositories, environment variables, deployment secrets, analytics workers, monitoring jobs and vendor configurations for Foundation JSON-RPC URLs, then test a gRPC or GraphQL replacement in a staging environment.

The current Sui documentation makes a practical recommendation rather than prescribing one universal transport. Use GraphQL where the product needs composable queries, filtered history or UI-friendly records. Use gRPC where an application benefits from streamed data and low latency. Some products will need both.

For end users, the reasonable response is to let the wallet, exchange or application operator handle the migration. Do not replace a network endpoint with an address offered in a chat channel or a social-media reply. Official Sui documentation and the provider’s own support pages are the appropriate places to confirm a migration notice.

The change arrives as crypto infrastructure providers compete to own the interface layer between chains and consumer products. Daily Crypto Briefs recently reported on Coinbase’s Deribit matching-engine rollout, another example of companies making trading access less dependent on one legacy connection path.

Broad market sentiment was still cautious. Alternative.me’s Crypto Fear and Greed Index read 24, or Extreme Fear, on July 28, a market-wide indicator that does not measure demand for Sui infrastructure.

The next checkpoints are whether app operators disclose service interruptions this week, whether providers publish final migration instructions, and whether builders complete their code changes before JSON-RPC is removed from Sui full-node software in October. The confirmed change is limited to the access layer, but its effect can be immediate for any product that has not updated its endpoint.