accessing-data

What problem does it solve?

This Skill prevents broken or outdated Sui data-access implementations by guiding you to the correct API surface for reading on-chain state, handling historical/pruned data, and avoiding deprecated JSON-RPC patterns.

Core Features & Use Cases

• Choose the right data surface (and switch correctly): select gRPC for low-latency real-time reads and streaming subscriptions, select GraphQL RPC for flexible composable queries and filtered/historical lookups, and use Archival routing when data has been pruned.
• Handle history and retention safely: explain that full-node gRPC does not fall back to archival, and show how GraphQL RPC routes supported point lookups to the Archival Store when operator-configured.
• Store large off-chain blobs the right way: route file/image/large JSON workflows to Walrus and store only the Walrus blob ID on-chain.
• Migration and correctness guardrails: enforce the “no JSON-RPC for new code” rule and map v1 method names/options to v2 Core API and GraphQL equivalents.

Quick Start

Ask the Skill: "I need to read X from Sui and may need historical versions—which API should I use and what client or query pattern do I follow?"