LP Burner Tracker
Rug prevention starts with one key check — was the LP burned? The LP Burner Tracker module in Forge watches every new token on Solana and logs whether the liquidity pool was permanently burned, locked, or left exposed.
This module works in tandem with the LP Scanner and feeds directly into token risk assessments, giving you real-time feedback on the most critical part of launch safety.
What the LP Burner Tracker Does
This module monitors:
LP burn transactions
Tokens sent to dead addresses (e.g.
11111111111111111111111111111111)LP tokens sent to lockers or burned by contract
Timing of the burn (immediate vs. delayed)
LP burn reversals or redeploys
It flags LPs as:
Burned – permanently destroyed, no owner
Locked – time-locked in a 3rd-party contract
Unlocked – still accessible by deployer or wallet
How It Detects LP Burns
The tracker looks at:
Token balances of LP tokens after creation
Transfers to known burn addresses
Interactions with locking protocols like PinkLock or Uniloc
Manual burns from deployer wallets
It matches these to a growing database of known burn addresses and locker contracts to verify burn legitimacy.
In-Chat Response Integration
Ask a question like:
“Is LP burned on $SPIN?”
Forge returns:
“$SPIN LP is unburned and still controlled by deployer wallet 7AuCty3w... No lock detected. LP can be removed at any time.”
If burned:
“$SPIN LP was burned 2 minutes after launch. Verified send to 111111111... No lock detected. LP is now permanent.”
Forge will also note delayed burns, which sometimes suggest bait setups. For example:
“LP was burned 6 minutes after launch, after a volume spike of $30k. High risk of post-entry rug bait.”
Risk Signal Integration
The LP Burner Tracker directly feeds into token safety scores:
Burned LP increases trust score
Unburned LP held by deployer flags high risk
Early volume before burn may reduce safety even if LP is later burned
Agents use these signals to adjust how they label and explain a token.
Burn Timing Breakdown
Burning LP isn’t just about if — it’s about when.
The tracker logs timing stats like:
Time between LP creation and burn
Volume at moment of burn
Number of unique buyers before burn
These are used to flag delayed bait tactics — where LP is left open just long enough to bait in early traders, then burned to fake legitimacy.
LP Lock Detection
The module also detects if LP is locked, not burned:
Uses a registry of locker contracts
Detects lock durations
Flags if LP can be reclaimed or unlocked prematurely
Locked LP is safer than unlocked, but still not as final as a burn.
Last updated