CLI tutorial
Full walkthrough of the DigStore CLI: initialize a store, commit files, and read content back. The parallel track to the web-first quickstart.
Full walkthrough of the DigStore CLI: initialize a store, commit files, and read content back. The parallel track to the web-first quickstart.
Complete command reference for the digstore CLI, including wallet, store, staging, history, content, remote, and maintenance commands.
Index en une page des entités essentielles du DIG Network — capsule, store, generation, URN, retrieval key, le dig RPC, le protocole chia://, et l'ancrage on-chain — chacune définie une fois et reliée à sa documentation détaillée.
The cross-implementation parity discipline: frozen canonical()/retrieval_key() goldens, the C8 crypto fixtures, the shared URN conformance vectors, the OpenRPC-vs-server diff test, and what every reimplementation MUST pass.
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.
The shortest path through the digstore CLI: install it, scaffold and preview for free, publish a capsule on-chain, share it over a remote, and read it back — each task linked to the page that walks it.
The normative urn:dig:chia URN grammar, the rootless retrieval_key = SHA-256(canonical) invariant, resourceKey normalization, the three-way scheme split (chia:// vs §21 dig:// vs dig://* browser), and the salt addressing extension.
Layer 1 read-crypto: HKDF-SHA256 key derivation (salt-mixed secret), AES-256-GCM-SIV fixed-nonce seal, the byte-exact constants table, and the one-crypto-implementation invariant (producer = host = verifier = dig-client-wasm).
Publishing stores to remotes, downloading with verification, revoking roots, and understanding public vs. private access models.
Streaming resources by URN or retrieval key, listing keys per deployment, and checking out entire generations.
A content-addressed protocol for opening stores and resources directly from the DIG Network, with URN and shorthand forms.
Architecture of the content-addressable, encrypted WebAssembly store format: identity, generations, URNs, and compiled modules.
URN format and semantics, derivation of retrieval and decryption keys, AES-256-GCM-SIV encryption, and public vs. private store differences.
Format de projet en forme de Git, adressable par contenu, avec chiffrement intégré et adressage basé sur URN ; se compile en un seul module WebAssembly auto-défendu.