Canonical identity
Network, contract or mint, venue, market type, base, quote, and settlement terms. Symbols are labels, not global IDs.
A framework for Solana and Ethereum token screens, technical analysis tools, HFT-style data, liquidity filters, alerts, and reproducible signal definitions.
Signal stack
A result should preserve contract or market identity, event time, source, quality flags, parameters, and enough liquidity context to judge whether the signal is usable.
Scanner architecture
Network, contract or mint, venue, market type, base, quote, and settlement terms. Symbols are labels, not global IDs.
Exchange event time, receipt time, processing time, corrections, and late messages. Processing order is not market order.
Spread, depth, recent trades, venue coverage, slippage, and position-size filters. Volume alone is not execution quality.
Input series, interval, lookback, smoothing, warm-up, missing-data policy, and calculation version.
Technical analysis tools
Moving averages, RSI, momentum, volatility, volume expansion, trend structure, and order-flow features are transformations of historical data. A scanner should state exactly what condition occurred and which parameters produced it. It should not convert a detected pattern into certain future performance.
Ranking should include quality and liquidity. A dramatic move in a barely traded pair can outrank a liquid market when a system sorts only by percentage change. Add minimum depth, trade count, freshness, venue coverage, and outlier controls first.
HFT and high-rate data
High-frequency altcoin analytics introduce clock drift, sequence gaps, duplicate messages, out-of-order events, exchange corrections, and uneven venue latency.
Return exchange, receipt, and processing times. Document precision, timezone, and clock synchronization limits.
Use deterministic cursors and event boundaries so pagination does not skip or duplicate changing markets.
Version revised candles or expose revision metadata. A backtest is not reproducible when bars change silently.
A safer scanner workflow
Confirm network, contract, venue, market type, and token metadata.
Check freshness, gaps, sample count, corrections, and mapping confidence.
Set spread, depth, slippage, trade count, and venue-coverage thresholds.
Run a fully specified indicator and retain parameters, version, and context.
Scanner FAQ
A scanner evaluates a defined market universe against filters or signals such as liquidity, price change, volatility, momentum, volume, or technical indicators.
No scanner can guarantee future performance. It can surface conditions for research, but market regime, manipulation, execution cost, project risk, and changing information remain material.
Different tokens can share a symbol. Chain and contract or mint identity prevent histories and signals from joining to the wrong asset.
Instrument, venue, observed condition, timestamp, source, parameters, liquidity context, quality flags, and a link to evidence.
High-rate data require sequence handling, multiple timestamps, clock assumptions, correction policies, deterministic snapshots, and tighter resource controls.
The scanner API guide covers canonical instruments, event time, indicators, liquidity, quality, pagination, and object-level security.