How it works
We read the chain. You make the call.
Lummiq is a reading tool. It collects public data about an address, runs written rules over it and shows you every input. It never trades, never holds funds and never decides for you.
The life of one scan
How indicators are graded
Every indicator applies one written rule to public data and returns a level:
- Warning: probably relevant to a holder, for example no code at the address, the top ten holding 80% or more, or very thin pools.
- Check: worth a closer look, for example a replaceable contract, a wallet owner with mint power, or unpublished source.
- Info: context, for example a contract owner or a recent burst of transfers.
A rule that could not read its data is shown as not read and never counts as clear. No combination of clear results means a token is safe.
How a report stays provable
A scan report is written as canonical JSON: sorted keys, no spaces, only the measured values, rule ids, versions and evidence. Its keccak-256 hash is the fingerprint. Change one character and the fingerprint changes.
Anchoring stores that fingerprint with the token address, the block the reads were taken at and the rules version (currently v1). It proves the report existed unchanged from that moment. It does not prove the report is right.
Every rule, in plain view
Token rules
| Id | Rule | Line drawn |
|---|---|---|
| LQ-01 | Deployed code at this address | No code at the address is a warning. |
| LQ-02 | Published source matches the code | No verified source is a check; a partial match is info. |
| LQ-03 | Logic can be replaced (proxy) | Any standard upgrade slot or beacon is a check. |
| LQ-04 | Administrative powers in the code | Any known power is a check; three or more with an active owner is a warning. |
| LQ-05 | Single owner in control | An owner that is a plain wallet is a check; a contract owner is info. |
| LQ-06 | Supply held by a few addresses | Top 10 holders at 80% or more is a warning; 50% or more is a check. |
| LQ-07 | Trading depth on DEX pools | Under $10,000 is a warning; under $100,000 is a check. |
| LQ-08 | One sender behind most transfers | One address sending 50% or more of recent transfers is a check; 30% is info. |
| LQ-09 | Sudden burst of transfers | The last hour at three times the earlier hourly average (and 30+ transfers) is info. |
| LQ-10 | Contract age | Deployed less than 2 days ago is a check; less than 7 days is info. |
| LQ-11 | Can holders actually sell | Would need a simulated purchase and sale. |
| LQ-12 | Data completeness | Missing code or activity data is a check; any other gap is info. |
| LQ-13 | Mentions the stock-token beacon without being a stock token | Code containing the issuer beacon address while not being the official stock proxy is info. |
Wallet rules
| Id | Rule | Line drawn |
|---|---|---|
| LW-01 | Wallet or contract | Code at the address is info. |
| LW-02 | Fresh or barely used | Two sent transactions or fewer is info. |
| LW-03 | Open token approvals | An unlimited approval still in force is a check; a limited one is info. |
| LW-04 | One counterparty dominates | One counterparty in 60% or more of 10+ transfers is info. |
| LW-05 | Tokens nobody asked for | Five or more tokens received and never sent is info. |
| LW-06 | Data completeness | Missing transfer data is a check; any other gap is info. |