-
Notifications
You must be signed in to change notification settings - Fork 42
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 on archival node couldn't trace block with failed transaction #1859
Comments
Hey - I tried it on my machine using transfer function of the contract, and it works Please add more detailed instructions to reproduce the bug (how many tokens were originally minted, and which function of the smart contract was called with which parameters?) |
Verified on legacy network Execution reverted in block 299549
Success execution in block 299549
|
3.18.1-beta.0 |
Note:
debug_traceTransaction
,debug_traceBlockByNumber
anddebug_traceBlockByHash
methods are affectedVersion:
skalenetwork/schain:3.18.1-develop.0-historic
Preconditions:
Active schain medium type
Archival node connected to schain
Address with whitelisted deployer role (schain owner is preferable)
Test token contract link
To Reproduce:
debug_traceTransaction
Expected Behavior:
The reverted transaction shouldn't affect other transactions within the block.
The reverted transaction should return a trace as on Ethereum - with readable error and without any errors with all accompanying structures.
Actual State:
The archival node returns the error with the index of failed transaction and doesn't return any information for other valid transactions within the block
Logs:
geth attach
JSON-RPC example:
debug_traceBlockByNumber ('latest')
The text was updated successfully, but these errors were encountered: