-
Notifications
You must be signed in to change notification settings - Fork 791
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
Falsely says sender account has 0? #102
Comments
Can you double check |
I tried master and didn't work. Trying to debug further now, but I don't quite understand the buffers. Using --deterministic on testrpc. Thus the first account is:
And when tx.from & fromAccount I get:
I'm assuming the first buffer (tx.from) means it is actually sending the right address through. I'm not sure what the second log gives me. This is after: I used Metamask to check the balance, and it confirms that it has ETH in it. |
@simondlr I think this was the solution: https://github.com/nexusdev/testrpc/blob/feature/persistent/lib/blockchain_double.js#L125 |
@mhhf glad to hear you had the same problem! The current testrpc blockchain_double to your blockchain_double is very different. Added that line at the end of initialize in blockchain_double, but didn't help. Next bet is to use your fork + new vm to see if that works. The reason why I believe it is the vm vs testrpc is because installing the new vm version (2.0.1) for testrpc caused this error to start occurring. Any further help is appreciated. |
Thanks a lot for your help @mhhf. I fixed it. The interface did indeed change and I opened up an issue in testrpc. |
…sers-2.2.6 Update karma-detect-browsers to the latest version 🚀
Hi. Not entirely sure where to post this, but I assume it's a vm error.
I updated testrpc to contain the latest version of ethereumjs-vm (2.0.1) in order to get around these issues I started encountering wrt invalid jumps (trufflesuite/ganache-cli-archive#196, #88).
However, now I get this error. I verified that all accounts have funds in them. So not sure where the issue is coming from. Either testrpc isn't passing the right address through OR the vm is screwing up here?
Any help?
The text was updated successfully, but these errors were encountered: