Registries as Boundaries

Registries sit at the protocol level, and facilitate both authenticity and risk management. Both permissioned and permissionless registries offer the DAO the ability to list, delist, or rate-limit vaults and facets without impacting user funds. The table below explores how registries serve to authenticate vaults for the entire ecosystem.

Registry	Control Surface	Use Case
VaultsRegistry	Admins can delist facets, cap protocol-level fees, or rotate the oracle pointer.	Mainnet deployments where vaults must adhere to DAO-approved configuration.
PermissionlessVaultsRegistry	No facet allow-list, zero protocol fee, same timelock for oracle updates.	Unsupported protocols, testnets, experimental chains, hackathons.

Because every vault checks isVaultRegistered during critical calls, delisted vaults can be flagged instantly by front-ends and indexers without pausing the contracts themselves. The abstract base registry defines common hooks so alternative trust models can inherit the same interface.