I assume this has been well discussed in at some point in the Bitcoin
community, so I apologize if I'm repeating old ideas.
Problem exploitable nodes:
It is plausible that people running these versions of bitcoind may not
be applying patches. Thus, these nodes may be vulnerable to known
exploits.
Perhaps if there were a message that would nag your stdout or log output
letting you know there's a new version available, or N more versions
available and that you might be missing out on X security patches, Y
protocol improvements, depending on how far back you are, you'd be tempted
to upgrade, w
On Thu, Dec 15, 2016 at 4:38 AM, Juan Garavaglia via bitcoin-dev
wrote:
> Older node versions may generate issues because some upgrades will make
> several of the nodes running older protocol versions obsolete and or
> incompatible. There may be other hard to predict behaviors on older versions
>
Maybe there are still some advantages but I don't know why this is not
considered as a major issue by the bitcoin community for the future and
why this looks to be never discussed:
- the size of the bitcoin network in terms of full nodes is ridiculous
and this is continuously decreasing, we cannot
Today according to the stats at https://bitnodes.21.co/nodes/ the top 10
Bitcoin running node versions are:
1.
_Version Satoshi:0.13.1
_Nodes 2071
_38.97%
2.
_Version Satoshi:0.12.1
_Nodes 1022
_19.23%
3.
Satoshi:0.13.0
_Nodes 604
_11.36%
4.
Bitcoin Unlimited:0.12.1
_Nodes 373
_7.02%
5.
