From 3cdf8934c04e3302368485efd5e6691279cfddb2 Mon Sep 17 00:00:00 2001 From: Ashutosh Tripathi <39340292+ashucoder9@users.noreply.github.com> Date: Wed, 5 Jul 2023 16:42:09 +0530 Subject: [PATCH] update: transaction execution document (#52) --- docs/protocol/transaction-execution.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/protocol/transaction-execution.md b/docs/protocol/transaction-execution.md index 5729b79..d609ff8 100644 --- a/docs/protocol/transaction-execution.md +++ b/docs/protocol/transaction-execution.md @@ -21,8 +21,16 @@ The **Trusted Sequencer reads transactions from the pool** and decides whether t Once a transaction is added to the L2 State, it is broadcast to all other zkEVM nodes via a broadcast service. It is worth noting that **by relying on the Trusted Sequencer, we can achieve fast transaction finality (faster than in L1)**. However, the resulting L2 State will be in a trusted state until the batch is committed in the Consensus Contract. -:::tip Verification on Layer 1 +## Verification on Layer 1 -Users will typically interact with trusted L2 State. However, due to certain protocol characteristics, the verification process for L2 transactions (on Layer 1 to enable withdrawals) can take a long time, typically around 30 minutes but up to 2 weeks in rare cases. As a result, users should be mindful of the potential risks associated with high-value transactions, particularly those that cannot be reversed, such as off-ramps, over-the-counter transactions, and alternative bridges. +Users will typically interact with trusted L2 State. However, due to certain protocol characteristics, the verification process for L2 transactions (on Layer 1 to enable withdrawals) can take a long time, typically around 30 minutes but up to a week in rare cases. + +:::note What is the rare case scenario? + +Verification of transactions on L1 will take 1 week only in the case when an **Emergency State is activated** or the **aggregator does not batch any proofs at all**. + +Additionally, the emergency mode is activated if a sequenced batch is not aggregated in 7 days. Please refer to [this guide](emergency-state.md) to understand more about the Emergency State. ::: + +As a result, users should be mindful of the potential risks associated with high-value transactions, particularly those that cannot be reversed, such as off-ramps, over-the-counter transactions, and alternative bridges.