blob-list is a public, evidence-backed registry that maps blob-submitting EVM addresses to entities. It is additive to ethereum-lists/chains: chain metadata, RPC URLs, explorers, currencies, and parent-chain relationships remain there, while this repo focuses only on attribution claims.
The registry is intended for blob explorers, dashboards, wallets, researchers, and data pipelines that need to answer: "Which entity submitted this blob transaction sender at this block?"
- Blob-submitting EVM addresses, grouped by entity.
- Block-range validity for each attribution.
- Evidence for every address claim.
- Chain references using CAIP-2 IDs such as
eip155-1. - Entities that are not necessarily chains, including infrastructure providers, bridges, exchanges, research users, and individuals.
entities/ Source YAML, one file per entity.
schemas/ JSON Schemas for source and generated artifacts.
tools/ Fetch, validate, and generate scripts.
data/chainlist/ Vendored Chainlist lockfile snapshot used by CI and releases.
artifacts/ Generated JSON artifacts for consumers.
icons/local/ Local icons only for entities not represented by Chainlist.
data/chainlist/snapshot.json is a vendored lockfile for the subset of
Chainlist entries referenced by source YAML. It exists to keep local validation,
CI, and release generation deterministic; it is not registry-owned chain
metadata. If chain facts drift upstream, refresh the snapshot with
npm run fetch-chainlist or let the scheduled refresh workflow open a PR.
- Load
artifacts/by-chain/{submission_chain}.json. - Normalize the transaction sender to a checksummed EVM address.
- Find address claims for that sender.
- Filter claims by block number.
- Prefer active, non-disputed, highest-confidence claims.
- Display the entity name, role, confidence, chain refs, and icon metadata.
npm ci
npm run fetch-chainlist
npm run generate
npm run validateBefore opening a pull request, run:
npm run format:check
npm run lint:md
npm run generate
npm run validate
npm run generate:checkPull request CI regenerates artifacts from the submitted source files and posts
the projected Chainlist snapshot and artifact diff as a PR comment. Attribution
PRs should include source YAML, schemas, docs, or icons only; CI rejects
committed data/chainlist/snapshot.json changes in attribution PRs, rejects
committed artifacts/ changes, and publishes at/generated-data for a
generated-data PR after merge.
Dataset releases use semver-style tags. Merges to main that add one or
more address attribution claims automatically publish the next minor release.
Manual tag pushes matching v*.*.* can still publish explicit releases for
schema changes or patch fixes.
- Major: schema changes.
- Minor: new entities, chains, or attribution claims.
- Patch: metadata, evidence, typo, or icon fixes.
Release artifacts include generated JSON files and SHA256 checksums.