-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Berlin fork causing panic when accessing private state. #1657
Comments
joshuafernandes
added a commit
to Consensys/quorum-dev-quickstart
that referenced
this issue
Jun 28, 2023
…s introduced in the berlin fork while Consensys/quorum#1657 is being worked on
joshuafernandes
added a commit
to Consensys/quorum-dev-quickstart
that referenced
this issue
Jun 28, 2023
* goq: temp fix for address being absent in the public stateDB which was introduced in the berlin fork while Consensys/quorum#1657 is being worked on * fix typo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual behaviour
When sending private transactions on a network that has the berlin fork enabled a panic is being fired at https://github.com/ConsenSys/quorum/blob/fbfb5dd12a8c2b8abd053f858ef539ab38196b75/core/vm/operations_acl.go#L66
Steps to reproduce the behaviour
Using https://www.npmjs.com/package/quorum-dev-quickstart/v/0.1.3 run the privacy transaction example.
The text was updated successfully, but these errors were encountered: