You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'd like to be able to check the userOpReceipt after waiting for the transaction. Instead of having to call eth_getUserOperationReceipt the receipt could be returned as well since its already queried.
Describe the solution you would like
Im happy to put in a PR for this since I have the patch using patch-patch but thought I'd hold off to see if its even something you'd consider. I would like access to the entire userOpReceipt so that I can check the status code of the innerOp and handle successful transactions reverting inner userOps. As a general improvement I am wondering why the entire txn payload is not returned since then you can do a lot more with it.
Describe alternatives you have considered
I could query eth_getUserOperationReceipt but it adds unnecessary latency.
Additional context waitForUserOperationTransaction already has queried the receipt I just thought it makes sense to return it alongside the txn.
The text was updated successfully, but these errors were encountered:
oh I knew there was something we meant to include in the v4 changes and it was this exact change!
Unfortunately, changing the API for waitForUserOperationTransaction would make this a breaking change. something we could do is add another action on the client called waitForUserOperationReceipt which would allow you to do this more easily. Happy to accept a PR for this if you've already got something!
Is your feature request related to a problem? Please describe.
I'd like to be able to check the userOpReceipt after waiting for the transaction. Instead of having to call
eth_getUserOperationReceipt
the receipt could be returned as well since its already queried.Describe the solution you would like
Im happy to put in a PR for this since I have the patch using patch-patch but thought I'd hold off to see if its even something you'd consider. I would like access to the entire
userOpReceipt
so that I can check the status code of the innerOp and handle successful transactions reverting inner userOps. As a general improvement I am wondering why the entire txn payload is not returned since then you can do a lot more with it.Describe alternatives you have considered
I could query
eth_getUserOperationReceipt
but it adds unnecessary latency.Additional context
waitForUserOperationTransaction
already has queried the receipt I just thought it makes sense to return it alongside the txn.The text was updated successfully, but these errors were encountered: