Quote from: jonald_fyookball on May 09, 2017, 07:23:46 PM

Quote from: franky1 on May 09, 2017, 05:34:30 PM

i have already, multiple times said to gmax, if segwit is so backward compatible why not just make a segwit TX, hand it to BTCC and get BTCC to make a segwit block containing a segwit tx. to show that its network safe and backward compatible..

would that block just get orphaned immediately right now?

nope(if the promise had merit/ were truly "backward compatible")
secretly YES, but shhhh

and thats the point in me saying for him to just do it.. because it then reveals its not as backward compatible and safe as promised.

what blockstream are not telling you is activation day is about changing the DNS seeds to make it so segwit nodes become the main tier of the network and old nodes are then manually add-noded as a secondary network layer

its ven in the documentation.. if you dont want to upgrade, you have to download segwit to use as a filter(gmaxbuzzword) / bridge(luk jr buzzword) to connect to the network

and then all the blocks are then stripped and formatted to the old nodes if the tier network allows old nodes to connect to it.
what will be noticed is the old nodes become part of a cesspit of incompatible nodes that connect and disconnect to other nodes that end up not having good block height, delayed syncing, or just prunned so that the amount of clean connectable nodes becomes harder to obtain.

as explained before

Quote from: franky1 on May 02, 2017, 08:15:46 AM

Quote from: jonald_fyookball on May 01, 2017, 09:56:39 PM

Franky, you should explain what you mean by tier network. I don't think anyone understands.

Quote

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' in the future

code in a DNS seed: (70001 is v0.8+)

Code:

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

simply change to: (70014 is 0.13.1+)

Code:

#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(addnode).
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, to be filtered down data from segwit nodes that ar upstream (a layer above, of a tier network).

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..

by tier, it means LAYERS. as oppose to a PEER network where the implementations are on the same layer (same level playing field)