Period reports

Every cycle arCCade settles is committed to a daily Merkle root written on Canton in a VenuePeriodAnchor. The root alone says “these cycles and no others”; this page is the data it commits to, and it re-verifies that data in your browser rather than asking you to take our word for it.

Period

Checks

Cycles

cycle	disposition	staked	fee	returned	leaf

What this proves, and what it does not

A row that verifies is one this report commits to and the ledger's anchor commits to in turn. Because the root covers the whole period, a cycle you can see on Canton but cannot find here is demonstrably omitted — that is the only claim an anchor is designed to support.

It does not prove the amounts are honest. That comes from the other direction: each row's custodyTag and committedUnits are checkable against the DSO-signed LockedAmulet on the ledger, which arCCade does not sign alone. Nor does this page prove the anchor exists — it reads what we serve. The contract id below is there so you can look it up yourself.

Verify it without this page

Fetch the report JSON. Its sha256 is the anchor's reportDigest.
Render any row as a canonical document (arccade-sdk-digest-v1, schema arccade.cycle-audit-row, fields sorted by name) and take its sha256 — that is the leaf.
Combine leaves pairwise with the arccade.merkle-node schema, promoting a lone node rather than duplicating it, up to the root.
Compare that root with merkleRootHex on the VenuePeriodAnchor contract.

Reference implementations in Daml, JavaScript, Python and Java are in the SDK, all pinned to the same fixtures.