Signal detected
A wallet, pool, route, or discovery source creates a chain-specific alert.
How a Qinlong candidate moves through review.
Qinlong is a multi-chain on-chain research system. A raw alert does not become approval. The system records source, chain, route, liquidity, validation sample, blocker reason, and current status.
Raw alert
Source-aware candidate
Route and liquidity evidence
Validation sample
Validation record
Core distinction
- Discovery is separate from validation
- Each chain has its own evidence rules
- Dashboards explain blockers and outcomes
Common blockers
- Source quality is too weak
- Route or liquidity evidence is incomplete
- Validation sample is too thin
Example review flow.
A candidate is only useful if the path can be inspected later. Qinlong records each step, including the reason a candidate was blocked, observed, or held for more evidence.
Candidate recorded
Chain, source, token or pool context, liquidity, and route metadata are stored.
Route reviewed
The system checks route evidence, quoteability, and sellability context.
Status assigned
The candidate is blocked, observed, held for more evidence, or moved into validation.
AI summarizes
AI turns the raw notes into a short explanation and tags blocker reasons.
Evidence preserved
Dashboards keep the trail available for later review and system learning.
System modules
The modules answer plain questions: what was observed, what was checked, why did it fail, and what evidence is still missing?
Signal discovery
Qinlong separates BSC, SOL, and ETH research lanes so wallet, pool, route, token, and liquidity evidence can be interpreted in the right market structure.
Source and actor scoring
Wallets, pools, routes, and discovery sources are scored separately. A strong signal on one chain is not automatically transferred to another chain.
Candidate gatekeeping
Candidates are checked against chain-specific rules such as source quality, liquidity, route evidence, sample freshness, cooldowns, and duplicate controls.
Quoteability and liquidity checks
Route evidence, DEX or AMM context, pool state, sellability checks, and failure reasons help separate usable signals from signals that cannot be validated cleanly.
Validation ledger
Research-mode entries, exits, rejection reasons, and rule outcomes are stored so results can be reviewed without mixing alerts, diagnostics, paper observations, and readiness evidence.
Dashboard and review layer
The dashboard shows process health, latest candidates, validation records, wallet-group behavior, and the reasons candidates were blocked.
How Qinlong blocks weak paths.
Most candidates should not move forward. Qinlong records the reason instead of hiding failed checks or mixing weak alerts with stronger validation records.
Alert evidence
Where did the signal come from, and which chain, wallet, pool, route, or source produced it?
Route evidence
Is there enough route, liquidity, and sellability context to keep reviewing the candidate?
Validation evidence
Are there fresh records, consistent samples, and clear outcomes instead of stale or polluted evidence?
Blocker attribution
If the candidate fails, Qinlong records whether the cause was source quality, liquidity, route failure, sample quality, or a chain-specific gate.
Review status
Each candidate can be blocked, observed, reviewed, or held for more evidence without being treated as an execution instruction.