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. Core Protocol Components

Registries

Once deployed, a vault registers with a contract that attests to its legitimacy and, optionally, enforces facet allow-lists.

Registry variant
Purpose
Enforcement model

BaseVaultsRegistry

Abstract template that tracks vault addresses and exposes role-based admin hooks. Other registries inherit from it.

N/A (abstract)

VaultsRegistry

Permissioned registry. Admins can add/remove facets and cap protocol-level fees, giving governance a circuit-breaker.

Facet allow-list + protocol-fee ceiling

PermissionlessVaultsRegistry

No facet allow-list and zero protocol fee. Anyone can deploy, aligning with testnets, experimental chains or protocols not included in VaultsRegistry.

None (open)

Registries are replaceable per network: a DAO can run a permissioned registry on mainnet as well as permissionless ones, without touching factory code.

PreviousCore FacetsNextInternal Libraries

Last updated 16 days ago