How Lens turns noisy crypto data into a risk decision.

Paragon Lens is built to behave like a research desk, not a raw API wrapper. It gathers evidence, marks uncertainty, and explains why an asset is blocked, watchlisted, or ready for a wallet-safe preview.

The product separates research from execution. Lens and the analyst layers investigate. Guardian decides whether the path is safe enough to continue. Volt prepares previews only after that gate.

Resolve the asset

Lens starts by separating a symbol, a project name, and an exact contract. Tickers are treated as ambiguous until chain, contract, pool, and registry evidence point to the same asset.

Map the live market

The system checks active pools, route depth, quote assets, turnover, volume quality, and cross-chain same-ticker spread before treating momentum as tradable.

Run risk forensics

On-chain analysis reviews contract controls, provider warnings, honeypot and tax evidence where available, LP quality, clone risk, and missing proof.

Gate with Guardian

Guardian turns research into an action state: block, review, or allow preview. Missing security evidence is never treated as a pass.

Prepare only safe handoff

Volt may prepare route previews and wallet-ready context only after Guardian clears the path. The user wallet remains the signer.

Output rule

Readable proof before confidence.

A useful answer should show what was checked, what failed, what is missing, and what the user should do next. If a provider is unavailable, the UI should say that plainly instead of hiding it inside a dense warning block.

Market context: regime, sentiment, majors, derivatives, chain activity, and narrative pressure.

Token context: verified identity, exact contract, live pools, liquidity depth, turnover, and route quality.

Risk context: symbol collisions, clone spread, contract controls, provider warnings, holder proof, and missing checks.

Execution context: route risk, approval risk, liquidity risk, wallet readiness, and user confirmation.