LogoLogo
AddressesAuditsGitHub
  • πŸ“₯Introduction
  • πŸŒ€Products
    • Introduction
    • Best Yield
      • Overview
      • Guides
        • Deposit funds on BY
        • Redeem funds on BY
      • FAQs
    • Yield Tranches
      • Overview
      • Adaptive Yield Split
      • Security
        • Covered risks
      • Guides
        • Deposit funds on YTs
        • Redeem funds on YTs
        • Live YTs guides
          • Lido stETH
      • FAQs
    • Fee structure
    • Get involved
      • Integrators program
      • Institutions program
  • πŸ’»Developers
    • Introduction
    • Networks and codebase
      • Ethereum mainnet
      • Polygon
      • Kovan testnet
      • ERC-4626 standard
    • Best Yield
      • Architecture
      • Deployed contracts
        • Ethereum
        • Optimism
      • Interface
      • Methods
        • mintIdleToken
        • redeemIdleToken
        • redeemInterestBearingTokens
        • rebalance
        • tokenPrice
        • tokenPriceWithFee
        • getAPRs
        • getAvgApr
        • userAvgPrices
        • getGovTokensAmounts
        • getAllocations
        • getGovTokens
        • getAllAvailableTokens
        • getProtocolTokenToGov
      • Edge cases
      • Security management policy
      • Get integrated as yield source
      • Get user earnings
    • Yield Tranches
      • Architecture
      • Deployed contracts
        • Ethereum
        • Polygon zkEVM
        • Optimism
      • Interface
      • Methods
        • AAStaking
        • BBStaking
        • AATranche
        • BBTranche
        • depositAA
        • depositAARef
        • depositBB
        • depositBBRef
        • fee
        • getApr
        • getContractValue
        • getCurrentAARatio
        • getIncentiveTokens
        • lastNAVAA
        • lastNAVBB
        • strategy
        • strategyToken
        • token
        • trancheAPRSplitRatio
        • tranchePrice
        • virtualPrice
        • withdrawAA
        • withdrawBB
      • Integration example
      • Edge cases
      • Security management policy
      • Subgraph
    • API
    • Security
      • Hats Finance vault
      • Hypernative monitoring
      • Immunefi bug bounty
      • Integration Standard Requirements
      • Risk Framework
      • Smart contract audits
  • πŸ›οΈGovernance
    • Introduction
    • Idle DAO
      • Governance process
        • Governance forum
        • Governance dashboard
        • Snapshot IDLE
        • Snapshot stkIDLE
      • Idle Leagues
        • Communication League
        • Development League
        • Treasury League
        • Leagues contributors
      • Treasury
        • Reports
      • Governance guides
        • How to monitor off-chain voting pools
        • How to propose an IIP
        • How to create an on-chain proposal
        • How to delegate votes
        • How to vote for an IIP
      • FAQs
    • IDLE token
      • Distribution
      • Use cases
        • Lending, borrowing & collateral
        • DEXs liquidity provision
      • Buybacks
      • Delegates
      • CoinGecko
    • IDLE staking
      • Prime staking
        • Examples
      • Staking integration
      • Guides
        • How to stake your IDLE
        • How to vote in Gauges
        • How to boost your $IDLE rewards
        • How to give VEV
  • πŸ—‚οΈOther
    • Brand assets
    • Guides
      • How to see IDLE in your wallet
      • Deposit funds through Idle
      • Deposit funds through smart contracts
      • Redeem funds through Idle
      • Redeem funds through smart contracts
    • FAQs
    • Glossary
    • Resources
    • Archive
      • πŸ‘‡Get in touch
        • πŸ›οΈGovernance Forum
        • πŸ†Idle Grants Program
        • πŸ‘ΎDiscord
        • 🐦Twitter
      • Gauges
        • Architecture
        • Deployed contracts
        • Gauges repository
        • stkIDLE repository
      • Gauges
        • Gauges integration
        • FAQs
      • Boost
      • DEXs liquidity provison
      • Risk Adjusted (deprecated)
      • Deployed contracts
      • Idle Smart Treasury (deprecated)
      • Ethereum LP staking (deprecated)
      • Polygon LP staking (deprecated)
      • Flash Loans (deprecated)
      • QuickSwap cxETH-WETH
      • Integrate PYTs
      • Idle Grants program
      • Idle on Polygon
        • Add Polygon network to MetaMask
        • Bridge $IDLE to Polygon
        • Deposit funds on Polygon
        • Add liquidity to $IDLE pools
        • Stake IDLE LP tokens on Polygon
Powered by GitBook

Ecosystem

  • Website
  • App
  • Governance
  • Brand assets

Developers

  • Feedback
  • GitHub
  • Bug bounty
  • Audits

Community

  • Blog
  • Twitter
  • Telegram
  • Discord

Analytics

  • Stats
  • Dune
  • DeFiLlama
  • CoinGecko
On this page

Was this helpful?

  1. Governance

Idle DAO

Governance > Idle DAO

Last updated 1 year ago

Was this helpful?

Since November 26th, 2020, the Idle protocol is governed and owned by a DAO powered by the . The Idle DAO promotes key activities to ensure proper protocol maintenance and improvements in the years to come.

  • Name: Idle DAO LLC

  • Address: Long Island Road, Majuro, MH 96960, Marshall Islands

  • Licence duration: 5 years from June 23rd, 2023

Reference:

The Idle DAO, composed of $IDLE token holders, enables community participants to drive and contribute to the protocol’s future developments.

Protocol changes are implemented through IIPs (Idle Improvement Proposals). Idle governance is based on the Governor Bravo governance architecture, for a more in-depth description of all methods available please refer to the official guide .

All admin powers have been transferred to $IDLE holders, allowing the community to lead the maintenance and development of the protocol.

The ability to pause deposits and rebalances is still in place for security purposes in case of emergencies and is maintained by the Guardian multisig. The guardian can be changed at any time by the DAO with a proposal.

The Security Management Policy for the protocol is further explained and .

In early 2021, Idle DAO decided to implement a , as a solution to the scaling problems that DAOs face.

Given the amorphous nature of the organizational structure of a DAO, varied participation often occurs and most members tend towards relatively passive participation. Rather than leaving every $IDLE token holder with the burden of planning, executing, and voting on all the protocol aspects, each subDAO takes care of the daily maintenance of the related area of expertise using the budget assigned by $IDLE token holders, on a mandate basis.

πŸ›οΈ
IDLE governance token
Governance post
here
here for BY
here for YTs
Leagues (subDAOs) model
13MB
Idle DAO LLC - Corporate Charter Certificate.pdf
pdf
481KB
Idle DAO LLC - FIBL Certificate.pdf
pdf
2MB
Idle DAO LLC - Operating Agreement.pdf
pdf