We successfully deployed all the contracts on the testnet, and we were able to transfer tokens between the ICON and Tezos blockchains in both directions.
Here are the contract addresses of bridges on the TEZOS chain.
BMC_MANAGEMENT = KT1XamvZ9WgAmxq4eBGKi6ZRbLGuGJpYcqaj
BMC_PERIPHERY = KT1ENZvToPx87LhuowJ1VixjjqQhSnYrcYLi
BTS_PERIPHERY = KT1XpmmVG25yTAVuGPK9Sxp5MY1rxBW6v8Lr
BTS_CORE = KT1EKPcM48hRp9MekjB8njTfqLMkerS7ytTt
BTS_OWNER_MANAGER = KT1QQA4ax5nuVPugrByHVYEASXmi3Fx1bnFH
Below is the transaction hash of both ICON and TEZOS.
NETWORK ICON : Berlin
NETWORK TEZOS: Ghostnet
CASE 1:
Transferred FA2 token from TEZOS to ICON
oojGYbpyThedZSwjhC67AKFwz1cstbNhQopQUtnGDe77fwy5dxn
Token Minted on ICON
0x7143a42ebf4d1f0d01eb32571e27666d6b63b5eb3fc6e84098948ec5212221dc
TransferEnd Event received from ICON
onruhsx4MjcMYyeGrbGbb4Vz9roEdpEfiaxU5yMWcP7dDoJoh74
CASE 2:
Transferred IRC2 token from ICON to TEZOS
0xf657724b4f04f57b1368790831618f0dce2bebeee0cd10b951da68dc6f339db4
Token Minted on Tezos :
op3Zosrs4qUGaR8PrAEUwXmFdq1Zy2EnhC6NFY2cbARwmHXwwgt
TranserEnd Event Received from TEZOS
0xa646fa912ac5982980afec4f8c6671d45d83257b146446fee7d5e099dbf389de
CASE 3:
Transferred Native Coin from TEZOS to ICON
opTcqHMoazWpD9LAeSmmnhEGrkSu5Dh9GXa66sUPJh36xJ4EJCL
Token Minted on ICON
0x24f45000e753946661b142606e0d4be75a4fd94c88ebdce05f3996446a5112eb
TranserEnd Event Received from ICON
oosyDYAdVMVnFTF2LfvtffMvdRT5WFbmFcN6dycYEHBnmQzinFT
CASE 4:
Transferred Native Coin from ICON to TEZOS
0x2c4c34b2fa83ead9647ef1a44920d3b8608e67003b2bff66b01d4a8490a4fc29
Token Minted on TEZOS
ooeuRT77iz2AhCWs3nJKSBFxvGpRrC5FDN6tMqbRg94Pet7bhhP
TranserEnd Event Received from TEZOS
0x8406f24ba5074433966e3c80b217c34df3e2ac1c809f52eea1d60a98f69b8ef7
Nomadic labs has taken a crucial step towards resolving the issue we discussed earlier. They have initiated a Merge Request in the TEZOS GitLab repository with the purpose of adding the necessary RPC (Remote Procedure Call).
Until this issue is resolved and the necessary adjustments are made, we will have to exercise patience and wait before deploying our products on the mainnet. It is crucial to ensure the stability and reliability of our solutions before transitioning to the live network.
The merge request: Add consensus key's public key information in RPC (!8856) · Merge requests · Tezos / tezos · GitLab
We have also identified an issue on the ICON Bridge, where addresses of other chains are being converted to lowercase, causing compatibility problems. We have raised this issue on the ICON Bridge repository and are awaiting a fix before proceeding with the mainnet launch. Here is the issue: Unable to parse actual address from lowercase string in inter-chain messaging · Issue #869 · icon-project/icon-bridge · GitHub
