Retrieve TxHash From UserOpHash #2
Comments
bh2smith
added a commit
that referenced
this issue
Jun 14, 2024
This PR adds NearEthAdapter and Signature producing. Some Encounterd Issues & Resolutions: Solved (kinda): Conflicting Import Formats in Dependencies Solved: Invalid Request Payload for sendUserOp Solved: Entry Point Not Supported. Solved: Reverted or Out of Gas [Likely Reverted] Solved: AA24 signature error Solved: Safe Address retrieval after deployment Solved: Safe already exists for nonce > 0. Unresolved/Open Issues (For Future PRs) - UserOpHash is returned from sendUserOp, not the TxHash. There are endpoints to get the a receipt (containing the txHash), but they are not immediately available... should we sleep or continue requesting until its available? #2 - Gas Fee Fetching is naive (bundler suggests using theirs). #3 - Integrate Paymaster #4 Bonus: Recovery: AddOwnerWithThreashold at or after Setup. Co-authored-by: Nicholas Rodrigues Lordello <[email protected]>
|
Looks like Safe Docs suggest the same thing: https://docs.safe.global/sdk/relay-kit/guides/4337-safe-sdk#check-the-transaction-status |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The bundler request
sendUserOperationreturns only aUserOpHashwhich is not sufficient to identify the mined transaction hash. #1 outlines a function call to the bundler endpointeth_getUserOperationReceiptthat ideally returns information containing the mined txHash. However, one must wait, presumably, until the transaction is mined before this endpoint will return the receipt.We could keep polling this endpoint with some exponential backoff... not sure they best approach, but we definitely need to wait some time for it to become available.
https://github.com/bh2smith/nearly-safe/blob/6b10b0aa6accd094e0f70eae425d93ba3e65bbc3/index.ts#L259-L262
The text was updated successfully, but these errors were encountered: