volume from chain · fees are ours · block 49,057,683

Leaderboards

Referred trading volume is read from the chain, but the payout rate is set by us and accounted off chain — so this is the one board that will not reconcile against a contract. Every other board here is derived from the chain’s own events and can be recomputed by anyone from the same events.

your standing

—not signed in

7d 30d all

The Dark holds the vault, 2–0

standing · as of block 49,057,683 · launches all time

Both crews rob the same Sheriff and differ only in method, so the count is which method the greenwood is choosing — a force is chosen once at launch, is permanent, and changes no fee, cap, curve or payout.

The Lightrobs in daylight, gives in the square

launched: 0
graduated: 0
traded: 0 ETH

leading projectno launch on this side yet
leading creatornobody launches mostly this side yet

The Darktakes the vault, splits with the crew

launched: 2
graduated: 2
traded

leading projectDonation Proofgraduated · traded
leading creator0xDd0a…2C53#1 on Creators · 2 of 2 graduated (100%)

#1leading
The Hood Executor0xDd0a…2C53
fees earned0 ETH
0 of 1 wallets have traded

our numbersThe volume behind these fees is read from the chain. The share paid on it is a rate we set and settle off chain — no contract pays it and no event records it, so this board’s fee column will not reconcile against the chain.

Referrers ranked by referral fees generated by wallets they referred. The volume behind the fees is read from the chain; the share paid on it is a rate we set and settle off chain, so this board's fee column will not reconcile against any contract.
rank	referrer	wallets	rate	fees earned	referred	badges
01	The Hood Executor0xDd0a…2C53 — view referrer address 0xDd0aF241Cd5F885e227DE30eCB6b6F2323db2C53 on the block explorer (opens in a new tab)	0 of 1 traded	10% of the treasury share	0 ETH	1	none yet

1–1 of 1 referrers · all time

Every figure on this page comes from the site’s own index of chain events, as of block 49,057,683 — 30 blocks behind the chain head at the last run, updated 3 minutes ago. It is not a live chain read, so it can disagree with one by that lag; anyone can recompute it from the events themselves.