@evoskuil I am talking about the required dependencies in the readme. please compare the two sections "next install the build system" in libbitcoin-system and libbitcoin-server
The leading provider of test coverage analytics. Ensure that all your new code is fully covered, and see coverage trends emerge. Works with most CI services. Always free for open source.
@michael I see now. https://coveralls.io/github/libbitcoin/libbitcoin-system thanks :). my issue was unnecessary. I didn't know it would happen so fast :). I have already created a build status PR. I can add a new one for coverage fix
The leading provider of test coverage analytics. Ensure that all your new code is fully covered, and see coverage trends emerge. Works with most CI services. Always free for open source.
Changes like this tend to generate problems for a long time, which is why we put it off for so long, but overall Phillip’s codegen work has kept it under control.
libbitcoin-consensus is optional. What is it for? What is the purpose of this library? I ask as somone who has not looked at the code. Is that some kind of check that somehow checks the consistency of the two implementations (core and libbitcoin)?
In short, it's the consensus critical code from bitcoind, wrapped as a library, which can be used to help ensure consensus consistency. Libbitcoin implements consensus natively as well, which is used if that external library isn't used.
@evoskuil the tool I linked you is for parsing C++ functions, types and classes using clang. My idea is to parse C++ to autogenerate C bindings. You know C has a higher marketshare than C++, and it's far easier to generate Python bindings too.
Right now I'm studying Google's Flutter which I think will become the most popular UI framework - it can be used for desktop (win/mac/linux) but with a focus on mobile (ios, android), and will be the default for Google Fuschia. It also implements a new native FFI interface that so far only works with C (although they plan C++).
@evoskuil "V4 does but doesn’t report it yet.", "V4 has percentage downloaded and percentage confirmed information" can I find this info in the bs output?
Client libs are but the node is not yet production. I’m home now for most of the next two months and hopefully I can finish the blockchain work. That’s the main holdup. It works but it’s not ideal.
Re: v4. Client side is close, with a pending PR (https://github.com/libbitcoin/libbitcoin-explorer/pull/627). There's an issue noted there as well, but not sure where that issue is (i.e. client side, or perhaps database, or somewhere in between)