wow, i just wasted so much fucking time...... at least i'm six beers and two joints in......
I haven't seen many people at all suggesting that "it is wrong to hard fork." could you point to any examples?
There are many examples of this, I have been arguing this point since I have entered this discussion, most recently:
Changing BTC as it is now, it means its dead. Leaving as it is now, it means dead too. I am not sure how BTC can survive in these circumstances.
I see many PRO and AGAINST fork.
so, in other words, no examples. okay.
In fact, i've seen quite the opposite from XT opponents. i'd love for you guys to fork now with a mining minority, so we can write the epilogue on this embarrassing chapter in bitcoin's history, when a group of developers tried to use populism to break consensus.
That is a ridiculous thing to say, Bitcoin XT does break the consensus mechanism and I will repeat again that XT will only cause Bitcoin to fork if 75% consensus is reached.
75% "consensus"? why not 51%? call it what it is, an attack. if the fork were capable of achieving consensus, why the need to force 1/4 of miners (or more, given the possibility of lucky runs) into submission? that is not "agreement." what you're looking for is a democracy, where a temporary majority forces its will on the minority---not so unlike a 51% attack.
please look elsewhere.
do me a favor: link me to the last hard fork that forked based on 75% hashing power or less. then consult the
Merriam-Webster dictionary and see the first definition of "consensus":
1 a : general agreement : unanimity
i'm wondering why we should ignore bitcoin's history, common usage and common sense based on little more than your propensity to construct sentences where "75%" is placed next to "consensus."
ever notice how "majority" is used several times in the bitcoin whitepaper in the context of transaction validity? yet "consensus" is used only once in regards to "needed rules and incentives." gosh, i wonder why that might be?
i've seen many suggesting that it is wrong to promote a contentious hard fork, because it threatens to break the consensus mechanism. that's a lot more risky than forking with a hashing minority. in the latter case, XT will just die as any invalid chain does (perhaps its life could be temporarily extended with checkpoints). in the former case, we would have multiple surviving blockchains.
It is not wrong to support a contentious hard fork. In the same sense that it is not wrong to support a contentious political party. The definition of contentious being "causing or likely to cause an argument; controversial." Synonyms of contentious are controversial, disputable, debatable, disputed, contended, open to question/debate. I do not think that these things should be considered wrong to support, furthermore who decides what is considered contentious? If anything this is actually a good example of a mentality that does promote group think so to speak.
https://en.wikipedia.org/wiki/GroupthinkThe similarities with the Bitcoin community and group think are uncanny. You have actually inspired me to further research this, really take a look for yourself in the wiki article, even if this is not the case with the current blocksize debate this could very well cause other problems down the line, we do need to make important decisions collectively that will determine the future of Bitcoin after all.
supporting a contentious political party does not "threaten to break the consensus mechanism" or result in "multiple surviving blockchains." stop blathering about the word "contentious" (red herring) and analyze the idea of a "contentious hard fork." try addressing the arguments made rather than baselessly throwing around the term "groupthink" as if that's relevant. this is a really dishonest form of debate. and i'm quickly losing patience with your impressive ability to write an incredible amount of words and still say absolutely nothing to address the points made. you just throw around meaningless opinions that boil down to a complete lack of understanding of technical issues.
the specific misinformation i was speaking of here was your assertion that "power" could be "centralized" among Core developers. that's patently false
That is not misinformation since "power" becoming to "centralized" among Core developers is a complex and nuanced multifaceted issue, even subjective. Therefore you can not say it is false as if it is some sort of fact, since we can not objectively measure or observe such things using scientific methods, this type of thinking is in the realm of the humanities. Which is why I felt like I could contribute to this discussion with my background in political philosophy, especially considering that most people in our community have technical backgrounds. You can of course say that you disagree, but that is different to saying that something is false.
it's almost as if you sit with a thesaurus next to you, believing that using the ideal synonym will win the argument.
firstly, re-read what you wrote earlier:
Centralization of power can not develop in the Core development team, exactly because of this ability to hard fork away from the Core development team. It is this mechanism that ensures this aspect of Bitcoins freedom. Which is why intrinsically at least it is not wrong to hard fork away from the Core development team.
secondly:
how can centralization of power develop, in this context? i argue that it cannot. there is no power. this greatly differs from the protocol-level discussion where the various parties hold some level of power to hold the others accountable (e.g. nodes have the power to enforce the protocol and render a miner's fork invalid). these incentive-induced checks and balances have absolutely fuck-all to do with developers. development is completely external to the protocol, and developers have zero power to enforce code on anyone. all this "centralization" talk in the context of development is a silly red herring to confuse simple-minded people who take the word at face-value without thinking about it.
bitcoin is not closed source. that's the only instance in which developers can hold any power over users, nodes and miners. otherwise the latter parties can simply audit the code and opt to run another version.
stop using it as a way to rationalize promoting implementations that lack merit. you repeatedly do this: when someone criticizes the merit of XT (for whatever reason -- node centralization, increased latencies, bandwidth/storage limitations, IP blacklists, etc) you concoct this falsehood that "supporting anything besides Core" is rational in order to "decentralize" development.
This is not true, I have actually addressed these issues you mention and there are certainly pros and cons to increasing the blocksize, it is certainly not clear cut and it should indeed be a balancing act. I have also never said that I "support anything besides Core", to be clear this is not what I believe.
i've watched your attempts at debate for some time. you never address the technical issues. rather, you write some "words" in response and use terms like "balancing act" to dismiss technical criticisms without addressing them. a cursory glance at the rest of your response here shows more of the same. your method of debate is never to address the points made, but rather to say "I don't think that is true" or something similar, then state your general "feelings" about the topic. merely writing a response to an argument is not sufficient to prevail in a debate. you're wasting everyone's time.
Ive made clear this does absolutely nothing to "decentralize" development; by definition, open source development is decentralized. so, in effect, you are using a patently false argument to baselessly argue in favor of XT.
Decentralization is not necessarily that easily measured, it is a spectrum after all. I have also never used decentralization of development as an argument in favor of XT. I support BIP101 because I think that increasing the blocksize according to the schedule in BIP101 is better then not increasing the blocksize at all. I do use decentralization of development and freedom as justifications for supporting BIP101 when confronted with the accusation that it is wrong for me to choose an alternative implementation because it is contentious.
suggests power and authority. you can dance around the subject all you want, but developers have no power or authority to do anything. they can release code; others can choose to run it or not. that goes for anyone, Core or otherwise.
and you've certainly used centralization of development (under Core) as an argument in favor of XT. and yes, your position on BIP101 is clear, too---you dismiss all technical issues while showing a feeble understanding of them, and conclude therefore that it is acceptable. your assessment of node viability under drastically increased block size the other day on the basis of calculating the downstream speed of one node---that was just
too cute.
no one said not to choose an alternative implementation "because it is contentious"---just another straw man. i said that a contentious hard fork threatens to break consensus and could result in multiple blockchains. that is why a contentious hard fork should be avoided.
further, erroneously projecting "centralization" onto Core is no mistake, as it has a loaded connotation among bitcoiners. this is a pretty dishonest form of debate, hence "misinformation" and "fallacy."
Because I am using a fairly subjective term like "centralization" which you think is erroneous. You think I am therefore "dishonestly" using "misinformation" and "fallacy". First of all it is obviously not misinformation as I explained before, secondly I do not see the fallacy, you should at least tell me what logical fallacy I am using or explain how what I am saying is a logical fallacy. I can give you an example, calling me dishonest is a case of ad hominem.
"centralization" isn't subjective at all in the context of bitcoin, hence your use of it to spread fear around Core development. it means "concentration of power" and you know it. ad hominem? i didn't say anything about you. i said it was a dishonest form of debate to concede that---
Centralization of power can not develop in the Core development team, exactly because of this ability to hard fork away from the Core development team. It is this mechanism that ensures this aspect of Bitcoins freedom. Which is why intrinsically at least it is not wrong to hard fork away from the Core development team.
---then afterwards, go on to continue to project "centralization" repeatedly on Core development. that's a red herring, as i have stated repeatedly. you are either unaware of common usage (unlikely), or you are attempting to project a loaded idea onto Core development with no basis. what "power" do developers have, exactly? last i checked, no one was forcing me to run anything.
if you fear that people don't properly understand that bitcoin is open source and will blindly follow any implementation they are told to, that doesn't amount to centralization of power. the developers still have no power to force anyone to do anything. peoples' ignorance does not change that.
Peoples ignorance does change that. Modern democracies are a great example of this, their dysfunction is largely fueled by peoples apathy and ignorance.
no. peoples' ignorance does not grant developers power to do anything. as always, everyone involved at every level has the freedom to do anything they want in this context. fork whatever they want, run whatever they want. this is just irrational fear mongering. you're trying to suggest in a quite illogical way that "people are ignorant" --> "Core is bad"...... sorry but no.
Many people today live in a cage that they do not know they can break out off, this is true for the present political system, even though it is based on their ignorance it still empowers the status quo.
In the same way if more people thought in the bizarre way that you described it would still give more "power" to the core development team even if just in the form of influence, which can be seen as a type of centralization of power.
nobody cares about your irrelevant analogies to modern democracy. they say nothing.
right, right, right... so more of this "people are ignorant" --> "Core is bad". really compelling.
expertise =/= power.
who
ought to have influence on discussions of bitcoin's security and technical viability? perhaps those with expertise in large scale systems engineering, database programming, who have established themselves as experts on cryptographic money? or should it be people who don't know have a technical background or technical understanding of the protocol, who "majored in political philosophy in college?"
serious question.
Bitcoin is far more then just open source in regards to decentralization. The consensus mechanism allows for much more complex and robust decision making processes to take place, the possibilities of which we are only just starting to explore.
oh? like what? do tell. i really don't even know what you're talking about.
So you are saying that we need a centralized review process within specific versions which is therefore centralized, which applies to Core and XT, I can agree with that. However extending that logic I can say that two centralized review processes are more decentralized then just one. I can even go further and say that the more of these centralized review processes are started through more alternative implementations it would make development even more decentralized. I do not see how this logic can be flawed, in the same sense that two nodes are more decentralized then one, increasing the node count increased decentralization, the same is true for Bitcoin development.
what makes an open source project decentralized is a lack of centralized control. again, as gavin and hearn showed us, no one has centralized control. that is true now, it is true with a billion code forks. get over it. this is a non-issue. as i said earlier, an open source project is decentralized by definition---prove me wrong.
and in that sense, no, it is not comparable to nodes at all. for the billionth time, go ahead with your alternative implementations. no one cares.
Thinking that we should only have one of these centralized review process so that people can no longer "hijack" Bitcoin and make any changes is inconsistent with the principles of decentralization. It is also completely missing the point of the Bitcoin consensus mechanism to think that if we do not have a centralized review process that the supply of Bitcoin will be increased. Bitcoin is meant to be distributed, decision making collective, psychology and game theory align incentive. This is why we do not need a centralized review process, at least not in the form of a singular one since that is the very definition of centralization after all.
I support BIP101 however I do not favor it, If BIP100 where implemented I would support that instead.
i've said repeatedly that alternative implementations are fine. please stop it with the straw men. you can lay off with the "principles of decentralization" since an open source project is decentralized by definition. the consensus mechanism refers to the protocol, not the development process---please make an effort to at least act like you have a basic understanding of bitcoin, rather than constantly reducing it to vague political ideas.
it really seems you're even having trouble constructing coherent sentences at this point. i really can't imagine i will continue this conversation. i have no doubt you will write an endlessly long reply that is little more than your opinions repeated over and over. cheers.
