Quote from: Quantus on April 28, 2017, 07:09:02 PM

wow just wow, you just went full retard franky1.

1. DNS seeds can RPC call the nodes EG trigger some buggy code in implementations - we all know thats possible

2. i wanted to see how many people would reply to protect the blockstreamers access to all nodes, and see if them same people are the same people screaming blue murder about anything not core having similar access to things that are not core. such as asics or other implementations. as an experiment on who factually knows whats possible and who is speculating about worse case scenarios.

i find it funny when people create drama about one thing, but are not equally as critical about the other

ever ask yourself why there are no 0.8 or below nodes on the network
and how easy it could be to start making other implementations not have access.
EG anything below 0.13.1 (70014) can find themselves 'lost'

#define REQUIRE_VERSION 70001
if (clientVersion && clientVersion < REQUIRE_VERSION) return false;

simply change to

#define REQUIRE_VERSION 70014
if (clientVersion && clientVersion < REQUIRE_VERSION) return false;

and anything not segwit just wouldnt get a list of nodes from a DNS

and most of the segwit users wont want to manually white list old nodes to offer up a nodes list the other way.
hence why even the segwit documentations says

https://bitcoincore.org/en/2016/10/27/segwit-upgrade-guide/#not-upgrading-1

Quote

The easiest way to prevent this problem is to upgrade to Bitcoin Core 0.13.1 or another full node release that is compatible with the segwit soft fork. If you still dont wish to upgrade, it is possible to use a newer Bitcoin Core release as a filter for older Bitcoin Core releases.

Filtering by an upgraded node

In this configuration, you set your current Bitcoin Core node (which well call the older node) to connect exclusively to a node running Bitcoin Core 0.13.1 or later (which well call the newer node). The newer node is connected to the Bitcoin P2P network as usual.
For the older node, first wait for the newer node to finish syncing the blockchain and then restart the older node with the following command line parameter (this may also be placed in the Bitcoin Core configuration file):

yep if you dont want to upgrade. you have to still download a segwit node just to whitelist yourself.

which makes me laugh about the whole "everything is fine segwit is backward compatible and no need to upgrade" promises of segwit going soft

i hope this wakes you up to the TIER network of gmaxwells (upstream filter) and (luke JRs bridge node) word twisting of said tier network of control
where blockstream becomes top of the foodchain..