From 0f8a7e8d8ed25e59567571e34015f566a3379d24 Mon Sep 17 00:00:00 2001 From: Ori Pomerantz Date: Mon, 10 Apr 2023 09:58:14 -0500 Subject: [PATCH] fix(specs): Still trying to get my md accepted --- specs/deposits.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/specs/deposits.md b/specs/deposits.md index 92c5aae7e5ad..653cc58addfa 100644 --- a/specs/deposits.md +++ b/specs/deposits.md @@ -118,9 +118,9 @@ Although we define only one new transaction type, we can distinguish between two transactions, based on their positioning in the L2 block: 1. The first transaction MUST be a [L1 attributes deposited transaction][l1-attr-deposit], followed by -2. an array of zero-or-more [user-deposited transactions][user-deposited] - submitted to the deposit - feed contract on L1 (called `OptimismPortal`). User-deposited transactions are only present in the first block of a L2 epoch. +2. an array of zero-or-more [user-deposited transactions][user-deposited] + submitted to the deposit feed contract on L1 (called `OptimismPortal`). + User-deposited transactions are only present in the first block of a L2 epoch. We only define a single new transaction type in order to minimize modifications to L1 client software, and complexity in general. @@ -321,7 +321,7 @@ generated by the [L2 Chain Derivation][g-derivation] process. The content of eac transaction are determined by the corresponding `TransactionDeposited` event emitted by the [deposit contract][deposit-contract] on L1. -1. `from` is unchanged from the emitted value (though it may +1. `from` is unchanged from the emitted value (though it may have been transformed to an alias in `OptimismPortal`, the deposit feed contract). 2. `to` is any 20-byte address (including the zero address) - In case of a contract creation (cf. `isCreation`), this address is set to `null`.