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.
What changed across the DIG developer surfaces — the digstore CLI, the dig RPC, and the window.chia provider — including breaking changes and the versioning rules for each.
Overview of the DIG Network primitives: DigStore for content-addressable publishing, dig RPC for blind hosting and retrieval, and the DIG Browser for content access.
Every DIG error code in one place: dig RPC JSON-RPC codes, digstore CLI exit codes, and DIGHub user-facing codes — each with what it means and what to do.
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.
Frequently asked questions about DIG — what it costs, whether you can iterate for free, how the host can't read your app, custom domains, and updates.
Where to get help with DIG — the community Discord, GitHub issues, and how to file a report that gets answered fast.
Ship your first site on DIG — free to build and preview, you only spend 100 DIG when you publish. Web-first path (no wallet to start) plus a parallel CLI track.
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.
Git-style remote protocol via chia:// URLs, per-request BLS signing, clone/pull/push operations, and self-hosted node setup.
Fixes for the most common DIG failures — funding, confirmation timeouts, push conflicts, verification errors, and wallet/session problems.
Detect and use the DIG Browser's injected Chia wallet provider for permission-gated key and signing operations.
Public RPC endpoint usage, portability across nodes, operating your own node, and rate limiting policies.