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
  • 🖥️User Guides
    • Wallet Setup
    • Bridge Your Assets
    • Earn Rewards via BTC Staking
    • Explore Our Ecosystem
  • Popular Token Contract Addresses
  • 📚Reference
  • 📦Cutodian Guides
  • 🔐Security Reports
    • Audit Report From Blocksec
  • 🔡Terms and Conditions
    • Terms Of Service
    • Privacy Policy
  • 🎁PR & Press
  • ☎️Contact US
Powered by GitBook
On this page
  • Native Layer
  • EVM Layer
  • Trustless Bridge between the Native and EVM Layers
  1. Developer Guides

Quick Start

PreviousEnvironment variablesNextNative Layer Developer Guides

Last updated 6 months ago

exSat consists of two layers: the Native Layer and the EVM Layer

Native Layer

The Native Layer is built using , with smart contracts written in C++ and running on the WebAssembly (WASM) runtime. It provides high performance and instant finality (blocks become irreversible in just 1 second). Data is managed in a database format, making it suitable for large-scale data processing and high-performance operations. Bitcoin data is stored in the database on the native layer. Developers working on this layer can directly read UTXOs, block headers, and the exSat consensus state, facilitating the creation of high-performance Bitcoin DApps.

EVM Layer

The EVM Layer is fully compatible with Ethereum's Shanghai upgrade and supports smart contract development using Solidity, a widely adopted language among blockchain developers. Most smart contracts running on Ethereum can be seamlessly executed on exSat's EVM Layer without modification. In the near future, smart contracts on the EVM Layer will also be able to access Bitcoin UTXOs, block headers, and other Bitcoin data from the exSat Native Layer.

Trustless Bridge between the Native and EVM Layers

The Native and EVM Layers can communicate seamlessly through a trustless bridge, enabling bi-directional token and message transfers. Contracts on both layers can interact with one another. By using this trustless bridge, developers can store DApp data and core logic on the Native Layer while managing user interactions on the EVM Layer, optimizing the full potential of exSat.

👨‍💻
Spring technology