Skip to content

Reobservation request: Optimism → Avalanche transfer signed by expired guardian set (seq 37289) #4979

Open

Description

@HFranxi

Description

I have an unredeemed Portal token transfer from Optimism to Avalanche from January 2024. The VAA was signed by guardian set 3, which has expired, so redemption on Avalanche fails. Could the guardians re-observe the source transaction so a VAA signed by the current guardian set can be produced?

  • VAA ID: 24/0000000000000000000000001d68124e65fafc907325e3edbf8c4d84499daa8b/37289
  • Source tx (Optimism): 0x5f3c9000c6c2fba3b86a398773d661ae682c2a42e41d59c79f79ff4a518b1b64
  • Timestamp: 2024-01-21 15:18:45 UTC
  • Amount: 10.70 USDC
  • Recipient (Avalanche): 0xD8EE87cee7765238573506b5b4388150CAE2E1F1
  • Wormholescan shows the transfer as "Pending Claim"
  • Portal "Resume transaction" shows "Error with transfer"

Experienced behavior

Calling completeTransfer on the Avalanche Token Bridge (0x0e082F06FF657D94310cB8cE8B0D9a04541d8052) with the VAA reverts. The VAA has guardianSetIndex 3.

Expected behavior

After re-observation by the current guardian set, a new VAA can be redeemed and the 10.70 USDC delivered to the recipient.

Thank you.

Activity

  1. HFranxi commented on Oct 14, 2026

    @HFranxi
    Author

    Following up on this request after 2 weeks. Could a guardian-support team member please take a look? Thank you.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions