-
Notifications
You must be signed in to change notification settings - Fork 79
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
Split libsilkworm into silkworm_core & silkworm_db #110
Conversation
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.
Looks good to me
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.
Is a large change.
OOF now ...please let me check a full compile on Windows tomorrow morning
@AndreaLanfranchi Sure, thank you! |
@yperbasis looks good to me too. I still get a lot of warnings though mainly due to CXX17 deprecations on subprojects: abseil cbor and mdb.c mainly |
Codecov Report
@@ Coverage Diff @@
## master #110 +/- ##
==========================================
- Coverage 84.09% 83.26% -0.84%
==========================================
Files 51 54 +3
Lines 3848 3920 +72
==========================================
+ Hits 3236 3264 +28
- Misses 612 656 +44
Continue to review full report at Codecov.
|
Essential Ethereum protocol logic will live in core (block execution, RLP, root hash algorithms, etc), while silkworm_db will contain LMDB access logic and TG-specific things. The reason is two-fold. First, a smaller core library will make Silkworm easier to use for things like eth_call, where TG & LMDB paraphernalia is not required. Second, the smaller core can potentially be compiled into WebAssembly, which is a strategic goal for us (in particular for the Internet Computer project by Dfinity).