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 Validator Nodes
  3. Getting Started

Propagation into the Validation Layer

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

PreviousGetting StartedNextTransaction Pool Generation

Last updated 10 months ago

After successfully joining as a node operator, your account undergoes a crucial "propagation" process. During this phase, your wallet address is entered into a distributed wallet pool across the network. This important step occurs before you're assigned to the existing validator network. Every node operator is a validator for their peers, assignment for which (peer and task) is randomly assigned with weight criterion for FLEXE token stakers and for validators with high node uptime levels, and long validation history.

Purpose of Propagation:

  • Ensures fairness in the validation process

  • Prevents potential manipulation by malicious validators

  • Protects against unfair scoring of your account

Rules for Propagation:

  • There should be no correlation between the geography of the wallet and the geography of the validator validating it

  • The process of wallet assignment must be agreed upon by more than 50% of the validators

How the propagation works

  1. The Flex smart contract adds connected wallets to the wallet pool. The wallet pool is a list of wallets in chronological order of being connected.

  2. Every Epoch (defined as 00:00 UTC), the validators begin sending requests to the wallet pool.

  3. Once the validator is assigned a wallet from the wallet pool, they must wait for 10 Seconds until they can request the next wallet. This ensures fairness such that a validator with more computing power does not necessarily outperform another.

Overview of wallet propagation