Flex Docs (Work-In-Progress | Last Updated: 12/07)
  • Current Landscape
  • Welcome to Flex
  • Overview
    • Infrastructure for the New Web
    • The Values of the Flex Ecosystem
  • Protocol
    • Flex Validator Nodes
      • Data and Validation Layer
      • Rewards Layer
      • Audit Layer
      • Sentinel Layer
      • Prediction Layer
      • Getting Started
        • Propagation into the Validation Layer
        • Transaction Pool Generation
        • Transaction Weight Assignment
        • Epoch Score Calculation
        • Reward Distribution
        • Reward Claiming
        • Epoch Reward Pool Mechanics
    • Proof-of-Collaboration (PoCol)
      • PoCol Governance using FLEXE
      • Actors in the Flex Ecosystem
    • Flex Commons
      • Code Tokenization
      • Code Registry and Indexing
      • Code Versioning and Forking
      • Code Licensing and Royalties
      • Code Marketplaces and Auctions
      • Code Search and Discovery
      • Flex Commons Governance using FLEXE
    • Ecosystem Tokens' Multi-Staking
    • Technical Roadmap for the Flex Ecosystem
      • Flex Virtual Machine (FVM)
      • Flex SDCK
      • re:Flex Smart Contract Language
    • Flex Improvement Proposal (FIP)
    • Flex Portal: Your Gateway to Web3
  • Contribute to the Ecosystem
    • Strategists: Roles and Contributions
    • Developers and Projects
  • Governance and Utility
    • Introducing the FLEXE Token (coming soon)
    • Flexonomics (coming soon)
    • How to get FLEXE tokens (coming soon)
      • Use the faucet (coming soon)
      • Run a node (coming soon)
  • Quicklinks
    • Supported Social Media
    • Official Website
  • Legal
    • Terms of Service
    • Privacy Policy
    • Digital Asset Disclosure (coming soon)
Powered by GitBook
On this page
  1. Protocol
  2. Flex Commons

Flex Commons Governance using FLEXE

Flex is a community-owned platform that rapidly boosts dApp user growth, ensuring the value generated directly benefits the Flex community.

The FLEXE token is a pivotal element in the governance structure of the Flex ecosystem, facilitating a decentralized and community-driven approach to managing the Flex Commons for ecosystem IP. In this context, FLEXE will be used primarily by the contributors and consumers of IP.

The IP Commons features a decentralized reputation and governance system for curating and maintaining the quality and integrity of the code registry. Developers can earn reputation scores and governance rights by contributing and reviewing code assets, and by participating in the platform's decision-making processes. Developers can mint new code NFTs by staking FLEXE tokens, the number of which will be determined by an on-chain vote. This staking requirement helps prevent spam and ensures that only high-quality submissions are added to the registry.

The reputation scores are calculated based on various metrics, such as the quality, popularity, and usage of the developer's code contributions, as well as their activity and behavior on the platform. Higher reputation scores unlock additional privileges and rewards, such as featured listings, higher royalty rates, and weighted voting power.

R=(QxU)/TR= (Q x U)/T R=(QxU)/T

where: Q is the quality score, 𝑈 is the usage metric, and 𝑇 is the total contributions (count).

The IP Commons also employs dispute resolution and arbitration mechanisms to handle code ownership, licensing, and quality disputes. Developers can stake FLEXE tokens to challenge or defend code NFTs, with the disputes being resolved by a decentralized panel of expert judges (holographic consensus model), who are incentivized to provide fair and accurate rulings based on predefined guidelines and evidence.

The steps involved in participating in Flex Commons governance derive from the overall Proof-of-Collaboration (PoCol) governance framework.

PreviousCode Search and DiscoveryNextEcosystem Tokens' Multi-Staking

Last updated 10 months ago