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

Debug tracing via debug_traceCall endpoint does not work on private smart contracts #1674

Closed
rodion-lim-partior opened this issue Sep 12, 2023 · 1 comment

Comments

@rodion-lim-partior
Copy link
Contributor

System information

Geth version: 1.10.3
OS & Version: Linux
Commit hash : 65de7ae

Expected behaviour

When running debug_traceCall api, private transactions to private smart contracts read from private state db

Actual behaviour

Private transactions to private smart contracts read from public state db, causing tracer to return 0x in simulated output

Steps to reproduce the behaviour

Send a private transaction's data to a deployed private smart contract via debug_traceCall JSON rpc

Backtrace

Expected to return an array of op codes and their corresponding program counter, stack and storage.

>debug.traceCall({to: "0x717a.....}, "latest")
  failed: false,
  gas: 21204,
  returnValue: "",
  structLogs: []
}
@rodion-lim-partior
Copy link
Contributor Author

rodion-lim-partior commented Sep 12, 2023

PR opened at #1673, @antonydenyer could you kindly help to take a look at this too please? Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants