Content source

All resources in the Web3 Builder Hub are maintained in Notion databases by the DIA team. Notion serves as the headless CMS. Each chain and each resource category exists as a structured page with fields for RPC URLs, chain IDs, faucet links, wallet compatibility, and related metadata.

Publishing pipeline

Content is fetched via the Notion Official API, parsed into structured blocks, and rendered with custom React components. Pages use Incremental Static Regeneration with 60-second revalidation. When the Notion source is updated, the next page request after the revalidation window triggers a rebuild with fresh data. The Notion page cache has a 24-hour TTL.

Verification process

RPC endpoints are tested for HTTP 200 response and correct chain ID return. Faucets are verified for token delivery. Wallets are checked for current chain support against the wallet's documentation and release notes. Testnet configurations are validated against the chain's official documentation, including chain ID, block explorer URL, and native currency symbol.

Verification happens on a rolling basis as chains update their infrastructure.

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 Telegram.