🔳
Sector Finance
  • 🔳WELCOME!
    • Introduction
    • Using Sector
    • FAQ
  • 🛠️PRODUCTS
    • Product Suite
      • Aggregator Vaults
      • Single-Strategy Vaults
    • Strategies
      • Delta-Neutral LP
      • Leveraged Delta-Neutral LP
      • Leveraged Convex Strategies
      • Lending
    • Risks
  • ⚙️Risk Engine
    • Description
    • Mechanics
    • Auto-Rebalancing
  • 🏛️SECTOR DAO
    • Tokenomics
    • veSECT
    • Permissions Architecture
  • 📚RESOURCES
    • Contracts
    • Audits & Bug Bounty
    • Github
Powered by GitBook
On this page
  1. SECTOR DAO

Permissions Architecture

PreviousveSECTNextContracts

Last updated 2 years ago

Sector is a non-custodial protocol. This means the admins of the Sector smart contracts will never be able to walk away with user funds.

For a protocol like Sector this is a challenge because the team needs to have an ability to add, remove and update investment strategies. To ensure the protocol remains non-custodial, we are putting all critical owner actions like adding strategies or changing configuration parameters behind a Timelock contract with an initial delay of 5 days. This means any owner transactions will first need to be submitted to the Timelock contract and 5 days will need to pass before the transaction can be executed. This gives users 5 days to inspect the pending admin transaction and decide whether it is safe to keep their deposits in the pool.

Diagram of the permissions architecture:

🏛️