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
  • Custodian Bridge Services
  • Background
  • Vaulta and EVM
  • Exsat EVM
  • Reserved Address
  • The Cross Chain Bridges
  • BTC Bridge
  • General Token Bridge
  1. Developer Guides

Brief Intro to the Custodian Bridge Services

PreviousBrief Intro to the Cross-Chain CommunicationNextCustodian Bridge for Non-BTC Tokens

Last updated 3 days ago

Custodian Bridge Services

We work with licensed custodian service providers to provide the bridge service from other chains to the Exsat EVM. The assets will stay in the addresses managed by custodian service provider. We will mint or release tokens on Exsat EVM accordingly. This approach will give us a safe and compliant way to manage crypto assets.

Background

Vaulta and EVM

We use the Vaulta () blockchain network. The Vaulta blockchain is a next-generation Layer-1 built for speed, scale and finality. Your transfers, swaps, and app interactions happen almost instantly with low (or no) fees.

Vaulta EVM is a powerful feature of the Vaulta blockchain that brings the best of Ethereum's capabilities to the Vaulta ecosystem. It allows you to use popular Ethereum-based applications (dApps) on Vaulta, benefiting from faster speeds, lower costs, and a more eco-friendly environment.

Exsat EVM

Vaulta EVM technology allow entities to run their own EVM layers on the Vaulta blockchain. Exsat runs it’s own EVM layer, the Exsat EVM.

Exsat EVM Mainnet

RPC:

Block explorer:

Exsat EVM Testnet

RPC:

Reserved Address

Each Vaulta account has a mapped reserved EVM address. The rule is using the uint64 value of the Vaulta name as the last 8 bytes of the EVM address, and then pad the rest with 0xbb. E.g. the name β€œeosio.evm” is mapped to β€œ0xbbbbbbbbbbbbbbbbbbbbbbbb5530ea015b900000”

The Cross Chain Bridges

As mentioned above, the support for native token of the EVM and other tokens will be different. However, the general idea is the same: the user first transfer tokens to addresses managed by the custodian service provider on the source chain, the bridge then mint or release tokens to the EVM address linked to the source chain address.

We also allow dApps to manage their own user funds. In this mode, the bridged tokens will be sent to a dApp appointed address. A notification will be sent to the dApp with extra context to distinguish origin later (but still in the same Vaulta Tx).

BTC Bridge

Deposit

  1. Transfer to the assigned BTC address.

  2. Tokens will be transferred to the EVM address linked to the BTC address.

Withdraw

  1. Transfer to 0xbbbbbbbbbbbbbbbbbbbbbbbb3d6f4ef81dc1b200 (reserved address of bproxy.xsat) with memo in certain format:

    memo format:<permission_id>,<evm_address>,<btc_address>,<gas_level>

    • permission_id:The id for a bridge routine. 1 is used for regular usages for now. It is possible that we have different settings for different routines. (e.g. maybe different custodian/speed/fees)

    • evm_address:The Sender address. Note that this address is mainly for record keeping, no validation is performed on this.

    • btc_address:Recipient address.

    • gas_levelοΌšβ€slow” or β€œfastβ€œ

The memo of the above transaction is:

1,0x1c892C483618a9EbF8250a437f9E952Fc6b7212d,bc1palegjlhn6v6fj5jdkvsg0fm0kdzgms8pzy9vkhzylug2fnmjfkcsx6y9he,slow

For more details, please check Custodian Bridge for BTC

General Token Bridge

Deposit

  1. Transfer token to the assigned address on source chain.

  2. Tokens will be transferred to the EVM address linked to the source chain address.

Withdraw

  1. Locate the helper contract for the token we want to bridge. Each token has a helper contract to handle the withdraw requests.

  2. Call the withdraw function:

function withdraw(
        uint256 _permissionId,
        string calldata _chainName,
        string calldata _recipientAddress,
        uint256 _amount,
        string calldata _remark
    ) external {}
  • _permission_id: The id for a bridge routine.

  • _chainName: Chain name:e.g. arb, bsc, eth, solana, tron, The chain name must match the settings indexed by the permission id.

  • _recipientAddress: Recipient address

  • _amount: Amount in wei

  • _remark: Memo for the transfer generated in the destination chain if applicable. Can be empty.

The current supported tokens are:

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

For more details, please check Custodian Bridge for Non-BTC Tokens

Block explorer:

Get the address for deposit. Currently, end users can apply for such addresses on . However, for application developments, it is preferable that the developer contact the Exsat to generate such addresses.

Example:

Get the address for deposit. Currently, end users can apply for such addresses on . However, for application developments, it is preferable that the developer contact the Exsat to generate such addresses.

πŸ‘¨β€πŸ’»
https://www.vaulta.com/
https://evm.exsat.network/
https://scan.exsat.network/
https://evm-tst3.exsat.network/
https://scan-testnet.exsat.network/
https://exsat.network/app/bridge
https://scan.exsat.network/tx/0x31f885b08611274700b49ac4c6f17af591e8ebff74d3d4a9ee734b275132eafd
https://exsat.network/app/bridge
Deposit tokens to user.
Withdraw tokens.
Deposit tokens to dApp.