23 篇文件帶有標籤「dighub」

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.

DIG Network 核心元件總覽：用於內容定址發布的 DigStore、用於盲目託管與取回的 dig RPC，以及用於存取內容的 DIG Browser。

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.

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.

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.

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.

從頭到尾完整流程：建立一個 React 應用骨架、用 dig-sdk 接上頁內 Chia 錢包（window.chia 加上 WalletConnect 備援）、透過 chip35 wasm 建構並簽署一筆花費，接著上鏈部署並加上自訂網域——一條主線串起每一個 DIG 核心元件。

在 DIG 上發布你的第一個網站——建置與預覽免費，只有在發布時才需支付統一的 capsule 價格。以網頁優先的路徑（一開始不需要錢包），並附上一條並行的 CLI 路徑。

每一次失敗都會提供一個穩定代碼與一個能直接對應到伺服器日誌的請求識別碼（request-id），鏈上花費具備競爭防護機制因此你絕不會重複付款，而明確的前置檢查機制則能在你花費 $DIG 之前，先攔下會被浪費的 capsule。

鑄造一整個 CHIP-0007 收藏系列，其藝術作品永久存放在防竄改的 DIG capsule 中——一個原子性的已簽署花費包、真實的版稅機制，以及誠實的發行機制，絕不假裝提供尚無法在鏈上證明的保證。

發布一個你真正擁有的網站或應用——以你自己的資產形式鑄造在鏈上，而不是租來的。免費建置與預覽；只有在發布時才需支付小額的統一 $DIG 價格，且所有檔案都在你的瀏覽器中加密，因此沒有任何主機能讀取它們。

一個完全機器可讀的平台——OpenAPI／OpenRPC、一套已編目的錯誤分類系統、即時定價、JWKS、逐頁 JSON，以及具型別的 @dignetwork/dig-sdk——讓你把錢包與經過驗證的讀取功能接進你的應用，完全不需要爬梳任何一行人類可讀的說明文字。