Yes I have. Including the comments about the untested random walk model. Why introduce a new unprove consensus system. Can we please not just increase the blocksize?@jonny1000 You have read the FAQ, haven't you?
https://www.reddit.com/r/btc/comments/56yhnq/have_you_read_the_bu_faq/
But why give Core the massive asymetric advantage by allowing them to wipe away the BU history, when BU cannot wipe away Core's history? At least make is symmetric then more people may support BU, since many do not want to be on the losing side. Please let me know the disadvantage of removing this large advantage for Core? Or do you people hate me so much for trying to make the hardfork safer and more successful, that you are not even willing to consider this? Please at least hear me out and let me explain why giving Core this asymmetric advantage is so compelling for speculators.The dowside of this perverted nakamoto consensus (5% Veto right to a group of vandals) is, that progress cannot happen. Of course you know that already.
They would be buying Core coins or even just double spending.Bitcoin.com and BU getting "very huge" are two very different things. Perhaps you do not understand the immense pressure miners are under to just break even, let alone make a profit. Pulling a stunt like this would be an extremely dangerous move for a pool. How exactly would it pay them back in the long run?
Agreed. That is why I in principle support BU, I just disagree with the default parameters.@jonny1000 You need to remember that BU hasn't actually done anything that isn't already possible. They've simply moved the blocksize parameter from the compiled source code to a variable that can be set by the GUI. That is it! If the Bitcoin ecosystem continues to grow then these types of client modifications will inevitably become common-place and system will need to be able to deal with it. You cannot stop this.
Please be respectful of the ethnicity. None of the problems on ether side are caused by "Chinese culture".And maybe it's time for some people to rethink their assessment of "Chinese" miners. And the alleged culture of leaders and followers. Repeated before, but the most anti-bitcoin pools/miners are Bitfury and BTCC, both lead by people from "the west".
Ok so you do not like a threshold of 90% or more. Would at least 75% be ok?The quoted question is just more trolling again. The author has already give us the answer answer to his question and that is it requires we have 98% agreement on what is safe and what is possible. He may have changed his opinion to 100% - if he has he is welcome to correct me.
A better question to ask is: What is the downside of making the hardfork to increase the blocksize limit practically safe? and I feel confident everyone here agrees the answer is: nothing.
No that's not how it works. After activation 100% of miners are required to upgrade or their blocks will be orphaned.mengerian said:Say a Segwit soft fork activates on the network with (for example) 75% support. To the 25% of miners who do not support Segwit, the Segwit outputs appear as "ANYONECANPAY". This creates a danger for this 25% of miner is that if they include a transaction in their block that spends one of these outputs, but does not conform to Segwit rules, then that block would be orphaned by the Segwit-supporting miners. This puts pressure on them to join the 75% majority and support Segwit.
Because so many miners are just waiting for the day they can attack & double spend the system they rely on. Sorry, I don't buy it. That is one shitty high risk attack with low profit potential.They would be buying Core coins or even just double spending.
They can simply set the version bits needed to prevent their blocks from being rejected, build on the longest chain, but refuse to include Segwit inputs in the blocks they build. All this can be done without them needing to run any Segwit-processing code.No that's not how it works. After activation 100% of miners are required to upgrade or their blocks will be orphaned.
That's nice. However, I don't think it's in my best interest to restrict my consideration of potential future events to your understanding of Core dev intentions.Also activation is 95% not 75%. My understanding is most Core devs respect the rights of a 10% miner to veto SegWit.
All you need to do is make one block at any time. This is a very easy and cheap attack. Just allocate 0.1% of the global hashpower to it and it happens once per week.That is one shitty high risk attack with low profit potential.
Yes miners could false flag and say they upgraded to SegWit when they have not. They could then refuse to include inputs redeemed when the signature is segregated. This is censoring transactions. These miners would still need to upgrade to a special censorship node.mengerian said:They can simply set the version bits needed to prevent their blocks from being rejected, build on the longest chain, but refuse to include Segwit inputs in the blocks they build. All this can be done without them needing to run any Segwit-processing code.
Why is the BU community so hostile to skeptics pointing out weaknesses and potential fixes in BU? If the hostility is too strong, BU will be too weak. Skeptics should be welcomed to help make BU robust.@jonny1000
I'd like to pass the gagball to you. Do you accept it?
Let's just ignore my points and carry on spewing the same bullshit.All you need to do is make one block at any time. This is a very easy and cheap attack. Just allocate 0.1% of the global hashpower to it and it happens once per week.
Because your 'weaknesses' are nothing but bullshit you've pulled out of your ass.Why is the BU community so hostile to skeptics pointing out weaknesses and potential fixes in BU? If the hostility is too strong, BU will be too weak. Skeptics should be welcomed to help make BU robust.
Looks like he heard you:Oh: And I would love to have /u/raisethelimit return. If s/he's reading this, would totally love some new cartoons I think enough stuff happened for some new biting visual commentary.
I take that as a no.Why is the BU community so hostile to skeptics pointing out weaknesses and potential fixes in BU? If the hostility is too strong, BU will be too weak. Skeptics should be welcomed to help make BU robust.