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
eth_getUserOperationReceipt returns null when the underlying UserOp bundle has failed on-chain
eth_getUserOperationReceipt
The eth_getUserOperationReceipt call should return the actual data (with the failed transaction receipt)
await networkInstance.addUserOpsToBatch({ to: recipient.toLowerCase(), value: utils.parseEther(value) }) await networkInstance.addUserOpsToBatch({ to: recipient.toLowerCase(), value: utils.parseEther(value) })
Submit a multi userop bundle on Klaytn chain and then call getUseropReceipt.
Issue is prevelant on Klaytn chain which expects a higher gas limit bundle size.
Linux
v1.0.24-alpha
The text was updated successfully, but these errors were encountered:
addressed in #175
getUserOpReceipt can't get receipts for failed userops, added a new endpoint for that skandha_userOperationStatus
skandha_userOperationStatus
Sorry, something went wrong.
0xSulpiride
Successfully merging a pull request may close this issue.
Describe the bug
eth_getUserOperationReceipt
returns null when the underlying UserOp bundle has failed on-chainExpected behavior
The
eth_getUserOperationReceipt
call should return the actual data (with the failed transaction receipt)Steps to reproduce
Submit a multi userop bundle on Klaytn chain and then call getUseropReceipt.
Additional context
Issue is prevelant on Klaytn chain which expects a higher gas limit bundle size.
Operating system
Linux
Skandha version or commit hash
v1.0.24-alpha
The text was updated successfully, but these errors were encountered: