Skip to content

Conversation

@pullurib
Copy link
Contributor

PR description

Expose revert reason through GraphQL queries

  • When Besu is configured to enable revert reasons, successful transactions would have null for revert reason and failed transactions would have it populated.
  • When Besu is configured to not enable revert reasons, all transactions would have a null for revert reason.

Fixed Issue(s)

Fixes #1273

@shemnon
Copy link
Contributor

shemnon commented Sep 25, 2024

Can you also propose this change to the official spec? Kind of like how it was done in this PR? https://github.com/ethereum/execution-apis/pull/471/files

@pullurib
Copy link
Contributor Author

Can you also propose this change to the official spec? Kind of like how it was done in this PR? https://github.com/ethereum/execution-apis/pull/471/files

Raised the PR for spec change - ethereum/execution-apis#593

@macfarla macfarla enabled auto-merge (squash) October 1, 2024 23:24
@macfarla macfarla merged commit db1899c into hyperledger:main Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose the revert reason in the GraphQL receipt

4 participants