GBLIN Rebalance Leaderboard

The vault in service rebalances through a Dutch auction: when a row drifts past its band, anyone can trade with the vault toward the target weights at the oracle price adjusted by a premium that rises over an hour, up to 0.25%. The premium is the whole reward — nothing is paid out of the vault, and the bidder brings the tokens. The previous contracts worked differently: they paid an adaptive bounty from a buffer to whoever called their rebalance function, and that history is kept below with the bounty each address was actually paid, read from the Rebalanced event. Auction fills on the vault in service appear here too, read from AuctionFill, with no bounty column because none exists. Executors operated by the protocol are flagged; the list is published in the honest-counters promise, so the split between protocol activity and third-party activity can be reproduced from the chain.

Loading on-chain keeper activity...

The auction state — whether it is open, the current premium, and the side and gap of each row — is published at /api/cron/rebalance and readable on-chain through the GBLIN Lens. The figures on this page are read live from Base mainnet. The reward is the premium over the oracle price, applied to the amount that closes the gap.