How LENS Works

The machine under the panel

Every signal LENS shows is read from public data on Base and X, here is the full path from a profile to a verdict

The pipeline

One read only flow, from the profile you are looking at to the panel under it

01
Profile
You open any X profile, LENS reads the public bio for wallet addresses, contract addresses, and GitHub links
→
02
Resolve
The handle and any addresses found are sent to the LENS backend to look up who and what they map to
→
03
Data layer
LENS pulls live on chain, market, and index data in parallel from several public sources
→
04
Signal engine
Every signal is computed from that data, the trust score, dev behaviour, token health, and the rest
→
05
Verdict
Signals roll up into a clear read, shown inline under the profile and inside the agent

Data layer

Four public sources, queried in parallel, nothing private is ever touched

on chain
Alchemy on Base
Token metadata, wallet balances, transfers, contract deploys, fee claim transactions, and the dev live token holdings behind Token Health
market
Dexscreener
Price, liquidity, FDV, volume, buys and sells, pair age, and the socials listed on a token, the inputs to the verdict thresholds
index
LENS index
A backend index of Bankrbot launches, fee claim history, token holders, and curated smart accounts, refreshed on a schedule
social
X public data
The public profile, bio, and follower list, used to surface notable followers and link a handle to its on chain activity

Signal engine

What gets computed from the data layer, every signal traces back to a public source

Trust Score
Dev Claim Fee
Deploy Count
PleaseBro
CA History
Token Health
Linked Accounts
Funding Trail
Smart Follower
AI Verdict
Verdict and Red Lines
Community Tags

The verdict gate

Where the agent turns data into a decision

For any token, the signals are checked against a fixed set of red lines using live data, things like thin liquidity, a brand new pair, heavy sell pressure, no presence, or a PleaseBro fee pattern. Each line either passes or triggers, and the count of triggered lines sets the verdict, so the call is consistent and explainable rather than a guess.

CLEAR · 0 triggered CAUTION · 1 to 2 STOP · 3 or more

What LENS will not do

The boundaries are structural, not a promise

[01] read only

LENS only reads public data, it never signs, sends, or moves anything on your behalf

[02] x.com only

The extension requests access to x.com and nothing else, no other site is touched

[03] no wallet, no keys

LENS never asks for wallet access or private keys, there is no connect step to read a profile

[04] public data only

It never reads your DMs, your posts, or any private account data, only what is already public

[05] information not advice

Every signal is information to help you decide, it is not financial advice and never a guarantee