Open tsadovska opened 4 weeks ago
@tsadovska I've tried the same source/dest configuration as well as another one with a low balance. I can't seem to repro the issue above. Can you verify on your end as well?
Checked on wormhole-connect-mainnet.
The first attempt to execute the transaction as described above resulted in an error (att. 1).
Wormhole Connect: error completing transfer Error: No receipt for 0x2d1b7e94fb5a1d3aeae44691bd35e90a4fb9c609907a215afd5fb1a6d4e5fc7e on Arbitrum
at E.parseTransactionDetails (index-lccCmM9l.js:1:3905)
at async CircleTransfer.st [as getTransferMessage] (main-RPuOtJsw.js:245:18376)
at async AutomaticCCTPRoute.initiate (main-RPuOtJsw.js:245:53829)
at async SDKv2Route.send (main-RPuOtJsw.js:273:70761)
at async St (main-RPuOtJsw.js:313:66416)
However, upon retrying, the transaction was successfully completed without any issues (att. 2).
Attachment 1:
https://github.com/user-attachments/assets/1f9f16ae-f6b5-46e0-a802-cba56865ffd4
Attachment 2:
Describe the current behavior in detail
Checked on wormhole-connect-mainnet (Connect v2) with macOS Sonoma 14.5 and Google Chrome Version 127.0.6533.120 (Official Build) (arm64).
Steps:
Actual result: Transaction fails. Expected result: Transaction proceeds without errors.
Notes/ Attachments
https://github.com/user-attachments/assets/be55212c-1f2e-4538-88cf-e918dff7f4eb