Skip to main content
ParalleliX Docs

// Section 5.4 · Protocol

Immutable Records

1 min5.4Protocol
// 4 of 5 · the proof model

The chain structure is the tamper-evidence.

// 5.4 · immutable records · previous_hash linkage · no zk machinery

Tamper-evidence comes from chain structure, not from zk.

Validated execution records anchor to the blockchain with previous_hash linkage. Any modification to a past record breaks the chain at that point. A reader walking backwards can detect tampering without trusting any single party. The tamper-evidence property comes from the chain structure, not from any zero-knowledge machinery.

The chain shape

// each record carries previous_hash · breakage is visible

// record_n-2request_id: prlx_7f3a91…node_id: nd_4f7c…poe_v1: 9c27a4…previous_hash: 0x4a8b…
→
// record_n-1request_id: prlx_7f3a91…node_id: nd_4f7c…poe_v1: 9c27a4…previous_hash: 8e91…
→
// record_nrequest_id: prlx_7f3a91…node_id: nd_4f7c…poe_v1: 9c27a4…previous_hash: c027…
→
// record_n+1request_id: prlx_7f3a91…node_id: nd_4f7c…poe_v1: 9c27a4…previous_hash: d104…

// modifying record_n-1 changes its hash; record_n's previous_hash no longer matches; the chain breaks at that point and is visible to anyone walking backwards

Anchoring cadence

// batched merkle commitments · l1 gas tradeoff

// AT LAUNCH1 / 10 min

Tight L1 gas budget. Network throughput allows lower freshness.

// PLANNED1 / 2 min

On-chain throughput economics improve. Tighter freshness for the open marketplace.

See §2.4 for the on-chain anchor categories and the ExecutionRecord shape.

// Reading path

The Proof Model · parent hubThe On-Chain Anchor · where records land (§2.4)Proof of Execution · the commitment recorded per request