When an address has no history
A screen that returns nothing can mean the address is new, that the vendor does not cover the chain, or that the lookup failed. The three are different, and only one of them is reassuring.
Screening an address and getting nothing back is common and ambiguous. Nothing found is not the same as nothing there, and neither is the same as the question never having been asked.
Four things a blank result can mean
- The address is new
It was created and used for the first time this week. There is no history because no history exists yet. This is ordinary: wallets create fresh addresses constantly.
- The address has history, and none of it is attributed
Funds have moved through it, but nothing in its past connects to anything the vendor has labelled. Most addresses are in this state, and it is the closest thing to a clean result you will get.
- The vendor does not cover that chain
Coverage varies by chain and by asset. An unsupported chain returns nothing in exactly the same shape as a clean address.
- The lookup failed
A timeout, a rate limit or an outage. The vendor answered with nothing because it never looked.
How to tell them apart
| Check | What it settles |
|---|---|
| First-seen date of the address | Separates a genuinely new address from one with unattributed history. |
| Transfer count and age | An address with two years of activity and no attribution is a different fact from one with none. |
| Whether the vendor lists the chain | Separates no coverage from no findings. |
| The response itself | An error and an empty result are different responses. Insist on being able to see which you got. |
What this changes
A new address is a reason to look at the customer rather than the chain, because the chain has nothing to say yet. An address with long unattributed history is mildly reassuring. No coverage and a failed lookup are both unscreened, and an unscreened address should be recorded as unscreened rather than passed.
Related
Last checked against the product on .