29 篇文档带有标签「anchoring」

端到端教程：搭建一个 React 应用，用 dig-sdk 接入页内 Chia 钱包（window.chia + WalletConnect 回退），通过 chip35 wasm 构建并签名一笔支出，然后上链部署并添加自定义域名 —— 一条贯穿每个 DIG 基础原语的完整线索。

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.

Full walkthrough of the DigStore CLI: initialize a store, commit files, and read content back. The parallel track to the web-first quickstart.

Complete command reference for the digstore CLI, including wallet, store, staging, history, content, remote, and maintenance commands.

DIG Network 核心实体的单页索引 —— capsule、store、generation、URN、retrieval key、dig RPC、chia:// 协议以及链上锚定 —— 每个术语只定义一次，并链接到其详细文档。

Auto-publish your built site or dapp to your existing DIG store on every push with the dig-network/deploy-action — git-push-to-deploy, free PR previews, and a PR comment + GitHub deployment status. Keyless CI auth, no long-lived hub secret.

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 价格，文件在你的浏览器中加密，因此任何主机都无法读取它们。

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.

The shortest path through the digstore CLI: install it, scaffold and preview for free, publish a capsule on-chain, share it over a remote, and read it back — each task linked to the page that walks it.

Chia AugScheme (G1 48B / G2 96B), the five mutually-distinct role DSTs (PUSH/NODE/TOMB/REQ/ATTEST) with their exact signing-message preimages, rogue-key rejection, and the host↔guest parity fixtures.

BINDING contract D1: the DIGS blob byte layout (big-endian, self-describing), all 12 SectionIds and their body formats (KeyTable D3, ChunkPool D4, MerkleNodes D5, ChainState, Filler), and the big-endian rationale.

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 §21 transport: dig:// locator resolution, the REST surface, the JSON-outer / Chia-codec-inner envelope, 2-leg push v1 (inline | presigned), the authenticated head (PUSH_DST), per-request §21.9 auth with exact signing messages, ETag/delta/pull, tombstone revocation, and decoy indistinguishability.

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.

Wallet seed setup, on-chain costs, funding, anchor status, and chain-verified downloads for DigStore projects.

The committable dig.toml manifest and how to inject PUBLIC build-time config (RPC endpoint, asset/CAT ids, feature flags) into a dapp — plus the one hard rule: a blind static capsule holds no server secrets.

Merkle proofs, verified downloads, signed roots, revocation, and host attestation for DigStore security.

DIG 协议被划分为七个自底向上的层次，兼具规范性与实现定义的内容。capsule（storeId:rootHash）是最基础的单位；主机保持盲态，读取方对照链上数据进行验证。这是权威的协议参考文档。

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

Publishing stores to remotes, downloading with verification, revoking roots, and understanding public vs. private access models.

Store identity via on-chain singleton launcher id, generations as capsules, content root, on-disk layout, and compiled module structure.

Git-style remote protocol via dig:// URLs, per-request BLS signing, clone/pull/push operations, and self-hosted node setup.

Architecture of the content-addressable, encrypted WebAssembly store format: identity, generations, URNs, and compiled modules.

Fixes for the most common DIG failures — funding, confirmation timeouts, push conflicts, verification errors, and wallet/session problems.

Workflow for initializing projects, managing staging areas, running multiple stores in one workspace, and typical release loops.

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.

Git 形态、内容可寻址的项目格式，内置加密与基于 URN 的寻址；编译为单一的自我防护 WebAssembly 模块。