This morning I tagged release of the full stack.

=====================================================
libbitcoin-server     2.2.0  (config updates)
libbitcoin-node       2.2.0  (sync fixes, config)
libbitcoin-blockchain 2.2.0  (sync-related updates)
libbitcoin-consensus  2.0.0  (satoshi v0.12.0)
---
libbitcoin-explorer   2.2.0  (p2p, config)
libbitcoin-client     2.2.0  (compatibility)
---
libbitcoin            2.10.0 (p2p, bip65/66, config)
=====================================================

There are no open bugs in any version 2 branch.

OSX (clang), Linux (gcc|clang) and Windows (vc++) builds are supported
and regularly tested for all libraries. Prebuilt, single-file, signed
executables for all three environments for BX and BS are available here:

https://github.com/libbitcoin/libbitcoin-server/wiki/Download-BS
https://github.com/libbitcoin/libbitcoin-explorer/wiki/Download-BX

The objective of this release is to improve the quality of the node. I
think you will be pleasantly surprised.

Initial sync time is down to a few hours (down from a few days to
weeks), depending on your network and luck in selecting peers. Sync can
be completed hands-off, although a little tuning may still improve
performance. This is not a headers-first implementation, it’s just a lot
of repair work to the existing implementation, using learning from work
in version3.

It's important to understand that BS is yet not a good citizen on the
p2p network. Formerly there was no support for the get_blocks message,
and there is still no support for get_headers. In this update I have
implemented support for get_blocks, so that in theory a libbitcoin peer
could sync with another. I have not yet spent any time testing this
capability. Satoshi nodes require get_headers and therefore cannot sync
with BS. There are similar issues pertaining to transactions. However,
version 2.2.0 is far better than past versions in terms of protocol.
Version3 will support the full network protocol, with the exception of
filtered blocks (Bloom filtering).

Both native (libbitcoin) consensus and libbitcoin-consensus now use
libsecp256k1, so OpenSSL is no longer present (again).

Configuration options have expanded and changed somewhat, please take
care in updating. Also, the default configuration is based on sync, not
post-sync operation. You will need to adjust settings after you pass
your last checkpoint. For more info see:

https://github.com/libbitcoin/libbitcoin-server/wiki/Configuration-Settings#default-settings


e