-
Notifications
You must be signed in to change notification settings - Fork 71
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
capi: execute single transaction #2665
base: master
Are you sure you want to change the base?
Conversation
…ch/silkworm into capi-execute-single-txn
Also see erigontech/silkworm-go#13 for the related silkworm-go update |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great progress 👍 see comments
@@ -53,6 +53,8 @@ struct SilkwormInstance { | |||
std::unique_ptr<silkworm::rpc::Daemon> rpcdaemon; | |||
std::unique_ptr<silkworm::stagedsync::ExecutionEngine> execution_engine; | |||
|
|||
std::optional<silkworm::ChainConfig> chain_config; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also have this field inside instance.node_settings.chain_config.
I have on my TODO list to split it to be separate from NodeSettings, because we believe that NodeSettings should just only reflect static CLI options.
So even if duplicate - it is a change in a good direction :)
Adds execution of a single transaction to be called externally (Erigon 3).
MDBX was updated to v0.38.4, in line with Erigon 3.
Minor modifications made to the domain data access, no prev_step is necessary. Please take a look at the breakdown below of how data is stored in Erigon 3, also in the Erigon 3 book:
Account:
Code (has_large_values):
Storage: