Build a dapp on Chia
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.
Building spends
Every on-chain action is built by the canonical CHIP-0035 wasm, signed by the user's wallet, and broadcast — the build → sign → broadcast split. Never hand-roll a spend bundle.
CHIP-0035 store-coin spends & delegation
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.
Concepts & glossary
Í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.
Deploy keys
Give your CI or an agent a revocable key that can publish new versions of your store — but never your wallet seed, and never the power to change ownership. Issue it once in DIGHUb, drop it into CI as DIGSTORE_WRITER_KEY, and revoke it any time.
For integration developers
Una plataforma totalmente legible por máquinas — OpenAPI/OpenRPC, una taxonomía de errores catalogada, precios en vivo, JWKS, JSON por página, y un @dignetwork/dig-sdk tipado — para que conectes una wallet + lecturas verificadas en tu app sin rastrear ni una sola línea de prosa humana.
For NFT developers
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.
How do I… integrate DIG into my app?
The shortest path for integrating developers: connect a wallet, read verified content, build a spend the right way, and deploy from CI — using the typed @dignetwork/dig-sdk and the dig RPC, no prose-scraping required.
L0 · Identity & naming
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.
L4 · DIG CAT payment & pricing
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.
L4 · On-chain anchoring (CHIP-0035)
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.
L6 · The blind host model
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.
L6 · The dig RPC (machine interface)
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.
L6 · Verification, provenance & anchoring
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.
Methods
Complete dig RPC method set: dig.getContent, dig.getProof, dig.getCapsule, dig.getManifest, dig.listCapsules, dig.listCollectionItems, dig.getCollection, and service discovery methods.
On-chain anchoring
Wallet seed setup, on-chain costs, funding, anchor status, and chain-verified downloads for DigStore projects.
Store Structure
Store identity via on-chain singleton launcher id, generations as capsules, content root, on-disk layout, and compiled module structure.
The DIG SDK
@dignetwork/dig-sdk — ChiaProvider (injected window.chia + WalletConnect→Sage), DigClient (verified reads), Paywall (pay-to-unlock / NFT-gating), and the canonical CHIP-0035 spends at the /spend subpath.
What is the dig RPC?
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.