Satu dokumentasi memiliki tag dengan "dig-sdk"

Every on-chain action is built by the canonical CHIP-0035 wasm, signed by the user's wallet, and broadcast — the build → sign → broadcast split. Never hand-roll a spend bundle.

Indeks satu halaman untuk entitas inti DIG Network — capsule, store, generation, URN, retrieval key, dig RPC, protokol chia://, dan anchoring on-chain — masing-masing didefinisikan sekali dan tertaut ke dokumen mendalamnya.

Platform yang sepenuhnya machine-readable — OpenAPI/OpenRPC, taksonomi error yang dikatalogkan, penetapan harga live, JWKS, JSON per-halaman, dan @dignetwork/dig-sdk yang bertipe — sehingga Anda menghubungkan wallet + pembacaan terverifikasi ke aplikasi Anda tanpa perlu meng-scrape satu baris pun prosa manusia.

Mint seluruh koleksi CHIP-0007 yang seninya hidup secara permanen dalam sebuah capsule DIG yang tamper-evident — satu bundle yang ditandatangani secara atomik, royalti sungguhan, dan mekanisme drop yang jujur yang tidak pernah memalsukan apa yang belum bisa mereka buktikan on-chain.

The shortest path for integrating developers: connect a wallet, read verified content, build a spend the right way, and deploy from CI — using the typed @dignetwork/dig-sdk and the dig RPC, no prose-scraping required.

Every machine-readable entry point: /openrpc.json, /error-codes.json, /llms.txt, /knowledge-graph.json, the sitemap, and per-page schema.org JSON-LD — so an agent integrates DIG without scraping a single line of human prose.

npm create dig-app — scaffold a wallet-wired, deployable DIG app in one command. Five templates (static, vite-react, next-static, nft-drop, dapp-window-chia), all free to build and preview; you pay the uniform capsule price only when you publish.

@dignetwork/dig-sdk — ChiaProvider (injected window.chia + WalletConnect→Sage), DigClient (verified reads), Paywall (pay-to-unlock / NFT-gating), and the canonical CHIP-0035 spends at the /spend subpath.

Normative, versioned specification of the window.chia Chia wallet provider — the provider object shape, the EIP-1193-style request contract, every CHIP-0002 method with params/returns/error codes, the connect/202-pending contract, capability discovery, and EIP-6963-style multi-provider discovery.