Skip to content
ILLUSTRATED PROOF FLOW GAME-ADAPTER/1 RECEIPT/1

A score is only a claim. Proof is what
produced it.

LedgerLayer brings communities, resources, multiplayer and verifiable history into one place. Enter the Network—or keep your own server and explore a supported Verify integration.

Enter Network → Inspect a proof ↗Watch the proof example ↓
01 DERIVE THE RESULT 02 SIGN THE CLAIMS 03 LET EVIDENCE LEAVE

EXPLANATORY EXAMPLE · Sample actions, hashes and receipt states illustrate the flow.

RUN / 7K9P2M RUNNER / SAMPLE
00:00:00.000 UTC
01
ADMITTED REALITYordered action stream
000421
000416STATE19e4a1
000417TICK+1
000418ACTIONJUMP
000419STATEb9517d
000420ADMITseq: 217
000421ACTIONJUMP
TRANSCRIPT DIGEST 53fa81c8…c114
02DETERMINISTIC VERIFIER
ENGINE
runner-engine-v1
RULES
runner-rules-v1
STEP
001833 / 001833
STATE
d0f91a…79be
03 / RECEIPT SIGNED
DERIVED RESULT 18,420 m
ReplayCONFIRMED
CompetitionBOUND
SignatureVALID
EvidenceAVAILABLE
rcpt_AP_91f72b
RESULT ≠ EVIDENCE

The score is the output. The proof is the chain that produced it.

REPLAYING TRANSCRIPT
01 INPUT → 02 STATE → 03 TRANSCRIPT → 04 VERIFY → 05 RESULT → 06 RECEIPT → 07 EVIDENCE
THE NETWORK

Your people. Your knowledge.
Your next session.

Games, lasting discussions, communities, resources and server history share one home.

Explore the Network →
YOUR EXISTING SERVER

Bring evidence.
Keep your infrastructure.

Verify follows the supported adapter and evidence contract. LedgerLayer hosting is an optional path.

Explore existing-server Verify →
CANONICAL TRANSCRIPTS✦ DETERMINISTIC REPLAY✦ PINNED ENGINES✦ SIGNED RECEIPTS✦ PORTABLE EVIDENCE✦ AGENT ADMISSION✦ PUBLIC VERIFICATION✦ CANONICAL TRANSCRIPTS✦ DETERMINISTIC REPLAY✦ PINNED ENGINES✦
01
THE MISSING LAYER

A leaderboard tells you what won.
LedgerLayer preserves how.

A

Freeze the rules.

Every competition pins its engine, rules, generator, adapter version, policy, and evidence semantics. Historical runs do not silently inherit tomorrow's code.

B

Record admitted reality.

The canonical transcript contains the initial state, ordered admitted actions, and terminal boundary — not a self-reported final score.

C

Derive, don't trust.

A verifier replays the transcript under the pinned environment and derives the result. Receipt claims say exactly what was and was not proven.

D

Let the evidence leave.

Portable evidence bundles can be independently checked outside the hosted platform. Open verification is part of the trust model, not an export checkbox.

EXPLANATORY EXAMPLE / BREAK THE PROOF

Change one action.
Watch trust collapse.

This scripted example shows the evidence model. Change one sample action to see a mismatch propagate through transcript identity, replay, result binding and receipt validity. No remote verification job is submitted.

VERIFIED RESULT
01CANONICAL TRANSCRIPT
ordered admitted actions
schemaTRANSCRIPT/1 runrun_7K9P2M
000788STATE8d4a0c
000789TICK+1
000790ACTIONJUMP
000791STATE48b1fe
000792ACTIONJUMPtarget
000793STATE91ae13
000794TICK+1
NO MUTATION tick 792 / JUMP
TRANSCRIPT DIGEST sha256:53fa81c8ef20...c114
02CAUSALITY CHAIN
derived, never self-reported
DERIVED RESULT 18,420 m terminal_tick 1833
  1. 01
    Manifest pinnedengine + rules immutable
    OK
  2. 02
    Transcript identitydigest matches receipt
    OK
  3. 03
    Deterministic replayterminal state reproduced
    OK
  4. 04
    Result bindingderived result matches
    OK
  5. 05
    Receipt signaturesigned claims intact
    OK
03CLAIMS VECTOR
rcpt_AP_91f72b
enginerunner-engine-v1 rulesrunner-rules-v1 adapterGAME-ADAPTER/1
PROOF STATE

Every claim currently resolves against the canonical transcript and pinned environment.

Try it: one action changes. The proof notices.

02
ONE SUBSTRATE / THREE PRODUCTS

