End-to-end: scaffold a React app, wire the in-page Chia wallet (window.chia + WalletConnect fallback) with the dig-sdk, build and sign a spend via the chip35 wasm, then deploy on-chain and add a custom domain — one thread through every DIG primitive.
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.
What changed across the DIG developer surfaces — the dig-store CLI, the dig RPC, and the window.chia provider — including breaking changes and the versioning rules for each.
One-page index of the core DIG Network entities — capsule, store, generation, URN, retrieval key, the dig RPC, the chia:// protocol, and on-chain anchoring — each defined once and linked to its deep doc.
Example DIG dapps you can clone and open in a template — a static site, a wallet-wired React app, and an NFT drop page. Start from working code instead of a blank folder.
A fully machine-readable platform — OpenAPI/OpenRPC, a catalogued error taxonomy, live pricing, JWKS, per-page JSON, and a typed @dignetwork/dig-sdk — so you wire a wallet + verified reads into your app without scraping a single line of human prose.
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.
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.
Where to check the health of the DIG services — the dig RPC (rpc.dig.net), DIGHUb (hub.dig.net), and the resolver (on.dig.net) — plus how RPC and provider versions are signalled.
The integrating-developer reference for the DIG window.chia wallet provider — the provider object fields, connect, events, every read and write method with params and returns, and the CHIP-0002 error codes to branch on.
A content-addressed protocol for opening stores and resources directly from the DIG Network, with URN and shorthand forms.
@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.
Detect and use the DIG Browser's injected Chia wallet provider for permission-gated key and signing operations.
How the DIG Chrome extension's built-in Chia wallet protects your keys: encryption at rest, phishing and scam warnings, revocable site permissions, and the Argon2id/AES-256-GCM crypto behind it.