How to Lock Liquidity on Monad

Monad is a treasury chain. The projects locking anything here run funded protocols with investors, auditors and counterparties who read unlock schedules — and for a large share of them, the liquidity question is already settled before they arrive. This page sorts out which situation you are in before it tells you what to do about it.

What does locking liquidity on Monad prove to a buyer?

Locking liquidity on Monad means depositing your LP tokens into a time-locked vault that nobody — including you — can withdraw from before a date fixed at the moment of the lock. The pool keeps trading. Fees keep accruing. What the lock removes is one specific power: the ability of whoever controls the position to withdraw the liquidity and leave holders with a market they cannot exit at any reasonable price.

That is a narrow claim, and the narrowness is the point. A liquidity lock does not prove the token supply is sound, the team allocation is disciplined, the mint authority is renounced, or the treasury is honestly managed. It proves one thing about one position for one defined period, and it proves it to anyone with a block explorer rather than to anyone willing to take your word. On Monad the proof is legible two ways — the position sits visibly in the locker contract on MonadVision, and each lock issues an on-chain certificate that travels with the claim. If your counterparty is an exchange listing desk, a fund conducting diligence, or a DAO reviewing a grant, that second-source verifiability is what they are buying, not the lock itself. How to verify a lock on Monad covers what they will actually check.

Do you hold LP tokens on Monad at all?

Many Monad teams hold no LP tokens whatsoever, and the answer depends entirely on how the pool came into existence. This is the fork that defines liquidity locking on this chain, and getting it wrong wastes weeks.

If you launched through nad.fun, the protocol already locked the liquidity and you hold nothing to lock. At graduation, in nad.fun’s own words, “the remaining token supply and gathered funds are moved to an internal DEX liquidity pool” — and the protocol-provided liquidity is locked through its LP tokens. nad.fun states the mechanism plainly: “The initial protocol-provided liquidity is locked through its LP tokens, and the LP fees earned by this locked liquidity stay in the pool and help deepen liquidity over time.” Under the legacy V1 arrangement creators received “50% of the remaining LP fees” — fees only, never the LP tokens themselves. There is no step you can take to lock that position, because it was never yours. Anyone advising a nad.fun graduate to go and lock their LP has not read the documentation. What genuinely remains open for a graduate is everything the bonding curve never touched, and after nad.fun graduation: what’s already locked and what isn’t walks through exactly where the gaps sit.

If you created a pool yourself on an AMM, you hold LP tokens and the lock is a live decision. Seeding a pair directly — because you raised outside the bonding curve, because you are adding a second venue, because you migrated an existing token to Monad — puts fungible LP tokens in your wallet, and nothing about them is constrained until you constrain it. That is the case how to lock LP tokens on Monad is written for, and it is the only case in which the phrase lock your liquidity means what people assume it means.

Why does Kuru’s dominance not change the answer?

Kuru carries roughly 71.7% of Monad DEX volume as of September 2026 — $98.16M in 24 hours — but it is a central-limit orderbook, not an AMM, so market-making there does not produce LP tokens and there is nothing to lock. This distinction is not pedantry. On an AMM, depositing into a pool mints a fungible claim on that pool, and that claim is the object a locker holds. On an orderbook, you post bids and offers you can cancel at any moment; there is no pooled position, no receipt token, and no mechanism by which a third party could observe that your quotes are committed. A market maker on Kuru can stand down between blocks and no lock in the world would prevent it.

The practical consequence is that Monad’s liquidity-locking surface is much smaller than its DEX volume suggests. Uniswap is the largest AMM on the chain at roughly 10.5% of volume — $14.34M in 24 hours as of September 2026 — followed by Metric at 5.6%, Hanji at 4.6% and Balancer at 3.2%. The top five venues together account for around 96% of volume. When you are sizing what a liquidity lock will actually signal to the market, measure it against the AMM slice, not against the headline number.

Why do Monad teams lock allocations more often than LP?

Because Monad’s activity is institutional, and institutional capital asks about cap tables before it asks about pools. Total value locked on the chain stands at $957.23M as of September 2026, concentrated in Aave V3 ($320.94M), K3 Capital ($310.9M), Euler V2 ($241.67M), Pendle ($221.76M) and Morpho Blue ($172.96M) — lending, yield and structured-credit venues, not launch infrastructure. Against that, nad.fun holds $411,668 of TVL as of September 2026 and its revenue has fallen 84% from its Q4 2025 peak of $958.2K to $150.25K in Q3 2026. Monad went live on mainnet on November 24, 2025, and nine months in, the money is in treasuries.

