Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bridge failed between 2 custom icon chains by running them first and then decentralising it later #352

Open
sindhu0820 opened this issue Jan 29, 2024 · 0 comments
Labels
bug Something isn't working jira

Comments

@sindhu0820
Copy link
Contributor

Overview

bridge failed between 2 custom icon chains by running them first and then decentralising it later

Steps to Reproduce

  1. dive chain icon -c ./sample-jsons/config0.json -g ../test/functional/config/genesis-icon-0.zip
  2. dive chain icon decentralize -p gochain -k keystores/keystore.json -n 0x3 -e http://172.16.0.4:9080/api/v3/icon_dex -s icon-node-0xacbc4e
  3. dive chain icon -c ./sample-jsons/config1.json -g ../test/functional/config/genesis-icon-1.zip
  4. dive chain icon decentralize -p gochain -k keystores/keystore.json -n 0x101 -e http://172.16.0.5:9080/api/v3/icon_dex -s icon-node-0x42f1f3
  5. dive bridge btp --chainA icon --chainB icon --chainAServiceName icon-node-0xacbc4e --chainBServiceName icon-node-0x42f1f3

Expected Behavior

bridge should start running

Screenshots

Screenshot (145)

@sindhu0820 sindhu0820 added bug Something isn't working jira labels Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working jira
Projects
None yet
Development

No branches or pull requests

1 participant