The Final Blocksize Showdown Round 1 Opens, Who Will Win the Skills Test? – Trustnodes

The Final Blocksize Showdown Round 1 Opens, Who Will Win the Skills Test?


After years of blocksize debate, the final showdown is here, as round one opened yesterday with some code changes in the segwit2x client.

Their move to camouflage nodes is obvious and expected, but neither XT nor Classic did so. Their reasons were many, but excuses are irrelevant.

Because at this stage, it is neither miners nor businesses or users that matter. It is not words or censorship on reddit. It is coding skill alone that determines which way bitcoin goes.

For the next three-four weeks, the code is the show, as the two teams need to prove their higher skill in both maintaining and directing bitcoin.

We nonetheless will hear plenty of campaigning and over the top language, but they are just empty words. Code action talks.

XT failed the test. Their nodes were DDoSed, something difficult to protect against, but protect they could if they wished by making their nodes as good as indistinguishable.

They didn’t, with their nodes DDoSed again. Objectively, regardless of views on the blocksize matter, that most likely showed to all they couldn’t be fully trusted to protect the network.

Because instead of taking code action to throttle the attack, they relied on publicizing the event. But words no longer have sway at showdown.

The two teams are on their own, with just code and intelligence, as they sit the skills test.

Classic learned nothing from XT, with their opponents easily showing superiority by just DDoSing them. Allowing 1xers to say no more than two words without mentioning experience or experts.

Rightly or wrongly, for good or bad reasons, 1xers were right. The meme now is Andresen was or is naive. Perhaps. It’s irrelevant. He failed the skills test.

Bitcoin Unlimited never claimed any coding skills, not least because their lack of it was shown many times by their nodes being sent down crashing.

Needless to say, it made Bitcoin Unlimited untouchable by businesses very mindful of their need to secure customer’s coins as they saw 1xers show Bitcoin Unlimited developers to be amateurs.

Harsh, but coding tests are no kitty affairs. There’s a $70 billion market on the line and however much old bankers might call bitcoin a plaything, it really isn’t.

So this test matters and greatly. Primarily it is about code, but it is also more widely about rounded intelligence. Showing naivety, of course, means you failed. Asking opponents who hate you to play nice with your code also means you failed.

But there are instances when such test is not necessary. Bitcoin Cash was an amicable parting of ways largely supported by their opponents, therefore faced no real test.

Segwit2x is different and the test has already begun. So far, they have passed, by responding to Bitcoin Core’s locking out of their nodes with camouflaging segwit2x clients.

A pass for one necessarily means a failure for the other as far as showing skill, both in code and intelligence, is concerned.

But the campaign has only begun. We are to enjoy four more weeks of Core Wars as the most skilled bitcoin developers go head to head to determine the trajectory of the people’s money.

Garzik is highly experienced, very senior and undoubtedly one of the most skilled bitcoin coders. He has also shown concrete intelligence.

But the team that defeated three, with two of them having highly skilled coders, certainly has all of Garzik’s qualities.

The question is which one is more skilled, in all ways, within the confines of code. The answer to that we will find out soon, as the two teams go head to head to prove they are to be trusted.

Because whoever is left standing with the best code, will most likely be known as bitcoin, for if they could defeat all others in the skills test, then the reward is well earned.

So best of luck to both teams and may the best win.


Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>