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
Checking transaction signatures in account abstraction (#225) involves calculating the hash of the transaction, excluding the data field containing the signature itself. This is not possible right now, as there are no opcodes for all transaction fields.
How can it be fixed
Add an opcode SIGHASH with byte value 0x3f that gets sha3(rlp(tx \ {data})), where tx \ {data} refers to the transaction without the data field.
The text was updated successfully, but these errors were encountered:
What is wrong?
Checking transaction signatures in account abstraction (#225) involves calculating the hash of the transaction, excluding the
data
field containing the signature itself. This is not possible right now, as there are no opcodes for all transaction fields.How can it be fixed
Add an opcode
SIGHASH
with byte value0x3f
that getssha3(rlp(tx \ {data}))
, wheretx \ {data}
refers to the transaction without the data field.The text was updated successfully, but these errors were encountered: