Question 1

Sui Indexer: How to Index Sui Data Without Running Your Own Pipeline

Accepted Answer

A Sui indexer turns raw Sui checkpoint and transaction data into queryable state for dashboards, analytics, and application backends. The hard part is rarely the query layer — it is keeping a reliable, low-lag stream of Sui data flowing into it. This article covers the indexing architectures developers actually use on Sui, the RPC and gRPC access patterns that feed them, and how to decide between self-hosted and managed infrastructure. It also explains where a reliable Sui RPC and dedicated node setup from OnFinality fits into that pipeline.

Question 2

Sui Mainnet RPC: How to Connect and What to Check

Accepted Answer

Learn how to connect to Sui Mainnet RPC endpoints, understand the JSON-RPC methods, and evaluate infrastructure options for production apps. This guide covers chain settings, request examples, and key considerations for choosing between public and dedicated nodes.

Question 3

How to Set Up a Custom Sui RPC Endpoint for Your dApp

Accepted Answer

Learn how to configure a custom Sui RPC endpoint for your dApp, whether you're using the public endpoint, a managed provider like OnFinality, or your own node. This guide covers endpoint configuration, JSON-RPC examples, and common troubleshooting steps to keep your Sui application reliable.

Question 4

Sui gRPC Providers: Public, Managed & Dedicated RPC Compared

Accepted Answer

Sui gRPC providers give applications a typed, streaming path to Sui data, but access models differ significantly. Public Foundation gRPC endpoints can suit prototypes and low-volume tooling; evaluate their current limits, support, and production terms before depending on them. Managed gRPC providers operate shared endpoints with documented capacity, monitoring, and support, making them a practical default for dApps, indexers, and backend workers. Dedicated Sui gRPC nodes isolate your workload on private infrastructure and are justified when burst behavior, latency, or compliance requirements outgrow shared capacity. The evaluation should be gRPC-first: confirm LedgerService and StateService read support, TransactionExecutionService for ExecuteTransaction and SimulateTransaction, and SubscriptionService for SubscribeCheckpoints, SubscribeTransactions, and SubscribeEvents. Also verify rate limits, burst allowances, regions, failover, and incident communication before moving production traffic. OnFinality provides managed Sui gRPC and RPC infrastructure for mainnet and testnet, with a path to dedicated nodes when workloads need isolation. Start from /networks/sui to review current Sui network support.

Question 5

Sui Testnet RPC & gRPC: Endpoint, Faucet & Developer Setup

Accepted Answer

Sui Testnet RPC gives developers a gRPC-first path to query checkpoints, objects, and balances; simulate and execute transactions; and stream real-time activity using OnFinality managed endpoints. The modern workflow uses LedgerService for checkpoint data, StateService for object and balance reads, TransactionExecutionService for SimulateTransaction and ExecuteTransaction, and SubscriptionService for SubscribeCheckpoints, SubscribeTransactions, and SubscribeEvents. Legacy Full Node JSON-RPC remains useful for migration comparisons, but new testnet integrations should target gRPC and treat JSON-RPC as a legacy surface. Use the official faucet at https://faucet.sui.io for test SUI, and keep testnet credentials separate from mainnet. Configure endpoint placeholders such as GRPC_ENDPOINT and authorization headers in SDKs, wallets, and CI. Because testnet endpoints can reset and faucet limits change, always build your testnet environment to be disposable and avoid hard-coding object IDs or transaction digests. Testnet is not permanent: verify current faucet policy, expect resets, and validate the same workflows before moving to Sui mainnet. For operational guidance, see /rpc-assistant/sui-rpc-guide and /networks/sui-testnet.

Question 6

Dedicated Sui gRPC Nodes: Streaming, Capacity & Isolation

Accepted Answer

Dedicated Sui gRPC nodes give your team an isolated full-node environment for high-throughput Sui data access. Instead of sharing rate-limited public or multi-tenant endpoints, you operate a node sized for your indexers, backend services, and subscription consumers. The gRPC API uses Protocol Buffers over HTTP/2, which makes checkpoint, transaction, and event streams more efficient than polling JSON-RPC. Dedicated capacity helps when you need stable throughput for backfills, multiple concurrent stream consumers, or transaction submission and simulation without noisy neighbours. You still own the operational surface: sync lag, disk growth, upgrades, and monitoring. The Sui gRPC surface includes LedgerService, StateService, TransactionExecutionService, and SubscriptionService. Streaming workflows such as SubscribeCheckpoints, SubscribeTransactions, and SubscribeEvents are central to low-latency indexing; ExecuteTransaction and SimulateTransaction support write and simulation paths. A dedicated node is not a managed magic box. Plan for state growth, snapshot recovery, TLS, load testing, and failover before production. This guide covers capacity planning, isolation, replay, monitoring, and full-node lifecycle decisions without vendor rankings or invented performance claims.

Question 7

Sui gRPC Guide: Endpoints, Streaming & JSON-RPC Migration

Accepted Answer

Sui gRPC is the type-safe, Protocol Buffers-based RPC interface exposed by Sui full nodes. It is the recommended production path for reading chain state, executing transactions, and consuming real-time streams. OnFinality provides managed Sui gRPC and RPC infrastructure on mainnet and testnet; the current endpoint details are published on /networks/sui. In practice, you use grpcurl with a GRPC_ENDPOINT placeholder and authorization metadata from your provider, then target services by name. LedgerService covers checkpoints and consensus data, StateService covers object reads and balances, TransactionExecutionService provides ExecuteTransaction and SimulateTransaction workflows, and SubscriptionService offers SubscribeCheckpoints, SubscribeTransactions, and SubscribeEvents for streaming. Because JSON-RPC is being retired, teams should plan a migration by mapping legacy read, write, and subscription workflows to these gRPC services. Work from generated clients or proto definitions, not hand-built JSON calls. Test on testnet with the faucet at https://faucet.sui.io, keep mainnet separate, and verify stream reconnection and field masks before production.

API Service

Dedicated Nodes

Enterprise Nodes

Indexer Services

Network Prototyping Tools

Staking & Validators

AI Agent

RPC documentation entries

Sui Indexer: How to Index Sui Data Without Running Your Own Pipeline

Sui Mainnet RPC: How to Connect and What to Check

How to Set Up a Custom Sui RPC Endpoint for Your dApp

Sui gRPC Providers: Public, Managed & Dedicated RPC Compared

Sui Testnet RPC & gRPC: Endpoint, Faucet & Developer Setup

Dedicated Sui gRPC Nodes: Streaming, Capacity & Isolation

Sui gRPC Guide: Endpoints, Streaming & JSON-RPC Migration

Never Worry about Infrastructure Again

Supported Networks

Product

Company

Resources

Sui RPC Assistant

RPC documentation entries

Sui Indexer: How to Index Sui Data Without Running Your Own Pipeline

Sui Mainnet RPC: How to Connect and What to Check

How to Set Up a Custom Sui RPC Endpoint for Your dApp

Sui gRPC Providers: Public, Managed & Dedicated RPC Compared

Sui Testnet RPC & gRPC: Endpoint, Faucet & Developer Setup

Dedicated Sui gRPC Nodes: Streaming, Capacity & Isolation

Sui gRPC Guide: Endpoints, Streaming & JSON-RPC Migration

Never Worry about Infrastructure Again

Supported Networks

Product

Company

Resources