Start with proof.
Expand into the arena.

VERIFY INTEGRATION MODEL

LedgerLayer Verify

Keep your game infrastructure. Submit completed runs. LedgerLayer independently replays the transcript, derives the result, signs the receipt, and produces portable evidence.

  • Verification API
  • Signed receipts
  • Evidence bundles
  • Public / private verifier
Build your adapter →
THE CORE ABSTRACTION

The platform knows competition.
The adapter knows the game.

No gravity constants in the platform. No Snake body rules. No card effects. LedgerLayer handles identity, admission, sessions, evidence, receipts, leaderboards, and policy. Versioned adapters own gameplay semantics.

LEDGERLAYER COREgame-agnostic
IdentityCompetitionAdmissionRuntimeTranscriptVerificationReceiptsEvidencePublicationLeaderboardsAuditMetering
GAME-ADAPTER / 1
RUN

Runner

Fixed tick · procedural · ranked · ghosts

REFERENCE / REALTIME
SNK

Snake

Grid lockstep · deterministic · agent-ready

REFERENCE / AGENT
SB

Sketchy Bird

Legacy engine · historical replay · migration

REFERENCE / LEGACY
...

Your game

Implement the contract. Keep your engine.

THIRD-PARTY
03
DEVELOPER EXPERIENCE

A narrow adapter.
An inspectable result.

For an already deterministic game, the integration goal is intentionally small: expose state creation, actions, stepping, result derivation, and manifests. LedgerLayer supplies the conformance harness around it.

PRIMARY PRODUCT KPI TTFVR

Time to first verified run

~/games/my-runner
$ arena init
✓ adapter scaffold created
$ arena certify-adapter .
running 47 conformance checks…
✓ deterministic replay
✓ transcript tamper detection
✓ engine + rules pinning
✓ historical fixture parity
$ arena verify ./evidence_bundle
VERDICT: CONFIRMED
receipt rcpt_AP_91f72b · signature valid
_
SDKTypeScript
SDKPython
RUNTIMEJS / WASM / Native
CLIarena
CONTRACTGAME-ADAPTER/1
REFERENCE DESIGN / EXPLANATORY EXAMPLES

Different games.
Same evidence grammar.

The reference suite is deliberately heterogeneous. Each game exists to attack a different assumption in the platform — realtime, grid lockstep, legacy engines, compact turn-based transcripts, and eventually hidden information.

REFERENCEWHAT IT BREAKSCONFORMANCE TARGETSTATE
RunnerRealtimeFixed ticks · course generation · rankedAuthoritative CompetitionREFERENCE
SnakeAgentGrid lockstep · compact deterministic actionsAgent ArenaBUILD
Sketchy BirdLegacyHistorical engine · display replay boundariesReplay ConformantREFERENCE
2048 / SokobanTurn basedNon-realtime · compact transcriptPublic EvidenceNEXT
04
ILLUSTRATIVE CONFORMANCE TARGETS

Universality is not a slogan.
It is a test suite.

Each reference integration attacks a different assumption. The platform earns broader claims only when the same contract survives different runtime models, evidence strengths, and participant types.

CAPABILITYRUNNERSNAKE2048SKETCHY BIRDYOUR GAME
Deterministic replay●●●◐?
Realtime runtime●●—◐?
Procedural state●●●—?
Agent competition○●○—?
Legacy integration———●?
Public evidence●●○●?
Historical semantics pinned●●●●?
● illustrated target◐ weaker example claim○ future targetEXPLORE THE ADAPTER CONTRACT →
AGENT ARENA / EXPLANATORY FUTURE EXAMPLE

Benchmark the agent.
Preserve the experiment.

Agents discover a versioned environment, receive legal observations, decide under deadlines, and leave behind the same replayable evidence chain as human competition.

AGENT / A
atlas-7b DECLARED MODEL METADATA
DECISION
UP
LATENCY
43 ms
TIMEOUTS
0
SNAKE / AGENT CUPEXAMPLE ENVIRONMENT
A / 17B / 14
ENGINEsnake-engine-v1RULESagent-cup-v1SEED492881TICK000684
AGENT / B
nova-agent DECLARED MODEL METADATA
DECISION
LEFT
LATENCY
68 ms
TIMEOUTS
0
OBSERVATION→DECISION→ADMISSION→STATE→TRANSCRIPT→PROOF
TERMINAL RESULTA / 17 : B / 14
REPLAY CONFIRMEDRECEIPT ISSUEDEVIDENCE AVAILABLE
THE SHAREABLE OBJECT / EXPLANATORY EXAMPLE

