End-to-end: scaffold aplikasi React, hubungkan wallet Chia dalam-halaman (window.chia + fallback WalletConnect) dengan dig-sdk, bangun dan tandatangani sebuah spend melalui wasm chip35, lalu deploy on-chain dan tambahkan domain kustom — satu alur melalui setiap primitif 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.
Ringkasan primitif DIG Network: DigStore untuk penerbitan content-addressable, dig RPC untuk blind hosting dan retrieval, serta DIG Browser untuk akses konten.
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.
Terbitkan situs atau aplikasi yang benar-benar Anda miliki — di-mint on-chain sebagai aset Anda sendiri, bukan disewa. Build dan preview gratis; bayar harga $DIG seragam kecil hanya saat menerbitkan, dengan file terenkripsi di browser Anda sehingga tak ada host yang bisa membacanya.
Platform yang sepenuhnya machine-readable — OpenAPI/OpenRPC, taksonomi error yang dikatalogkan, penetapan harga live, JWKS, JSON per-halaman, dan @dignetwork/dig-sdk yang bertipe — sehingga Anda menghubungkan wallet + pembacaan terverifikasi ke aplikasi Anda tanpa perlu meng-scrape satu baris pun prosa manusia.
Mint seluruh koleksi CHIP-0007 yang seninya hidup secara permanen dalam sebuah capsule DIG yang tamper-evident — satu bundle yang ditandatangani secara atomik, royalti sungguhan, dan mekanisme drop yang jujur yang tidak pernah memalsukan apa yang belum bisa mereka buktikan on-chain.
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.
Terbitkan situs pertama Anda di DIG — gratis untuk build dan preview, Anda hanya membayar harga capsule seragam saat menerbitkan. Jalur web-first (tanpa wallet di awal) plus jalur CLI paralel.
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.
Setiap kegagalan memberi Anda sebuah kode stabil dan sebuah request-id yang langsung terhubung ke log server, spend on-chain dijaga terhadap race-condition sehingga Anda tak pernah membayar dua kali, dan pemeriksaan pre-flight yang jelas mencegah capsule sia-sia sebelum Anda mengeluarkan $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.