Quote from: jonald_fyookball on May 10, 2017, 11:24:28 PM

Quote from: franky1 on May 10, 2017, 11:19:32 PM

Quote from: jonald_fyookball on May 10, 2017, 11:16:41 PM

Quote from: franky1 on May 10, 2017, 11:12:39 PM

pools didnt have the power of vote/veto until someone gave them that power.

How so? Don't pools decide what goes in the blockheaders and always have?

pools can collate data in any fashion they like.. but if nodes see it doesnt follow node rules that block is not accepted..
nodes then wait a few seconds for another pools that has a solution that does fit the rules and accepts that one instead.

thats what the consensus/orphan security feature is all about..

Right but if you're going to have signaling, then it has to be done at the pool level as long as there's pools. So I don't
see how "core gave the vote to the pools". What am I missing?

at the moment
34% sgwit flag https://blockchain.info/charts/bip-9-segwit
49% dynamics flag https://blockchain.info/charts/bitcoin-unlimited-share
=17% abstaining

lets say there was 100% dynamics flag for pools.. but at node level
only 10% nodes would accept a block over 1mb.. if a pool actually make a block any different than native rules. it would get rejected in 3 seconds

lets say there was 100% segwit flag for pools.. but at node level
only 66% nodes would accept a block in a segwit format. if a pool actually make a block any different than native rules. it would get rejected in 3 seconds by the nodes that dont have a segwit node to 'filter' 'bridge' them a stripped version.

the node network is slowly reconnecting and becoming a tier network, of the segwit nodes being directly connected to pools to allow the whole filter(gmax buzzword) bridging(luke jr buzzword) to help with the 'backward compatible' pretense.

its still not a perfect network setup and can still cause orphan drama.. so pools wouldnt try it if there was more then a few percent orphan risk.

this is why i said to gmax.. if segwit is so 'backward compatible' as promised. go get btcc to make a block thats segwit on mainnet and see how acceptable it is to give pools confidence to flag it..

gmax now knows that segwit is not as 'soft' / compatible as he/they promised in 2015 (before having production ready code..)

but in short
only counting pool flags is meaningless,