On-Chain Data Indexing
Forge wouldn't work without data. But not just any data — it needs real-time, deep, and structured access to everything happening on the Solana blockchain. Most tools rely on public APIs or post-processed stats. Forge goes deeper. It runs its own indexer built specifically for AI use cases.
This page explains how Forge gathers data from the Solana network, how it organizes that data for use by agents and MCP, and why this custom indexing approach gives Forge an edge over dashboards and other bots.
🧠 What Is an Indexer?
An indexer is a backend system that listens to every block on the blockchain, extracts useful information, and saves it in a format that can be searched instantly.
Forge’s indexer is designed to capture memecoin-scale activity. That means:
Fresh token deployments
Sudden LP adds and burns
Wallet funding patterns
Contract events
Buy/sell flows across tokens
Known sniper or deployer behavior
Telegram-linked wallet movements
Everything is stored with low latency, optimized for triggering agent logic and MCP injection in real-time.
🔍 What Forge Indexes
Forge doesn’t just copy everything from the blockchain. It listens selectively for high-signal events:
Token Events
Token creation
Contract renounce or ownership changes
Burn function presence
Metadata injected (like social links or fake audits)
Liquidity Events
LP created, burned, or modified
Initial LP ratio
LP lock timing
Rug detection signals
Wallet Activity
Wallet buys and sells (amount, timing, price)
Sniper detection patterns
Repeat deployers
Wallets that fund new creations
Project Behavior
How fast tokens hit market cap milestones
How often deployers reuse code
Which Telegram groups a deployer joins
Cross-wallet clustering
All of this is tagged and stored in an optimized database, ready for agent use.
⚙️ Architecture
The indexer is built in a modular way:
Stream Handlers – These listen to specific Solana programs (like SPL Token, Raydium, and LP routers)
Event Filters – Only high-signal events are stored, based on pre-set triggers and custom logic
Entity Builders – Forge reconstructs relationships between tokens, wallets, and LPs as first-class objects
This means Forge can instantly answer things like:
“Which wallets bought this token in the first minute?”
“Did this deployer burn LP?”
“What’s the average lifespan of tokens from this address?”
🔄 Real-Time Sync
The indexer operates with minimal delay — usually within 0.5 to 1.5 seconds from the actual transaction.
This is why Forge can respond in chat to events that just happened:
“Token just launched, deployer has rugged 3 times today, LP was added and instantly removed.”
No need to refresh pages or wait for a daily update. It’s live.
🧠 Built for Agents
Every Forge agent pulls directly from the indexer, not from third-party APIs. That’s why responses are faster, more accurate, and richer in detail.
TokenAgent looks at deployer patterns, social metadata, LP setup
WalletAgent looks at how wallets fund, buy, and sell
LPAgent listens for lock periods, burn events, and liquidity depth
Because Forge owns its index, it can inject exactly the right details into every prompt — and nothing else.
🔧 Extensible and Private
The Forge indexer can be extended to track new types of data or chains, such as:
NFT mints and swaps
Multi-chain deployer behavior
Telegram and Twitter crossover signals
Time-series patterns like sell-offs or volume spikes
It can also be deployed privately, so teams running their own Forge instance don’t need to rely on public APIs or give away their queries.
📌 Why It Matters
In crypto, seconds matter. Especially in memecoins. Forge’s indexer makes it possible to ask about something that just happened and get a full breakdown before anyone else even sees it.
This isn’t possible with dashboards that refresh every few minutes or rely on lagging RPC providers.
Forge sees the blockchain like a live organism — and makes it readable in plain English.
Last updated