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
  • Transaction criteria
  • Transaction structure:
  1. Protocol
  2. Flex Validator Nodes
  3. Getting Started

Transaction Pool Generation

Flex is a community-owned platform that rapidly boosts dApp user growth through a multi-chain, proof-of-collaboration protocol. The Validator node's Data layer creates a Transaction pool:

After being assigned to a validator node, your on-chain and social activities within the Flex ecosystem are meticulously tracked and mapped into a transaction pool. This crucial process is handled by the data layer of the validator node, forming an integral part of the Flex network's architecture.

Note that running the Flex node enables you to earn rewards by contributing to tasks while the node in the background also serves a dual purpose by making you a validator of other network participants' activity.

The generation and maintenance of this transaction pool play a vital role in ensuring the network's trustlessness and tamper resistance. By recording and storing your actions in this secure manner, Flex maintains a transparent yet privacy-conscious system that accurately captures all your contributions to the ecosystem.

Transaction criteria

The transaction pool consists of community member wallet addresses and their Off-chain and On-chain activities.

In this layer, every single activity completed by the community member is mapped in the pool.

Examples of off-chain transactions:

  • Liking a post on X

  • Posting a video on Youtube

  • Following another community member

Examples of on-chain transactions:

  • Staking ecosystem project tokens

  • Minting ecosystem Project NFTs

  • Deploying a smart contract on ecosystem project infrastructure

Transaction structure:

The transaction pool structure is as follows:

// Transaction Structure

{
    "wallets": [
        {
            "address": "0x1234567890abcdef1234567890abcdef12345678",
            "actions": {
                "onchain": [
                    {
                        "action_id": "onchain_001"
                    },
                    {
                        "action_id": "onchain_002"
                    }
                ],
                "offchain": [
                    {
                        "action_id": "offchain_001"
                    },
                    {
                        "action_id": "offchain_002"
                    }
                ]
            }
        },
        {
            "address": "0xabcdef1234567890abcdef1234567890abcdef12",
            "actions": {
                "onchain": [
                    {
                        "action_id": "onchain_003"
                    },
                    {
                        "action_id": "onchain_004"
                    }
                ],
                "offchain": [
                    {
                        "action_id": "offchain_003"
                    },
                    {
                        "action_id": "offchain_004"
                    }
                ]
            }
        }
    ]
}

PreviousPropagation into the Validation LayerNextTransaction Weight Assignment

Last updated 10 months ago