18 篇文件帶有標籤「merkle-proof」

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.

透過 JSON-RPC 2.0 讀取 DigStore capsule 的全網通用讀取介面；天生具有盲目性、無需信任即可驗證，且可在任何大小下進行串流傳輸。

DIG Network 核心實體的單頁索引——capsule、store、generation、URN、retrieval key、dig RPC、chia:// 協定，以及鏈上錨定——每個詞彙都僅定義一次，並連結到其深入文件。