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

Code Licensing and Royalties

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

The Flex IP Commons enables flexible and enforceable licensing of code assets through the use of smart contracts and programmable royalties. Developers can specify the licensing terms and conditions for their code NFTs, such as permissions, limitations, and pricing models, using standardized or custom license templates.

The licensing terms are encoded in the code NFT metadata and enforced by the IP Commons' smart contracts, which automatically grant or revoke access to the code based on the purchaser's compliance with the terms. The smart contracts also handle the distribution of royalties and fees to the code creators and other stakeholders, based on predefined revenue-sharing models.

The IP Commons supports various licensing models, such as one-time purchases, subscriptions, revenue-sharing, and pay-per-use, through the use of different token types and transfer mechanisms. For example, a subscription-based code NFT may require the purchaser to hold a certain amount of FLEXE tokens in their wallet to maintain access, while a pay-per-use code NFT may charge a micro-transaction for each function call or API request.

PreviousCode Versioning and ForkingNextCode Marketplaces and Auctions

Last updated 10 months ago