Sample proof. Meridian Coffee 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.
Meridian Coffee (fictional) · activation · 2026-06-08 → 2026-06-14
Neighborhood cupping week
A week of open cupping sessions with a tab-covered giveaway pool, run by the brand's agency across five neighborhood locations. This is a fictional sample event with illustrative numbers — no real campaign has run on HemiAI yet.
Disclosure: the brand made 4 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
Private
0xb46782deaa7d86acd3b55a708b674a867335b295cd321bb3df2461a9e9d55264The brand chose to keep this number private. It is still committed under the same root — if the brand reveals it later, the reveal is checkable against this exact leaf.
Actually given away
$10,165
0x1b88ac1bc173681bc4e89256a9a525f4f2a7aa55c9aaee5fa8726f0e2b949cc0Published opening: value 1,016,500 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
People who received
903
0x9824c73e8beb0a867164b241d9e497a651de17734e05ca36539e36b0e76213e0Published opening: value 903 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
Participants
2,240
0x46f5226ab7b6270add2ef94f4e2a342e4e43600e78bb5623bb688f23c0d21977Published opening: value 2,240 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
Engagements counted
Private
0x79a0e289dd0a0ae82244cf2c3a1783b4eda91ee6a1d8778a97d0a00692bbb066The brand chose to keep this number private. It is still committed under the same root — if the brand reveals it later, the reveal is checkable against this exact leaf.
Positive reactions
1,930
0x8c2f3a9c41c8621d22a92be1963215e86d745146471d8fa59f945980e24131dcPublished opening: value 1,930 + salt, with a 3-step branch to the event root. Anyone can recompute this leaf and walk the branch.
The on-chain anchor
0xd68b914b1bd9d564298c7ab267f60ff9609f2e26a2ca1d48338c925fa0ec1cbc0xab9c7541750270a83c12bdf66fad477a8ef2419f8350f6c1876452c3a504abdb0x3cab63aa5d74eb5f45c813e06b69dc3c2a11f3c929846d9ee2eaeb168d16c815Not 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.