zeptin

That isn't really workable with an HD wallet, as the default address gap limit means that the wallet won't detect incoming transactions for address indexes that are too far away...

Looking into this in more detail, the reason why the version is incorrectly set is actually due to the following: `ConnectionManager` calls `CreateNetworkPeerServer` without specifying the version parameter: ``` NetworkPeerServer...

@bokobza Note that the protocol version actually gets used in several different payloads. But yes, it does. `7c1101` = `70012` when you flip the endian-ness and convert to decimal: ```...

(The above are some incoming connections from testnet. They all sent `sendprovhdrs` during handshaking, so they have presumably not applied 2733 or 2727 yet)

Examining this further, there appears to currently be no impact having this flag set. The `NetworkPeer` code makes a distinction between preferred and supported transaction options, and the witness option...

Can you give examples of how you would optimise the one over the other? There is a cost to converting between formats that may remove any perceived advantages, particularly for...

My initial understanding of this is that the `Algorithm014` folder represents the implementation as it existed in Bitcoin Core 0.14. There were changes in 0.15 described here: https://gist.github.com/morcos/d3637f015bc4e607e1fd10d8351e9f41 So I...

I looked into this further, we are missing a few defined bits from the enum (e.g. `NODE_NETWORK_LIMITED`, indicating a pruned node). However, the required services in the block puller get...

Note that in the scenarios above a Core bitcoind was used to generate 433+ blocks, thereafter SBFN was allowed to attempt to synchronise with it.

This approach looks sound, and I don't see any problems with the PR per se. However, this functionality is effectively mimicing what the `BuriedDeploymentsArray` within `NBitcoin.Consensus` class is already being...