exSat Network
  • 🔗Important Links
  • 🌌Our Approach
    • What is exSat
      • exSat’s Docking Layer Approach
      • The Paradigm Shift of the Bitcoin Economic Ecosystem
      • Challenges Addressed by exSat
    • Architecture
      • Data Consensus Protocol
        • Network launch phases
        • Decentralized UTXO index
        • Synchronizers and Validators
        • Hybrid Consensus Mechanism
        • Decentralized execution
      • Decentralized Asset Custody (Coming soon)
      • Enhancing the Bitcoin Ecosystem with Smart Contract Capabilities
      • Expanding Possibilities with Rollups
    • $XSAT Tokenomics
      • Total Supply and Issuance
      • Rewards to Synchronizers and Validators
  • 🛠️Guides of Data Consensus
    • Quick Start
    • UTXO Initialization
      • Data preparation
      • Analysis on the UTXO data tobe uploaded
      • Verify the data uploaded to exSat
    • Run a Sychronizer
      • Requirements for Synchronizers
      • Rewards for synchronizers
      • Run as Synchronizer
        • Run from source code
        • Run with Docker
    • Run a BTC Validator
      • Requirements and rewards for BTC Validators
      • Run as BTC validator
        • Run from source code
        • Run with docker
    • Run a XSAT Validator
      • Run as XSAT Validator
        • Run from source code
        • Run with docker
      • Run multiple XSAT Validators
    • Others
      • Operation references
        • Preparation Before You Start
          • Account Preparation
          • Run a BTC node
          • Environment requirements
          • Prerequisites
        • Synchronizer operations
          • Create New Synchronizer Account
          • Synchronizer Registration
          • Execute the synchronizer client
          • Revote For Consensus
          • Change Reward Address
          • Check and claim rewards for synchronizer
          • Update to new Docker version for Synchronizer
        • Validator operations
          • Create New BTC Validator Account
          • Create New XSAT Validator Account
          • Stake for Validator and claim rewards
          • Change Stake Address
          • Change Commission Address
          • Change Commission Ratio
          • Configure Display Information for Your Validator Account
          • Execute the validator client
          • Update to new Docker version for Validator
        • Common operations
          • Import from seed phrase
          • Import from Private Key
          • Set BTC RPC Node
          • Refill BTC for Gas Fees
          • Export private key
          • Remove Your Account
          • Upgrade to new version
          • View Logs
          • Environment variables
  • 👨‍💻Developer Guides
    • Quick Start
    • Native Layer Developer Guides
      • exSat consensus contracts
        • Pool Register Contract
        • UTXO Management Contract
        • Reward Distribution Contract
        • Block Consensus Contract
        • Block Synchronization Contract
        • Validator Management Contract
        • Staking Contract
      • Run exSat native layer RPC Node
    • Trustless Bridge for Native Tokens
    • Trustless Bridge For ERC20 Tokens
    • Brief Intro to the Cross-Chain Communication
    • Brief Intro to the Custodian Bridge Services
    • Custodian Bridge for Non-BTC Tokens
    • Custodian Bridge for BTC
  • 🖥️User Guides
    • Wallet Setup
    • Bridge Your Assets
    • Earn Rewards via BTC Staking
    • Explore Our Ecosystem
  • Popular Token Contract Addresses
  • Set Up a Safe Wallet
  • 📚Reference
  • 📦Cutodian Guides
  • 🔐Security Reports
    • Audit Report From Blocksec
    • Audit Report From CertiK
  • 🔡Terms and Conditions
    • Terms Of Service
    • Privacy Policy
  • 🎁PR & Press
  • ☎️Contact US
Powered by GitBook
On this page
  1. Our Approach
  2. Architecture

Data Consensus Protocol

PreviousArchitectureNextNetwork launch phases

Last updated 3 months ago

Most blockchains operate on a state machine model, and Bitcoin adheres to this framework as well, comprising three key elements:

  1. State (Sn): This represents the current state of the blockchain, such as account balances or the present state of smart contracts. In Bitcoin's case, it refers to the set of UTXOs (unspent transaction outputs).

  2. Transactions (Txs) : The transactions are external inputs which trigger the State switch from current to the next. In Bitcoin's case, it refers to the new block data.

  3. State Transition Function f(x): This function describes how the blockchain’s state transitions from the current state to the next based on the new transactions. For Bitcoin, it encompasses all rules applied to UTXOs, such as the transfer rules.

exSat’s Data Consensus Protocol decentralizes and securely maps these three elements of Bitcoin onto the exSat network. This process includes:

  1. Storing Bitcoin's State Data: Using exSat's RAM to fully store Bitcoin’s state ,which's the complete set of UTXO data.

  2. Transaction Parsing: Each transaction from the uploaded Bitcoin blocks is parsed within exSat smart contract to update UTXO data. This parsing capability is also available to DApps, allowing them to filter their relevant Bitcoin transactions and build Bitcoin-based application databases directly on exSat.

PoW + PoS for Block Updates: (mining pools) and upload and verify the latest Bitcoin blocks on exSat in a decentralized pattern.

🌌
Synchronizers
Validators