RPC call trace_transactions doesnt return CREATE2 opcode but debug_traceTransactions does it #9384
Unanswered
raulpuente
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Do you know why call trace_transactions doesn't return CREATE2 opcode
EXAMPLE:
curl --request POST --url ERIGON_NODE_URL --header 'accept: application/json' --header 'content-type: application/json' --data '{"id": 1,"jsonrpc": "2.0","method": "trace_transaction","params": ["0x7232237dd82d3a3e19f1881ee04c5e6358f0857b49ab91595ffd28e2ae57f88e"]}'RESULT: "type": "create"
But with the tdebug_traceTransaction
curl -s ERIGON_NODE_URL -X POST -H "Content-Type: application/json" -d '{"method":"debug_traceTransaction","params":["0x7232237dd82d3a3e19f1881ee04c5e6358f0857b49ab91595ffd28e2ae57f88e", {"disableMemory": true, "disableStack": true, "disableStorage": true, "EnableReturnData": false, "Tracer": "callTracer", "tracerConfig": { "OnlyTopCall": false, "WithLog": true}}],"id":1,"jsonrpc":"2.0"}'RESULT: "type": "CREATE2"
Thank you
Beta Was this translation helpful? Give feedback.
All reactions