De ponta a ponta: faça o scaffold de uma aplicação React, conecte a carteira Chia embutida na página (window.chia + fallback WalletConnect) com o dig-sdk, construa e assine um spend via o wasm chip35, depois faça o deploy on-chain e adicione um domínio personalizado — um único fio por todo primitivo da DIG.
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.
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.
Índice em uma página das entidades centrais da DIG Network — capsule, store, generation, URN, retrieval key, o dig RPC, o protocolo chia:// e a ancoragem on-chain — cada uma definida uma vez e ligada ao seu documento aprofundado.
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.
Uma plataforma totalmente legível por máquina — OpenAPI/OpenRPC, uma taxonomia de erros catalogada, precificação ao vivo, JWKS, JSON por página, e um @dignetwork/dig-sdk tipado — para você conectar uma carteira + leituras verificadas na sua aplicação sem raspar uma única linha de texto humano.
Minte uma coleção CHIP-0007 inteira cuja arte vive permanentemente em um capsule DIG à prova de adulteração — um único pacote atômico assinado, royalties reais, e mecânicas de drop honestas que nunca simulam o que ainda não conseguem provar on-chain.
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.
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 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.
Store identity via on-chain singleton launcher id, generations as capsules, content root, on-disk layout, and compiled module structure.
@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.
Interface de leitura de toda a rede para capsules DigStore via JSON-RPC 2.0; cega por construção, verificável sem confiança, e transmissível em qualquer tamanho.