Staking on Monad: the receipt, the queue, and the MON you cannot spend

MonadBFT is proof of stake, and the docs say delegation is allowed. That sentence is the whole of the consensus page’s interest in your deposit. Everything a retail screen calls staking is an application on top of that sentence. A validator set on the order of 200 operators, which the Foundation described in the September highlights, is the set a delegator is choosing among, directly or through a pool that chooses for them. Ledger, in that same note, ships MON staking inside the Ledger wallet. The existence of a button in a hardware wallet does not change the asset you receive. If the button gives you a receipt token, you hold the receipt. If it delegates and leaves a claim in a module you cannot transfer, you hold a claim. Neither one pays gas. The chain will still want native MON for the next transaction, including the transaction that asks to unstake.

What a receipt is

A liquid staking receipt is an ERC-20 whose issuer promises that burning it, or waiting and then claiming, returns MON, minus a fee, on a schedule. The number of tokens in your wallet often stays fixed while the MON they claim grows, or the number grows while each token stays one MON. Those are different accounting choices and they must not be mixed when you mark a balance. aprMON, sMON, and gMON are the three receipts the money page on this desk already refuses to call MON. They accrue. They are not a balance you can put on a swap path that asks for WMON. An agent that stakes and then trades the MON has, if it is lucky, staked and then failed the trade for lack of funds. If it is unlucky, it has approved a router for the receipt and sold the receipt thinking it was the coin. The receipt has a market price because someone makes a pool in it. That price is not one, except on the days the pool says it is. A discount to MON is the market’s opinion about the queue, the fee, and the time. It is not a rounding error.

Inclusion is not settlement

The request to unstake can be included in one slot. The MON comes back when the contract’s clock says so. That clock is often in rounds or in days, because the stake itself is committed on a schedule the consensus protocol cares about, not on the schedule of your card. An agent that books the MON as spendable at the moment the request is mined will try to swap a balance it does not have. The simulation reverts. If the agent then raises the gas or retries in a loop, it pays for the education in base fees and learns nothing, because the revert is not a gas problem. Read the claim function. Call it when the contract says the claim is ready. Until that call succeeds, the spendable balance is the native MON you did not stake, plus anything the claim just paid. The receipt is inventory of a different asset. Show it on a different row. The moment a screen adds the receipt’s mark to the native balance and calls the sum available to trade, the screen is lying in a way that will survive every test except a real swap.

The request lands in one slot. The MON comes back on the contract’s clock. The green digits are the receipt. They do not add to the red number.

Why the trade and the stake must not share a profit

A receipt that accrues looks like a gain. A swap that loses looks like a loss. Put them in one figure and a bad week of trading disappears into the staking yield, or a quiet week of staking gets blamed on the cards. This desk keeps them apart. The stake row is the receipts and the marks it has accrued. The trade row is the fills. The exit row is the profit the vault can actually return to the owner, which is MON above the gas float, not a receipt. An agent that withdraws a receipt to the owner has moved the claim. It has not paid the owner in gas money. An agent that tries to withdraw the receipt by calling the MON withdraw path will revert, if the contract was written by someone who had seen this mistake, or it will do something worse if it was not. The function name is the whole safety check. withdraw of MON and redeem of a receipt are different functions. A prompt that says withdraw when it means redeem is how the wrong one gets signed.

Names move

A token called aprMON can outlive the brand that launched the pool. Projects rename. They buy other projects. They keep the token address and change the word on the website. Before you delegate, read the current contract from the project’s own docs, then match it on the explorer, and do not trust a ticker you saved in July. The September highlights are a snapshot of products that existed in that month. They are not a registry. The registry that matters is the address your wallet will hold and the function that burns it back toward MON. If you cannot name both, you are not staking. You are clicking. If the docs and the token list disagree, stop and resolve the address before you fund it. A liquid staking token is not WMON, and the WMON contract will not unwrap it. Depositing a receipt into the WMON address is a donation.

What an agent should store

Store native MON separately from WMON separately from each receipt. Store the claim status as a fact you refresh, not as a boolean you set when the request mined. Keep enough native MON for gas outside the stake, or the unstake request itself cannot be sent. Do not let a model net the rows into one purchasing-power number and then size a trade from it. The trade size comes from the coin the pool will pull. On this desk that coin is MON, WMON, WETH, WBTC, or USDC, and a receipt is none of those. The stake can be a good idea. It is a different idea. The chain being fast changes how quickly you can request the exit. It does not change how the exit is defined.