-
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
Eth API: Trace installed bytecode in the Ethereum JSON-RPC trace_block
output
#11635
Comments
@rjan90 @jennijuju Why has this been prioritised ? |
An interim solution is to only handle smart contracts that live beyond the end of the block. Basically:
Note: we're only altering the trace of the last successful attempt to deploy a contract at any given address. Given that we won't have any intermediate and/or reverted state, that's all we can do. On the other hand, that's probably sufficient in most cases. |
Basically:
|
The Ethereum JSON-RPC
trace_block
API currently returns0xfe
as the EVM bytecode for all newly created actors:To fix this, we need some way to get the bytecode of an EVM smart contract in the middle of a block. We'll need to implement both:
Then, every time we see a "create" event in the trace, we can lookup the state of the smart contract after it finished running the constructor to retrieve the bytecode.
The text was updated successfully, but these errors were encountered: