Sample proof. Aurora Trail Co. is a fictional brand and every number below is illustrative. No real campaign has run on HemiAI yet — this page exists to show exactly how a real event's proof will look and verify.
Aurora Trail Co. (fictional) · giveaway · 2026-05-16 → 2026-05-17
City Trail Weekend giveaway
A two-day city trail event with gear giveaways at every checkpoint, executed end-to-end by the brand's agency. This is a fictional sample event with illustrative numbers — no real campaign has run on HemiAI yet.
Disclosure: the brand made 6 of 6 numbers public. Every number — public or private — is committed under one root; disclosure only controls whether you see the value or just its commitment.
Pool committed
$25,000
0x423c40b865c8e479e3be2093b3501e9c6746c1a706b62ad63c409402cba8ef34Published opening: value 2,500,000 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
Actually given away
$23,840
0x129c598528dc0cc8a7e65abfc1bb9fa6edc79f44b1333a5e91205d8c340bb1c0Published opening: value 2,384,000 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
People who received
412
0xf962d458d7648ff1e1a6b5a07968370b5f12cb25f72dd3a83023a0dd5727f0dbPublished opening: value 412 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
Participants
1,870
0xa08c3e8e7a6301f87e9312f34703c82c4580e62eb282b90be476769216d1cc0aPublished opening: value 1,870 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
Engagements counted
9,640
0xa6fdbd66e8ca05ff198bbc57a990da6925be164d10516ac66769604e773da33fPublished opening: value 9,640 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
Positive reactions
1,495
0x22dd04b8f3c85c93eb04001bad3eaff74444a48a8394dde5d0cf8f94b1b96742Published opening: value 1,495 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
The on-chain anchor
0xcf6de568f72f4b99efba1f47078b9cac744dd14a50de27eea8fafc78342ef4070xab9c7541750270a83c12bdf66fad477a8ef2419f8350f6c1876452c3a504abdb0x6ea7654e30078568c699bb09b0e17a679ddee8bc272bdf0c7ef5c421297c8443Not on a chain yet — honestly. HemiAI is pre-launch: this root is computed locally on every render, and the write to the anchor registry is not live in this build. When it ships, the root above is written to an append-only registry on a public testnet, and this panel links the transaction. Until then, nothing on this page claims otherwise.
Giveaway settlement rail: dormant. HemiAI will settle giveaway payouts as its own merchant on the shared Access0x1 router (0xe92244e3…3a475EB5, testnets only), so each payout becomes a publicly checkable event under HemiAI's merchant id. That registration has not happened yet — no money moves through HemiAI today.
How anyone verifies this
- Each number is committed as
keccak256(canonical({eventId, field, salt, value})). The salt blinds private fields so a count can't be guessed from its hash. - The six leaves build one Merkle root (sorted-pair hashing, OpenZeppelin-proof compatible). That root is the single value destined for the on-chain registry.
- For every public number, this page publishes the opening — value, salt, and branch — and checks it against the root. You can rerun that check with any keccak256 implementation.
- Once the anchor write ships, step 3 checks against the root read from a public testnet explorer instead of this page — the brand can't restate a number after the fact, and neither can we.