Legacy Optimism withdrawal (2022) - 0.1 ETH not finalized?

[miracle-pirates]

Did you check the documentation and specs?

• Yes

Was there anything unclear or missing?

Hello,

I need help verifying the status of a legacy OP Mainnet withdrawal initiated before the Bedrock upgrade.

Withdrawal details:

• Date: June 22, 2022
• Amount: 0.1 ETH
• Network: OP Mainnet to Ethereum
• Wallet: 0xB40f0e7B8EC9Ef24bbB8679639205C45B2C8B8A9
• Legacy message nonce: 106778

Transaction:
https://optimistic.etherscan.io/tx/0xa065a103b768d25f79d7fdd284b7bdbe4b6796b5029f5484f6c3a54d45df6f3a

The withdrawal was successfully initiated on OP Mainnet. The transaction logs include SentMessage and WithdrawalInitiated.

However, I cannot confirm whether the withdrawal was successfully relayed or finalized on Ethereum.

The transaction is also not visible in Superbridge’s activity history.

My questions:

1. Has this legacy withdrawal already been finalized on Ethereum?
2. If it is still pending, can it be finalized after the Bedrock upgrade?
3. What is the correct procedure to safely complete this withdrawal?

Thank you for your assistance.

Did you check for duplicate questions?

• Yes

Similar Questions or Issues Found

No response

Please select the type of request

• Bug Report
• Feature Request

Steps to Reproduce

No response

Expected vs. Actual Behaviour

No response

Software Versions

No response

Operating System

No response

Hardware Resources

No response

Configuration Files, Startup Flags & Environment Variables

No response

Error Messages / Logs

No response

Feature Description

No response

Purpose and Benefits

No response

Relevant Context or Examples

No response

I have confirmed that the 0.1 ETH withdrawal was initiated successfully on OP Mainnet on June 22, 2022.

I also found the corresponding L1 state root submission, but I understand that this does not confirm that the withdrawal was relayed.

Could someone help me identify the L1 relay transaction, or explain how to check whether this specific pre-Bedrock withdrawal message was successfully relayed?

The original L2 transaction hash is:
0xa065a103b768d25f79d7fdd284b7bdbe4b6796b5029f5484f6c3a54d45df6f3a

Thank you.

Hello Optimism team,

I’m trying to recover or verify the status of a legacy 0.1 ETH withdrawal initiated on June 22, 2022, before the Bedrock upgrade.

L2 transaction:
https://optimistic.etherscan.io/tx/0xa065a103b768d25f79d7fdd284b7bdbe4b6796b5029f5484f6c3a54d45df6f3a

Wallet:
0xB40f0e7B8EC9Ef24bbB8679639205C45B2C8B8A9

Legacy message nonce: 106778

The withdrawal is not visible in my current bridge history. I also checked the L1 CrossDomainMessenger’s successfulMessages and failedMessages mappings using a calculated legacy message hash; both returned false.

Could you please help me determine:

1. Whether this withdrawal was finalized before or after Bedrock.
2. Whether it was migrated as a pending legacy withdrawal.
3. If still pending, the exact steps required to prove and finalize it today.

Thank you for your help.

[mtf0919]

Hello Optimism team,

I am facing the EXACT same issue as the original poster. My Pre-Bedrock withdrawal (initiated on April 23, 2022) is also stuck and not visible in Superbridge.

My details:

• L2 Tx Hash: 0x1cd3449f75b4ae40cf90268f69807aed20086528a2f6dafdef8022ed12eac22b
• Wallet: 0xfd3d8bc8e46ed736f82cbe892b6fe17369dd2f44
• Amount: ~0.0969 ETH

I tried both the official viem SDK and @eth-optimism/sdk but both fail.

1. viem throws ReceiptContainsNoWithdrawalsError because the old SentMessage event doesn't have the new MessagePassed signature.
2. The SDK throws state root for message not yet published.
3. When trying to manually build the proof using recent DisputeGameFactory (Super Root) games, the l2BlockNumber resolves to a massive l2SequenceNumber timestamp (e.g., 4523128486...), causing eth_getProof to reject it.

Could you please confirm if there is an official working script or a specific contract interface (like the old Legacy portal) to handle these pre-Bedrock txs after the Upgrade 20 / Super Root changes?

Thank you!