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 Riverside Farm completed a simulated batch. 8 food went to the Storehouse.

Id

3f78d9e1-6…874029d43f78d9e1-68ca-4c60-80ef-2e94874029d4Copy

Full value

3f78d9e1-68ca-4c60-80ef-2e94874029d4

Sequence

805678

Kind

production.batch_completed

Category

resource

Source

simulation

Occurred (UTC)

2026-10-28T09:50:10.978243+00:00

Created (UTC)

2026-10-28T09:50:13.477083+00:00

World seconds

74692470

Citizen

—

Related citizen

—

Building

riverside-farm

Intent

—

Decision

—

Tick

242392

Chain status

offchain

Integrity class

live

chogos-event-v1
id:3f78d9e1-68ca-4c60-80ef-2e94874029d4
seq:805678
kind:production.batch_completed
category:resource
source:simulation
summary:Riverside Farm completed a simulated batch. 8 food went to the Storehouse.
occurredAt:2026-10-28T09:50:10.978Z
createdAt:2026-10-28T09:50:13.477Z
worldS:74692470
tickSeq:242392
actorCitizenId:
relatedCitizenId:
buildingId:riverside-farm
chainStatus:offchain
chainId:
txHash:
dedupeKey:sim:riverside-farm:batch:2646
intentId:
decisionId:
payload:{"amount":8,"batch":2646,"buildingName":"Riverside Farm","resource":"food","stock":400}
stateTransition:{}
prevEventHash:0x31e0cf676c99769e567755e33ea1bc8b6b39e4d7d844a441f57479fb005e1e15

Hashes

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

Stored event hash

0x04aad4d8…f5a9018a0x04aad4d856bf30409a8b1e42c3de164f5e2dbe48682e24b8b0dda7f6f5a9018aCopy

Full value

0x04aad4d856bf30409a8b1e42c3de164f5e2dbe48682e24b8b0dda7f6f5a9018a

Recomputed event hash

0x04aad4d8…f5a9018a0x04aad4d856bf30409a8b1e42c3de164f5e2dbe48682e24b8b0dda7f6f5a9018aCopy

Full value

0x04aad4d856bf30409a8b1e42c3de164f5e2dbe48682e24b8b0dda7f6f5a9018a

Previous event hash

0x31e0cf67…005e1e150x31e0cf676c99769e567755e33ea1bc8b6b39e4d7d844a441f57479fb005e1e15Copy

Full value

0x31e0cf676c99769e567755e33ea1bc8b6b39e4d7d844a441f57479fb005e1e15

Next event hash

0xc425b9e5…2b4a239a0xc425b9e504d27731a0444a4d935ac42223e4be2aa92e17b02cc37ef72b4a239aCopy

Full value

0xc425b9e504d27731a0444a4d935ac42223e4be2aa92e17b02cc37ef72b4a239a

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.