MORE
  • Introduction
  • MORE Vaults
    • Vaults Framework
      • Diamond Standard (EIP-2535)
      • Component Interactions
      • Upgrade & Governance Flow
    • Core Protocol Components
      • Factory
      • Core Facets
      • Registries
      • Internal Libraries
      • Accounting
    • Connectors
      • AMMs & DEXes
      • Staking
      • Lending
      • Leverage
      • Oracles
      • External Interfaces
      • Multicall
    • Security & Governance
      • Roles & Access Control
      • Upgrade Flow & Timelock
      • Configuration Guard Rails
      • Registries as Boundaries
      • Error & Event Catalogue
    • Developer Workflows
      • Deploying a New Vault
      • Extend with New Facets
      • Indexer Integration
    • Reference & Glossary
      • Event Index
      • Capabilities
      • Terms & Abbreviations
      • Contracts
  • MORE Markets
    • Markets Framework
      • Liquidity Protocol
      • Supply
      • Borrow
      • Repay
      • Withdraw
      • Liquidations
      • Flash Loans
      • Risks
    • Markets
      • Liquidity Pool
      • Reserve
      • Incentives
      • Oracles
    • Contracts
    • Build
  • Resources
    • Code, Licenses & Audits
    • Brand Assets
  • Privacy Policy
  • Terms of Use
Powered by GitBook
On this page
  1. MORE Vaults
  2. Security & Governance

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.

PreviousConfiguration Guard RailsNextError & Event Catalogue

Last updated 14 days ago