Docs / Programs

Verify a cycle

How to check a published list against the chain, and what a check does and does not prove.

Revvy's committer key builds each list, so you do not have to take Revvy's word for it. Every list is published, and its hash is committed on chain. This page shows what you can check yourself.

What each cycle publishes

On the token page, under Past cycles, each cycle shows:

• Dividends: a link to the list with proofs, and a link to the commit transaction.
• Games: a link to the ticket list, the pot, and the winners with their amounts. The token page does not link a game's transactions, so you find them on Basescan, in the transaction list of the token's pool contract.

Level 1: look at the chain

Open the commit transaction on Basescan. It contains the hash of the published list file. For a game, also find the transaction that delivered the Chainlink VRF random number, and check that it came after the commitment.

Level 2: check the file

1. Download the list file from the token page. Keep it exactly as downloaded, in its compressed form (.gz).
2. Compute its Keccak-256 hash with any tool you trust.
3. Compare it with the hash in the commit transaction. They must match.

A match proves that the file you hold is the one Revvy committed.

Level 3: recompute the result

A full check recomputes the root, the winners and the amounts from the file and the balances. A tool that recomputes everything is not published. Until it is, levels 1 and 2 are the checks you can do yourself, and nobody outside Revvy can recompute the list.

What a check proves

Levels 1 and 2 prove the file matches what was committed. They do not prove that the balances behind the list were right. If Revvy's committer key were compromised or misused, a list could favour a wallet and still pass these checks. For that reason a new dividend list waits 12 hours before claims open: the time is there so that someone can read it and raise a problem. Trust and limits explains the rest.

Related: Programs, Claim a dividend.