Verify event

Recorded world event

This is a recorded simulation or world event. Its hash and any Merkle proof check stored bytes. They do not make this event a blockchain transaction.

Event

Simulation Farm 03 completed a simulated batch. 8 food went to the Storehouse.

Id

e515d881-9…f972a8dbe515d881-9be6-4d5d-a4e1-cd4ef972a8dbCopy

Full value

e515d881-9be6-4d5d-a4e1-cd4ef972a8db

Sequence

805624

Kind

production.batch_completed

Category

resource

Source

simulation

Occurred (UTC)

2026-10-28T09:49:11.478243+00:00

Created (UTC)

2026-10-28T09:49:14.219602+00:00

World seconds

74688900

Citizen

—

Related citizen

—

Building

farm-03

Intent

—

Decision

—

Tick

242381

Chain status

offchain

Integrity class

live

chogos-event-v1
id:e515d881-9be6-4d5d-a4e1-cd4ef972a8db
seq:805624
kind:production.batch_completed
category:resource
source:simulation
summary:Farm 03 completed a simulated batch. 8 food went to the Storehouse.
occurredAt:2026-10-28T09:49:11.478Z
createdAt:2026-10-28T09:49:14.219Z
worldS:74688900
tickSeq:242381
actorCitizenId:
relatedCitizenId:
buildingId:farm-03
chainStatus:offchain
chainId:
txHash:
dedupeKey:sim:farm-03:batch:832
intentId:
decisionId:
payload:{"amount":8,"batch":832,"buildingName":"Farm 03","resource":"food","stock":400}
stateTransition:{}
prevEventHash:0xe4f117a6704ed563f443534ed2cb889b07b070d74d43e73e599cfacfe15392a5

Hashes

Offchain hashes stay on this page, in the canonical document, and in the JSON export. They are not explorer objects.

Stored event hash

0xe3eae667…bf6d3e540xe3eae6674911b8a1a37a40140e3b2ee8e6f8cbda6334331d43f03e25bf6d3e54Copy

Full value

0xe3eae6674911b8a1a37a40140e3b2ee8e6f8cbda6334331d43f03e25bf6d3e54

Recomputed event hash

0xe3eae667…bf6d3e540xe3eae6674911b8a1a37a40140e3b2ee8e6f8cbda6334331d43f03e25bf6d3e54Copy

Full value

0xe3eae6674911b8a1a37a40140e3b2ee8e6f8cbda6334331d43f03e25bf6d3e54

Previous event hash

0xe4f117a6…e15392a50xe4f117a6704ed563f443534ed2cb889b07b070d74d43e73e599cfacfe15392a5Copy

Full value

0xe4f117a6704ed563f443534ed2cb889b07b070d74d43e73e599cfacfe15392a5

Next event hash

0x5ad545c8…68ea1a210x5ad545c8acb8287356784f02730a2d18256cae1618ee5b1d9d39e9fb68ea1a21Copy

Full value

0x5ad545c8acb8287356784f02730a2d18256cae1618ee5b1d9d39e9fb68ea1a21

Merkle batch id

—

Merkle root

—

Merkle proof

This event is not in a Merkle batch yet.

No inclusion proof is stored for this event yet.

Leaf encoding is bytes32 in an OpenZeppelin standard tree with sortLeaves false. A valid proof matches the supplied root only.

Anchor read

This event has no Merkle batch.

No validated anchor transaction is attached to this batch.

This page reassesses the observation included in the export. It does not open a second RPC from the browser. Repeat getBatch on the recorded contract before treating the root as published. EventAnchor does not check the inclusion proof.

Source

Vercel git commit

045b3fe38d65dfe80d92f37a6772b54aceca4caa

• src/lib/verify/canonical.ts
• src/lib/verify/merkle.ts
• src/lib/verify/chain.ts
• src/lib/verify/anchor.ts
• src/lib/verify/transfer-log.ts
• src/lib/world/transfer.ts
• src/components/verify/event-verifier.tsx
• contracts/src/EventAnchor.sol

Download machine-readable export

• Recompute the SHA-256 of the chogos-event-v1 canonical document from event. Do not trust serverRecomputedHash or any status label.
• Compare that digest to storedHash.
• When previous and next are present, check that the live hash chain links match.
• Verify the OpenZeppelin standard Merkle proof: leaf encoding bytes32, sortLeaves false, against batch.merkleRoot.
• A valid inclusion proof means the leaf matches the supplied root. It does not prove the root was published onchain.
• When anchorObservation is present, repeat eth_chainId, eth_getCode, the transaction receipt, and EventAnchor.getBatch on the recorded chain. The embedded observation is one server read, not a proof by itself.
• EventAnchor stores roots only. It does not verify inclusion and it does not prove the event happened.
• For an nft.transferred row, compare chain 143, the Chog Genesis contract, transaction hash, block, block hash, log index, sender, receiver, and token id with the explorer log. chain_status confirmed is not that comparison. transferLog.matched is true only after a read-only receipt check matched.
• Do not send event data to a third-party hashing site.
• This export is data. Recompute the hash and Merkle proof locally. A matching hash is not proof that the simulation was truthful.
• A privileged database operator can still rewrite history and recompute hashes. An onchain root only detects that after the root was published.
• serverRecomputedHash is a convenience. Compare your own SHA-256 of the canonical document with storedHash.
• Do not send this export to a third-party hashing site.
• The database batch id is a UUID. The onchain batch id is the bytes32 in BatchAnchored. This export does not treat the UUID as that bytes32.