HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network
Developers/HybridScript 0.1/Receipts and verification
LANGUAGE & RUNTIME · VERSION 0.1

Receipts and verification

Check reproducibility, commitments, and signer evidence without overstating what they prove.

Preview profilehybridscript-0.1-previewReviewed 2026-09-30

Read a receipt in context

Receipt fieldsPurpose
profile, policy_hash, capability_hash, resource_scheduleIdentify the admitted language and execution boundary.
source_hash, entrypoint, input_hashIdentify the code and input commitment.
prior_state_root, resulting_state_rootDescribe the state transition commitments.
output, output_hash, reads, writes, eventsDescribe the result and recorded effects.
execution_units, execution_limit, termination, error_codeExplain accounting and completion status.
receipt_hashCommit to the canonical receipt payload without its receipt_hash field.

Three distinct checks

Replay requires the original source, input, state, context, capabilities, and policy—not only public hashes. Public records may intentionally omit private material. A reference CLI receipt-hash check should not be described as full execution replay or signature verification.

CheckWhat it establishesWhat it does not establish
Recompute the receipt hashThe provided payload matches its hash.That the program was executed or the signer is trusted.
Replay with the pinned profileThe supplied inputs and state reproduce the expected result under that implementation.That private inputs are true or a financial action occurred.
Verify a node attestationA trusted key signed the specified job/receipt/worker evidence.Universal correctness, downstream finality, or business authorization.

Practical review checklist

Start from full identifiers. Match the package and policy, inspect termination and errors, check the relevant commitments, and verify the attestation against an independently trusted key where available. Keep package publication evidence separate from execution evidence. Finally apply business acceptance criteria to the result; deterministic computation can faithfully reproduce an incorrect algorithm.