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 Mossy Woods completed a simulated batch. 18 wood went to the Storehouse.

Id

d82fbc0d-c…a558b418d82fbc0d-c2c4-4885-a110-dd30a558b418Copy

Full value

d82fbc0d-c2c4-4885-a110-dd30a558b418

Sequence

805065

Kind

production.batch_completed

Category

resource

Source

simulation

Occurred (UTC)

2026-10-28T09:24:53.478243+00:00

Created (UTC)

2026-10-28T09:24:56.476621+00:00

World seconds

74601420

Citizen

—

Related citizen

—

Building

mossy-woods

Intent

—

Decision

—

Tick

242094

Chain status

offchain

Integrity class

live

chogos-event-v1
id:d82fbc0d-c2c4-4885-a110-dd30a558b418
seq:805065
kind:production.batch_completed
category:resource
source:simulation
summary:Mossy Woods completed a simulated batch. 18 wood went to the Storehouse.
occurredAt:2026-10-28T09:24:53.478Z
createdAt:2026-10-28T09:24:56.476Z
worldS:74601420
tickSeq:242094
actorCitizenId:
relatedCitizenId:
buildingId:mossy-woods
chainStatus:offchain
chainId:
txHash:
dedupeKey:sim:mossy-woods:batch:3583
intentId:
decisionId:
payload:{"amount":18,"batch":3583,"buildingName":"Mossy Woods","resource":"wood","stock":19}
stateTransition:{}
prevEventHash:0x092d2dc8ec01635b41ad9c7fbf6a78306ab94ae836c01a6f04e1b4104d02d911

Hashes

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

Stored event hash

0x5ca702cb…2a8246be0x5ca702cb0a5f90ef4dabf3aa20c8f9688702da2854afe6e7be1b60c62a8246beCopy

Full value

0x5ca702cb0a5f90ef4dabf3aa20c8f9688702da2854afe6e7be1b60c62a8246be

Recomputed event hash

0x5ca702cb…2a8246be0x5ca702cb0a5f90ef4dabf3aa20c8f9688702da2854afe6e7be1b60c62a8246beCopy

Full value

0x5ca702cb0a5f90ef4dabf3aa20c8f9688702da2854afe6e7be1b60c62a8246be

Previous event hash

0x092d2dc8…4d02d9110x092d2dc8ec01635b41ad9c7fbf6a78306ab94ae836c01a6f04e1b4104d02d911Copy

Full value

0x092d2dc8ec01635b41ad9c7fbf6a78306ab94ae836c01a6f04e1b4104d02d911

Next event hash

0xe002e1ec…6a1f67b80xe002e1ec5a8e54592c10dfa30368c4c528f453370bb29414d5400e9a6a1f67b8Copy

Full value

0xe002e1ec5a8e54592c10dfa30368c4c528f453370bb29414d5400e9a6a1f67b8

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.