18 篇文档带有标签「merkle-proof」

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

The cross-implementation parity discipline: frozen canonical()/retrieval_key() goldens, the C8 crypto fixtures, the shared URN conformance vectors, the OpenRPC-vs-server diff test, and what every reimplementation MUST pass.

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

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

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

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

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.

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

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

Public RPC endpoint usage, portability across nodes, operating your own node, and rate limiting policies.

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