Pinned environments
Historical runs stay attached to the engine, rules, generator, adapter, and interpretation they actually used.
engine_id / rules_id / generator_idPRODUCT / 01 / AVAILABLE FIRSTVerify
Verify
the run.
Keep your game infrastructure. LedgerLayer takes a completed canonical transcript, replays it under a pinned environment, derives the result, signs the supported claims, and emits portable evidence.
THE SMALLEST COMPLETE TRUST LOOP
Submit. Replay.
Derive. Sign.
Verify is designed to be useful before LedgerLayer manages matchmaking, sessions, or realtime competition. The customer keeps those systems and sends the evidence-producing run envelope.
YOUR GAME→TRANSCRIPT→LEDGERLAYER VERIFIER→RESULT→RECEIPT→EVIDENCE
WHAT YOU GET
Proof infrastructure
without a rewrite.
Verify deliberately minimizes integration surface. Your engine remains yours. LedgerLayer standardizes the evidence boundary around it.
Canonical transcripts
Evidence identity comes from the initial state, admitted actions, and terminal boundary — not from a final score field.
SHA256(canonical transcript)Claims vectors
Receipt semantics distinguish what is confirmed, unknown, display-only, released, or ineligible.
transcript_integrity ≠ rank_eligibilitySigned receipts
Interpretation-changing fields are bound into an asymmetric signature with versioned issuer keys.
receipt_id / key_id / signaturePortable evidence
Evidence bundles can be exported and verified without relying on the hosted UI.
arena verify evidence_bundle/Public verification
Share a result as inspectable claims, environment identity, replay verdict, and evidence state.
https://ledgerlayer.org/verifySTART WITH ONE RESULTMake your first run
Make your first run
reproducible.
The first customer milestone is intentionally concrete: one external game, one public adapter contract, one run independently replayed and receipted without changing platform core.