$BOTFMLYBotFamily

The setup, and what would break it

It is quiet — $9K traded in a day with a quiet last hour, and the pool stands at $21K.

The case for $BOTFMLY: there is not enough here to review properly.

Breaks if: This only becomes a case if something actually ships and they publish the contract address on their own site — until then there is nothing to invalidate; The pool is $21K 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

• 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.

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.

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.
• Coordinated-buyer read has not run for this token yet — this is not a finding of nothing.
• Whether the early buyers have sold could not be read.
• The exit could not be modelled — most often because this token's pool holds no active liquidity at the current price, which means nothing can be sold into it at any size.
• No Telegram is linked from this token's listing, so its community size is unmeasured.
• No app contract found on the site to measure.
• No readable public repository.
• No X account is linked from this token's listing.
• 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.