# exSat’s Docking Layer Approach The philosophy of the exSat Network is to extend Bitcoin's powerful and well established trust based on the data and assets within the Bitcoin ecosystem. This allows for more possibilities in functionality, scalability, utility and interoperability of Bitcoin assets and empowers the omnichain application ecosystem. Ultimately, it aims to provide an intent-centric user experience for more Web3 users. At the core of exSat's innovative approach lies the philosophy of extending Bitcoin's powerful consensus by leveraging the data and assets within the Bitcoin ecosystem. This data and asset-driven integration unlocks new possibilities for Bitcoin assets, empowering a powerful bedrock for the omnichain application landscape.
# Challenges Addressed by exSat Bitcoin's ecosystem development has suddenly exploded, catalyzed by the emergence of groundbreaking technologies and innovative solutions that extend the utility and reach of the world's premier cryptocurrency. This rapid expansion has unlocked new frontiers, driving mainstream adoption and solidifying Bitcoin's position as a versatile and indispensable asset in the burgeoning DeFi and Web3 landscapes. Drawing parallels to Ethereum's growth trajectory, the Bitcoin ecosystem will likely experience user adoption surges driven by viral use cases that kickstart the flywheel. This, in turn, will attract more developers and increase the ecosystem's application TVL. Considering Bitcoin’s $1.3T market capitalization is about 3 times that of Ethereum’s $400B, while its application TVL is currently only a tiny fraction at about $364 Million compared to Ethereum’s $112B, this scenario presents a potential tenfold growth opportunity for the Bitcoin ecosystem to reach the similar level of maturity on the application front as Ethereum, not counting additional liquidity influxes once the ecosystem gains momentum. #### **The landscape of Ethereum Ecosystem** \~$390B MCap, 30+ Layer2 chains, 124M+ users, and 5000+ DApps #### **The landscape of Expected Bitcoin Ecosystem** \~$1200B MCap, 70+ Layer2 chains, 300M+ users, and many more DApps are coming \*Data source: Crypto.com Despite Bitcoin's immense growth potential and vast market opportunities, we must recognize that its network attributes and infrastructure differ significantly from Ethereum, creating challenges for dapp development. To address these limitations, it is essential to offer diverse solutions that comply with Bitcoin’s network requirements while resolving the issues hindering dapp development, and build infrastructure that is more conducive to dapp innovation.
# Architecture exSat introduces a first-of-its-kind Docking Layer solution to overcome the siloed nature of existing blockchain infrastructures, for a more interconnected, efficient, and versatile blockchain ecosystem. Unlike typical L2 solutions that aim to increase transaction speed or reduce costs, exSat introduces [a Docking Layer](/approach/what-is-exsat/exsats-docking-layer-approach) to scale the Bitcoin ecosystem comprehensively.
# Expanding Possibilities with Rollups exSat, powered by Antelope, provides a modular blockchain solution that enhances the Bitcoin ecosystem. It serves as both Data Availability (DA) and settlement layer within rollup systems, streamlining the deposit and withdrawal processes and bolstering trust in Bitcoin L2 solutions. Developers can leverage exSat to create secure and efficient Bitcoin L2 solutions with minimal effort and resources.
exSat provides the DA and settlement layer for BTC. This naturally enabled all the Rollup solutions including Optimism (OP) and ZK. As both DA and settlement are performed on exSat, we don’t need Data Availability Sample (DAS) for data publication. The verification of Zero-Knowledge Proofs (ZKP) from Bitcoin L2 Rollups are executed on exSat.
This modular approach allows developers to customize Bitcoin L2 solutions to meet diverse requirements, promising a flourishing ecosystem of DApps as Bitcoin continues to evolve.
For the modular scaling solution architecture, please refer to the figure below.
# $XSAT Tokenomics The economic framework for exSat is deeply rooted in the principles that guided Bitcoin's original launch, embodying a commitment to transparency and equality. This is reflected in our adoption of a fair launch strategy for the distribution of the official exSat token, XSAT. # Total Supply and Issuance * **Total Supply:**\ The total supply of XSAT is capped at 21,000,000 tokens, mirroring the supply of Bitcoin. * **Issuance and Halving:**\ The issuance of XSAT rewards follows a structure similar to Bitcoin's halving rules. The exSat network begins synchronizing Bitcoin blocks starting from block height 840,000, which is also when XSAT rewards start to be distributed. Rewards are issued after each Bitcoin block is processed and becomes irreversible. Initially, the reward per block is 50 XSAT. Every 210,000 Bitcoin blocks (approximately every 4 years), the block reward is halved. # Rewards to Synchronizers and Validators The distribution of XSAT rewards differs before and after the [BTC and XSAT staking phase](https://docs.exsat.network/approach/usdxsat-tokenomics/pages/HN9EbwSXkw8VEDM0jci8#id-3.-btc-and-xsat-staking-coming-soon) begins. ### Before **BTC & XSAT Staking phase (**Deprecated from 2025.5.8) * **Synchronizer:**\ A Bitcoin mining pool that has mined at least one block within the last **432 blocks** qualifies as a Synchronizer. A Synchronizer that successfully uploads and completes the parsing of a Bitcoin block will earn **10% of the current block rewards**. If the Bitcoin block was mined by the same Synchronizer, the reward increases to **50%**. * **Validator:**\ Participants can stake at least **100 $BTC** to qualify as a BTC Validator. * The first 2/3 of Validators to submit the correct Bitcoin block hash will share 10% of the current block rewards, distributed proportionally based on their staked BTC. * Validators who submit the correct Bitcoin block hash will receive 40% to 80% of the current block rewards, depending on whether the Synchronizer that uploaded the block also mined it on the Bitcoin network. XSAT rewards are distributed among these Validators proportionally to their staked BTC. ### After **BTC & XSAT Staking phase (Enabled on 2025.5.8)** * **Synchronizer:** A Bitcoin mining pool that has mined at least one block within the last **432 blocks** qualifies as a Synchronizer. A Synchronizer that successfully uploads and parses a Bitcoin block will receive 10% of the current block rewards**.** If the Bitcoin block was mined by this Synchronizer on the Bitcoin network, the reward increases to 15%. * **Validator:** * **XSAT Validator:**\ Participants can stake **2,100 $XSAT** to qualify as an XSAT Validator. A qualified XSAT Validator that submits the correct Bitcoin block hash will receive 20% of the block rewards, which will be distributed evenly among all XSAT Validators. Delegate staking is not permitted for XSAT Validators. * **BTC Validator:**\ Participants can stake a minimum of 100 $BTC to qualify as a BTC Validator. A qualified BTC Validator that submits the correct Bitcoin block hash will earn 65% to 70% of the block rewards, depending on whether the Synchronizer that uploaded the block also mined it on the Bitcoin network. \ BTC Validators can stake through either Credit Staking or XBTC Staking, with each method offering distinct reward weightings. The reward weighting for BTC Staking is always equal to or higher than that of Credit Staking.\ Rewards are allocated proportionally based on the reward weighting associated with staked BTC. Delegate staking is not permitted for the initial 100 BTC, but once a Validator stakes this amount, they can accept delegate staking from the community. \ If you hold fewer than 100 XBTC, you can still earn XSAT rewards by delegating your XBTC to a BTC Validator through Delegate Staking.
# Incentives and Staking Requirements * **Mining and Staking Incentives**: Like Bitcoin, the entire distribution of XSAT tokens is synchronized with the mining of new BTC blocks through a mining process. This ensures that anyone with the necessary computational resources can participate in the network and earn tokens, promoting a decentralized and egalitarian distribution mechanism. This method not only incentivizes participation but also enhances the security and decentralization of the network by dispersing token ownership widely among those contributing to the network’s operations. * **Block Data Submission and Discovery Rewards**: Synchronizers receive 10% of the block's token incentive for submitting verified BTC block data first. This reward increases to 50% if the synchronizer is also the miner of the BTC block. This incentive design aligns the interests of Bitcoin miners with the exSat network, encouraging contributions to both ecosystems. * **Block Data Verification Rewards**: Immediately after the network launch, the first 2/3+1 validators to verify signatures for each block will share 10% of the total XSAT generated in that period as the verification incentive. After the commencement of staking XSAT, only qualified validators among the top stakers by XSAT amount will be eligible for these rewards. * **BTC Staking Rewards**: If the synchronizer, who is also a mining pool, does not discover a Bitcoin block, all participating validator nodes will share 80% of the total XSAT generated in that period based on their BTC staking ratio. If the synchronizer does discover a block, all participating nodes share 40% of the total XSAT generated. This approach ensures a fair and equitable distribution of rewards, recognizing the contributions of all network participants. * **Validator Participation**: Validators are required to stake a minimum of 100 BTC and XSAT, securing a significant financial commitment to the network’s security. To become a validator node, a participant must be among the top stakers by the staked amount of XSAT. # Quick Start In the exSat system, participants are divided into different roles: * **Synchronizer (Mining pools)**: Synchronizers are key participants in exSat's underlying protocol and typically come from BTC mining pools. Only miners who have successfully mined a block on the BTC chain in the past 72 hours are eligible to become Synchronizers. Synchronizers are responsible for uploading the latest BTC blocks to exSat and completing the validation and parsing works. Click [here ](/guides-of-data-consensus/run-a-sychronizer)to learn more about Synchronizers. * **Validator**: Validators are key participants in exSat's underlying protocol. Users must stake at least 100 $BTC or 2100 $XSAT to become Validator. Validators provide security for exSat and are responsible for reaching consensus on the latest BTC blocks. Only BTC block data that has got consensused by Validators will be accepted as valid on the exSat network. You can read more about [BTC Validator](/guides-of-data-consensus/run-a-btc-validator) and [XSAT Validator](/guides-of-data-consensus/run-a-xsat-validator). * **Developer**: Developers use the various infrastructures provided by exSat (such as the Data Consensus Protocol, UTXO index, Custody service, etc.) to build a wide range of decentralized applications (DApps) based on BTC. These applications may cover a variety of scenarios, including BTC lending, payments, asset issuance, cross-chain bridges, and more. Developers can write smart contracts using C++ on the native layer or develop contracts based on EVM on the extended layer. Developers can quickly access development resources [here](/developer-guides/quick-start) or learn more about EVM support. * **User**: Users can use the services provided by exSat or access various DApps created by developers. Users will be able to bridge their BTC to exSat via the cross-chain bridge, to use it as gas fees or for other purposes. Users can also participate in consensus by [staking their BTC to Validators](/user-guides/earn-rewards-via-btc-staking), enhancing the security of exSat and getting XSAT rewards. Click [here ](/user-guides/wallet-setup)to explore more. * **Custodian** (coming soon) : Custodians play a key role in exSat's asset protocol, building the connection between BTC and exSat on the assets. Custodians provide security and trust for exSat's cross-chain bridge and various asset protocols. Click [here ](/cutodian-guides/custodian-coming-soon)to learn more about Custodians. # UTXO Initialization exSat begins synchronizing and processing Bitcoin blocks starting from block height 840,000. For Bitcoin data before block 840,000, including UTXOs and block headers, the data is gathered and verified before being uploaded to the exSat network in a fully verifiable manner. To ensure the accuracy and integrity of this data initialization process, the following requirements should be met: * The UTXO and block header data to be uploaded to exSat must be accurate and verifiable, allowing any party, including professional auditing firms, to review and verify the data. * Once uploaded, the data on the exSat chain must exactly match the prepared data. A snapshot of the exSat chain should be provided for anyone, including auditing firms, to inspect and verify the consistency between the prepared data and the data on the exSat chain. # Data preparation ### **Block Header Preparation:**
### How to get block rewards from blocks mined by your pool For Bitcoin blocks mined by a pool, the pool will have additional priority time when uploading the block to exSat. As long as the client is running properly, the pool has a high probability of getting the block rewards. ### How to get the rewards from blocks not mined by your pool If a Synchronizer's client isn’t running, or if gas fee runs out, preventing him/her from submitting a block within the priority window, other Synchronizers may get the block rewards. Additionally, for blocks mined by pools not yet connected to the exSat network, a pool can get the rewards if it handles the block faster than other Synchronizers. # Run as Synchronizer Please confirm that you have: * [Prepared the necessary accounts](/guides-of-data-consensus/others/operation-references/preparation-before-you-start/account-preparation#account-preparation-for-synchronizer) * [Got an available BTC RPC node](/guides-of-data-consensus/others/operation-references/preparation-before-you-start/run-a-btc-node) * [Got a server to run the client](/guides-of-data-consensus/others/operation-references/preparation-before-you-start/environment-requirements) * [Install the software dependencies on the server](/guides-of-data-consensus/others/operation-references/preparation-before-you-start/prerequisites) The client can be: * [Run from source code](/guides-of-data-consensus/others/operation-references) * [Run with Docker](/guides-of-data-consensus/run-a-sychronizer/run-as-synchronizer/run-with-docker) Choose your preferred method, and let's get started! # Run from source code ## Download the Client Execute the following command to clone the repository : ``` git clone https://github.com/exsat-network/exsat-client ``` ## Build the client ``` cd exsat-client yarn install && yarn build ``` ## Edit the .env configuration file Please generate ".env" file by coping from ".env.example": ``` cp .env.example .env ``` Please edit the ".env" file to configure the settings. ``` vim .env ``` Please ensure all configurations are correctly set. Some settings can also be adjusted by executing the Client. Detailed configurations can be found [here](/guides-of-data-consensus/others/operation-references/common-operations/environment-variables). ## Execute the client ### 1. Initiate the synchronizer account #### Create or import the account If you don't have a synchronizer account, please [create a new account](/guides-of-data-consensus/others/operation-references/synchronizer-operations/create-new-synchronizer-account). If you already have a synchronizer account, and wish to import it to your client, please [import seed phase](/guides-of-data-consensus/others/operation-references/common-operations/import-from-seed-phrase) or [import private key](/guides-of-data-consensus/others/operation-references/common-operations/import-from-private-key). #### Register account as synchronizer You must [register your account as synchronizer](/guides-of-data-consensus/others/operation-references/synchronizer-operations/synchronizer-registration) to be qualified for Synchronizer tasks. ### 2. Configurations You can complete some client configurations or perform operations on your account: * [Set BTC RPC Node](/guides-of-data-consensus/others/operation-references/common-operations/set-btc-rpc-node) (**required**, can also be done by editing the .env file) * [Bridge BTC for gas fee ](/guides-of-data-consensus/others/operation-references/common-operations/refill-btc-for-gas-fees)(**required**) * [Change Reward Address ](/guides-of-data-consensus/others/operation-references/synchronizer-operations/change-reward-address)(optional) * [Export private key](/guides-of-data-consensus/others/operation-references/common-operations/export-private-key) (optional) * [Remove your account](/guides-of-data-consensus/others/operation-references/common-operations/remove-your-account) (optional) * [New version check](/guides-of-data-consensus/others/operation-references/common-operations/upgrade-to-new-version) (optional) ### 3. Execute the client Please be aware that completing [Set BTC RPC Node](/guides-of-data-consensus/others/operation-references/common-operations/set-btc-rpc-node) and [Bridge BTC for gas fee ](/guides-of-data-consensus/others/operation-references/common-operations/refill-btc-for-gas-fees)is mandatory. Once the above operations are completed, your account and client are ready, and you can [start it for long-term running](/guides-of-data-consensus/others/operation-references/synchronizer-operations/execute-the-synchronizer-client). ### 4. Check and claim rewards You could [check and claim rewards ](/guides-of-data-consensus/others/operation-references/synchronizer-operations/check-and-claim-rewards-for-synchronizer)on the front-page with the reward address. # Run with Docker Please ensure that [Docker ](/guides-of-data-consensus/others/operation-references/preparation-before-you-start/prerequisites#running-with-docker)is installed on your Linux server. ## 1. Download docker image ``` docker pull exsatnetwork/exsat-client:latest ``` ## 2. Download and configure the environment variables (.env) Please create a directory (e.g., `$HOME/.exsat/`) to store the files for running the exSat Client via Docker. We will download the `.env` file directly from GitHub into this directory, and edit it. ``` mkdir -p $HOME/.exsat/ curl -o $HOME/.exsat/.env https://raw.githubusercontent.com/exsat-network/exsat-client/main/.env.example vim $HOME/.exsat/.env ``` Please ensure all configurations are correctly set. Some settings can also be adjusted in the next steps. Detailed configurations can be found [here](/guides-of-data-consensus/others/operation-references/common-operations/environment-variables). ## 3. Initialize the account and configure the Client Start Docker in interactive mode： ``` docker run -it --name commander -v $HOME/.exsat/:/app/.exsat -e CLIENT_TYPE=commander exsatnetwork/exsat-client:latest ``` Perform below actions in the docker. ### 3.1 Initiate the synchronizer account #### Create or import the account If you don't have a synchronizer account, please [create a new account](/guides-of-data-consensus/others/operation-references/synchronizer-operations/create-new-synchronizer-account). If you already have a synchronizer account, and wish to import it to your client, please [import seed phase](/guides-of-data-consensus/others/operation-references/common-operations/import-from-seed-phrase) or [import private key](/guides-of-data-consensus/others/operation-references/common-operations/import-from-private-key). #### Register account as synchronizer If you didn't register your account as synchronizer, please [register as synchronizer.](/guides-of-data-consensus/others/operation-references/synchronizer-operations/synchronizer-registration) ### 3.2 Configurations You can complete some client configurations or perform operations on your account: * [Set BTC RPC Node](/guides-of-data-consensus/others/operation-references/common-operations/set-btc-rpc-node) (**required**, can also be done by editing the .env file) * [Bridge BTC for gas fee ](/guides-of-data-consensus/others/operation-references/common-operations/refill-btc-for-gas-fees)(**required**) * [Change Reward Account](/guides-of-data-consensus/others/operation-references/synchronizer-operations/change-reward-address) (optional) * [Export private key](/guides-of-data-consensus/others/operation-references/common-operations/export-private-key) (optional) * [Remove your account](/guides-of-data-consensus/others/operation-references/common-operations/remove-your-account) (optional) ## 4. Execute the Client Please ensure that you have [configured the BTC RPC Node](/guides-of-data-consensus/others/operation-references/common-operations/set-btc-rpc-node) and [Bridge BTC for gas fee](/guides-of-data-consensus/others/operation-references/common-operations/refill-btc-for-gas-fees). There are several ways to start the client using Docker, differing in how the keystore password is provided. Choose the method you prefer. Assuming the keystore file is stored at `$HOME/.exsat/synctest_keystore.json`and the password is `123456` .the keystore file path in ".env" file should be look like: ``` SYNCHRONIZER_KEYSTORE_FILE=/app/.exsat/synctest_keystore.json ``` ### Option1 : Password stored in ".env" Configure password in the `.env` file: ``` SYNCHRONIZER_KEYSTORE_PASSWORD=123456 ``` Then, start the Docker container with the following command: ``` docker run -d --restart always --name synctest -v $HOME/.exsat/:/app/.exsat -e CLIENT_TYPE=synchronizer exsatnetwork/exsat-client:latest ``` ### Option2 : Input password in the command Start docker container with the password as parameter in the command: ``` docker run -d --restart always --name synctest -v $HOME/.exsat/:/app/.exsat -e CLIENT_TYPE=synchronizer -e SYNCHRONIZER_KEYSTORE_PASSWORD=123456 exsatnetwork/exsat-client:latest ``` ### Option 3 : Interactive Password Input Start Docker in interactive mode and enter the password in the command line interface. ``` docker run -it --name synctest -v $HOME/.exsat:/app/.exsat -e CLIENT_TYPE=synchronizer exsatnetwork/exsat-client:latest ``` > Different startup methods vary in terms of security and convenience. If you start the client interactively and enter the password in the interface, the password won't be stored in plain text in the startup command or files, reducing the risk of exposure. However, if you provide the password in the `.env` file or directly in the command line, it may be more prone to leakage but offers greater convenience during startup. If your Synchronizer Client is running correctly, the following logs should appear on your screen: ``` 2025-02-28T12:34:59.176+00:00 info: ExsatApi initialized successfully. 2025-02-28T12:34:59.934+00:00 info: synchronizer[synctest.sat] client configurations are correct, and the startup was successful 2025-02-28T12:35:00.939+00:00 info: Upload block task is running 2025-02-28T12:35:00.942+00:00 info: Verify block task is running 2025-02-28T12:35:00.945+00:00 info: Parse block task is running ``` Check [this guide](/guides-of-data-consensus/others/operation-references/common-operations/view-logs) for detailed instructions on viewing the logs. ## 5. Check and claim rewards You could [check and claim rewards ](/guides-of-data-consensus/others/operation-references/synchronizer-operations/check-and-claim-rewards-for-synchronizer)on the front-page with the reward address. ## 6. Update to new Docker image Please refer to the [Docker version update](/guides-of-data-consensus/others/operation-references/synchronizer-operations/update-to-new-docker-version-for-synchronizer) instruction. # Run a BTC Validator The operations of a BTC Validator involve two roles: ### **Validator** In exSat, there is a group of Validators responsible for reaching consensus on the BTC block hashes to ensure the imported BTC block data is correct. Each Validator independently obtains the BTC block hash and submits it to exSat. Consensus on the current block hash is achieved when the block hash submitted by more than 2/3 of the Validators matches. Validators must stake at least 100 $BTC to participate in the consensus. Validators must stake an initial 100 $BTC themselves to qualify as a Validator. Once this requirement is met, they can accept delegated staking from the community. Validators can set a commission rate, where a portion of the rewards is allocated to the Validator as a commission, and the remainder is distributed to the Stakers who delegated their stakes to the Validator. To perform their duties, Validators must obtain Bitcoin block hashes from reliable sources, such as by operating their own Bitcoin node. Additionally, they need to run the Validator client to submit these block hashes to the exSat network. ### **Delegate Staker** Everyone who holds $BTC can be a delegate staker. Delegate stakers can stake their $BTC to a BTC Validator to earn the $XSAT staking rewards. Delegate stakers can view the validators on [this page](https://btcyield.io/) and choose one to stake. Delegate stakers can claim rewards on [this page](https://btcyield.io/my-staking). Delegate stakers do not need to run the Validator Client themselves, the $XSAT rewards comes from the validator he/she staked to, so when selecting a BTC Validator, consider factors like the commission rate and operational stability. # Requirements and rewards for BTC Validators ### Requirements for $BTC Validator $BTC Validators must stake a minimum of 100 $BTC to qualify as a **BTC Validator**. This initial 100 $BTC cannot be raised through delegated staking from the community. Once a Validator becomes qualified, they are allowed to accept delegated staking from community members. ### XSAT rewards received If the Bitcoin block hash submitted by a BTC Validator matches the final exSat consensus, the Validator will receive the reward for that block. BTC Validators receive 65% or 70% of the block rewards, depending on whether the Synchronizer receives current block rewards also mined the corresponding Bitcoin block: * If the Synchronizer mined the corresponding Bitcoin block, the BTC Validator receives 65% of the current block rewards. * Otherwise, the BTC Validator receives 70% of the current block rewards. ### **Reward Types:** BTC Validator rewards are divided into two categories: 1. **Staking Rewards:**\ These are rewards earned from staking BTC. The amount is proportional to the quantity of BTC staked. This portion of the reward is received by [the EVM address that completed the staking process](/guides-of-data-consensus/others/operation-references/validator-operations/change-stake-address). 2. **Commission:**\ Community members who either do not meet the 100 BTC minimum or prefer not to run a Validator client can delegate their BTC to a BTC Validator to earn consensus rewards.\ In return, the BTC Validator may charge a commission on the delegated BTC. The **Commission = Total Staking Rewards × Commission Rate**, and the commission rate is determined by the BTC Validator. The commission is received by the [Reward Address](/guides-of-data-consensus/others/operation-references/validator-operations/change-reward-address) set by the Validator. > For BTC Validators using [Credit Staking](/guides-of-data-consensus/run-a-btc-validator/credit-staking-and-xbtc-staking#credit-staking), the BTC staking occurs on the Bitcoin network, not on the exSat chain. As a result, there is **no** Stake Address on the exSat chain for the staking operation.\ > Therefore, both the **staking rewards** and the **commission** earned are distributed to the Validator’s designated [Reward Address](/guides-of-data-consensus/others/operation-references/validator-operations/change-reward-address). ### Rewards distribution XSAT rewards are distributed among BTC Validators proportionally based on the amount of BTC they have staked. After receiving the rewards, a validator deduct its commission, and the remaining amount is distributed among all stakers proportionally based on their BTC stakes. For example: * BTC Validators can receive 70% of the current block rewards, equivalent to 35 $XSAT. * If a Validator staked 10% of the total BTC staked, it receives 3.5 XSAT. * Assuming the Validator’s commission rate is 5%, and there are two stakers: * The Validator itself, staking 100 BTC. * A delegate staker from the community, staking 10 BTC. The rewards are distributed as follows: 1. **Commission**: 3.5×5%=0.175 $XSAT, retained by the Validator and claimable through its Reward Account. 2. **Validator's Stake Rewards**:\ (3.5−0.175)×100/110 ≈ 3.0227 $XSAT, claimable by the staker address of the validator. 3. **Delegate Staker's Rewards**:\ (3.5−0.175)×10/110 ≈ 0.3023 $XSAT,claimable by the delegate staker. # Credit Staking and XBTC Staking BTC holders can become BTC Validators on the exSat network by staking their #BTC through either [**Credit Staking**](/guides-of-data-consensus/others/operation-references/validator-operations/stake-for-validator-via-credit-staking) or [**XBTC Staking**](/guides-of-data-consensus/others/operation-references/validator-operations/stake-for-validator-via-xbtc-staking-or-xsat-staking). Each method has distinct features and benefits, as outlined below. *** ### **Credit Staking** Credit Staking allows BTC holders to retain self-custody of their #BTC on the Bitcoin network. By proving control over a specific BTC address and maintaining a locked balance of at least **100 #BTC**, users can qualify as BTC Validators. This method plays a key role in promoting decentralization and enhancing the security of the exSat network. However, it comes with certain limitations: * **Fixed Staking Amount:**\ Only two states are recognized: 0 #BTC or 100 #BTC. * If the BTC address balance falls below 100 #BTC, Credit Staking is deactivated and considered 0 #BTC. * If the balance is 100 #BTC or more, the staking amount is fixed at 100 #BTC—regardless of the actual balance (e.g., even with 1,000 #BTC, only 100 #BTC counts toward Credit Staking). * **No XBTC Minting:**\ BTC staked via Credit Staking does **not** generate XBTC, meaning it cannot be used in any on-chain yield-generating activities, such as quantitative strategies or restaking on the exSat chain. * **Lower XSAT Reward Weight:**\ Credit Staking typically earns a lower XSAT reward per BTC compared to XBTC Staking. * **Mandatory XSAT Donation:**\ A **20% portion** of the XSAT rewards earned through Credit Staking must be donated to the XSAT Foundation. *** ### **XBTC Staking** In contrast, XBTC Staking involves bridging BTC to the exSat network and minting XBTC, which can then be staked to become a BTC Validator. This approach offers several advantages: * **Secure Custody with Licensed Providers:**\ Bridged BTC is safeguarded by regulated custodians such as **Ceffu** ,**Standard Chartered Bank** and **Cactus**. For large holdings, assets are stored in **dedicated cold wallets**, and users can monitor their BTC to ensure full transparency and security. * **No Staking Limitations:**\ A minimum of **100 #XBTC** is required to become a BTC Validator, but there is no upper limit. The more #XBTC you stake, the more #XSAT rewards you earn. * **Participation in On-Chain CeDeFi Yields:**\ XBTC holders can access the full suite of CeDeFi opportunities on the exSat network—such as **quantitative strategies**, **restaking**, and other high-yield protocols—while simultaneously participating in consensus. * **Higher XSAT Reward Weight:**\ The reward weight per unit of XBTC is **higher** than that of BTC staked via Credit Staking, enabling greater XSAT earnings for the same notional amount. * **No Mandatory Donations:**\ XSAT rewards earned through XBTC Staking are **fully retained** by the staker—no contributions to the XSAT Foundation are required. # Run as BTC validator Please confirm that you have: * [Prepared the necessary accounts](/guides-of-data-consensus/others/operation-references/preparation-before-you-start/account-preparation#account-preparation-for-validator) * [Got an available BTC RPC node](/guides-of-data-consensus/others/operation-references/preparation-before-you-start/run-a-btc-node) * [Got a server to run the client](/guides-of-data-consensus/others/operation-references/preparation-before-you-start/environment-requirements) * [Installed the software dependencies on the server](/guides-of-data-consensus/others/operation-references/preparation-before-you-start/prerequisites) The validator client can be: * [Run from source code](/guides-of-data-consensus/run-a-btc-validator/run-as-btc-validator/run-from-source-code) * [Run with Docker](/guides-of-data-consensus/run-a-btc-validator/run-as-btc-validator/run-with-docker) Choose your preferred method, and let's get started! # Run from source code ## Download the Client Execute the following command to clone the repository : ``` git clone https://github.com/exsat-network/exsat-client ``` ## Build the client
cd exsat-client
yarn install && yarn build
cd exsat-client
yarn install && yarn build
# Run a BTC node ## Hardware Requirement Recommended Configuration: * CPU: 4 Cores * RAM: 8GB * System Disk: 30GB * Data Disk: 1TB * Data traffic： * The initial sync : 600 GB, takes about 6 days. * Monthly: 200 GB Refer to the AWS Virginia cloud service pricing: approximately 80 USD/month. Prices in Asia may be higher. ### Run the BTC node #### BTC mainnet Please refer to the commands [here ](https://github.com/exsat-network/exsat-initialize-data?tab=readme-ov-file#set-up-the-btc-fullnode)to run a **full** Bitcoin node. Please refer to the commands [here ](https://github.com/exsat-network/exsat-initialize-data?tab=readme-ov-file#set-up-the-mainnet-btc-prune-node)to run a **light** Bitcoin node. #### BTC test3 net Please refer to the commands [here ](https://github.com/exsat-network/exsat-initialize-data?tab=readme-ov-file#set-up-the-btc-fullnode)to run a Bitcoin test3 full node. Please be aware to change the script mentioned in the notes. # Environment requirements ## Hardware Requirement Recommended Configuration: * CPU: 2 Cores * RAM: 4GB * Disk: 50GB ## Operation System Recommend to use Ubuntu 22.04.4 LTS. Other supported Linux OS version: * CentOS 7 * CentOS 7.x * CentOS 8 * Ubuntu 18.04 * Ubuntu 20.04 * Ubuntu 22.04 ## Tools Required * SSH Terminal: iTerm * EVM Wallet: Metamask # Prerequisites Some commands may need the root account permission to execute, please use sudo as needed, or just start the client as root: ``` sudo -i ``` ### Running from source code If you wish to run the client from source code, please install the following dependences. ### Node.js Running the Client requires installing Node.js. #### Check if Node.js is Installed Open a terminal window. To check if Node.js is installed, run the following command: ``` node -v ``` If Node.js is installed, the terminal will display the version number, such as `v20.15.1`. 1. If Node.js is installed, ensure that the version is `20.15.1` or higher. 2. If the installed version is lower than `20.15.1` or it is not installed, proceed to the installation below. #### Install Node.js Version 20.15.1 To install Node.js version 20.15.1, first ensure your system is updated: ``` sudo apt update ``` Install Node.js from the NodeSource repository: ``` curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash - sudo apt install -y nodejs ``` Verify the installation by checking the Node.js version again: ``` node -v ``` This should return v20.15.1 or a higher version if installed successfully. ### Git #### Check if Git is Installed To check if Git is installed, run the following command in the terminal: ``` git --version ``` If Git is installed, the terminal will display the version number, such as `git version 2.25.1`. #### Install Git if Not Installed If Git is not installed, you can install it by running the following commands: ``` sudo apt update sudo apt install -y git ``` Verify the installation by checking the Git version: ``` git --version ``` This should return the version number of Git, confirming the installation. ### Yarn #### Check if Yarn is Installed Open a terminal window. Check if Yarn is installed by running: ``` yarn -v ``` #### Install Yarn if Not Installed If Yarn is not installed, add the Yarn repository and install it: ``` npm install -g yarn ``` Verify the installation by checking the Yarn version: ``` yarn -v ``` By following these steps, you will ensure that both Node.js (version `20.15.1` or higher) ,Git and Yarn are installed and properly configured on your system. ### Running with Docker If you wish to run the client with docker, please install docker. 1. **Download and Run the Official Installation Script** Docker provides a convenient installation script that you can download and run with the following commands: ```sh curl -fsSL https://get.docker.com -o get-docker.sh sh get-docker.sh ``` 2. **Verify the Docker Installation** Check the Docker version to confirm that the installation was successful: ```sh docker --version ``` # Synchronizer operations # Create New Synchronizer Account If you're running from source code, please execute "yarn start-commander" to run the client. If you're running with docker, please skip this. ``` yarn start-commander ``` If you don't have an account, please select "Create New Account" to create one.\ If you already have an account, you could import it by choosing "[Import Seed Phase](/guides-of-data-consensus/others/operation-references/common-operations/import-from-seed-phrase)" or "[Import Private Key](/guides-of-data-consensus/others/operation-references/common-operations/import-from-private-key)".
docker rm commander
docker run -it --name commander -v $HOME/.exsat/:/app/.exsat -e CLIENT_TYPE=commander exsatnetwork/exsat-client:latest
| Name | Needed | Description |
|---|---|---|
| code | must | string The name of the smart contract that controls the provided table |
| table | must | string The name of the table to query |
| scope | must | string The account to which this data belongs |
| index_position | optional | string Position of the index used, accepted parameters |
| key_type | optional | string Type of key specified by index_position (for example - |
| encode_type | optional | string representing the encoded type of the key_type parameter, either dec or hex, defaults to dec. |
| lower_bound | optional | string Filters results to return the first element that is not less than provided value in set |
| upper_bound | optional | string Filters results to return the first element that is greater than provided value in set |
| limit | optional | integer <int32>Default: 10 Limit number of results returned. |
| reverse | optional | boolean Default: false Reverse the order of returned results |
| show_payer | optional | boolean Default: false Show RAM payer |
Cross chain communication
Deposit tokens to user.
Withdraw tokens.
Deposit tokens to dApp.
| permission id | chain name | symbol | token contract | call contract |
|---|---|---|---|---|
| 0 | eth | USDT | 0xA7366BE06B2867a207c0C4F37481fF7B0cE62D87 | 0x4f9cC2c21F35f92ee25CBA295684d56E4044F725 |
| 0 | eth | USDC | 0x893AfC357b656EdD4F0c028670516F846FE89CFb | 0xBB4D7B8953151Cf583dde191c4df4f50b6E96b38 |
| 1 | tron | USDT | 0xA7366BE06B2867a207c0C4F37481fF7B0cE62D87 | 0x4f9cC2c21F35f92ee25CBA295684d56E4044F725 |
| 2 | solana | USDT | 0xA7366BE06B2867a207c0C4F37481fF7B0cE62D87 | 0x4f9cC2c21F35f92ee25CBA295684d56E4044F725 |
| 2 | solana | USDC | 0x893AfC357b656EdD4F0c028670516F846FE89CFb | 0xBB4D7B8953151Cf583dde191c4df4f50b6E96b38 |
| 0 | bsc | USDC | 0x893AfC357b656EdD4F0c028670516F846FE89CFb | 0xBB4D7B8953151Cf583dde191c4df4f50b6E96b38 |
| 0 | arb | USDT | 0xA7366BE06B2867a207c0C4F37481fF7B0cE62D87 | 0x4f9cC2c21F35f92ee25CBA295684d56E4044F725 |
| 0 | arb | USDC | 0x893AfC357b656EdD4F0c028670516F846FE89CFb | 0xBB4D7B8953151Cf583dde191c4df4f50b6E96b38 |
| 0 | bsc | USDT | 0xA7366BE06B2867a207c0C4F37481fF7B0cE62D87 | 0x4f9cC2c21F35f92ee25CBA295684d56E4044F725 |
| 0 | eth | ETH | 0x81e1Da8BDEbC4686B9025839c72c7FB0229F180C | 0xE077aB9D41F441E5F2C0cB3FA099A92EcFAC3E80 |
Deposit ERC20 token to user address.
Withdraw ERC20 token.
Deposit ERC20 token to dApp.
Deposit BTC to user address.
Withdraw BTC.
Deposit BTC to dAp