Demos Network Specifications
  • Introduction
    • What is Demos Network
    • Demos Network Architecture
  • FAQ
  • Cookbook
    • Project setup
      • Run the project (MacOS)
      • Run the project (Windows)
        • WSL 2 Setup on Windows (10 and 11 only)
        • Issue Troubleshooting
      • Run the project (Ubuntu)
  • SDK
    • Getting Started
    • WebSDK
      • Authentication
        • FIDO2 Passkeys
          • Under the Hood: FIDO2 Passkeys
      • NodeCalls
      • Transactions
        • Creating a transaction
        • Signing a transaction
        • Broadcasting a transaction
      • L2PS SDK
        • The l2ps module
        • Interacting with the L2PS
        • L2PS Messaging System
      • Instant Messaging
        • What is the Instant Messaging Protocol?
        • Architecture Overview
        • Encryption
        • Quickstart
        • Message Types
        • API Reference
        • FAQ
    • Cross Chain
      • General layout of the XM SDKs
      • EVM
      • BTC
      • Solana
      • MultiversX (EGLD)
      • NEAR
      • IBC
      • TON
      • XRPL
      • The XMScript
      • Identities
    • Demoswork
    • Cookbook
      • Demoswork
        • Creating work steps
        • Conditional Operation
        • Base Operation
        • Signing and broadcasting
      • Transactions
        • Crosschain Transaction
        • Native Transactions
      • SWAP
        • Crosschain SWAP
    • Web2
      • Quick Start
      • DAHR API Reference
        • Types
      • Making Requests
      • Identities
        • Twitter
        • GitHub
    • API Reference
    • Bridges
      • Rubic Bridge Test
    • Post Quantum Cryptography
  • Backend
    • Internal Mechanisms
      • Network Time Synchronization
      • Cross Context Identities
    • Global Change Registry
      • GCR Structure
      • How is GCR Synced?
    • Consensus Mechanism
      • Unparalleled Scalability
      • Decentralization in PoR-BFT
      • Enhanced Security
      • Comparative Advantage
      • Addressing Potential Criticisms
      • Conclusion
    • Communications Stack
    • L2PS (Subnet) Framework
      • How are L2PS transactions handled?
    • Miscellaneous
      • Browsing the Postgres DB via psql
    • Bridges
      • Rubic Bridge
    • Developers Testbed
      • Setting up the environment
      • Setting up the repository
      • Installing dependencies
      • Node Configuration
      • Running the node
  • Frontend
    • Demos Providers Discovery Mechanism
Powered by GitBook
On this page
  1. Backend
  2. Consensus Mechanism

Decentralization in PoR-BFT

Node Distribution Mechanism

  • Why: True decentralization requires balanced distribution of power and resources across the network.

    • Example: Unlike centralized systems where a few nodes control most operations, PoR-BFT employs mathematical algorithms to ensure node distribution across geographical regions and network segments through pseudorandom seed allocation.

Governance Structure

  • Why: Decentralized governance is crucial for maintaining network autonomy and preventing centralization of power.

    • Example: Traditional blockchain systems often face challenges with governance decisions being influenced by large stakeholders. PoR-BFT implements a weighted voting system based on mathematical proofs, ensuring more democratic decision-making.

Economic Incentives

  • Why: Proper economic incentives are essential to maintain decentralization and prevent wealth concentration.

    • Example: While some PoS systems favor wealthy participants, PoR-BFT's mathematics-based system rewards and encourages broader participation by considering factors beyond mere stake size, using mathematical formulas to calculate fair shard generation rotation.

Technical Architecture

  • Why: The technical design must support decentralization at its core.

    • Example: Unlike centralized databases or permissioned blockchains, PoR-BFT's architecture enables:

      • Distributed node validation through mathematical consensus

      • Peer-to-peer communication protocols

      • Decentralized storage solutions

      • Cross-shard coordination using pseudorandom seeds

Community Participation

  • Why: Wide community participation strengthens decentralization and network resilience.

    • Example: Unlike systems where technical barriers limit participation, PoR-BFT provides:

      • Lower hardware requirements through efficient resource utilization

      • Simplified node operation processes

      • Community-driven development initiatives

      • Mathematical verification of participation fairness

PreviousUnparalleled ScalabilityNextEnhanced Security

Last updated 7 months ago