August 2025

I've started on the libbitcoin-network http stack. I'll be weaving this in between installing the remainder of my flooring over the next few weeks.

I'm moving a few p2p specific aspects from network::proxy into network::channel. This allows proxy (connection-oriented low level abstractions, such as simplified asynchronous message I/O) to be a general purpose layer over network::socket which wraps raw sockets (adding stranded handling of asynchronous I/O).

I just completed the proxy/channel refactor and did a full sync, no effect on perf, 58 mins to block 900,000.

Still on a trip, will join next week.

I tracked down and resolved a minor issue in the automatic pruning and snapshot events. Pruning of the prevouts table was invalidating any preceding snapshot, as snapshots assume that table bodies are append only. This was resolved by optionally incorporating prevouts head pruning into snapshotting. This ensures that the atomicity guarantee still holds, so that either the prune/snap succeeds, or the store remains recoverable under the most recent snapshot.

Hi! From the old messages in this channel I concluded that Libbitcoin node runs considerably slower on Linux than on Windows. Is this conclusion/assumption valid, or has anything changed in this regard?