3/ What we’ve built to support builders To help teams experiment with safer liquidity setups, we built RealSafe — the first lightweight LP locker on Monad that supports both V2 (ERC-20) and V3 (NFT-based) positions, with fee claiming on locked V3 positions. It’s live on Monad testnet right now. Come lock some test liquidity, try to break it, or just poke around and let us know what’s missing. → realsafe.app → docs.realsafe.app

2/ Why LP lockers matter in launches LP lockers were created to solve a simple problem: preventing liquidity from being pulled unexpectedly. • V2 LPs are fungible ERC-20 tokens, so you can lock any portion of them. • V3 LPs are NFT positions, so you lock the position as a whole. → With RealSafe you can still claim trading fees anytime while the V3 position is locked. By locking these tokens for a set duration, teams show that liquidity is committed, not temporary. This adds transparency for communities and structure for launchpads, DEX tools, and token deployers.

1/ What LP tokens actually represent Liquidity pool (LP) tokens are receipts that represent your share of a trading pool. When a project creates a pool, the LP token becomes the sole proof of ownership over that liquidity. This means whoever holds the LP token has the power to add, move, or remove the liquidity. Understanding LPs is key to understanding how security and trust work in early token launches.

The easiest way to kill a token is to pull the liquidity. The easiest way to prove you won’t is to lock it. We just shipped the first LP locker on Monad that works with both Uniswap V2 and V3 (including fee claiming on V3 while locked). Testnet is live → realsafe.app 🧵👇