Where the money goes and what the team can change

Every flow of $CARDS and ETH, and the short list of things the owner can touch, all behind a 48-hour timelock.

The $CARDS you spend is burned. The ETH you spend goes to the treasury. The veins are fed by the keeper bot, which forwards the Pons creator fee on $CARDS trades into them on a schedule, and by anyone else who sends ETH. The only way ETH leaves the mine is a claim, and it leaves as tokenised stock. The team can rotate the keeper, the router, the stock addresses and the metadata base, each after 48 hours in public. It cannot touch prices, supply, emission, cost, or your bond.

Where the money goes #

At sellout the mint burns 146,464,700 $CARDS, 14.65% of the 1 B supply, and sends 4.032 ETH, $10,080 nominal, to the treasury. Both figures are derived from the price table.

How the veins are fed Nothing on-chain moves mint ETH or royalties from the treasury into the veins, and there is no fixed ratio in the code. What feeds them is the Pons creator fee on $CARDS trades: the keeper bot receives it and forwards it into the three veins on a schedule, through fundPool. Anyone can top a vein up the same way.

$CARDS itself is a Pons launcher token with a fixed 1 B supply. The contracts only require that it can be burned. The 5% creator fee on $CARDS trades is a Pons setting, outside these contracts; it is what the keeper bot forwards into the veins.

What the team can change #

Every proposal is a public transaction with an ETA and can be cancelled. Nothing applies early.

What the team cannot change #

• The price table, supply, tranche geometry, wallet limits, MINT_START, REVEAL_DEADLINE, the seed commitment and the royalty are constants or immutables with no setter.
• EMISSION_DIVISOR 28, BURN_TARGET_BPS 1500, STALE_AFTER 2 h, PRICE_BAND_BPS 2000, MAX_DECK_CARDS 128, CYCLE_SECONDS, the required-bond estimate and the weight and set-bonus math have no setter.
• No function withdraws vein ETH or bonded $CARDS to the owner. No function mints extra cards, alters traits, or locks and unlocks cards by hand.
• MinersNFT has no pause and no upgrade path. Minting and merging cannot be stopped.

Pause, exactly #

A pause freezes bindDeck, buyShifts, unbindDeck, roll and rollStale. claim and fundPool keep working. It is a brake on new activity, not on your money.

What you still trust #

• The keeper posts the $CARDS price each roll, within 20% of the last one, and runs the schedule that forwards the Pons creator fee into the veins. A wrong keeper can be rotated after 48 h, rollStale lets anyone advance the mine after 2 h of silence, and if the bot stops forwarding, anyone can fund a vein.
• The router and the three stock addresses, because every claim goes through them. minStockOuts is your floor per vein, and a bad router can be rotated after 48 h.
• The seed. Its sha256 hash has been on-chain since deploy; the seed itself is disclosed at reveal.

The audit at docs/AUDIT.md recorded three code findings, B1 keeper-only roll, B2 the reveal gate and B6 ERC-4906. All three are fixed in the deployed code. B3, seed entropy, and B7, the ETH rate refresh, are steps taken before mainnet.

Not in the game #

• "70% of every fee flows back to the vault". No split exists in code. The keeper bot forwards the Pons creator fee into the veins on a schedule, not by a percentage written in the contract.
• "Pause halts claim and merge". Claim runs under pause; merge lives in a contract with no pause.

Next #

Reference for every constant, address and revert.