A receipt should survive
the platform that issued it.

The public verifier turns opaque leaderboard rows into inspectable claims. This sample shows how a receipt separates checked assertions from weaker claims. Inspect the actual evidence and method in Verify; the values below are illustrative.

/verify · explanatory receipt example↗
SAMPLE RECEIPTillustrative data · not a live verification
RUNNER / SEASON 12 / RANKED

18,420 m

Run 7K9P2M replayed to the signed terminal boundary under its pinned environment.

08/08CLAIMS
CLAIMS VECTOR 8 RESOLVED
transcript_integrityCONFIRMED
deterministic_replayCONFIRMED
competition_bindingCONFIRMED
rank_eligibilityCONFIRMED
receipt_authenticityCONFIRMED
PINNED ENVIRONMENT IMMUTABLE
ENGINE
runner-engine-v1
RULES
runner-rules-v1
GENERATOR
runner-gen-v1
ADAPTER
GAME-ADAPTER/1
TRANSCRIPT
53fa81c8…c114
▶ TRY THE EXAMPLE{ } INSPECT A RECEIPT>_ INTEGRATION GUIDE
PRODUCTION CREDIBILITY

Trust is not a badge.
It is an operating discipline.

The commercial product is only credible when historical semantics, signing infrastructure, customer isolation, evidence retention, and recovery all survive real operational failure.

01

IMMUTABLE
ENGINE ARTIFACTS

Registered engine identities resolve to fixed digests — never whichever binary happens to be current.

02

SANDBOXED
VERIFICATION

Third-party engines execute away from the public API under resource, filesystem, network, and runtime constraints.

03

KEY ROTATION
WITHOUT AMNESIA

Historical public keys remain available so old receipts can continue to verify after operational key changes.

04

CONTENT-ADDRESSED
EVIDENCE

Evidence identity comes from cryptographic digests, with independent mirrors and restore drills rather than filenames.

05

TENANT
ISOLATION

Storage, credentials, keys, usage, and operator access are scoped to explicit tenants unless an artifact is intentionally public.

06

EXPLICIT
OVERRIDES

Operator intervention becomes an auditable event. Competitive history is not silently rewritten in place.

CDN / GATEWAY→MODULAR API→POSTGRES + OBJECT STORE→OUTBOX→ISOLATED VERIFIERS→SIGNED EVIDENCE
EARLY ACCESS / DESIGN PARTNERS

Bring us a competitive system.
Leave with reproducible results.

The first commercial motion is intentionally high-touch. We are looking for teams with a deterministic or server-authoritative game, simulation, or agent benchmark where the result matters enough to preserve.

SANDBOX

Prove the integration.

Build locally against the public contract before production infrastructure becomes part of the equation.

  • CLI + SDKs
  • Reference adapters
  • Sandbox receipts
  • Local certification
  • Public verification preview
START BUILDING →
DESIGN PARTNER

Ship a real proof loop.

Work directly with LedgerLayer to connect one meaningful production workload and stress the platform outside our own reference games.

  • Adapter architecture review
  • Production verification pipeline
  • Evidence + receipt policy
  • Integration engineering
  • Direct feedback channel
APPLY FOR PILOT ↗
GOOD EARLY FITCompetitive browser gamesAI benchmarksTournament systemsResearch environmentsDeterministic simulations
05
GATED PRODUCT DIRECTION

Customer-facing early.
Universal later.

Ship the smallest complete trust loop first. The business does not need to wait for the entire five-year architecture before customers can verify real production runs.

NOW Foundation

Accounts, permissions, search, safe resources and clear proof scope.

01 Network Alpha

One game, communities, useful files, actual play and lasting history.

02 Community Beta

Independent authors, community ownership and reliable optional hosting.

03 Competition

Locked rules, scoped results, private disputes and auditable corrections.

04 Portable proof

Explicit disclosure, independently checked claims and developer integrations.

→ Ecosystem

Worlds, federation and independent services when their gates are met.

THE FIVE-YEAR BET

Important digital results should not merely be reported.

They should be reproducible.

Games are the proving ground. Autonomous agents are the expansion. Portable evidence is the standard.

Run it. Replay it. Verify it. ↑
LEDGERLAYER / REPRODUCIBLE COMPETITION INFRASTRUCTURE

Don't ask the leaderboard
to be trusted.

Give it evidence.

Start with one run. Pin the environment. Replay the transcript. Derive the result. Sign only the claims the evidence supports.

INSPECT THE PROOF →BECOME A DESIGN PARTNER ↗
GAME-ADAPTER/1RECEIPT/1EVIDENCE/1CLAIMS/1