@@ -118,9 +118,9 @@ Although we define only one new transaction type, we can distinguish between two
118
118
transactions, based on their positioning in the L2 block:
119
119
120
120
1 . The first transaction MUST be a [ L1 attributes deposited transaction] [ l1-attr-deposit ] , followed by
121
- 2 . an array of zero-or-more [ user-deposited transactions] [ user-deposited ]
122
- submitted to the deposit
123
- feed contract on L1 (called ` OptimismPortal ` ). User-deposited transactions are only present in the first block of a L2 epoch.
121
+ 2 . an array of zero-or-more [ user-deposited transactions] [ user-deposited ]
122
+ submitted to the deposit feed contract on L1 (called ` OptimismPortal ` ).
123
+ User-deposited transactions are only present in the first block of a L2 epoch.
124
124
125
125
We only define a single new transaction type in order to minimize modifications to L1 client
126
126
software, and complexity in general.
@@ -321,7 +321,7 @@ generated by the [L2 Chain Derivation][g-derivation] process. The content of eac
321
321
transaction are determined by the corresponding ` TransactionDeposited ` event emitted by the
322
322
[ deposit contract] [ deposit-contract ] on L1.
323
323
324
- 1 . ` from ` is unchanged from the emitted value (though it may
324
+ 1 . ` from ` is unchanged from the emitted value (though it may
325
325
have been transformed to an alias in ` OptimismPortal ` , the deposit feed contract).
326
326
2 . ` to ` is any 20-byte address (including the zero address)
327
327
- In case of a contract creation (cf. ` isCreation ` ), this address is set to ` null ` .
0 commit comments