FireDAO
English
中文English
English
中文English
  • FireDAO
  • 1. FireDAO Overview
    • 1.1 FireDAO Profile
      • 1.1.1 FAQ
    • 1.2 Mainnet Launch Announcement
    • 1.3 FireDAO Github
    • 1.4 Founding Team
    • 1.5 Get Started
      • 1.5.1 Minting PID to Obtain Forum ID
      • 1.5.2 Zealy Early Contributors Program
      • 1.5.3 Forum Bounty Program
      • 1.5.4 FireDAO Community Volunteers
    • 1.6 Development History and Milestones
      • 1.6.1 Development History
      • 1.6.2 Milestones
      • 1.6.3 Annual Roadmap
    • 1.7 Social Media
    • 1.8 Marketing and Partnerships
    • 1.9 Articles and Media Coverage
      • 1.9.1 Media Coverage of Rainbow City
      • 1.9.2 Media Coverage of FireDAO
      • 1.9.3 Historical Articles by RainbowKun
  • 2. The Construction of FireDAO
    • 2.1 Decentralized Society & Web3’s Soul
    • 2.2 The Essence of "Bit Civilization"
    • 2.3 Creation and Mission of RainbowCity
    • 2.4 Creation and Mission of FireDAO
    • 2.5 Phoenix Rebirth: Rising from the Ashes
  • 3. Overview
    • 3.1 Positioning
    • 3.2 Philosophy: Vision, Mission, Values
    • 3.3 Introduction of the Tokenomics
    • 3.4 How to join FireDAO
    • 3.5 FID and On-chain Reputation
    • 3.6 Community Activities
    • 3.7 Expansion of FireDAO Ecosystem
  • 4. Tokenomics
    • 4.1 Three Ecological Tokens
    • 4.2 Soulbound Account and FID Reputation System
    • 4.3 Introduction of Seven SBTs
    • 4.4 FDT Initial Issuance Plan
    • 4.5 FLM Initial Issuance Plan
    • 4.6 Ecological Revenue Sources for RainbowCity Treasury
    • 4.7 Allocation of RainbowCity Treasury Revenue
  • 5. Operational Structure
    • 5.1 FireSeed Invitation & Referral System
    • 5.2 Guild System
    • 5.3 Citynode System
    • 5.4 Global Community Management System
    • 5.5 Ecology Forum
    • 5.6 FLM Soul Airdrop and Rewards
    • 5.7 FDT Liquidity LP Mining
    • 5.8 FDT Lock-up Mining
  • 6. Community System
    • 6.1 Community Governance
      • 6.1.1 Governance Structure
      • 6.1.2 Proposal Threshold
      • 6.1.3 Voting Delegation
      • 6.1.4 Voting Execution
      • 6.1.5 Voting Result
      • 6.1.6 Result Execution
      • 6.1.7 Guardians Contract
    • 6.2 Community Participation and Contribution Guide
    • 6.3 Ecosystem Partners and Collaborative Projects
    • 6.4 Community Events and Competitions
    • 6.5 Community Support and User Services
  • 7. FireDAO Technical and Design
    • 7.1 Development Overview
    • 7.2 Development Structure
    • 7.3 Development Documentation and Sample Code
    • 7.4 Decentralized Data Storage
    • 7.5 Integration and Extensibility Interfaces
    • 7.6 User Guides & Tutorials
    • 7.7 Frontend Files and Tutorials
    • 7.8 Contract Risks and Audits
    • 7.9 Subgraphs and Decentralized Indexing
  • 8. Risk Management and Security
    • 8.1 Project Risks and Considerations
    • 8.2 Data Security and Privacy Protection
    • 8.3 Smart Contract Audit and Security
    • 8.4 Community Governance and Risk Management
  • 9. Legal Compliance and Disclaimer
    • 9.1 Legal Compliance and Regulatory Requirements
    • 9.2 Disclaimer and Limitation of Liability
    • 9.3 Intellectual Property and Open Source Licenses
Powered by GitBook
On this page

Was this helpful?

  1. 6. Community System
  2. 6.1 Community Governance

6.1.6 Result Execution

If the proposal is approved, the result will be queued in Timelock with a Timelock delay of 2 days. After the Timelock period ends, any account can apply the changes in the proposal to the target contract, which will access each operation in the proposal.

Previous6.1.5 Voting ResultNext6.1.7 Guardians Contract

Last updated 1 year ago

Was this helpful?