23 篇文档带有标签「dighub」

端到端教程：搭建一个 React 应用，用 dig-sdk 接入页内 Chia 钱包（window.chia + WalletConnect 回退），通过 chip35 wasm 构建并签名一笔支出，然后上链部署并添加自定义域名 —— 一条贯穿每个 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.

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.

发布一个你真正拥有的网站或应用 —— 作为你自己的链上资产铸造出来，而不是租来的。构建与预览完全免费；只有在发布时才需要支付少量统一 $DIG 价格，文件在你的浏览器中加密，因此任何主机都无法读取它们。

一个完全机器可读的平台 —— OpenAPI/OpenRPC、一套完整分类的错误体系、实时定价、JWKS、逐页 JSON，以及一个类型化的 @dignetwork/dig-sdk —— 让你无需抓取一行人类阅读的文字说明，就能将钱包与已验证的读取能力接入你的应用。

铸造一整套 CHIP-0007 合集，其艺术作品永久存放于一个防篡改的 DIG capsule 中 —— 一个原子性的已签名支出包、真实的版税，以及诚实的发行机制，绝不会假装能证明尚未在链上得到证实的事情。

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.

在 DIG 上发布你的第一个站点 —— 构建与预览免费，只有在发布时才需要支付统一的 capsule 价格。网页优先路径（无需先备好钱包），并附带一条并行的 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.

每一次失败都会给你一个稳定的错误码和一个可以直接对应到服务器日志的 request-id，链上支出具备竞态防护因此你永远不会重复付款，清晰的预检防护会在花费 $DIG 之前拦截无谓的 capsule 浪费。

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.