-
Notifications
You must be signed in to change notification settings - Fork 40
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
Skaled returns error on valid debug_traceCall request #1748
Comments
still relevant for 3.17.2-develop.3-historic request regular eth_call
response:
request debbug_traceCall
response:
|
UPD need to add a handler for the absence of an empty object in the params field.
But, according to the documentation https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-debug, JSON RPC call should be valid without the empty object
|
3.17.2-develop.3-historic callTracer:
4byteTracer
prestateTracer
noopTracer
replayTracer
allTracer (Skaled only available)
|
will be fixed in a separate issue #1780 |
Preconditions
Active chains
Archival node
Address with Sfuel and with Whitelist deployer role
Contract to deploy: Example ERC20
Versions
skalenetwork/schain:3.17.2-develop.2-historic
Steps to reproduce
eth_call
debug_traceCall
Actual state:
Eth-call returns the total supply value
0x000000000000000000000000000000000000000000000000000000003b9aca00
debug_traceBlock returns:
INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised
errorExpected behavior
Skaled should return the number of possible tracing result by executing an eth call within the context of the given block execution.
The text was updated successfully, but these errors were encountered: