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

Id

7e57ecc1-9…44d312887e57ecc1-96a3-4a50-8614-83cd44d31288Copy

Full value

7e57ecc1-96a3-4a50-8614-83cd44d31288

Sequence

805718

Kind

production.batch_completed

Category

resource

Source

simulation

Occurred (UTC)

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

Created (UTC)

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

World seconds

74694750

Citizen

—

Related citizen

—

Building

farm-04

Intent

—

Decision

—

Tick

242399

Chain status

offchain

Integrity class

live

chogos-event-v1
id:7e57ecc1-96a3-4a50-8614-83cd44d31288
seq:805718
kind:production.batch_completed
category:resource
source:simulation
summary:Meadow Farm completed a simulated batch. 3 food went to the Storehouse.
occurredAt:2026-10-28T09:50:48.978Z
createdAt:2026-10-28T09:50:55.278Z
worldS:74694750
tickSeq:242399
actorCitizenId:
relatedCitizenId:
buildingId:farm-04
chainStatus:offchain
chainId:
txHash:
dedupeKey:sim:farm-04:batch:839
intentId:
decisionId:
payload:{"amount":3,"batch":839,"buildingName":"Meadow Farm","resource":"food","stock":400}
stateTransition:{}
prevEventHash:0xf0c2120eb6caba3448f7c9f66a86d7c934e3ae87b9f44e443fc4a7e6451211a8

Hashes

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

Stored event hash

0x2e6e9449…414fdb1a0x2e6e94499eb1e6741fc0700dcaa7b74e4ec398644f5dd45dda0508e7414fdb1aCopy

Full value

0x2e6e94499eb1e6741fc0700dcaa7b74e4ec398644f5dd45dda0508e7414fdb1a

Recomputed event hash

0x2e6e9449…414fdb1a0x2e6e94499eb1e6741fc0700dcaa7b74e4ec398644f5dd45dda0508e7414fdb1aCopy

Full value

0x2e6e94499eb1e6741fc0700dcaa7b74e4ec398644f5dd45dda0508e7414fdb1a

Previous event hash

0xf0c2120e…451211a80xf0c2120eb6caba3448f7c9f66a86d7c934e3ae87b9f44e443fc4a7e6451211a8Copy

Full value

0xf0c2120eb6caba3448f7c9f66a86d7c934e3ae87b9f44e443fc4a7e6451211a8

Next event hash

0xfb668e2f…fc3ecc250xfb668e2f836857864c4dc763d38a0108d8eecce571a09a6da61f7135fc3ecc25Copy

Full value

0xfb668e2f836857864c4dc763d38a0108d8eecce571a09a6da61f7135fc3ecc25

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.