Open DanBurton opened 2 years ago
Note that if you create a "custom rpc" network option, and point it at 127.0.0.1:12537
(it will not allow you to do localhost:12537
), then everything works as expected. I have no idea why the built-in localhost:12537 settings are misbehaving.
Describe the bug When I attempt to sign & send a transaction using the built-in network settings for Localhost 12537, after clicking "confirm", it fails to sign the transaction with an error about "net2999", even though the to/from addresses in my transaction are both "net999".
To Reproduce
Expected behavior
sendAsync
should transfer the funds on the devnet running at localhost:12537. (It works on TestNet.)Browser details (please complete the following information):
Additional context
Sometimes it will not let you click Confirm, claiming that there is no balance (even on accounts with a balance on your localhost devnet.) Other times, it will fail with the following error:
This is nonsense. See the output of the
console.log
included in the html snippet above, which will indicate that the transaction being sent is fornet999
as it should be.