IPOR Protocol
  • The IPOR Protocol Documentation
  • IPOR Protocol V2
  • Research / Whitepapers
    • Conceptual Whitepaper
  • Audits
  • Community Links
  • IPOR Protocol Roadmap
  • IPOR FAQ
    • About the IPOR Protocol
    • Using the IPOR Protocol
    • Liquidity Mining
    • Swaps VS Perps
    • $FUSN Snapshot
  • About IPOR
    • Who Uses IPOR and for What?
    • Why IPOR?
    • IPOR Manifesto
  • IPOR Fusion ⚛️
    • Fusion Introduction
      • Defragmenting DeFi Yield
    • Why Fusion?
    • Users
    • Use Cases
    • Architecture Overview
      • Atomists
      • Alphas
    • Vaults
      • Access Management
    • Fuses
    • Security
      • For Liquidity Providers
      • For Vault Owners
      • Testing
    • Open-source Repository
    • Aragon Integration
  • IPOR Index
    • What is the IPOR Index
    • Working with the IPOR Index
    • IPOR stETH Index
  • Interest Rate Derivatives
    • Interest Rate Derivative
    • Index Calculation
    • IPOR Publication
    • IBT
    • Indicative Term Sheet
  • Automated Market Maker
    • The Automated Market Maker
    • Liquidity Provisioning
    • IPOR Swaps
      • Hedging example with Morpho protocol
    • Spread
      • Math behind the demand spread
    • Risk oracle
    • SOAP
    • Liquidations
    • Asset Management
  • Tokenomics
    • IPOR Token
    • Token distribution model
    • Power IPOR
    • Liquidity mining
      • Math behind the rewards contract
    • Power Token Liquidity Mining for Developers
  • IPOR DAO
    • IPOR DAO Governance
      • Discord - All Channels
      • Discord - Open Governance Forum
      • Discord - Formal Governance
      • Snapshot - Formal Governance
      • Governing Multisig wallets
    • Decentralizing IPOR
      • Configuration Parameters
  • Developers Docs
    • Fusion
      • Developing а Fuse
      • Configuring Pre-hooks
    • Deployed Contracts
      • Ethereum
      • Arbitrum
      • Base
    • Working with IPOR Router
    • ABI
    • V2 changes
    • IPOR Oracle
    • Vault Wrapper
Powered by GitBook
On this page
  • Verified Fuses
  • Verified Alphas
  • Timelocks
  • Access Management

Was this helpful?

Edit on GitHub
  1. IPOR Fusion ⚛️
  2. Security

For Vault Owners

PreviousFor Liquidity ProvidersNextTesting

Last updated 8 months ago

Was this helpful?

Verified Fuses

As an Atomist, your responsibility is to create the vault's strategy. Part of that is selecting fuses that will be used by the Alpha to operate the vault. All interactions with external parties are governed by the fuses. It is therefore vital that you verify the integrity of the fuses. IPOR DAO keeps a record of the fuses and their verification status. Also, each fuse, on this list is open-sourced and verified on Etherscan.

Verified Alphas

If you decide to let the 3rd party Alpha manage the vault you can select from Alphas in the IPOR Fusion network or an unverified Alpha. On the web app interface, each vault run by the authorized alpha will be marked.

Actions that an Alpha can take are limited by the connected fuses, actions such as swaps are constrained by the fuse configuration that you, as an atomist set up when adding or modifying the fuse list. Configuration is fuse-specific, but generally, you can limit the tokens that can be used or slippage in case of swapping.

Timelocks

When creating a vault, you will have to decide what the "minimum timelock" should be. This value defines how much time has to pass, from when you initiate changes to the vault's configuration until those changes can take effect. The minimum timelock will define how fast you can enact the changes, at the same time it will communicate to vault shareholders how much time will they have to act if they wish to move assets. The timelock can also be set to 0 in which case, all the changes would be instant.

Access Management

Access management in IPOR Fusion is handled by the . Roles are assigned during vault creation but some can be changed later. Please refer to a dedidcated page

OpenZeppelin Access Manager
Access Management