We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have raised the question in discord: https://discord.com/channels/697535391594446898/722244032407011359/1028984434483023922
Ideally, the client side code should receive the exact message of transaction failure or validation error triggered using the require checks.
I have tried the other options using web3j references but they are not working. web3/web3.js#1707 https://github.com/pertsev/web3_utilz/blob/master/revert%20reason/index.js https://ethereum.stackexchange.com/questions/84545/how-to-get-reason-revert-using-web3-eth-call
https://web3js.readthedocs.io/en/v1.2.8/web3-eth.html#handlerevert
Please provide some insights into this.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
I am able to achieve this by enabling revert reason in the quorum node.
https://consensys.net/docs/goquorum/en/stable/configure-and-manage/manage/revert-reason/
Sorry, something went wrong.
No branches or pull requests
I have raised the question in discord:
https://discord.com/channels/697535391594446898/722244032407011359/1028984434483023922
Ideally, the client side code should receive the exact message of transaction failure or validation error triggered using the require checks.
I have tried the other options using web3j references but they are not working.
web3/web3.js#1707
https://github.com/pertsev/web3_utilz/blob/master/revert%20reason/index.js
https://ethereum.stackexchange.com/questions/84545/how-to-get-reason-revert-using-web3-eth-call
https://web3js.readthedocs.io/en/v1.2.8/web3-eth.html#handlerevert
Please provide some insights into this.
Thanks in advance.
The text was updated successfully, but these errors were encountered: