Author

Topic: Bitcoin Unlimited Consensus Broken.. (Read 363 times)

legendary
Activity: 4424
Merit: 4794
July 19, 2017, 12:19:39 PM
#2
lol.. article to scare people.. mainly fud

so lets clarify

1. think of the "maximum acceptable block size" as the hard consensus (like todays1mb) and the "excessive block size" as the policy (like the last 8 years 0.25-0.999) and same rules apply.
only now nodes and POOLS have a symbiotic control of the 'policy' (EB) movement. rather than just POOLS

2. 'miners' are just asics. they hold no hard drives, no blocks, they just process hashes. meaning 'miners' do not really matter in what is 'capable' as it is and always has been what a POOL decides to collate the data as, and then NODES of the network to accept and form the highest height as their data 'seed'(torrent analogy) for other nodes to leach off of.

3. 'forks' does not mean split chaining, forks means changing the levels rules. ofcourse changing the levels of a rule = changing the levels of a rule.. and yes dynamics means it will happen more often.. this is a good thing. it means no longer are we wasting 2+ years waiting on developers to be god like creatures. the network itself makes the decision. not puppetmasters.

4. let me make this clear. even if there was a pool of 90% hash power.. if only 10% of nodes accept the blocks of the 90% hash power.. the block will not be accepted, due to the nature of consensus. we have seen it already. the network has dropped blocks that do not fit the acceptable rules of the network. these are called orphans. they get dropped in seconds without caring or second thoughts about hashpower that pool carries. rules are rules after all.

5. the reality is that these mechanisms actually make pools more reliant on the network and makes pools more cautious. because they can try all they like to make a block of XXmb .. but if the nodes dont like it.. it has been a waste of time for the pool. the reality is that we will see pools making small tweaks to the level, NOT large tweaks. they will take baby step increments which the node network would happily receive.
to a point where the majority of nodes do not like it and at which point. the pools slow down or stop, until the nodes recheck their capabilities and new acceptable levels are available to grow to.

so in short. do not be fooled by the Fudsters screaming "gigabytes per nidnight" because the EC and other dynamic parts are actually EXTRA safety buffers and mechanisms, that will help the symbiotic relationship. they are simply taking away the puppetmaster dev control. and putting the control back into the hands of the symbiotic relationship of the network
Jump to: