LogoLogo
  • 📘Introduction
    • What is Forge?
    • Why We Built Forge
  • 🧠How Forge Works
    • Core Architecture
    • Agent System Overview
  • Model Context Protocol (MCP)
  • On-Chain Data Indexing
  • AI Query Handling
  • ⚙️Using Forge
    • Setting Up Forge
    • How to Ask Questions
  • Supported Use Cases
  • Interacting with Agents
  • Limitations and Data Scope
  • 🛠️Advanced Features
    • Agent Personalities and Prompt Logic
  • Creating Custom Agents
  • Integrating External APIs
  • Running Multi-Agent Workflows
  • Token Behavior Tracking
  • Suspicious Wallet Detection
  • 📀Forge Modules
    • Liquidity Pool Scanner
  • LP Burner Tracker
  • Telegram Sniper Detector
  • Contract Creator Profiler
  • Whale Movement Watcher
  • ⚙️Developer Tools
    • Custom Prompt Engineering
  • 📃Appendix
    • Glossary
    • Security and Privacy
    • Roadmap and Vision
Powered by GitBook
On this page
  • What Is Token Behavior?
  • What Forge Looks For
  • Behavior Tags
  • How It Helps
  • Custom Behavior Filters
Export as PDF

Token Behavior Tracking

Not all tokens behave the same. Some are slow burns. Some spike and rug. Some are bought by insiders only. Forge can identify these patterns by analyzing a token’s lifecycle from creation to sell-off.

This page covers how Forge tracks token behavior over time and how agents detect trends, risk factors, and unusual movements.


What Is Token Behavior?

Token behavior refers to the patterns that emerge after launch:

  • How fast volume builds

  • Who’s buying and when

  • If LP is manipulated

  • When and how early wallets sell

  • Whether social metadata is used to bait entries

  • If it’s being farmed by repeat wallets

Forge tracks this behavior in real-time and uses it to help agents answer questions like:

  • “Is this token being botted?”

  • “Does this look like an organic launch?”

  • “Any signs of insider trading?”


What Forge Looks For

Each token is continuously scored across several dimensions:

Launch Quality

  • Was LP added in a normal time window?

  • Was ownership renounced?

  • Did the deployer join Telegram groups before launch?

Buy Pattern

  • Are entries spread out or clumped into a few wallets?

  • Any early buys from known sniper clusters?

  • Was the LP front-run?

Volume Curve

  • Did the volume ramp up smoothly?

  • Was there a sharp spike then instant dump?

  • Are new buyers sustaining the chart?

LP Behavior

  • Is liquidity burned or locked?

  • Any sudden removal of LP?

  • Any unusual LP minting or transfers?

Wallet Exit Timing

  • How fast are wallets selling?

  • Are most sells below profit?

  • Did the deployer sell into volume?

These metrics are all recorded per token and used to inform Forge’s responses.


Behavior Tags

Forge automatically labels tokens with behavior tags like:

  • Organic Launch

  • Sniper Farmed

  • High Risk: Fast Exit

  • Volume Spike + Dump

  • Stealth Launch

  • Bot-Heavy Distribution

  • No Socials

These tags appear in chat replies and are also available when viewing a token’s full breakdown.


How It Helps

Let’s say you ask:

“Is $MEOW safe?”

Forge might respond:

“$MEOW launched 6 mins ago with 18 SOL LP. LP not burned. Wallet 7AuCty... bought 15% of supply at launch and sold 3 mins later. High concentration of buys from sniper cluster wallets. No socials. High risk pattern: sniper farmed + no burn.”

This combines:

  • Token metadata

  • Buyer wallet behavior

  • LP conditions

  • Volume slope

  • Sell timing

All into one reply you can act on instantly.


Custom Behavior Filters

If you’re self-hosting or building a private tool, you can set your own thresholds for what counts as suspicious.

For example:

  • Label “sniper farmed” if more than 40% of buys come in within 10 seconds

  • Tag “slow burn” if volume grows steadily for 30+ minutes without sharp exits

  • Create custom alerts for tokens where deployer joins Telegram 1 hour before launch

These filters can also trigger automated workflows like alerts or deeper agent chains.

PreviousRunning Multi-Agent WorkflowsNextSuspicious Wallet Detection

Last updated 12 days ago