Skip to content

Conversation

tersec
Copy link
Contributor

@tersec tersec commented Apr 19, 2025

@arnetheduck
Copy link
Member

needs a version bump release of nim-json-rpc to pass tests (so nimble finds the new code)

@jangko jangko changed the base branch from master to dev/etan/ff-yparity July 30, 2025 06:32
@jangko
Copy link
Contributor

jangko commented Jul 30, 2025

merge this to #209, to assist json-rpc bump

@jangko jangko merged commit 859cb76 into dev/etan/ff-yparity Jul 30, 2025
2 of 20 checks passed
@jangko jangko deleted the YNe branch July 30, 2025 06:33
jangko added a commit that referenced this pull request Jul 30, 2025
* On JSON-RPC, authorization serializes v as yParity

JSON uses yParity for authorization instead of v like in transaction,
because v for transaction has additional information mixed in in legacy
case (chain ID and magic value); this legacy case is not relevant for
authorizations. Existing logic ignored yParity value from JSON and uses
default initialized v = 0 value. Create our own web3 type, same as how
we do it for transactions and receipts, and use correct yParity key.

* Fix deps

* Use flavor automatic serialization

* eth_api seq[string]

* adjust JSON marshalling tests (#202)

Co-authored-by: Jacek Sieka <[email protected]>

* Custom serializer for TransactionArgs: oneof input or data field

* cleanup

---------

Co-authored-by: jangko <[email protected]>
Co-authored-by: tersec <[email protected]>
Co-authored-by: Jacek Sieka <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants