On bad reporting

[vc_row][vc_column][vc_column_text]A thought experiment:

You have a service located in a specific building.

Only people who are given access to this building are allowed to store their valuables in this building.

The building itself is otherwise unassuming and therefore safe. It’s supposedly a very, very safe place to store stuff.

You have thought this out very well, and there really is nothing unsafe about this location, and so you are eager to get on with business.

You are going to recruit people to store their valuables with you by handing out business cards with the address on it.

However, someone has deftly pickpocketed your cards and replaced them with a set that has the address of an equally safe and unassuming building on it.

Eagerly, you start distributing the cards.

Then you get a phone call from your colleague who says no one is showing up.

You check the cards, realise your mistake…


Question: who do you blame? The safe house or the person who didn’t check the address on his cards?

News? Rather olds.

If we are to believe CNBC, Business Insider and even Coindesk, this is just another example of things that happen in ICO’s.

“Welcome to the lawless world of ICOs.”, CNBC tells us. Business Insider knows that “Cryptocurrencies like bitcoin and Ethereum have long had a reputation as being somewhat of a “Wild West,” beset by hype bubbles, scams, and hacks — and that seems unlikely to change any time soon.”

The glee is almost palpable in all news about the hack, but the one thing that all except Motherboard fail to mention is that the hack was of a the ICO website, not any contract or whatsoever.

Coindesk even has the gall to say “The hacking of this ICO is reminiscent of last year when $50m was stolen in a similar fashion from a project called The DAO. “, a claim so woefully off the mark one wonders if the writer knows what industry he is working in and if he was even around when the DAO fiasco went down.

Of course, that statement is preposterous. The DAO hack was an exploit of a badly coded smart contract allowing the attacker to siphon of ETH. Coindash’s mistake is much more basic: bad website security.

Can the stupidly bad news gathering stop?

I am sorry, but stupid is stupid and I am not going to let it lie.

To date, we’ve had numerous scams, outrageous mistakes, exchanges folding and huge intercommunity fights in crypto. Really, in the last three and a half years, I’ve seen a lot.

What I haven’t seen yet, however, is a real hack of a large blockchain.

And any journalist worth his salt should be advised to include that in his reporting if he doesn’t wish to be ridiculed as an idiot from now on.

Sorry guys: you want to report on blockchain, the least you need to do is get educated. History, especially if it can be preserved like it can now, is generally not kind to people who are willfully idiotic in their profession.

Yes, even a blockchain can be hacked, provided it’s small enough to be unsafe. A worthless PoS chain or a nearly non-mined PoW chain is frankly useless. It’s useless because it’s unsecured. However, the large chains are much, MUCH harder to succesfully attack, and therefore aren’t.

Basic reporting should from now on include WHAT was hacked and why it was possible. If not, it’s just bad reporting.




[/vc_column_text][/vc_column][/vc_row][vc_row preset=”preset_0″ content_preset=”_preset_0″][vc_column width=”1/3″][vc_separator border_width=”2″][vc_column_text]

I believe in earning bitcoin.
If you think my work has value, leave a donation using this button.

[/vc_column_text][vc_raw_html]JTNDY2VudGVyJTNFJTNDZGl2JTIwaWQlM0QlMjJjZDE3NiUyMiUzRSUzQyUyRmRpdiUzRSUwQSUzQ3NjcmlwdCUzRSUwQSUyMCUyMCUyMWZ1bmN0aW9uJTI4YyUyOSU3QnZhciUyMHQlM0Rkb2N1bWVudC5jcmVhdGVFbGVtZW50JTI4JTIyc2NyaXB0JTIyJTI5JTNCdC50eXBlJTNEJTIydGV4dCUyRmphdmFzY3JpcHQlMjIlMkN0LmFzeW5jJTNEJTIxMCUyQ3Qub25sb2FkJTNEYyUyQ3Quc3JjJTNEJTIyJTJGJTJGbGFiLnN1Ymluc2IuY29tJTJGcHJvamVjdHMlMkZmcmFuY2l1bSUyRmNyeXB0b2RvbmF0ZSUyRndpZGdldC5qcyUyMiUzQnZhciUyMGUlM0Rkb2N1bWVudC5nZXRFbGVtZW50c0J5VGFnTmFtZSUyOCUyMnNjcmlwdCUyMiUyOSU1QjAlNUQlM0JlLnBhcmVudE5vZGUuaW5zZXJ0QmVmb3JlJTI4dCUyQ2UlMjklN0QlMjhmdW5jdGlvbiUyOCUyOSU3QiUwQSUyMCUyMCUyMCUyMEZyLmxvYWRDRCUyOCUyMmNkMTc2JTIyJTJDJTIwJTdCJTBBJTIwJTIwJTIwJTIwJTIwJTIwY29pbiUzQSUyMCUyMmJpdGNvaW4lMjIlMkMlMEElMjAlMjAlMjAlMjAlMjAlMjBhZGRyZXNzJTNBJTIwJTIyMUJhc1dpNEpDcVEzSkJCVlB5RHBLZ3h3OVhiZ2NpaUdIVyUyMiUyQyUwQSUyMCUyMCUyMCUyMCUyMCUyMGJ1dHRvbkNsYXNzJTNBJTIwJTIybGFyZ2UlMjIlMkMlMEElMjAlMjAlMjAlMjAlMjAlMjBkaWFsb2dDbGFzcyUzQSUyMCUyMmxhcmdlJTIyJTJDJTBBJTIwJTIwJTIwJTIwJTdEJTI5JTNCJTBBJTIwJTIwJTdEJTI5JTNCJTBBJTNDJTJGc2NyaXB0JTNFJTNDJTJGY2VudGVyJTNF[/vc_raw_html][/vc_column][vc_column width=”1/3″][/vc_column][vc_column width=”1/3″][vc_separator border_width=”2″][vc_column_text]Sign up for my newsletter:

[mc4wp_form id=”6597″][/vc_column_text][/vc_column][/vc_row]
Bas Wisselink
Follow me
Latest posts by Bas Wisselink (see all)

Add comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Recent Comments