Skip to content

Commit 7d48a40

Browse files
lightclientfjl
andauthored
eth: add optional v value for 2930 and 1559 txs (#446)
It looks like many clients are currently either not returning yParity or returning both v and yParity. To align the spec with this, I'm proposing we add an optional (but deprected) v value for 2930 and 1559 txs. This way clients can continue use it and tooling can have some space to upgrade to yParity. --------- Co-authored-by: Felix Lange <fjl@twurst.com>
1 parent a4bd432 commit 7d48a40

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

src/schemas/transaction.yaml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -181,6 +181,10 @@ Transaction1559Signed:
181181
title: yParity
182182
description: The parity (0 for even, 1 for odd) of the y-value of the secp256k1 signature.
183183
$ref: '#/components/schemas/uint'
184+
v:
185+
title: v
186+
description: For backwards compatibility, `v` is optionally provided as an alternative to `yParity`. This field is DEPRECATED and all use of it should migrate to `yParity`.
187+
$ref: '#/components/schemas/uint'
184188
r:
185189
title: r
186190
$ref: '#/components/schemas/uint'
@@ -202,6 +206,10 @@ Transaction2930Signed:
202206
title: yParity
203207
description: The parity (0 for even, 1 for odd) of the y-value of the secp256k1 signature.
204208
$ref: '#/components/schemas/uint'
209+
v:
210+
title: v
211+
description: For backwards compatibility, `v` is optionally provided as an alternative to `yParity`. This field is DEPRECATED and all use of it should migrate to `yParity`.
212+
$ref: '#/components/schemas/uint'
205213
r:
206214
title: r
207215
$ref: '#/components/schemas/uint'

0 commit comments

Comments
 (0)