Signals
Timeline of detected events for a project
The Signals tab shows a chronological timeline of events detected for a project. Each signal represents a discrete, verifiable fact derived from tracked discussions.
The Timeline
Signals appear in reverse chronological order with the most recent at the top. Each entry shows a category badge indicating the type of event, followed by a concise description of what happened. Scroll to navigate through the project's signal history.
Signal Categories
AIXBT classifies signals into the following categories:
| Category | Description |
|---|---|
| FINANCIAL EVENT | Token sales, TGEs, airdrops, funding rounds, grants, incentive programs |
| TOKEN ECONOMICS | Emissions, burns, supply changes, fee distribution, staking/locking terms |
| TECH EVENT | Mainnet/testnet launches, upgrades, feature releases, audits, major infra changes |
| MARKET ACTIVITY | Listings, delistings, new trading pairs, liquidity pools, market-making programs |
| ONCHAIN METRICS | Achieved TVL, volume, fees, user counts, active addresses |
| PARTNERSHIP | Integrations, collaborations, co-launches, co-marketing with named counterparties |
| TEAM UPDATE | Founders/leads joining or leaving, major hires, role changes |
| REGULATORY | Licenses, approvals, bans, enforcement actions, legal/regulatory moves |
| WHALE ACTIVITY | Very large transfers, accumulations, distributions, position changes |
| RISK ALERT | Hacks, exploits, outages, halts, critical bugs, recovery events |
| VISIBILITY EVENT | Conference talks, hackathons, AMAs, interviews, media coverage, award nominations |
What Becomes a Signal
Signals are detected when tracked discussions describe:
- A specific change or confirmed future change for the project
- An onchain or market metric that has been achieved
General marketing, vague hype, and simple project descriptions do not become signals. Neither do predictions about future metrics ("could reach X") or speculation about what might happen.
One real-world fact produces one signal. If multiple sources report the same event, the signal is reinforced.
Reinforcement
When multiple sources report the same event, they reinforce a single signal rather than creating duplicates. Each reinforcement updates the signal's timestamp and is recorded in its activity log.
A signal created days ago can still be relevant if it continues to receive reinforcements. This indicates the event remains part of active discussion. The Indigo agent factors in reinforcement activity when assessing what matters now, so older signals that are still being talked about surface alongside recent ones.
Activity
Each signal includes an activity log showing the sequence of reinforcement events. Activity entries record the cluster the information originated from and how the signal's description evolved with each new piece of evidence. This data is available in the terminal and through the API.
The first report of an event is rarely the most detailed. Early signals often capture the headline while later reinforcements add specifics like figures, timelines, and counterparties. For example, if the first tweet says "ETH exchange balances hit record lows" and a later tweet adds "10.5M ETH, representing 8.7% of supply", the signal description may be updated to include those figures.
Activity makes this evolution visible, enabling information flow analysis: tracking which clusters surface a story first, how it spreads across communities, and how the description sharpens over time.
Empty Signals Tab
Some projects show no signals. This happens when:
- The project is new and hasn't generated signal-worthy activity
- Recent discussions have been general chatter without concrete events
- The project primarily attracts opinion rather than news
Activity still contributes to momentum even when it doesn't produce signals. The momentum bars and score reflect all tracked mentions, while the signals tab filters down to detected events.