MULTIPOOLS V2 IS OPEN. $MOOLS HAS ARRIVED.
You can now launch tokens natively across Ethereum, Base, and Robinhood Chain with a single launch.
Alongside V2, we’re launching $MOOLS the native token of the MultiPools Ecosytem.
We’re launching $MOOLS to create a shared economic layer around MultiPools aligning users, creators, and liquidity as the protocol grows across chains. As MultiPools expands, $MOOLS will play a growing role across the ecosystem through incentives, liquidity, governance, and future protocol utilities.
Launch → https://t.co/Z7o3pHATwG
Contract: 0xffdf46706c5fc8e808b9132a7ae368e31d514f82
A new way to launch tokens. Multichain from day one.
Here is exactly what happens, step by step:
Step 1. Creator calls launch() on any supported chain. That is the only action they take. No second transaction, no approval, nothing else.
Step 2. The factory deploys the token using CREATE2 with a deterministic salt derived from the creator address, name, symbol, and a mined nonce. This means the token address is the same on all three chains before anyone bridges a single token. The supply is fixed at deployment. There is no mint function available after this point. No one can create more tokens.
Step 3. A Uniswap v4 pool is initialized on the source chain and liquidity is seeded into it. The LP position is locked permanently by the hook contract. No one can remove that liquidity, not the creator, not the team, not anyone.
Step 4. A LayerZero V2 message is sent to each remote chain. Our custom DVN picks it up, signs the packet, and calls commitVerification() in one atomic transaction. Our custom executor then calls lzReceive() on the destination, which repeats steps 2 and 3 automatically with the same parameters.
Step 5. The token is now live on all three chains with real AMM liquidity and open trading. All subsequent swaps happen through Uniswap v4 directly. Pricing is fully market driven. The protocol charges a 1% swap fee: 70% goes to the token creator, 30% to the platform.
When you bridge a token, the OFT contract burns your tokens on the source chain and mints the equivalent amount on the destination chain. The total supply across all chains stays constant at all times. This is standard LayerZero OFT mechanics, auditable in the open source contracts.
No one can print new tokens. No one can pull the liquidity. The contracts enforce this.
Contracts and DVN are open source. https://t.co/jVZwRepkLe
285 cross-chain transfers in 24 hours. 197 delivered. 3 pending. @layerzero_core
Every one of those transfers is a real token launch or a holder bridge on MultiPools. When a creator launches a token, it does not go live on one chain and migrate later. It goes live on Ethereum, Base, and Robinhood Chain simultaneously, at the same contract address, with liquidity seeded and trading open on all three chains from the first block.
LayerZero V2 is what makes that possible. A message leaves the source chain carrying the full token and pool configuration. Our custom DVN verifies it, our custom executor delivers it, and the remote chain deploys and seeds the pool without any manual step from the creator. Every launched token is also a native OFT, so holders bridge freely across all three chains through the same layer.
Contracts and DVN are open source. https://t.co/jVZwRepkLe
Alot of people ask why the market cap number for $MOOLS looks different depending on where you check it. The reason is that MOOLS exists on three chains at the same time: Ethereum, Base, and Robinhood Chain. Most trackers only see one chain at a time, so they only count the tokens sitting on that chain and miss everything else. That gives you a partial number, not the real one.
The correct way to calculate market cap is simple. You take the total number of MOOLS tokens in existence across all three chains and multiply by the current price. There is a fixed supply of 69 billion MOOLS total. That number never changes.
Right now the math looks like this.
Total supply: 69,000,000,000 MOOLS Current price: $0.00000089 Global market cap: $61,300
69,000,000,000 x $0.00000089 = $61,300.
That is the real number. Not the ETH slice. Not the Base slice. The whole thing.
Every token launched on MultiPools follows the same fixed supply model: 69 billion tokens split across all chains at launch. So every token page on our platform now shows the correct global market cap calculated this way, updated in real time as the price moves.
You can see it live on the MOOLS token page right now.
https://t.co/zYocmU3KCE
Understanding $MOOLS price, market cap, and cross-chain supply
A few questions keep coming up, so here is breakdown.
"The market cap is huge, why does the price still drop?"
Market cap is not a price floor. It is simply price multiplied by total supply. When price drops, market cap drops by the same percentage. They always move together. A high market cap does not protect or guarantee a price level, it is just a measurement derived from price.
"Does bridging tokens to another chain increase the supply and push price down?"
No. The total supply of $MOOLS is fixed across all three chains combined. Bridging does not create new tokens. What actually happens: tokens are locked on the source chain and released on the destination chain. The global number never changes.
However, if someone bridges a large amount of tokens to Robinhood Chain and immediately sells them, the local liquidity pool on that chain receives more tokens at once. This temporarily pushes the price down on that chain.
This is where MultiPools cross-chain arbitrage system comes in. The arb bot detects the price gap, buys the cheaper tokens on the affected chain, and sells on the chain where price is higher. This rebalances prices across all three chains within minutes.
What actually moves the price
Selling pressure in a pool → price drops
Buying pressure in a pool → price rises
Thin liquidity → larger price impact per trade
Cross-chain arb → prices converge across chains
Supply does not change.
Total market cap reflects the global price at any moment. Price volatility on one chain is usually a temporary imbalance being corrected, not a sign of something being wrong with the token.
We submitted MultiPools to the @LayerZero_Core ecosystem program today.
MultiPools is a token launchpad built on Uniswap v4 hooks @Uniswap . Every token launched through the protocol deploys natively across @ethereum , @base , and @RobinhoodCrypto in a single transaction, with liquidity seeded on all three chains simultaneously.
LayerZero V2 is core infrastructure, not a wrapper. We run our own DVN, executor, and cross-chain arbitrage system to keep prices consistent across chains. OFT handles token supply, total supply is fixed globally, distributed across chains.
Why the opportunity only grows
Every new token that launches on MultiPools creates three new liquidity pools across three chains, which means more price discrepancy for the bot to find and capture. As the protocol gets more activity, arb opportunities compound.
More launches. More profit. More rewards for $MOOLS holders. The flywheel runs itself.
(4/4)
ARBITRAGE ON MULTIPOOLS · COMING SOON
MultiPools runs across three chains at once. Every token launched here lives on Ethereum, Base, and Robinhood Chain simultaneously. Three separate markets, one token, prices moving independently based on who is buying and selling where.
That gap between chains is not a bug. It is an opportunity. And the MultiPools arb bot is built to capture it.
(1/4)
What this means for $MOOLS holders
A portion of every arb profit is distributed to holders. The requirement is simple: hold a minimum of 69 million $MOOLS. That is your position. Hold it, and you earn from every cycle the bot runs.
The more you hold, the larger your share. No staking.
(3/4)
Platform Status Update. All Systems Operational.
We want to give our community full transparency on a security event that occurred recently and the steps we have taken to resolve it.
What happened
One of our platform wallet keys was compromised. Out of an abundance of caution, we immediately rotated the affected wallet to a new secure address and updated all protocol configurations accordingly. No user funds were at risk at any point the FeeVault contract stores each creator's claimable fees independently and was unaffected. All previously accumulated creator fees remain intact and claimable.
What we fixed
Platform wallet rotated to a new secure address across all three chains (Ethereum, Base, Robinhood Chain)
Hook initialization parameters recomputed and updated to reflect the new platform configuration
All keeper infrastructure restarted and verified against the new configuration
Old wallet's claim rights on the FeeVault are preserved all pending creator fees are safe
Current status
Token launches are fully operational again. The LaunchPad is open.
We appreciate the patience of everyone who noticed the downtime. Security is our top priority, and we acted quickly to contain and resolve the situation.
If you have any questions, reach out to us directly.
Security Disclosure
MultiPools runs on fully on-chain, immutable smart contracts. User funds, token contracts, and all protocol logic are secured by the blockchain itself and cannot be touched by anyone, including us. This disclosure is about an internal tooling credential, not the protocol.
(1/4)
MultiPools Contract Safety Addressing the "Unsafe" Flags
Automated security scanners flagging MultiPools tokens as "Unsafe" is a known false positive caused by these tools being built for Uniswap v2/v3 architecture. Here is a factual breakdown of each warning.
TradeRestriction HIGH
This flag is triggered by the presence of antisniperEnabled and maxWalletEnabled parameters in the hook contract. What the scanner cannot detect is that these restrictions are hardcoded to expire after exactly 60 seconds from launch (LAUNCH_WINDOW = 60 in MultiPoolsHook.sol). After that window, the hook is permanently locked via lockForever() called by the factory. The factory address is stored as an immutable in the hook constructor and is the only address authorized to call this function. Once locked, no wallet limit or trade restriction of any kind can ever be re-activated. The owner cannot extend anything.
Burnt/Locked LP less than 80% HIGH
This is a direct consequence of Uniswap v4 architecture. In v4, liquidity does not produce ERC-20 LP tokens. There is nothing to burn. Security scanners check for burnt LP tokens because that is how v2/v3 rugs are prevented. In v4, that model does not exist. Instead, our hook contract implements beforeRemoveLiquidity which unconditionally reverts with "MultiPools: LP locked forever". Liquidity cannot be removed by anyone, ever, including the deployer. The liquidity lives inside the Uniswap v4 PoolManager at https://t.co/97TXxoTgWg on RobinhoodChain and is not accessible to any EOA.
Hook Risk MEDIUM
Yes, this token uses a Uniswap v4 hook. Every MultiPools token does. The hook is deployed at a deterministic CREATE2 address by the MultiPools Factory at https://t.co/OXUXSTFHos and its source code is verifiable on-chain. After the 60-second antisniper window expires, the hook's only active function is collecting the fixed 1% swap fee and routing it to the creator, platform, buyback, and rewards allocations, all set immutably at launch. The hook cannot restrict or block any trade after it is locked.
The "Unsafe" label is a scanner limitation, not a reflection of actual contract behavior. Every flag shown maps to a safety mechanism that either has already expired or is enforced by an on-chain revert that nobody can bypass.
Transparency Update: LayerZero DVN & Pending Messages #LayerZero
There are currently 17 cross-chain messages in pending status on the LayerZero network. This is expected behavior and every single one will resolve automatically.
What is a DVN?
A DVN (Decentralized Verifier Network) is the security verification layer inside the LayerZero protocol. Every time a token is launched on MultiPools and needs to be propagated to another chain (Ethereum to Base, RobinhoodChain to Ethereum, etc.), the message must be verified by a DVN before it can be executed on the destination chain. MultiPools operates its own custom DVN rather than relying entirely on third-party verifiers, meaning the verification infrastructure is under full team control.
Why pending?
Each token launch generates at least two cross-chain messages, one per destination chain. With recent launch activity, our DVN worker is currently processing 17 messages across six separate routes (ETH↔️Base, ETH↔️RBH, Base↔️RBH) simultaneously. The worker processes these in sequence and every message is guaranteed delivery. Nothing is lost.
Contracts you can verify on-chain
MultiPoolsDVN (our verifier) is deployed at 0x5C9e2fBE672D29562A955B7B7cb11c804f460000 on Ethereum, the same address on Base, and on RobinhoodChain.
The MultiPools Factory (the LayerZero OApp that initiates all cross-chain messages) is live at 0x61A4e6e6ceCfc04f44719C15F88D1d3Eea270000 on Ethereum, Base, and RobinhoodChain. All message activity is publicly visible on LayerZero Scan.
Coming next: DVN Infrastructure Improvements
We are actively working on optimizing our DVN infrastructure to process verification jobs faster across all six routes in parallel, reducing the time messages spend in pending state as launch volume continues to grow.
Bug Bounty
We welcome security researchers and developers to help us keep MultiPools safe. If you discover a vulnerability, please report it to us privately before public disclosure. Verified reports that lead to a fix will be rewarded.
DM us on X to report a finding or email us at [email protected]
(4/4)
Security Disclosure
MultiPools runs on fully on-chain, immutable smart contracts. User funds, token contracts, and all protocol logic are secured by the blockchain itself and cannot be touched by anyone, including us. This disclosure is about an internal tooling credential, not the protocol.
(1/4)
What we did
We identified the root cause within hours and resolved it completely:
The administrative endpoint and frontend admin panel have been permanently removed. All credentials have been eliminated from the codebase, and the platform wallet has been rotated to a new secure address.
All factory contracts have also been updated to point to the new wallet. A full audit has been completed, confirming that no other exposure exists.
Current Status: The platform is secure and fully operational.
The platform is fully operational. All systems are confirmed secure. This class of vulnerability no longer exists in our codebase.
(3/4)
Bridge is Live!
Track Your Transaction at https://t.co/QUcmU3ejRv Powered by @LayerZero_Core
Cross-chain bridging is now fully operational across Ethereum, Base, and Robinhood Chain. You can track the status of any bridge transaction in real-time directly on the app, just open the Bridge tab and paste your tx hash.
If your bridge shows as pending, no action needed on your end. All cross-chain messaging runs through LayerZero V2, the protocol handles DVN verification, packet commitment, and execution autonomously. Typical delivery time is under 2 minutes, but during network congestion it can take longer. The system will always complete delivery; there is no stuck state that requires manual intervention from users.
Arbitrage, Open to Everyone, Right Now
Because MultiPools tokens exist natively on three chains simultaneously (ETH, Base, RBH), price discrepancies naturally emerge between chains based on local supply and demand. Any trader can exploit these discrepancies manually today:
1. Identify a price gap between two chains (e.g. token is cheaper on Base vs ETH)
2. Buy on the cheaper chain
3. Bridge to the more expensive chain via the Bridge tab
4. Sell on the destination chain
The mechanism is entirely permissionless and trustless. No whitelisting, no KYC, no keeper involvement. You are interacting directly with Uniswap V4 pools and the LayerZero bridge on-chain.
V2 Arbitrage, Coming Soon for MOOLS Holders
We are building a structured arbitrage system exclusive to $MOOLS holders.
Lock your $MOOLS tokens and earn a proportional share of protocol arbitrage profits. Profits are generated by the on-chain arb bot running across all three chains and distributed in ETH, sourced directly from arb captures. The longer you lock, the higher your share weight. No active management required, lock once, earn passively while the protocol operates.
Security
All contracts are non-upgradeable post-launch. Hook ownership is permanently renounced. Liquidity is locked at the protocol level with no admin key. Bridge security is inherited from LayerZero V2's DVN architecture with our own dedicated DVN node running independent verification on every cross-chain packet.
Everything on-chain. Everything verifiable.
MultiPools V2 is ready for launch.
The launchpad will officially open soon on https://t.co/Z7o3pHAlH8
V1 launched 33 multichain tokens across Ethereum, Base, and Robinhood Chain, processing $783,307 in total trading volume.
V1 proved the concept. Now, V2 is built to scale it.
Over the past few days, we’ve thoroughly tested every part of the new system cross-chain delivery, custom hooks, auto LP, fee splits, and global supply enforcement via LayerZero.
All core features are working as intended across Ethereum, Base, and Robinhood Chain.
One launch. Three chains. One global supply.
The launchpad will open alongside something we’ve been preparing for a while.
Multipools begins soon.
MultiPools V2 is coming.
The first launchpad built for multichain tokens, live on Ethereum, Base, and Robinhood Chain simultaneously at launch.
Here's what's new in V2:
1. Custom Hook Every token gets a fully configurable fee split built into the AMM hook itself. Set your trading fee (0.30–5%), split between creator revenue, buyback & burn, holder rewards, and auto LP. No extra contracts. No extra trust assumptions.
2. Auto LP 0.1% of every trade automatically adds liquidity back to the pool, across all 3 chains. Liquidity compounds forever without any manual action.
3. One launch. Three chains. One token address. Cross-chain messaging via LayerZero.
V2 drops soon at https://t.co/Z7o3pHATwG