Welcome to our dedicated repository, a central hub for tracking and documenting the ongoing advancements in BEP2/BEP8 asset binding within the BC Fusion initiative. This repository serves as a vital resource for developers, investors, and enthusiasts interested in the intersection of these cutting-edge blockchain technologies.
Asset Binding is at the heart of this initiative. By effectively binding BEP2 and BEP8 assets to BEP20, we can ensure greater liquidity, interoperability, and utility across BNBChain ecosystem. This process not only enhances the efficiency of transactions but also opens the door for innovative cross-chain functionalities. For details, please refer to BEP2/BEP8 asset sunset annoucement.
In this repository, we meticulously track the progress, challenges, and milestones of BEP2/BEP8 asset binding in the BC Fusion project. Our aim is to provide a comprehensive and up-to-date resource that reflects the dynamic and evolving nature of blockchain technology.
Be noted: even a BEP20 token is already issued on the BSC, it does not mean the asset is bound, the asset owner must
take actions to bind them together to enable the crosschain transfer. Please refer to the aforementioned announcement
for more information. In the following table, the BSC Contract Address field only shows the contract address for
the bound assets.
Tokens Cannot Bind
| Asset | Symbol | Comments |
|---|---|---|
| WIN | WINB-41F | please deposit BEP2 to exchanges (e.g., Binance) and withdraw BEP20 for transfer |
| TUSD | TUSDB-888 | please deposit BEP2 to exchanges (e.g., Binance) and withdraw BEP20 for transfer |
| TRX | TRXB-2E6 | please deposit BEP2 to exchanges (e.g., Binance) and withdraw BEP20 for transfer |
| IDRT | IDRTB-178 | please deposit BEP2 to exchanges (e.g., Binance) and withdraw BEP20 for transfer |
| TROY | TROY-B98 | https://www.troyswap.io/bridge |
![@github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=64&v=4){kind=small}
