Skip to content
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

BUG: getUserOperationReceipt returns null when the underlying UserOp bundle has failed on-chain #122

Closed
ch4r10t33r opened this issue Nov 30, 2023 · 1 comment · Fixed by #130
Assignees

Comments

@ch4r10t33r
Copy link
Member

Describe the bug

eth_getUserOperationReceipt returns null when the underlying UserOp bundle has failed on-chain

Expected behavior

The eth_getUserOperationReceipt call should return the actual data (with the failed transaction receipt)

Steps to reproduce

 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.

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

@ch4r10t33r ch4r10t33r linked a pull request Dec 6, 2023 that will close this issue
8 tasks
@0xSulpiride 0xSulpiride reopened this Dec 8, 2023
@0xSulpiride
Copy link
Member

0xSulpiride commented Apr 26, 2024

addressed in #175

getUserOpReceipt can't get receipts for failed userops, added a new endpoint for that skandha_userOperationStatus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants