De principio a fin: genera una app React, conecta la wallet de Chia integrada en la página (window.chia + respaldo WalletConnect) con el dig-sdk, construye y firma un gasto vía el wasm de chip35, luego despliega en cadena y agrega un dominio personalizado — un solo hilo a través de cada primitivo de DIG.
The canonical CHIP-0035 wasm builder constructs every store-coin spend; admin / writer / oracle delegation is the on-chain primitive behind Teams and revocable CI deploy tokens — never hand-rolled.
Full walkthrough of the DigStore CLI: initialize a store, commit files, and read content back. The parallel track to the web-first quickstart.
Índice de una página de las entidades centrales de DIG Network — capsule, store, generation, URN, retrieval key, el dig RPC, el protocolo chia:// y el anclaje en cadena — cada una definida una vez y enlazada a su documento en profundidad.
Blind serving model, decoy streams, CORS, caching, rate limiting, and conformance checklist for dig RPC endpoints.
Auto-publish your built site or dapp to your existing DIG store on every push with the dig-network/deploy-action — git-push-to-deploy, free PR previews, and a PR comment + GitHub deployment status. Keyless CI auth, no long-lived hub secret.
Resumen de los primitivos de DIG Network: DigStore para publicación direccionable por contenido, dig RPC para hospedaje y recuperación ciegos, y el DIG Browser para el acceso al contenido.
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.
Lanza un sitio web o app que TÚ posees — acuñado en cadena como tu propio activo, no alquilado. Construye y previsualiza gratis; paga un pequeño precio uniforme en $DIG solo cuando publicas, con los archivos cifrados en tu navegador para que ningún host pueda leerlos.
Abre contenido chia:// que tu propio navegador verifica contra la blockchain — ningún host puede alterarlo ni falsificarlo, el contenido privado permanece privado frente al host, y es permanente y re-hospedable en cualquier lugar, así que nadie puede darlo de baja ni encerrarte en un proveedor.
Acuña una colección CHIP-0007 completa cuyo arte vive PERMANENTEMENTE en un capsule DIG infalsificable — un paquete atómico firmado, regalías reales, y una mecánica de drop honesta que nunca finge lo que aún no puede demostrar en cadena.
Every store gets a public, shareable tip page, and a one-line script embeds a Tip button on any site. Visitors tip you directly in $DIG, wallet to wallet — no account, no backend, no middleman.
The shortest path through DIGHUb: create a store, publish a capsule, give it a web address, and get tipped — all from the browser, wallet connected only when you publish or spend.
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.
Layer 0 of the DIG Protocol: store vs capsule vs generation. store_id is the CHIP-0035 singleton launcher id. A store is an ordered sequence of capsules.
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.
Chia AugScheme (G1 48B / G2 96B), the five mutually-distinct role DSTs (PUSH/NODE/TOMB/REQ/ATTEST) with their exact signing-message preimages, rogue-key rejection, and the host↔guest parity fixtures.
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).
The D5 per-resource UNTAGGED leaf = SHA-256(ciphertext), the NODE_TAG fold, odd-node carry-up, the proof-length ≤ ceil(log2 n) binding contract (D8), and the base64 X-Dig-Inclusion-Proof wire layout.
BINDING contract D1: the DIGS blob byte layout (big-endian, self-describing), all 12 SectionIds and their body formats (KeyTable D3, ChunkPool D4, MerkleNodes D5, ChainState, Filler), and the big-endian rationale.
Fixed-size obfuscation (128 MiB uniform blob, deterministic ChaCha20 filler), WASM injection memory layout (BINDING D2: 2 MiB offset, 384 MiB ceiling), the self-serving guest pipeline, oblivious gather, decoy generation, and the disabled host-attestation gate.
The DIG CAT TAIL asset id, the treasury inner puzzle hash, 3-decimal units, the dynamic USD-pegged per-capsule amount (no protocol constant), the atomic commit-bundle convention, and its non-enforcement caveat.
store = a CHIP-0035 singleton; capsule = a singleton update + root-advance. Free mint vs DIG-paid commit, the owner-discovery memo hint, and admin/writer/oracle delegation as the Teams / deploy-token primitive.
The provider-blindness invariant, serve_blind (framing-only decode), the root-pinned immutable response cache, the *.on.dig.net + custom-domain resolver, the /v1 control plane (CHIP-0002 login, JWT sessions, refresh reuse-detection, action re-auth, GitHub-OIDC CI), and the accept-on-signature push trust model.
The dig RPC is THE machine interface of the protocol: JSON-RPC 2.0 over HTTP POST, the full method catalogue, the chunk wire object (chunk_lens first-window-only, NO decoy field), range/window math, error codes incl. -32004, and the node profile vs the network profile.
The four ordered integrity gates (merkle inclusion → authenticated decryption → anchored-root pinning → risc0 execution), anchored-root pinning against the CHIP-0035 singleton via coinset.org, the authenticated head, tombstones, the MOCK-by-default risc0 caveat, the freshness contract, and provenance UX surfacing.
Complete dig RPC method set: dig.getContent, dig.getProof, dig.getCapsule, dig.getManifest, dig.listCapsules, dig.listCollectionItems, dig.getCollection, and service discovery methods.
Wallet seed setup, on-chain costs, funding, anchor status, and chain-verified downloads for DigStore projects.
The committable dig.toml manifest and how to inject PUBLIC build-time config (RPC endpoint, asset/CAT ids, feature flags) into a dapp — plus the one hard rule: a blind static capsule holds no server secrets.
El protocolo DIG como siete capas de abajo hacia arriba, normativas y definidas por implementación. El capsule (storeId:rootHash) es la unidad fundamental; el host es ciego y el lector verifica contra la cadena. Esta es la referencia autoritativa del protocolo.
Lanza tu primer sitio en DIG — gratis para construir y previsualizar, solo pagas el precio uniforme del capsule cuando publicas. Camino web-first (sin wallet para empezar) más una vía paralela por CLI.
Qué es un dig-node, por qué querrías ejecutar uno, y cómo instalarlo — el repositorio apt para Ubuntu/Debian o el instalador universal multiplataforma.
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.
Store identity via on-chain singleton launcher id, generations as capsules, content root, on-disk layout, and compiled module structure.
Streaming chunk model for byte methods: chunk object structure, 64 KiB alignment, reassembly, proof verification, and reference client loop.
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.
Cada fallo te da un código estable y un request-id que enlaza directamente con el log del servidor, los gastos en cadena están protegidos contra condiciones de carrera para que nunca pagues dos veces, y verificaciones previas claras evitan capsules desperdiciados antes de gastar $DIG.
Workflow for initializing projects, managing staging areas, running multiple stores in one workspace, and typical release loops.
Public RPC endpoint usage, portability across nodes, operating your own node, and rate limiting policies.
Register an HTTPS endpoint to be notified when a deployment changes state — queued, building, ready, or error. Each event is signed so you can verify it came from DIGHUb. The event contract — payload shape and signature — is stable; delivery is rolling out.
Proyecto direccionable por contenido con forma de Git, con cifrado integrado y direccionamiento basado en URN; compila a un único módulo WebAssembly autodefendido.
Interfaz de lectura de toda la red para capsules de DigStore vía JSON-RPC 2.0; ciega por construcción, verificable sin confianza, y transmisible en cualquier tamaño.