What $MXMX actually does

The flow

The treasury has no withdraw, sweep or rescue function — there is no call that empties it. Its only outflows are basket buys and a capped top-up that keeps the keeper in gas: at most 10% of the balance at a time, and only up to a small target balance, with a hard ceiling of 10 ETH written into the contract as a constant. Those bounds cannot be raised by anyone.

What a trade costs

Where the penalty goes: not to the team. Within the decay window it is routed back to the token contract, which splits it between the reward pot and permanent liquidity — currently 60% rewards, 40% liquidity. Selling early deepens the pool and pays the people who stayed. That split is one of the owner-adjustable settings listed below; the two destinations are not.

Why it is charged in ETH: both charges come out of the ETH leaving the pool, never by taking your tokens on transfer. That keeps $MXMX a normal ERC-20 — routers, aggregators and bridges handle it without special cases, sending it wallet-to-wallet costs nothing, and no code path in the penalty can make a sell revert. It cannot honeypot.

Why it cannot be dodged: the penalty is keyed to the wallet that signed the transaction, and that wallet must hold at least as much $MXMX as it is selling or it pays the maximum. You cannot borrow an older wallet's clock by routing through it. The accepted cost of that choice is that flows where the signer is not the holder — UniswapX fillers, account-abstraction wallets — pay the maximum penalty on sells.

Your holding clock is balance-weighted, so topping up does not reset it. Adding 1% to a two-week-old bag barely moves it; doubling your position moves it roughly halfway back to today.

Your basket

The distributor keeps a registry of payout slots, and each holder chooses which of them they want to be paid in. Your choice is stored on chain as a bitmap — one bit per slot — so a whole basket is a single number. There is no lock-up and no fee to change it; your next payout uses your new picks.

If you never choose, you receive the default basket. A payout cycle's cost is roughly holders × tokens-picked, so defaulting everybody to all 21 would spend a full 21-token payout every cycle on people who never expressed a preference. The default is deliberately kept to a single token; anyone who wants the full spread only has to say so.

A slot is permanent. Once a token is added to the registry it can never be removed or swept, which is why adding one is a deliberate act rather than a form submission.

When you get paid

Payout cycles are run by an automated keeper. It checks the same conditions every time and either runs a cycle or waits. There is no human decision in the loop.

A cycle's gas cost is roughly linear in the number of holders, and it costs the same whether it moves $5 or $500. Paying out continuously would mean spending that cost over and over to deliver fractions of a cent. So the system waits until there is enough for the trip to be worth taking, then pays everybody at once.

The bar — highest of three floors

The first is a ratio, so it falls as gas gets cheaper — the right shape for “is this worth the gas”, the wrong shape for “is this worth doing at all”. On a chain this cheap the ratio alone would let a cycle fire to split a few dollars across hundreds of wallets. The flat reward floor is what prevents that.

• Fees below the bar are never lost. They sit in the treasury and keep accruing. A balance sitting still is fees building up, not money stuck.
• An in-flight cycle is always finished first, before anything else is considered.
• The keeper refuses to start a cycle it cannot finish, so a payout is never left half-delivered.

The Index League

You do not sign up. You enter by picking a basket and holding enough $MXMX — the election you already made is your entry. The question is simply whether your picks beat the index, which is the average of all the slots.

The record is a daily snapshot committed to a public repository. The league is scored from those files, so the history is a timestamped, public record that nobody edited a price after the fact.

What can change, and what cannot

The per-wallet cap is checked against the recipient's balance after a transfer, which is why sending a large amount to an address that already holds some can be refused even when neither side alone is over the line.

Addresses

The pool is a Uniswap v4 MXMX/ETH pool with a 1% LP fee and the hook attached. Every figure on this site — fees collected, tokens bought, holders paid — is read from these contracts and can be checked against them directly.