44 篇文档带有标签「capsule」

端到端教程：搭建一个 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.

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

Blind serving model, decoy streams, CORS, caching, rate limiting, and conformance checklist for dig RPC endpoints.

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.

DIG Network 各基础原语概览：用于内容可寻址发布的 DigStore、用于盲目托管与检索的 dig RPC，以及用于内容访问的 DIG Browser。

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

打开由你自己的浏览器对照区块链验证的 chia:// 内容 —— 任何主机都无法篡改或伪造它，私密内容对主机保持私密，并且内容永久存在、可在任何地方重新托管，因此没有人能下线它或将你锁定在某个平台上。

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

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.

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.

Layer 0 of the DIG Protocol: store vs capsule vs generation. store_id is the CHIP-0035 singleton launcher id. A store is an ordered sequence of capsules.

The normative urn:dig:chia URN grammar, the rootless retrieval_key = SHA-256(canonical) invariant, resourceKey normalization, the three-way scheme split (chia:// vs §21 dig:// vs dig://* browser), and the salt addressing extension.

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.

Layer 1 read-crypto: HKDF-SHA256 key derivation (salt-mixed secret), AES-256-GCM-SIV fixed-nonce seal, the byte-exact constants table, and the one-crypto-implementation invariant (producer = host = verifier = dig-client-wasm).

The D5 per-resource UNTAGGED leaf = SHA-256(ciphertext), the NODE_TAG fold, odd-node carry-up, the proof-length ≤ ceil(log2 n) binding contract (D8), and the base64 X-Dig-Inclusion-Proof wire layout.

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.

Fixed-size obfuscation (128 MiB uniform blob, deterministic ChaCha20 filler), WASM injection memory layout (BINDING D2: 2 MiB offset, 384 MiB ceiling), the self-serving guest pipeline, oblivious gather, decoy generation, and the disabled host-attestation gate.

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 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.

The dig RPC is THE machine interface of the protocol: JSON-RPC 2.0 over HTTP POST, the full method catalogue, the chunk wire object (chunk_lens first-window-only, NO decoy field), range/window math, error codes incl. -32004, and the node profile vs the network profile.

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.

Complete dig RPC method set: dig.getContent, dig.getProof, dig.getCapsule, dig.getManifest, dig.listCapsules, dig.listCollectionItems, dig.getCollection, and service discovery methods.

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.

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

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

什么是 dig-node、为什么要运行一个，以及如何安装它 —— 面向 Ubuntu/Debian 的 apt 仓库，或者跨平台的通用安装程序。

npm create dig-app — scaffold a wallet-wired, deployable DIG app in one command. Five templates (static, vite-react, next-static, nft-drop, dapp-window-chia), all free to build and preview; you pay the uniform capsule price only when you publish.

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

Streaming chunk model for byte methods: chunk object structure, 64 KiB alignment, reassembly, proof verification, and reference client loop.

A content-addressed protocol for opening stores and resources directly from the DIG Network, with URN and shorthand forms.

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

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

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

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.

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

用于读取 DigStore capsule 的全网统一读取接口，基于 JSON-RPC 2.0；天生盲态、无需信任即可验证，且可在任意大小下流式传输。