You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/stack/rollup/outages.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ For all transactions sent to the `OptimismPortal`:
97
97
3. Transactions are processed in the order they are received.
98
98
4. Transactions are processed within the [`sequencer_window`](https://specs.optimism.io/glossary.html#sequencing-window).
99
99
100
-
In practice, this means that transactions sent to the `OptimismPortal` contract will always be processed in the order they are received and within a maximum delay of the `sequencer_window` (set to 24 hours by default but may differ from chain to chain).
100
+
In practice, this means that transactions sent to the `OptimismPortal` contract will always be processed in the order they are received and within a maximum delay of the `sequencer_window` (set to 12 hours by default but may differ from chain to chain).
101
101
If the Sequencer is unavailable or transactions are not published to L1 within this `sequencer_window`, OP Stack chains will automatically reorganize themselves to guarantee that these transactions are included in the L2 chain.
102
102
103
103
Refer to the [L2 Chain Derivation Specification](https://specs.optimism.io/protocol/derivation.html) for a much more detailed explanation of how transactions sent to the `OptimismPortal` contract are processed.
@@ -111,7 +111,7 @@ The following scenarios make different assumptions about the state of the Sequen
111
111
112
112
In this scenario we'll assume that the Sequencer is completely unavailable and unable to process any transactions.
113
113
Users must send transactions directly to the `OptimismPortal` contract to have them included in the L2 chain.
114
-
We'll also assume that the `sequencer_window` has been set to 24 hours.
114
+
We'll also assume that the `sequencer_window` has been set to 12 hours.
115
115
Here, two users are sending transactions to the `OptimismPortal` contract.
116
116
117
117
Observe how the transactions sent by both users are included in the L2 chain automatically after the `sequencer_window` has elapsed.
@@ -128,8 +128,8 @@ sequenceDiagram
128
128
Note over S: Sequencer goes offline
129
129
U1->>OP: User 1 sends transaction 1 to OptimismPortal
130
130
U2->>OP: User 2 sends transaction 2 to OptimismPortal
131
-
Note over U1: User 1 waits 24 hours
132
-
Note over U2: User 2 waits 24 hours
131
+
Note over U1: User 1 waits 12 hours
132
+
Note over U2: User 2 waits 12 hours
133
133
OP->>L2: Transaction 1 included in L2 automatically
134
134
OP->>L2: Transaction 2 included in L2 automatically
0 commit comments