You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could be considered a sort of a memo and a discussion ticket on loading custom transaction tracers in Nethermind without compiling the main code source code.
I had a question with @tkstanczak on the channel about persisting transaction data to a separate database while syncing a full node. In effect this would allow one to build a system functionally like an archive node if being able to maintain the information otherwise but without managing a large storage in a flat file system. Basically the case described at ethereum/go-ethereum#2104 (comment) while syncing. A similar case is storing VM trace data to a separate system.
To do this currently one needs:
Acquire the source code.
Implement a custom tracer and compile a custom version of the software.
Run a custom version of the software.
During the discussion the following pieces of software were presented as points of modifications:
It appears respecting the license the modifications ought to be available somewhere. Either in this repository or perhaps a fork and one question then is what quality of work should be added to the main project and if it would be purposeful to have very purpose specific code and examples available outside of the main codebase.
The need to implement the tracers in the source code and compile a custom binary and the license together prompts a consideration as to what would be needed to build a plugin where one can load external tracers into the system? What would such a subsystem need and what could be the extension points?
The text was updated successfully, but these errors were encountered:
This could be considered a sort of a memo and a discussion ticket on loading custom transaction tracers in Nethermind without compiling the main code source code.
I had a question with @tkstanczak on the channel about persisting transaction data to a separate database while syncing a full node. In effect this would allow one to build a system functionally like an archive node if being able to maintain the information otherwise but without managing a large storage in a flat file system. Basically the case described at ethereum/go-ethereum#2104 (comment) while syncing. A similar case is storing VM trace data to a separate system.
To do this currently one needs:
During the discussion the following pieces of software were presented as points of modifications:
IBlockProcessor
IBlockTracer
ITxTracer
And as concrete examples
GethLikeTxTracer
ParityLikeTxTracer
It appears respecting the license the modifications ought to be available somewhere. Either in this repository or perhaps a fork and one question then is what quality of work should be added to the main project and if it would be purposeful to have very purpose specific code and examples available outside of the main codebase.
The need to implement the tracers in the source code and compile a custom binary and the license together prompts a consideration as to what would be needed to build a plugin where one can load external tracers into the system? What would such a subsystem need and what could be the extension points?
The text was updated successfully, but these errors were encountered: