Skip to content

Commit b30ddc5

Browse files
authored
Merge pull request #1313 from ethereum-optimism/alcueca-patch-2
Add detail on how to finalize a withdrawal
2 parents 7951767 + 60d1fd6 commit b30ddc5

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

pages/stack/transactions/withdrawal-flow.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,8 @@ The next step is to wait the fault challenge period, to ensure that the L2 outpu
7979

8080
Finally, once the fault challenge period passes, the withdrawal can be finalized and executed on L1.
8181

82+
To do so, a user, either an externally owned account (EOA) directly or a contract acting on behalf of an EOA, calls the [`finalizeWithdrawalTransaction`](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/packages/contracts-bedrock/contracts/L1/OptimismPortal.sol#L320-L420) function of the [`OptimismPortal`](https://github.com/ethereum-optimism/optimism/blob/62c7f3b05a70027b30054d4c8974f44000606fb7/packages/contracts-bedrock/contracts/L1/OptimismPortal.sol) contract.
83+
8284
## Expected internal reverts in withdrawal transactions
8385

8486
During the withdrawal process, users may observe internal reverts when viewing the transaction on **Etherscan**. This is a common point of confusion but is expected behavior.

0 commit comments

Comments
 (0)