# DIG Network Documentation

> DIG Network is a Proof-of-Stake Layer 2 on Chia — a decentralized network for publishing, addressing, and serving content without trusting the host. These are the developer docs for the network and its primitives: DigStore (the content-addressable, encrypted store format and CLI), the dig RPC (the network-wide read interface), and the DIG Browser (a browser with the native chia:// protocol and an injected Chia wallet).

The unifying concept is the **capsule**: one immutable store generation — the pair `(storeId, rootHash)`, written `storeId:rootHash`. It is the network's atomic unit of compilation (one fixed-size WASM module), pricing (a flat 100 DIG to mint or commit), retrieval (a URN names one capsule), caching, and provenance. A store is a sequence of capsules, one per commit. This definition is identical across DigStore, the dig RPC, and the DIG Browser.

Audiences, simple to deep: (1) Hub users / frontend deployers, (2) integrating developers (CLI, RPC, window.chia), (3) protocol developers (whitepapers).

## Start here

- [DIG Network overview](https://docs.dig.net/docs/): the primitives at a glance — DigStore, dig RPC, DIG Browser, and the capsule.
- [Quickstart](https://docs.dig.net/docs/quickstart): ship your first site — free to build and preview, you spend a flat 100 DIG only when you publish a capsule. Web-first path (connect a wallet only at the end) plus a parallel CLI track.
- [Concepts & glossary](https://docs.dig.net/docs/concepts): every core entity defined once (capsule, store, generation, URN, retrieval key, the dig RPC, chia:// protocol, on-chain anchoring), each linked to its deep doc. The human-readable spine of the knowledge graph.
- [Tags index](https://docs.dig.net/docs/tags): the controlled vocabulary of entities, each tag listing every doc about it.

## Core concepts

- [What is DigStore?](https://docs.dig.net/docs/digstore/what-is-digstore): a Git-shaped, encrypted, content-addressable project that compiles to a single self-defending WebAssembly module — both the data and the server that gates it.
- [The DigStore WASM Store Format](https://docs.dig.net/docs/digstore/format/overview): the whole format in one read — store, generation/capsule, URN, and compiled module.
- [Store structure](https://docs.dig.net/docs/digstore/format/store-structure): store identity (the on-chain singleton launcher id), generations and root hashes, the on-disk layout, and the compiled module.
- [URNs & Encryption](https://docs.dig.net/docs/digstore/format/urns-and-encryption): the URN that is both address and key; retrieval key = SHA-256(canonical_urn); AES-256-GCM-SIV; public vs private stores.
- [Proofs & Security](https://docs.dig.net/docs/digstore/format/proofs-and-security): Merkle inclusion proofs over ciphertext, signed roots, revocation, host attestation, and the threat model.
- [On-chain anchoring](https://docs.dig.net/docs/digstore/cli/onchain-anchoring): every store is a Chia mainnet singleton; init mints it, commit anchors each root; DIG + XCH costs paid atomically in one spend.

## Quickstarts (Hub users & frontend deployers)

- [CLI quick start](https://docs.dig.net/docs/digstore/cli/quickstart): create a store, commit a file, and read it back in minutes.
- [Using DigStore in your project](https://docs.dig.net/docs/digstore/cli/project-workflow): capture a build directory, manage staging, run multiple stores in one workspace, the release loop.
- [Publish from the web (DIGHub)](https://hub.dig.net/new): deploy a capsule with no CLI.

## Build a dapp (integrating developers)

- [Build a dapp on Chia](https://docs.dig.net/docs/build-a-dapp/tutorial): the end-to-end thread — scaffold a React app (digstore new / npm create dig-app), develop free (digstore dev), wire the in-page wallet (window.chia + WalletConnect fallback via @dignetwork/dig-sdk), build and sign a spend (chip35 wasm via the SDK /spend subpath), deploy on-chain (100 DIG), and add a custom domain.
- [Scaffold an app (create-dig-app)](https://docs.dig.net/docs/build-a-dapp/scaffold): npm create dig-app — the JS front door; scaffolds a runnable starter (app + dig.toml + the DIG SDK on wallet templates) from five templates (static, vite-react, next-static, nft-drop, dapp-window-chia). Free to scaffold/build/preview; 100 DIG only at publish. The npm companion to the Rust CLI's digstore new.
- [Example gallery](https://docs.dig.net/docs/build-a-dapp/example-gallery): example projects mapped to scaffold templates — static, vite-react, nft-drop, next-static, dapp-window-chia (example repo links are placeholders during pre-release).

## DigStore CLI (integrating developers)

- [Installing the CLI](https://docs.dig.net/docs/digstore/cli/install): self-contained installer per OS, or build from source with Rust.
- [Command reference](https://docs.dig.net/docs/digstore/cli/command-reference): every digstore command — wallet, project, staging, history, content, remote, maintenance.
- [Project config & build-time values](https://docs.dig.net/docs/digstore/cli/configuration): the committable dig.toml manifest (store-id, output-dir, build-command, …; flags > env > dig.toml > defaults) and how to inject PUBLIC build-time config; the rule that a blind static capsule holds no server secrets.
- [Deploy from GitHub Actions](https://docs.dig.net/docs/digstore/cli/deploy-from-github-actions): git-push-to-deploy with dig-network/deploy-action@v1 — installs digstore, runs digstore deploy (advances the store, never mints), and reports the capsule + URLs + cost as a PR comment + GitHub deployment status. if-changed makes unchanged pushes a no-op (no spend); preview-per-PR is scaffolded. v1 puts a dedicated deploy wallet's seed in CI (passphrase + mnemonic); scoped deploy tokens are the planned safe replacement.
- [Sharing over a remote](https://docs.dig.net/docs/digstore/cli/sharing): publish, clone/pull with verification, revoke, public vs private sharing.
- [Streaming & retrieval keys](https://docs.dig.net/docs/digstore/cli/streaming-and-keys): cat by URN (decrypted) or retrieval key (encrypted); list keys; checkout a whole generation.

## The dig RPC (integrating developers)

- [What is the dig RPC?](https://docs.dig.net/docs/rpc/what-is-the-dig-rpc): network-wide read interface over JSON-RPC 2.0 — blind by construction, verifiable without trust, streamable at any size.
- [Methods](https://docs.dig.net/docs/rpc/methods): dig.getContent, dig.getProof, dig.getProofStatus, dig.getCapsule, dig.getManifest, dig.getMetadata, dig.listCapsules, dig.health, dig.methods.
- [Streaming](https://docs.dig.net/docs/rpc/streaming): the chunk object, 64 KiB alignment, reassembly, inclusion-proof verification, and a reference client loop.
- [Conformance & Security](https://docs.dig.net/docs/rpc/conformance): the blind serving model, decoy streams (no existence oracle), CORS, and the node conformance checklist.
- [Using the public network RPC](https://docs.dig.net/docs/rpc/public-network-rpc): rpc.dig.net, node portability, running your own node, rate limits.
- [The chia:// remote](https://docs.dig.net/docs/rpc/dig-remote): git-style clone/pull/push over chia:// URLs with per-request BLS identity-key auth.

## DIG Browser (integrating developers)

- [The chia:// protocol](https://docs.dig.net/docs/browser/chia-protocol): the browser's native content-address scheme — the typeable front end of the urn:dig: URN; addressing forms and the shared parser grammar.
- [Using window.chia](https://docs.dig.net/docs/browser/using-window-chia): the injected CHIP-0002 wallet provider — detect, connect (per-origin), and call key/signing methods; a drop-in WalletConnect alternative.

## Protocol specs (protocol developers)

- [The window.chia provider spec](https://docs.dig.net/docs/protocol/window-chia-provider): the normative, versioned specification of the window.chia provider — the provider object shape, the EIP-1193-style request/connect contract, every CHIP-0002 method (params/returns/error codes), the connect/202-pending contract, capability/version feature-detection, and EIP-6963-style multi-provider (announce/request) discovery. DIG Browser is the reference implementation; @dignetwork/dig-sdk's ChiaProvider is the recommended consumer. Normative vs. proposed surface is marked inline.

## Whitepapers (protocol developers)

- [Whitepapers index](https://docs.dig.net/docs/whitepapers/): the three normative specifications.
- [Part 1 · Consensus](https://docs.dig.net/docs/whitepapers/consensus): a Proof-of-Stake Layer 2 on Chia — Groth16 + BLS finality, five CLVM puzzles, the validator lifecycle. PDF: https://docs.dig.net/whitepapers/DIG-Network-Part1-Consensus.pdf
- [Part 2 · DFSP](https://docs.dig.net/docs/whitepapers/dfsp): the Decentralized File Storage Protocol — availability-audited capsule hosting, full replication, paid to serve. PDF: https://docs.dig.net/whitepapers/DIG-Network-Part2-DFSP.pdf
- [Part 3 · Digstore](https://docs.dig.net/docs/whitepapers/digstore): the content-addressable WASM store format — immutable capsules, URN-derived keys, ZK execution proofs, Git workflow. PDF: https://docs.dig.net/whitepapers/DIG-Network-Part3-Digstore.pdf

## Support

- [Get help](https://docs.dig.net/docs/support/get-help): community Discord, GitHub issues, and how to file a report that gets answered.
- [Troubleshooting](https://docs.dig.net/docs/support/troubleshooting): fixes for the common failures — insufficient DIG, confirmation timeout, non-fast-forward, verification failed, wallet/session.
- [FAQ](https://docs.dig.net/docs/support/faq): what it costs (flat 100 DIG/capsule), iterate-for-free, blind hosting, custom domains, updates, public vs private.
- [Error codes](https://docs.dig.net/docs/support/error-codes): one table for every code — dig RPC JSON-RPC (-32xxx), digstore CLI exit codes (0–16), and DIGHub user-facing codes (DIG_INSUFFICIENT, SLUG_TAKEN, WALLET_DECLINED, …).
- [Changelog](https://docs.dig.net/docs/support/changelog): what changed across the developer surfaces — digstore CLI (semver), dig RPC (method set + chunk wire format), window.chia provider, dig-sdk and chip35-dl-coin-wasm (npm) — plus how each is versioned and any breaking changes.
- [Status](https://docs.dig.net/docs/support/status): health of the DIG services (rpc.dig.net, hub.dig.net, on.dig.net) and the RPC + provider versioning notes (a live dashboard is planned).

## Machine-readable

- [Knowledge graph](https://docs.dig.net/knowledge-graph.json): nodes (concepts + docs) and typed edges (defines, part-of, requires, relates-to, see-also) derived from tags and related-links.
- [Sitemap](https://docs.dig.net/sitemap.xml): every public route.

## Optional

- [DigStore source](https://github.com/DIG-Network/digstore): the open-source (GPL-2.0) CLI and store format.
- [DIG Network site](https://dig.net): the project home and whitepapers landing.
- [DIGHub](https://hub.dig.net): publish and manage capsules from the web.