Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for debugging Quorum private transactions #9057

Open
rodionlim opened this issue Oct 8, 2024 · 0 comments · May be fixed by #9058
Open

Add support for debugging Quorum private transactions #9057

rodionlim opened this issue Oct 8, 2024 · 0 comments · May be fixed by #9058
Labels
A-compatibility Area: compatibility T-feature Type: feature T-to-discuss Type: requires discussion

Comments

@rodionlim
Copy link

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

@rodionlim rodionlim added T-feature Type: feature T-needs-triage Type: this issue needs to be labelled labels Oct 8, 2024
@github-project-automation github-project-automation bot moved this to Todo in Foundry Oct 8, 2024
@rodionlim rodionlim linked a pull request Oct 8, 2024 that will close this issue
@zerosnacks zerosnacks added A-compatibility Area: compatibility and removed T-needs-triage Type: this issue needs to be labelled labels Oct 8, 2024
@zerosnacks zerosnacks linked a pull request Oct 8, 2024 that will close this issue
@grandizzy grandizzy added the T-to-discuss Type: requires discussion label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-compatibility Area: compatibility T-feature Type: feature T-to-discuss Type: requires discussion
Projects
Status: Todo
Development

Successfully merging a pull request may close this issue.

3 participants