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
  • Background
  • Vaulta and EVM
  • Exsat EVM
  • Runtime Contract
  • Reserved Address
  • Trustless Bridge for ERC20
  • Tokens originally issued in Vaulta side
  • Tokens originally issued in EVM side
  1. Developer Guides

Trustless Bridge For ERC20 Tokens

PreviousTrustless Bridge for Native TokensNextBrief Intro to the Cross-Chain Communication

Last updated 3 days ago

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:

Block explorer:

Runtime Contract

The Vaulta EVM system is run in a way that each EVM transaction is actually part of Vaulta transactions. The EVM runtime contract will process Vaulta transactions invoking EVM transactions.

We will use evm_runtime to represent the Vaulta account of the evm runtime contract.

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”

Trustless Bridge for ERC20

Tokens originally issued in Vaulta side

Tokens native to Vaulta can be converted to EVM's ERC20 through the trustless bridge. The converted tokens meet the standard ERC20. When bridging from Vaulta to EVM, the tokens on the Vaulta side will be locked in the bridge contract (”erc2o.xsat” for Exsat), and the corresponding tokens will be minted on the EVM side. The reverse cross-chain will burn the EVM side tokens and release the locked vaulta side tokens.

The tokens on the EVM side have a standard ERC20 interface, and the following additional interfaces are available for bridge operation:

function bridgeTransfer(address to, uint256 amount, string memory memo) external payable returns (bool);
function egressFee() external returns (uint256);

Tokens originally issued in EVM side

For tokens native to the EVM side, since we cannot add bridge functions to the contracts of these tokens, we need to implement cross-chain by calling the interface of a separate portal contract. When crossing the chain from the EVM side to the Vaulta side, the token will be locked in the portal contract, and the corresponding token will be minted on the Vaulta side. When crossing the chain in the reverse direction, the Valta side token will be recovered and the EVM side token will be released. The portal contract also has a similar bridge interface:

function bridgeTransfer(address to, uint256 amount, string memory memo) external payable returns (bool);
function egressFee() external returns (uint256);
function token() external returns (IERC20);

The extra function token() will return the linked ERC20 token address of the portal.

Note that as portal contract is not the token contract, approve() is required before hand.

👨‍💻
https://www.vaulta.com/
https://evm.exsat.network/
https://scan.exsat.network/
https://evm-tst3.exsat.network/
https://scan-testnet.exsat.network/