-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Extend transaction revert handling for eth.sendSignedTransaction #3345
Comments
@nivida Hi Samuel. Please help... Lost 12 hours debugging this... I've tried [email protected]'s way to get it:
My code is here - https://gist.github.com/AnthonyAkentiev/e8cd38328769284c110626b9e4a1379b i've also tried this script -> https://gist.github.com/gluk64/fdea559472d957f1138ed93bcbc6f78a but nothing helped :-(((( Thank you very much! |
@AnthonyAkentiev ah sorry to hear that! our ci is working with geth 1.9.13 so it should be working for you with 1.9.12. see here: [Edited link for sendSignedTransaction test -cg] can you confirm you are on 1.9.12 and not |
@ryanio Thx for quick answer! Really appreciate it. |
@AnthonyAkentiev Yes, revert with reason only works up with geth up until 1.9.13. 1.9.14 introduced a bug which they just fixed today at go-ethereum 21083. When that's published we'll be able to restore reason fetching in the next patch release here. |
@cgewecke thx. checked current stable 1.9.15 and it worked! |
Side-note for anyone else running into this... it looks like there will need to be code changes here to get the revert reason working again per the existing API for geth 1.9.15. PR #3571 should resolve. |
Expected behavior
eth.sendSignedTransaction
should return the revert reason string as expected.Actual behavior
eth.sendSignedTransaction
does get executed but the signed transaction doesn't get decoded to get the revert reason string as expected.Steps to reproduce the behavior
eth.sendSignedTransaction
and the revert instruction opcode does get called.Versions
web3.js: latest
The text was updated successfully, but these errors were encountered: