From 93d2cb3deac869673626c41160936a8b13a97528 Mon Sep 17 00:00:00 2001 From: Sabnock <24715302+Sabnock01@users.noreply.github.com> Date: Mon, 2 Oct 2023 19:25:55 -0500 Subject: [PATCH] Update site/docs/glossary/types.md Co-authored-by: Will Cory --- site/docs/glossary/types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/docs/glossary/types.md b/site/docs/glossary/types.md index 67a87c10..19674ba8 100644 --- a/site/docs/glossary/types.md +++ b/site/docs/glossary/types.md @@ -24,7 +24,7 @@ An [event](https://github.com/ethereum-optimism/optimism/blob/develop/packages/c ## WithdrawTransaction -A withdraw transaction is a special type of transaction format specific to the OP Stack. It is for creating L1 transactions from L2. The withdrawal flow consists of three parts. First, there is the withdraw initiating transaction which the user submits on L2 and emits a [MessagePassedEvent](#messagepassedevent). Second, there is the withdrawal proving transaction which is submitted on L1 by the user to prove legitimacy of the withdrawal. This transaction emits a [WithdrawalProvenEvent](#withdrawalprovenevent). Lastly, there is the withdrawal finalizing transaction which is submitted on L1 by the user after the fault challenge period has passed which emits a [WithdrawalFinalizedEvent](#withdrawalfinalizedevent) and executes the transaction on L1. +A withdraw transaction is a special type of transaction specific to the OP Stack. It is for creating L1 transactions from L2. The withdrawal flow consists of three parts. First, there is the withdraw initiating transaction which the user submits on L2 and emits a [MessagePassedEvent](#messagepassedevent). Second, there is the withdrawal proving transaction which is submitted on L1 by the user to prove legitimacy of the withdrawal. This transaction emits a [WithdrawalProvenEvent](#withdrawalprovenevent). Lastly, there is the withdrawal finalizing transaction which is submitted on L1 by the user after the fault challenge period has passed which emits a [WithdrawalFinalizedEvent](#withdrawalfinalizedevent) and executes the transaction on L1. ## WithdrawalFinalizedEvent