Ana içeriğe geç

"merkle-proof" ile etiketlenmiş 18 doküman etiketlendi

Tüm Etiketleri Görüntüle

Conformance & parity

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.

Conformance & Security

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

dig RPC nedir?

DigStore capsule'leri için JSON-RPC 2.0 üzerinden ağ genelinde okuma arayüzü; tasarım gereği kör, güvenmeden doğrulanabilir ve her boyutta akıtılabilir.

Inclusion vs execution proofs

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.

Kavramlar & sözlük

Temel DIG Network varlıklarının tek sayfalık dizini — capsule, store, generation, URN, alma anahtarı, dig RPC, chia:// protokolü ve zincir üzeri sabitleme — her biri bir kez tanımlanmış ve derinlemesine belgesine bağlanmış.

L1 · Merkle inclusion proofs

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.

L2 · Capsule format (the DIGS data section)

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.

L2/L3 · The self-defending module

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.

L6 · The dig RPC (machine interface)

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.

L6 · Verification, provenance & anchoring

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.

Methods

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

Proofs & Security

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

Protokol: Genel Bakış

Normatif ve uygulamaya bağlı olarak yedi alttan üste katman şeklinde DIG Protokolü. capsule (storeId:rootHash) temel birimdir; host kördür ve okuyucu zincire karşı doğrular. Bu, yetkili protokol referansıdır.

Sharing over a remote

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

Store Structure

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

Streaming

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

The DigStore WASM Store Format

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