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. Developer Workflows

Deploying a New Vault

A deployment involves a single factory call followed by automatic registry listing. No manual proxy setup nor ABI juggling is necessary.

  1. Assemble facet bundle: Compile the set of facets that allow you to implement your strategy and load their function selectors into an array.

  2. Call deployVault on the VaultsFactory: Pass the facet bundle, the wrapped‑native token address, and the registry you want to join. The factory mints a Diamond proxy, wires the facets, emits VaultDeployed, and pushes the address into deployedVaults[].

  3. Registry handshake: The new vault registers itself in the chosen registry, marking it discoverable by front‑ends that filter on isFactoryVault.

  4. Verify on‑chain: Query getDeployedVaults() or listen for the VaultDeployed event to fetch the address and initial facet map.

PreviousDeveloper WorkflowsNextExtend with New Facets

Last updated 14 days ago