DIG Network
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 docs cover the network and its primitives: the composable building blocks developers use to build on DIG. The network is still expanding, and more primitives will be documented here over time.
$DIG is the engine and economy of DIG Network. Every value exchange — publishing a capsule, owning a store, tipping a creator — flows through $DIG. Consuming content stays effortless and free: you never pay to read, only to publish and own.
The capsule
One concept runs through every primitive. A capsule is a single immutable store generation — the pair (storeId, rootHash), written canonically as storeId:rootHash. A store is a sequence of capsules, one per commit (each commit advances the on-chain root and produces a new capsule).
The capsule is the network's unit of:
- Compilation — each capsule compiles to one fixed-size WASM module (padded so its length leaks nothing about content size).
- Pricing — a uniform per-capsule price (mint or commit), paid in $DIG at the live rate; a store's lifetime cost is the uniform per-capsule price × the number of capsules.
- Retrieval — a URN names one capsule (plus an optional resource within it).
- Caching — a host or browser caches a capsule keyed by
storeId:rootHash; the local cache is a set of capsules. - Provenance — each capsule's root carries the publisher's BLS signature and a Merkle root.
This is the ecosystem-wide definition: "capsule = (storeId, rootHash)" means the same thing in dig-store, the dig RPC, and the DIG Browser.
Create your first capsule in DIGHUb ↗ — publish a site in the browser, no CLI required. Each capsule (mint or commit) costs the uniform capsule price in $DIG.
Primitives
🗄️ dig-store
The first and most fundamental primitive: a content-addressable, encrypted WASM project format. You point it at a build directory, commit deployments like Git, and get a single self-defending .wasm file that is both your data and the server that gates access to it. The URN is the key — it both locates and decrypts.
| What is dig-store? | The one-file idea, in a nutshell |
| The Format | Projects, deployments, URNs, encryption, proofs |
| CLI Tutorial | Install and use dig-store in your project |
🛰️ dig RPC
The networking primitive: a standard interface for reading content from hosted dig-store deployments. JSON-RPC 2.0 over HTTPS POST — every hosting node speaks it identically, so content is portable and clients are node-agnostic. It serves ciphertext + inclusion proofs by retrieval key, whole deployments by (store_id, root), and the public discovery manifest — streamed in chunks, blind by construction, verified and decrypted entirely client-side.
| What is the dig RPC? | One endpoint for the whole network's read path |
| Methods | dig.getContent, dig.getCapsule, dig.getManifest, dig.listCapsules, … |
| Streaming | The chunk model, reassembly, and proof verification |
| Conformance & Security | The blind model, CORS, and what a node must implement |
🌐 DIG Browser
The client primitive: a browser with a built-in Chia wallet. It injects a window.chia provider on every page, so any web app can request the user's address, signatures, and spends with no WalletConnect setup — a drop-in alternative for apps that already speak CHIP-0002. It also resolves chia:// content addresses directly.
→ Build against the DIG Browser
Using window.chia in your app | Detect the injected wallet, connect, and call CHIP-0002 methods |
Get the DIG Browser ↗ — download the browser to open chia:// content and use the built-in wallet.
More primitives — settlement and node operation — will get their own sections as they land.
Pick your path
The docs are organized around what you're doing. Each track opens with a ten-second "why", the mental model you need, and the high-signal how-to — then links into the protocol when you want to go deeper.
- Publish a site or app you own — ship a website/app as your own on-chain asset; build free, publish a capsule.
- Mint NFTs & collections — CHIP-0007 drops backed by permanent, tamper-evident capsules.
- Integrate DIG into your app — a typed SDK + a fully machine-readable platform.
- Run a node — serve content provably and provider-blind.
- Open chia:// content — read content your own browser verifies against the chain.
- Get unstuck — find your failure by its stable code.
New to the vocabulary? Skim Concepts & glossary. Want the full design? Read the Protocol deep-dive.
DIG Network and its primitives are open source. dig-store is licensed under GPL-2.0; see the dig-store repository.
Related
- Quickstart — ship your first site; free to build and preview
- Build a dapp on Chia — every primitive in one end-to-end tutorial
- Concepts & glossary — the core DIG entities, defined and linked
- What is dig-store? — the content-addressable store format
- What is the dig RPC? — the network-wide read interface
- The chia:// protocol — opening content in the DIG Browser
- Get help — community, troubleshooting, and error codes