protocol identification
two sourcesIdentification (as of September 4, 2026). Name: BlackRock USD Institutional Digital Liquidity Fund (BUIDL), tokenized and serviced by Securitize. Website: Securitize BUIDL product page. Docs: No public technical documentation repository was located; the operational interface is Securitize’s BUIDL page and bridge. Category: permissioned, institutional RWA/tokenized money-market fund—not a conventional permissionless DeFi protocol. Launch: March 20, 2024, initially on Ethereum. Chains: Ethereum, Arbitrum, Avalanche, BSC/BNB Chain, OP Mainnet, Polygon, Solana, and Aptos. Securitize confirmed the first seven by March 25, 2025; BNB Chain was added subsequently.
Native token: no governance or protocol token. “BUIDL” is the fund-share/security token, with permissioned transfers and issuer-controlled compliance functions. Contract identifiers / verification. Independent listings agree on these primary identifiers: Ethereum 0x7712…2aec; Arbitrum 0xa652…5872; Avalanche 0x53fc…6a2f; BSC 0x2d5b…f84f; OP Mainnet 0xa1cd…7cf5; Polygon 0x2893…0e99; Solana GyWgeq…6phr; Aptos 0x5003…5f89. Full addresses and a Dune cross-check are Not verifiable as of September 4, 2026 because Dune MCP was unavailable. The registry reports explorer/source verification for Ethereum and Solana and explorer verification for the EVM deployments, but this was not independently re-run here.
> Contradiction / evidence gap: DeFiLlama labels BUIDL as eight-chain and supplies the same truncated identifiers; no raw on-chain/Dune query is available to validate balances, deployment provenance, or chain-by-chain canonical-vs-bridged status. Fork lineage. BUIDL is not evidenced as a fork of an upstream DeFi protocol; it is an issuer-specific tokenized fund deployment. Therefore, “what changed versus upstream” is not applicable.
Public audit evidence for the canonical BlackRock/Securitize deployments, including scope-to-address mapping and whether all eight deployments were audited, is Not verifiable as of September 4, 2026. Search results contain audits for unrelated “BUIDL Official” projects using the same ticker/name, a material name-collision risk. A verified malicious-modification history in comparable BUIDL forks is Not verifiable as of September 4, 2026.