$FOLIO

The setup, and what would break it

It is holding its shape — the pool stands at $255, and $713 traded over the day.

The case for $FOLIO: there is a story here but the evidence behind it is thin.

Breaks if: This only becomes a case if they publish the contract address on their own site and code starts landing in the repo — until then there is nothing to invalidate; The pool is $255 today — if that shrinks while the price holds, the liquidity providers are leaving and the exit gets narrower than it looks..

Where the money went

• The contract holds no supply of its own, so there is nothing parked in it to be sold into buyers later.

The liquidity lock

• 20.89% of the supply is sitting in the Uniswap v4 pool.
• The Pons launch locker still holds 8.16% of the supply. That is the launch allocation rather than the traded float, and it can be released into the market.
• Uniswap v4 liquidity is held as position NFTs on the PositionManager, so whether the pooled side itself is locked or withdrawable cannot be read yet — unknown, not clear.

Is there a product

• The documentation is real — it loads and it says something.
• No public code.
• The domain was registered 1 days ago — around the launch.
• The site never names this contract, so we could not confirm the two belong together.
• There is something on the site that behaves like an app, not just a page.

Third-party read

• No sell-blocking behaviour is reported against this contract, and no tax is taken on the way out. Nobody has run an actual test sell, so this is not proof you can leave.
• The liquidity sits in 1 Uniswap v4 position held by 1 address. Whether those positions are locked could not be established, so this is not an all-clear on the liquidity being stuck.

What this read could not see

• No actual test sell was executed against this contract — we can say nothing was flagged, not that selling works.
• The tax taken on a sell could not be established.
• Whether the Uniswap v4 liquidity positions are locked cannot be read yet — the positions are visible, their lock state is not.
• Coordinated-buyer read has not run for this token yet — this is not a finding of nothing.
• The exit could not be modelled — the pool behind this token could not be read on this pass.
• No app contract found on the site to measure.
• No readable public repository.
• We have never recorded this token's liquidity before, so we cannot say whether the pool is growing or being pulled. This scan just took the first reading.
• We have no price history for this token, so we cannot say how far it is off its high.