Wallet groups and DEX checks
Tracks profiled wallet groups, candidate source, DEX route evidence, liquidity state, blocker reason, and validation record.
A research system for checking on-chain signals before they scale.
Qinlong watches BSC, SOL, and ETH research lanes, records where each candidate came from, checks route and liquidity evidence, and keeps blocker reasons visible. AI appears only as a review layer; it does not bypass the gates.
Signal source
Candidate record
Route evidence
Validation record
Review dashboard
What the system records
- Which chain and source produced the alert
- Whether route and liquidity evidence exists
- Why a candidate passed, failed, or stayed under review
Review note
- Turns raw chain events into short review notes
- Tags blocker reasons for human review
- Does not currently place live orders automatically
What the system watches.
Qinlong is not sold as an automated trading product. It is a review system for chain signals: wallet groups, pool and route context, blocker reasons, and validation records stay separated by chain.
Pool, route, and sellability checks
Checks route availability, pool context, sellability, quote quality, and execution-risk notes before a candidate moves forward.
Pool and token evidence
Tracks new pool context, token metadata, route availability, early risk signals, and the validation conditions still missing.
What is built now.
Qinlong is an early system with live research lanes and internal dashboards. This page states what exists, what is still being hardened, and what Qinlong does not offer.
- BSC / SOL / ETH research lanes
- Wallet and source monitoring
- Candidate records
- Quoteability and liquidity checks
- Blocker logs and validation ledgers
- Internal review dashboards
- Cleaner forward-validation samples
- Short review notes
- Chain-specific risk gates
- More reliable process monitoring
- Future automation-readiness checks
- No managed trading
- No custody of user assets
- No public digital-asset issuance
- No outcome promise
- No advisory service
- No current automatic live-order execution
What we can show publicly.
The live system contains operational logs and research records. Public pages show only the shape of the work: lane health, candidate state, blockers, and review notes. Wallet identifiers, exact amounts, credentials, running config, and strategy details stay private.
System health and lane state
- BSC / SOL / ETH lane separation
- Scanner freshness and process health
- Review status without public capital figures
Candidate and blocker trail
- Source-aware candidate records
- Route and liquidity evidence
- Blocked, observed, or validation-ready status
Reports and diagnostics
- Signal summaries for human review
- Blocker classification and review notes
- Strategy review without live-order automation
What makes this more than a signal list.
The useful part is not a single alert. It is the trail around it: where the alert came from, what failed, which route was checked, and why the candidate stayed blocked or moved into validation.
01
Source-aware records
Signals are tied to chain, source, wallet or pool context, route evidence, liquidity state, and rule outcomes.
02
Separation between alert and validation
Alerts, diagnostics, research validation, and execution-readiness review are kept separate.
03
Risk controls before scale
Promotion depends on route quality, sample quality, lane health, blocker review, and explicit approval.
Why it needs reliable systems.
Chain signals age quickly. Qinlong needs repeated ingestion, route checks, validation storage, process monitoring, and report generation so the same candidate can be reviewed later with context.
Streaming ingestion
Structured analytics
Diagnostics
Evidence storage
Operational logging
Operational boundaries