Address verification methodology
Addybook treats protocol discovery, address observation, and address identity verification as separate facts.
Current coverage
4413 catalogued protocols188 with addresses4537 addresses1 evidence verified
Quality levels
- Evidence verified
- Per-address official identity evidence plus independent explorer or onchain evidence.
- Source backed
- A legacy explorer claim has a deployment source URL, but not a complete per-address evidence record.
- Legacy claim
- A historical verified boolean exists without enough machine-checkable provenance.
- Observed
- At least one source records the address. The verified threshold is not met.
- Conflict
- Sources disagree. The address should not be used without manual review.
Acceptance rules
- New EVM addresses must be EIP-55 checksummed.
- Every new or changed address needs a dated verification record.
- Verified requires at least two independent source kinds: one official and one explorer or onchain source.
- Empty legacy placeholders never enter public address artifacts.
- CI rejects changed addresses that do not meet these rules.
Auditability
The canonical JSON, validation code, and change history are public at https://github.com/subsquid-labs/addybook. Download the NDJSON dataset with its SHA-256 manifest.