Compound leaderboard
Any vault depositor can call compound() and earn the 0.9% caller bounty. This page reads on-chain logs directly — no backend, no API.
Why This Matters
Compounding happens whenever any address calls compound(). The bounty exists so upkeep does not depend on a single operator. The leaderboard shows which addresses have called it and how often.
The bounty curve — 0.9% of vault-wide pending rewards — means the longer the protocol goes uncompounded, the larger the next caller's reward. Callers are funded from vault rewards according to the contract rules; the protocol pays for its own upkeep.
Total compounds
—
Total bounty paid
—
Unique callers
—
Avg bounty per compound
—
Days since last compound
—
All-time bounty distributed
—
Look up an address
All callers
Sort:
| # | Caller | Compounds | Bounty earned | |
|---|---|---|---|---|
| Scanning on-chain history… | ||||
How this works
- compound() is permissionless. Any vault depositor (anyone with a non-zero vault-token balance) can call it. There is no admin caller; there is no whitelist.
- The bounty is 0.9% of the vault's entire harvested rewards — flat, not weighted by the caller's vault-token balance. Any depositor who calls
compound()in a given cycle receives the same bounty for that cycle, regardless of stake size. First caller per cycle wins it. - The longer no one calls, the larger the bounty grows. The protocol pays for its own resilience. First caller per cycle wins it.
- Read directly from the chain. This page scans
Compoundedevents from the v4.6 vault contract via public Harmony RPC. The caller distribution above is the on-chain receipt of who is actually winning bounties.