From 46ff55c6ec34d92cb328dbb2d4f0d040c1bc82fa Mon Sep 17 00:00:00 2001 From: pcw109550 Date: Wed, 6 Dec 2023 19:09:45 +0900 Subject: [PATCH] specs: Fix Span batch EIP-155 description --- specs/span-batches.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/span-batches.md b/specs/span-batches.md index c7c7e935433d..d84a6e896351 100644 --- a/specs/span-batches.md +++ b/specs/span-batches.md @@ -208,7 +208,7 @@ not risking codebase with gnarly custom encoding/decoding implementations. ### Store `y_parity` and `protected_bit` instead of `v` -Only legacy type transactions can be optionally protected. If protected([EIP-155]), `v = 2 * ChainID + y_parity`. +Only legacy type transactions can be optionally protected. If protected([EIP-155]), `v = 2 * ChainID + 35 + y_parity`. Else, `v = 27 + y_parity`. For other types of transactions, `v = y_parity`. We store `y_parity`, which is single bit per L2 transaction. We store `protected_bit`, which is single bit per L2 legacy type transactions to indicate that tx is protected.