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

User is not able to bridge NFT via CLI #560

Open
VladOSTAFI opened this issue Jul 19, 2023 · 0 comments
Open

User is not able to bridge NFT via CLI #560

VladOSTAFI opened this issue Jul 19, 2023 · 0 comments

Comments

@VladOSTAFI
Copy link

Expected Behavior

As a user I have to be able to bridge NFT from one network to another.

Current Behavior

User configurations loaded
? Select the source network from which to beam goerli
? Select the destination network which to beam to mumbai
? Enter the address of the collection smart contract 0xa1a1f7cea2a8f05bedf41152dd44b39231800000
? Enter the token ID of the NFT to beam 1
Loading network RPC providers... done
Contract at 0xa1a1f7cea2a8f05bedf41152dd44b39231800000 does not exist on goerli network
Checking if the collection is deployed on both source and destination networks... done
[2023-07-19T21:16:56.435Z] [BridgeNFT] [Goerli] Collection does not exist on goerli network.
You can deploy the missing contracts with the "create:contract" or "bridge:contract" command.

How to reproduce (for bugs)

  1. Deploy contract to Goerli
  2. Deploy contract to Mumbai
  3. Mint NFT on Goerli network
  4. Try to bridge NFT from Goerli to Mumbai
  5. Input contract address for contract on Mumbai nettwork(0xa1a1f7cea2a8f05bedf41152dd44b39231800000)

Possible Solution

  1. Improve docs on github(README.md)
  2. Improve CLI user flow.

Environment:

Testnet

Version: 2.0.0-beta.X

Give me permisions and I will fix it ASAP :)))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant