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.
What changed across the DIG developer surfaces — the digstore CLI, the dig RPC, and the window.chia provider — including breaking changes and the versioning rules for each.
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.
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.
Every DIG error code in one place: dig RPC JSON-RPC codes, digstore CLI exit codes, and DIGHUb user-facing codes — each with what it means and what to do.
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.
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.
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.
Where to get help with DIG — the community Discord, GitHub issues, and how to file a report that gets answered fast.
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.
Two proof types: synchronous Merkle inclusion proofs that pin served bytes to an on-chain root, and asynchronous ZK / risc0 execution receipts that attest faithful serving — gated on the control plane.
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.
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.
Where to check the health of the DIG services — the dig RPC (rpc.dig.net), DIGHUb (hub.dig.net), and the resolver (on.dig.net) — plus how RPC and provider versions are signalled.
Git-style remote protocol via dig:// URLs, per-request BLS signing, clone/pull/push operations, and self-hosted node setup.
Fixes for the most common DIG failures — funding, confirmation timeouts, push conflicts, verification errors, and wallet/session problems.
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.
Detect and use the DIG Browser's injected Chia wallet provider for permission-gated key and signing operations.
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.