Rewards

AntSeed's on-chain rewards engine: epoch points, the 5.00M ANTS each epoch schedules and its 40/20/15/15/10 split (seller pools/usage/team/reserve/verification), locked seller rewards and the legacy USDC stake. The staking market itself is on the Staking page →, and the DIEM provider-capacity pool, on its own reward-epoch clock, on the DIEM page →

From epoch 22 the emission stopped being a fixed split. Team, reserve and verification are fixed; the seller-pool and usage buckets scale from a floor up to their ceiling with how close the network gets to two targets. Whatever no bucket claims is burned, up to 30% of the epoch, rest to reserve.

Nothing has minted for epoch 23 yet. The gate refuses any claim while the epoch is still running, so epoch 23 only becomes claimable once epoch 24 starts. The 1.50M ANTS above is what would be burned if the leftover were settled at today's figures, and the burn is not automatic either: someone has to call settleEpochRemainder on each reward controller. That call is permissionless, so anyone can make it, but if nobody does, nothing is burned and the leftover simply stays unminted. Across the epochs already settled, 1.50M ANTS has actually been burned (1.50M ANTS for epoch 22). Note that burning mints to a dead address rather than reducing supply, so it never lowers totalSupply().

The largest bucket of the epoch emission is paid out by stake behind provider pools. This is the per-seller cut of it: who holds a pool, and how much of the traffic is served by sellers who do not. The pools and positions themselves are on the Staking page →

The bucket's share rises with active stake on a saturating curve: 400.00M ANTS staked would take it to the halfway point of its 2–40% range (21%), and the ceiling is approached but never reached outright. In epoch 23 the only active stake is the one-per-seller seed of 1 ANTS, and those 26.00 ANTS are what keep the bucket at its 2% floor rather than at zero; positions created since activate in epoch 24. The 1.90M ANTS between this epoch's budget and the ceiling stays unallocated: burned at settlement up to the epoch cap, the rest minted to the reserve. No seller without a pool accrued points in our index this epoch. Sellers proven to be wash trading on-chain are held out of the count above, since their zero is the wash policy rather than the pool gap. A position activates one epoch after it is created, so stake already committed for epoch 24 is not counted above: the Staking page carries it, and its totals are larger for that reason.

A different system from the $ANTS provider pools, and the numbers are not comparable. This is the older bond a seller posts in USDC on its own behalf, and it can be slashed; the pools are $ANTS locked for a chosen number of epochs, by anyone, into any seller's pool. A seller can hold both, one, or neither.

Points are an on-chain fact (EmissionsV2 BuyerPointsAccrued / SellerPointsAccrued, 1:1 buyer↔seller). Rewards = points × epoch budget ÷ total points, read directly from the contract; seller rewards mint to a locked pool that needs two on-chain conditions to release, not one: sellerClaimPolicy installed (the card above reads it live), and the pool allowed to move $ANTS at all — either transfers open to everyone, or the pool on the token's transfer whitelist. Locked total ties out exactly to totalLockedRewards(). No $ANTS market price exists yet (transfers gated).