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
Quorum private transactions store a 64 bytes private transaction manager (ptm) hash in the transaction's input, and also sets the signature recovery id (v) to either 37/38. Calling cast run on a quorum private transaction is not giving the correct trace output since the EVM is executing the ptm hash instead of the actual transaction input.
Proposing to include a feature where we check for a 64 bytes input, and a v that is set to 37/38, and fetch the actual transaction input from the PTM before simulating the transaction, to cater for the specific instance when we want to replay a Quorum private transaction.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component
Cast
Describe the feature you would like
Quorum private transactions store a 64 bytes private transaction manager (ptm) hash in the transaction's input, and also sets the signature recovery id (v) to either 37/38. Calling
cast run
on a quorum private transaction is not giving the correct trace output since the EVM is executing the ptm hash instead of the actual transaction input.Proposing to include a feature where we check for a 64 bytes input, and a v that is set to 37/38, and fetch the actual transaction input from the PTM before simulating the transaction, to cater for the specific instance when we want to replay a Quorum private transaction.
Additional context
No response
The text was updated successfully, but these errors were encountered: