Skip to content

Latest commit

 

History

History
64 lines (35 loc) · 2.23 KB

bridge.md

File metadata and controls

64 lines (35 loc) · 2.23 KB
Raw

Summary

Users can map ETH, BTC, stable coins and other assets to Heco through the asset cross-chain bridge, which is achieved by locking a certain number of assets on the source chain and generating the corresponding number of Tokens in Heco.

Heco encourages community developers to provide more decentralized cross-chain solutions.

This document describes the option for project parties to map Tokens from the source chain to Heco on their own.

heco-brige ref here

The project owner self maintains the total balance of Token on the multi-chain including Heco, and endorses the credibility of Token.

The main processes include：

1）Initial Preparation
2）Source Chain -> Heco Chain
3）Heco Chain -> Source Chain

Glossary

Source Chain: The source chain where the Token is located (e.g. Ethereum)

Src_Token: Token on the source chain, possibly a contract, or a native Token

Locked address or contract: the address used to lock the Token

Heco_Token: Token on Heco's chain

Initial Preparation

  1. Deploy the lock address or contract on the source chain Src_Lock_Addr

  2. Deploy Token on Heco: Heco_Token

  3. Deploy a lock address or contract on Heco Heco_Lock_Addr

If you need multiple sign contracts, you can refer to gnosis/MultiSigWallet.

If you need contracts with mint/burn, you can refer to OpenZeppelin/openzeppelin-contracts contracts/token/ERC20).

Translated with www.DeepL.com/Translator (free version)

In order to maintain credibility, the project needs to publicize the above information to the community and invite the community to supervise it. And to monitor the total amount of coins on both chains.

Source Chain->Heco Chain

  1. Source chain locking Src_Token

Transfer a certain amount of Src_Token to Src_Lock_Addr for locking

  1. Release Heco_Token on the Heco chain

Execute mint operation to give Heco_Lock_Addr the corresponding amount of Heco_Token

Heco chain->Source chain

  1. Heco chain lock Heco_Token

Execute burn operation, destroy Heco_Token

  1. Release Src_Token on the source chain

operation Src_Lock_Addr to unlock the corresponding volume