Data Sources and Methodology
Content source
Every resource in the Web3 Builder Hub is curated by the DIA team. There are two stores behind it. The resource tables — RPC URLs, chain IDs, faucet links, wallet compatibility and the metadata beside them — live in Notion databases, one per chain and category. The page copy around those tables lives in this site's own repository as markdown, one file per page.
Publishing pipeline
Page copy is read from the markdown files at build and request time. Resource tables are fetched from the Notion Official API on render. Both are parsed into structured blocks and drawn by custom React components. Pages use Incremental Static Regeneration with 60-second revalidation: the first request after that window rebuilds the page against fresh data. The Notion response cache has a 24-hour TTL, so a table edit can take up to a day to appear.
Verification process
Verification is manual, done by the DIA team. There is no automated uptime monitor behind these listings. An RPC endpoint is called and checked for a response and the expected chain ID before it is added. A faucet is used once to confirm it still delivers tokens. Wallet listings are checked against the wallet's own documentation and release notes for current chain support. Testnet configurations — chain ID, block explorer URL, native currency symbol — are read off the chain's official documentation.
Because the checks are manual, they happen on a rolling basis rather than on a schedule. A resource that goes down between reviews stays listed until someone notices.
Update frequency
New chains are added at testnet or mainnet launch. Deprecated testnets are removed. RPC provider changes are reflected within the update cycle. The DIA team monitors chain announcements and ecosystem changes to keep the directory current.
Limitations
Resources in the Builder Hub link to third-party services. DIA does not operate the RPCs, faucets, or wallets listed. Availability of external services is outside DIA's control. If a listed resource is offline or a link is broken, report it via our contact form.