Liquidity Pool Scanner
One of the fastest ways to spot a rug or a high-risk token is by analyzing its liquidity pool (LP). Forge includes a dedicated LP Scanner module that tracks the creation, behavior, and structure of LPs across new tokens on Solana. It works in real-time and feeds data directly into Forge’s agents and query responses.
This page explains how the LP Scanner works, what it detects, and how it can help you avoid traps and find legitimate setups.
What the LP Scanner Does
The LP Scanner monitors new tokens for:
When and how LP is added
What ratio of token to SOL was seeded
Whether LP is burned, locked, or still owned
Changes in LP over time (additions, removals)
Unusual patterns that often lead to rugs
It operates as part of Forge’s indexer, watching every transaction and routing updates into the token context.
What It Looks For
Here are some of the key LP signals the scanner detects:
LP Creation Event
Timestamp of first LP creation
Source of liquidity (deployer vs. fresh wallet)
Pair type (e.g. SOL/token)
LP Ratio
How much SOL vs. how much token was added
Detects underseeded or overinflated liquidity
Flags setups where deployer keeps a large supply while LP looks balanced
LP Burn or Lock
Whether the LP was sent to a burn address
Locked via external service or renounced router
If still owned by a wallet, it’s marked as “LP Unlocked”
LP Transfers
LP moved after creation
Removed liquidity events
Transfer to stealth wallets or mixers
LP Removal Timing
How long LP stayed in place before being pulled
If LP is removed early, triggers an instant rug tag
How It Helps You
You ask:
“Is $BAG safe?”
Forge includes LP Scanner data in the response:
“$BAG launched 7 minutes ago with 12.3 SOL LP. LP not burned, still held by 7AuCty3w... Volume spiked to $26k, and deployer has 2 prior rugs. LP is at risk.”
This gives you real, on-chain info you can act on immediately.
Real-Time Alerts
If you’re using the hosted version or have notifications enabled, the LP Scanner can:
Trigger alerts when LP is added without burn or lock
Auto-flag tokens with LP removed in the first few minutes
Push notifications to Discord, Telegram, or browser
These alerts are fast — usually less than 2 seconds after the on-chain event.
Advanced Features
For self-hosted or advanced users:
Set your own LP thresholds (e.g. min 10 SOL LP, min 90% burn)
Customize risk rules (e.g. flag if LP is added from funded wallet)
Combine LP Scanner output with WalletAgent for deeper analysis
You can also write your own scripts to scan every new token against LP rules and automatically tag good setups for entry.
Example Use Cases
Avoiding Rugs: LP not burned and held by deployer? Walk away.
Finding Real Launches: LP burned, good ratio, renounced ownership? Worth watching.
Sniper Farming Detection: LP added with bait ratio, but no burn and instant sniper buys? High risk.
Entry Opportunity: LP added clean, volume still low, solid holder spread? Early window.
Last updated