Pools $POOLS
Revenue by window
Every window annualised, so the multiples are comparable. A short window on a young protocol is noisy, and a window longer than the protocol's earning history is marked.
| Window | Earned | Holder rev | Fees | Annualised rev | Trend | P/R | P/HR |
|---|---|---|---|---|---|---|---|
| 24h | $0.0 | $0.0 | $91k | $0.0 | – | – | – |
| 7d | $0.0 | $0.0 | $323k | $0.0 | – | – | – |
| 30d | $0.0 | $0.0 | $1.2M | $0.0 | – | – | – |
| Since launch | $0.0 | $0.0 | $2.1M | – | – | – | – |
Revenue basis
DefiLlama shows fees and no revenue line, and our audit confirms that is correct. The FeeSplitter holding every launch position has an immutable two-entry split with no protocol address in it, so nothing accrues to pools.trade or to POOLS holders at the pool level. Any front-end or router revenue was not screened.
| Stream | Kind | Enforced | Note |
|---|---|---|---|
| Creator share, 40% of ETH-side LP fees | excluded | code | Paid to the holder of a transferable Fee Beneficiary NFT, currently the launch signer. About 6.28 ETH to date. It leaves the protocol and never reaches POOLS holders |
| Compounded fees back into the locked position | excluded | code | 60% of ETH plus all token fees are added back to the permanently locked position, which is why its liquidity rose 30.6%. It deepens the book everyone sells into, and no holder can claim it |
| Uniswap v4 protocol fee, 400 pips per direction | excluded | discretionary | Diverts 13.8% of the gross swap fee to the chain's v4 fee controller, owned by the same account that owns the PoolManager, which can reset the rate to the v4 cap at any time. It accrues to that owner, not to pools.trade or POOLS holders |
| Any payout to POOLS holders | excluded | code | None exists. No staking, claim, vault or reward contract, and the token received none of the roughly $129,000 the pool has produced |
Liquidity is permanently locked and deepening. The token itself has no claim on anything.
Launch screen COORDINATED
37 distinct origins bought 70.2% of supply within 50 blocks (about 5 seconds). One cluster of 8 wallets bought in the same block through the same forwarder at the same gas price with adjacent nonces and exited in the same three blocks. Shared funder not proven.
Token audit (ours) GO-WITH-CONDITIONS
POOLS is a fixed-supply token with no admin, no proxy and no privileged control path, and its launch liquidity sits in a Uniswap liquidity-launcher FeeSplitter that has no function to move the position or withdraw principal. Across the pool's entire life the launch position recorded 245 liquidity events with not one negative delta, and it grew 30.6% because 60% of ETH fees and all of the token fees compound back into it. A $5,000 exit quotes 3.39% below spot, a real sale of 0.377% of supply cleared 5.9% below spot 19 minutes before the pin, and ownership is spread across 4,507 holders with the largest non-pool wallet at 3.06%. The conditions: the token carries no enforceable right and received none of the roughly $129,000 of fees the pool has produced, the launch was a coordinated 37-wallet event that has since fully exited, and one account controls the chain's v4 deployment and already diverts 13.8% of the gross swap fee.
- A-1: The runtime carries no mint, burn, pause, blacklist, seize, fee-setting, ownership or upgrade selector and no CALL, DELEGATECALL, CREATE2 or SELFDESTRUCT opcode; supply is fixed and minted once in the launch transaction
- B-1: The launch position is a PositionManager NFT over an ETH/POOLS pool, owned by a FeeSplitter with no approval set
- B-2: The custodian's runtime contains no NFT transfer or approval selector and no owner or admin, and its matched source states that positions sent to it are permanently locked
- B-3: A complete replay from mint found 245 liquidity events with zero negative deltas, liquidity rising 30.6% to 87.1% of the pool's in-range total; the other 12.9% is third-party liquidity that can leave at any time
- C-1: Quoter: a $5,000 sell is 3.39% below spot, 1% of supply 10.18%, and 5% of supply 36.0%
- C-2: An executed sale of 3.77M POOLS, 0.377% of supply, settled for 2.44 ETH, confirming the quoted depth is real
- D-1: Across a universe reaching 84.41% of supply, 4,507 addresses hold POOLS; excluding the PoolManager's 11.4% pooled inventory the largest holder is 3.06%, the top 10 hold 13.61% and the top 50 hold 33.46%, with 15.59% unattributed because a middle block range was not replayed
- E-2: The launch cohort's residue is zero: all 30 analysed origins of the 37 that took 70.20% of supply hold none today, and the launch signer holds none
- F-1: The fee split is fixed at construction with no setter: 40% of ETH fees to a transferable Fee Beneficiary NFT and the rest compounded back into the locked position, so there is no discretionary protocol take and no treasury
- F-2: A complete scan found 140 collections totalling 15.69 ETH and 52.5M POOLS, about $129,000, of which the only payout is roughly 6.28 ETH to the Fee Beneficiary NFT held by the launch signer
- F-5: A Uniswap v4 protocol fee of 400 pips per direction is live on this pool, diverting 13.8% of the gross swap fee to a controller owned by the same account that owns the chain's PoolManager
- G-1: POOLS confers no redemption, no fee share, no governance and no reward accrual; beyond ERC-20 its only functions are two views
- H-2: POOLS did not launch through the advertised contracts. It used an older launcher and strategy, and the pool's tick spacing shows the deployed build predates the v3.2.0 source tree
Professional audit audited: OpenZeppelin, Spearbit +2
Pools.trade runs on Uniswap Labs' Liquidity Launcher, which OpenZeppelin, Spearbit, Cantina and ABDK have audited at v1.0 and v2.0.0. Our audit found that POOLS itself did not launch through the currently advertised contracts: it used an older launcher and strategy, and the pool's tick spacing shows the deployed build predates the v3.2.0 source tree. So the audited versions do not correspond to the contracts holding this token's liquidity. The POOLS token itself is a launch output and was never in any audit scope.
- OpenZeppelin (2026-01-23): Uniswap Liquidity Launcher v2.0.0 · does not cover what is deployed here
- Spearbit (2026-01-21): Uniswap Liquidity Launcher v2.0.0 · does not cover what is deployed here
- Cantina (2025-10-27): Uniswap Token Launcher v1 code review · does not cover what is deployed here
- ABDK (2025-10-20): Uniswap Token Launcher v1.0 · does not cover what is deployed here
- OpenZeppelin (2026-06-16): Continuous Clearing Auction v2.0.0 (Crowd Launch auctions) · deployed-scope match unknown
- Spearbit (2026-06-16): Continuous Clearing Auction v2.0.0 · deployed-scope match unknown
Contracts
Data sources
Get the next audit before it trends
New token audits, detailed technical assessments and Robinhood Chain revenue news. No spam, unsubscribe any time.