For most teams shipping here, the credible-commitment problem is not will you pull the pool but what happens to the team allocation, the advisor grants and the treasury over the next three years. Those are the positions a fund models, and they are the positions that are almost always still unlocked when someone asks. Team token locks on Monad covers the single-date commitment; how to set up token vesting on Monad and vesting schedules for Monad projects cover the case where tokens are earned over time rather than released in one event — which is what a hire, an advisor or a staged investor tranche actually requires. If you have limited attention and one thing to lock, on this chain it is more often the allocation than the pool.

What does the lock process involve, and what does a third party see afterwards?

The process is four stages, and only one of them happens on-chain. Team Finance locks liquidity on Monad at app.team.finance on the same terms as every other supported chain.

1. Establish what you actually hold. Confirm whether you hold fungible LP tokens from a pool you seeded yourself, or whether your liquidity was placed and locked by a launch protocol on your behalf — the second case has no lock to perform.
2. Decide coverage and duration. Choose how much of the project-held position goes into the lock and what date it opens, and expect to defend both numbers in a diligence conversation rather than a community announcement.
3. Execute the lock and pay the fee. The position moves into the locker contract, the unlock date is written on-chain, and the fee is charged in MON — after which no party, including Team Finance, can shorten or reverse the lock.
4. Publish the proof. Put the lock record, the explorer view of the locker contract and the on-chain certificate into your documentation and your data room, so that anyone verifying the claim reaches the same conclusion without asking you.

What a third party sees afterwards is a position held by a contract they can inspect, an unlock timestamp they can read, and a certificate they can trace — three independent confirmations of the same fact, none of which requires trusting a screenshot. That is the whole product. The rest is duration.

How long should you lock, and what do you give up?

Lock for at least twelve months if the lock is doing diligence work, and understand that the cost of a long lock is optionality you may later want. A lock is a one-way commitment by design: you cannot shorten it, and neither can we. If you lock a position for three years and then need to migrate the pair to a different venue, restructure the pool, or respond to a token upgrade, the locked portion is unavailable for that entire period. Teams that discover this in month eight tend to have locked reflexively rather than deliberately.

The way through is coverage rather than duration extremism. Lock substantially all of the project-held position for a defensible term, keep the term long enough that it clears the horizon your counterparties care about, and split the position into tranches with separate unlock dates where you genuinely need staged flexibility. Locks support splitting and ownership transfer, both recorded on-chain — which matters on a multi-year protocol where treasury custody changes hands at least once. A twelve-month lock you can explain beats a five-year lock you will quietly regret, and a partial lock disclosed accurately beats a full lock described vaguely.

What does a liquidity lock cost on Monad?

A liquidity lock costs $150 on Monad as of September 2026, fixed in USD and charged in MON, with no percentage of the locked position taken. Token and team locks are priced the same; vesting is $100. The flat structure is the part worth checking against alternatives, because percentage-based lockers are cheap on a $20,000 pool and expensive on a $2M one — at 1%, a $2M position costs $20,000 to lock, against $150 here, and any model that also takes a share of collected fees keeps charging for the life of the lock. At the position sizes Monad treasuries actually run, that arithmetic is not close.

FAQ

Can I lock my nad.fun liquidity? No — nad.fun locks the protocol-provided liquidity through its LP tokens at graduation, so a graduate never holds the LP tokens and has nothing to lock. What remains open is the team allocation, treasury and advisor grants.

Can I lock liquidity on Kuru? No. Kuru is a central-limit orderbook rather than an AMM, so providing liquidity there does not mint LP tokens and there is no position for a locker to hold.

What does a liquidity lock cost on Monad? A liquidity lock costs $150 on Monad as of September 2026, fixed in USD and charged in MON, with no percentage of the locked position taken.

Can I withdraw early? No. A lock cannot be withdrawn, shortened or overridden before the unlock date by anyone, including Team Finance.

Should I lock liquidity or the team allocation first? On Monad the team allocation is more often the open question, because the chain’s activity is concentrated in lending and yield protocols whose counterparties assess cap tables rather than pool depth. Lock whichever position a diligence reader would ask about first.

Next steps: what nad.fun already locked · lock LP tokens you hold · lock the team allocation · back to the Monad hub