Skip to content
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.

Cannot use ark URIs on a different network than the current profile #1531

Closed
alessiodf opened this issue Nov 4, 2019 · 2 comments · Fixed by #1533
Closed

Cannot use ark URIs on a different network than the current profile #1531

alessiodf opened this issue Nov 4, 2019 · 2 comments · Fixed by #1533

Comments

@alessiodf
Copy link
Contributor

Using an ark: URI whose address is for a different network than the current profile always fails because the network of the transaction inherits the current profile's network version rather than the version of the destination network. The transaction modal is populated correctly with wallets from the correct network, and the transaction itself is sent to peers on the correct network, but it is rejected because the network version number is wrong.

For example, if you're on the ARK Mainnet profile and access an ark: URI that will send a transaction to ARK Devnet, the network will be 23 instead of 30 so will fail despite being sent to devnet peers.

@ghost
Copy link

ghost commented Nov 4, 2019

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

@ghost
Copy link

ghost commented Nov 14, 2019

This issue has been closed. If you wish to re-open it please provide additional information.

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

Successfully merging a pull request may close this issue.

1 participant