You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked there isn't already an issue for the bug I encountered.
Viem Version
2.57.11
Current Behavior
Serialization succeeds without throwing, but changes the authorization’s yParity from 0x1c to 0x01, producing:
0x5547e9755be8809632ca622efb267ac59e2b3edb9f706e442aa71d0757e119e8
I independently fetched the raw transaction using eth_getRawTransactionByHash. Changing only the serialized authorization parity back to 0x1c exactly reproduces those raw bytes and the original hash.
Expected Behavior
Serialization should preserve the original authorization tuple and reproduce the transaction hash:
0xaec8420968abd74e70ef5b3099d6ba7baa3f069c4f718d7c4d729d591cffcb09
EIP-7702 permits authorization y_parity values below 2**8 at the transaction-encoding level. Authorization processing can fail and skip a tuple without invalidating the entire transaction. Such values therefore need to survive serialization unchanged, rather than being normalized to a valid signature parity.
This issue has been locked since it has been closed for more than 14 days.
If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest Viem version. If you have any questions or comments you can create a new discussion thread.
Activity
fix: preserve eip-7702 authorization `yParity` in `serializeAuthoriza…
github-actions commentedon Nov 10, 2026
This issue has been locked since it has been closed for more than 14 days.
If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest Viem version. If you have any questions or comments you can create a new discussion thread.