<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mathias Frey on Medium]]></title>
        <description><![CDATA[Stories by Mathias Frey on Medium]]></description>
        <link>https://medium.com/@mathias.c.frey?source=rss-72b513db2f84------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*hDown8ZeHsK_nwo8</url>
            <title>Stories by Mathias Frey on Medium</title>
            <link>https://medium.com/@mathias.c.frey?source=rss-72b513db2f84------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:33:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mathias.c.frey/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What blockchain and submarines have in common]]></title>
            <link>https://medium.com/@mathias.c.frey/what-blockchain-and-submarines-have-in-common-2c65b7722bb3?source=rss-72b513db2f84------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c65b7722bb3</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[encryption]]></category>
            <category><![CDATA[submarine]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[warfare]]></category>
            <dc:creator><![CDATA[Mathias Frey]]></dc:creator>
            <pubDate>Fri, 08 Mar 2019 15:02:10 GMT</pubDate>
            <atom:updated>2019-03-08T15:02:10.869Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<blockquote>As a teenager I developed an awkward obsession for submarines after having read Tom Clancy’s <a href="https://www.amazon.com/Submarine-Guided-Inside-Nuclear-Warship/dp/0425138739">Guided Tour Inside a Nuclear Warship</a>. When summoned to the physical examination before joining the Austrian forces I got asked what part in the military I was the most interested in: I answered “submarines” — a somehow offensive answer given my country today, is land-locked and decommissioned its last sub roughly a hundred years ago.</blockquote><p>I have always been fascinated by the fact that naval warfare and my own field — IT — were so closely related. Studying the history of computing is like watching dozens of war and spy movies.</p><p>So here comes a list of such movies — a list I compiled mostly because my peers still look surprised when I start to annoy them with stories about encryption algorithms and their genesis in intelligence agencies, secret research labs and the military in general. Have fun!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vl120ljVMPcoTGZE8GFpWA.jpeg" /><figcaption>Cryptography, search theory, GPS-based timing, countless algorithms and programming languages— a lot of what is my daily reality of computing stems from (naval) warfare.</figcaption></figure><h4>Cryptography</h4><p>Although the securing of communication dates back <a href="https://en.wikipedia.org/wiki/Caesar_cipher">thousands of years</a>, things get really interesting with the invention of radio communication and the break out of the two World Wars.</p><p>Any wireless communication between headquarters and a submarine out in the ocean could be easily intercepted by enemy forces. Therefore the information needed to be encrypted. Most notably the Germans came up with the infamous <a href="https://en.wikipedia.org/wiki/Enigma_machine">Enigma</a> at the end of WW1 — a device that allowed the U-Boats to communicate with mission control leaving the Allies in the dark about their whereabouts and plans.</p><p>Interestingly US forces could simply talk in <a href="https://en.wikipedia.org/wiki/Code_talker">American native languages</a> unknown to Europeans.</p><p>See Jon Bon Jovi capture the Enigma from a German U-Boat:</p><p><a href="https://www.imdb.com/title/tt0141926/?ref_=nv_sr_1">U-571 (2000)</a></p><p>Key figure behind the invention of the modern-day computer <a href="https://en.wikipedia.org/wiki/Alan_Turing">Alan Turing</a> — back then hated for his homosexuality, today hated for <a href="https://en.wikipedia.org/wiki/CAPTCHA">hard-to-read images</a> on the internet — conducted world-changing research at <a href="https://en.wikipedia.org/wiki/Bletchley_Park">Bletchley Park</a> resulting in the codebreaking of the Enigma and a sudden end of German superiority at sea.</p><p>See Sherlock Holmes break the Enigma’s cipher thanks to repetitive patterns in German weather report data:</p><p><a href="https://www.imdb.com/title/tt2084970/?ref_=ttls_li_tt">The Imitation Game (2014)</a></p><p>Speaking of submarines and wireless communication there’s a name I have to mention as an Austrian: <a href="https://en.wikipedia.org/wiki/Hedy_Lamarr">Hedy Lamarr</a>. Besides her successful career as an actress in Hollywood she worked on radio-controlled torpedoes using a technology called <a href="https://en.wikipedia.org/wiki/Frequency-hopping_spread_spectrum">frequency hopping</a> that later made it into Bluetooth and several other communication protocols.</p><p>The 1970s gave birth to a completely different way of encrypting communication — asymmetric encryption systems were invented by research units and intelligence agencies. As of today a lot of these mechanisms might be already broken; e.g. Ethereum chose the KECCAK-256 (close to SHA-3) hashing algorithm as it probably has the “l<a href="https://ethereumclassic.github.io/blog/2017-02-10-keccak/">east likelihood</a>” of not yet being broken by the NSA. Sounds like confidence, right?</p><p>Security on any computer system just means a very, very low probability that an attacker will find the secret key — so eventually all of our “secured” data can be decrypted, it’s just a question of time and hardware (usually it takes thousands of years, so you’re okay to not care at all). But with the advent of quantum computing things could change, literally, quickly. (And I have to drop yet another Austrian name here, <a href="https://en.wikipedia.org/wiki/Anton_Zeilinger#Quantum_communication,_quantum_cryptography,_quantum_computation">Anton Zeilinger</a> who’s working on <a href="https://en.wikipedia.org/wiki/Quantum_cryptography">quantum cryptography</a> — something that sounds like pure science fiction to me.)</p><p>Bottom line: All of the above (besides the quantum physics stuff) relies on using a pair of keys — public and private. And since the latter must be kept secret at all costs both military and engineering are in need of managing keys:</p><h4>Key management</h4><p>Once a submarine is submerged it becomes (almost) impossible to communicate with its crew from the outside. Hence <a href="https://en.wikipedia.org/wiki/Two-man_rule">procedures</a> have been set up to be in algorithmic control of the weaponry. Both human error and malicious behaviour have to be ruled out by the very design of the launch procedure — so this is why you need two different keys carried around by two different people to fire a missile. Luckily, this fact creates good movie plots:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FemRY0Cv58CY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DemRY0Cv58CY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FemRY0Cv58CY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/49007081d1f42a0303f99f801d212d96/href">https://medium.com/media/49007081d1f42a0303f99f801d212d96/href</a></iframe><p>See Denzel Washington and Gene Hackman having severe issues with each other at their workplace:</p><p><a href="https://www.imdb.com/title/tt0112740/">Crimson Tide (1995) - IMDb</a></p><p>In the blockchain world the very same concept is called <a href="https://en.wikipedia.org/wiki/Multisignature">multisig</a>: You need two secret keys (or any combination of n out of m) to process a transaction on the blockchain. There’s a really nice article explaining the different approaches to setting this up:</p><p><a href="https://medium.com/kzen-networks/threshold-signatures-private-key-the-next-generation-f27b30793b">Threshold Signatures: Private Key, The Next Generation</a></p><p>And if you’re getting it wrong it can be very, very expensive:</p><p><a href="https://medium.com/chain-cloud-company-blog/parity-multisig-hack-again-b46771eaa838">Parity Multisig Hacked. Again</a></p><p>And if you just don’t care about all of this and — allegedly — die in India, the whole system ecosystem is just f***:</p><p><a href="https://www.wired.com/story/crypto-exchange-ceo-dies-holding-only-key/">A Crypto Exchange CEO Dies-With the Only Key to $137 Million</a></p><p>In any case, there are striking similarities between submarines and blockchain:</p><p>First, a fully decentralized network of nodes where no one has direct control (apart from inventing the protocol in the first place) is comparable to a fleet of submarines out in the ocean.</p><p>Second, the irreversibility of a weapon launch has its counterpart in the immutability of data. Thus it’s critical to secure access, and cross-check every step as there is no roll-back.</p><p>The fictional world of war movies is full of captains, naval officers and blind passengers who take control over the missile key. And so are the fairy tales of pale guys in washed-out hoodies cracking the one single password of the evil corporation we all hate.</p><p>Interestingly all of the above procedures worry about the procedure itself. It’s kind of philosophical, but how can you be sure that something — although properly authenticated — is actually the right thing. Read about <a href="https://en.wikipedia.org/wiki/Harold_Hering">Major Harold Hering</a> and this conundrum.</p><p>Conclusion: Blockchain is really dangerous — usually I prefer a world of reversible actions☺</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c65b7722bb3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why blockchain is a perfect fit for IT security]]></title>
            <link>https://medium.com/@mathias.c.frey/why-blockchain-is-a-perfect-fit-for-it-security-9a36548c0c17?source=rss-72b513db2f84------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a36548c0c17</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[it-security]]></category>
            <dc:creator><![CDATA[Mathias Frey]]></dc:creator>
            <pubDate>Sun, 16 Dec 2018 22:06:00 GMT</pubDate>
            <atom:updated>2018-12-20T11:19:36.398Z</atom:updated>
            <content:encoded><![CDATA[<p>Blockchain is shaking up the financial industry. Countless projects are somewhere either in their starting <em>blocks</em> or already running; all of that accompanied by tremendous media buzz. <a href="https://medium.com/@mathias.c.frey/what-is-a-blockchain-actually-fcd7f9721bd1">In my last article</a> I explained blockchain and its key advantage — ensuring cheap(er) trust — by using yet another example from the very domain of moving money from A to B.</p><p>However, blockchain has not been widely adopted outside the realm of accounts and transfers. Not surprisingly the term <em>blockchain real world application</em> has almost become a salvation-like promise on its own now as so many projects strive to successfully apply the technology in new contexts. Apparently this has been proven to be challenging — nonetheless at <a href="https://vchain.us/">vChain Inc</a>. we’re driven to make exactly that happen.</p><p>So let me share with you why blockchain is a perfect fit for the IT security space. But before I can do this let’s delve into why I think blockchain could not bring real advantage in other domains so far (admittedly I often tend to be a gloomster).</p><h3>The real world is a tough turf</h3><p>I’m convinced blockchain projects are not successful outside of the financial context due to four conceptual problems:</p><ol><li>Complexity</li><li>Connection</li><li>Credibility</li><li>Cost</li></ol><h4>Complexity</h4><p>Blockchain and smart contracts are often referred to as <em>truth machines </em>since the technology can, without any doubt, guarantee integrity of data and its processing. You will no longer need to trust an agent, middle man, big corporate, whoever in between you and your contractual counterpart — blockchains enable <em>trustless</em> interactions.</p><p>Therefore it is highly tempting to assume real-world agreements — let’s say your accident insurance policy — could be replaced by <a href="https://en.wikipedia.org/wiki/Ricardian_contract">Ricardian contracts</a> (implemented in the form of a smart contract on Ethereum for example).</p><p>Sounds good, right? But have you actually ever read through all the pages of your accident insurance policy? Or have you at least counted them? You’ve for sure experienced software bugs many times already. Their numbers are usually growing exponentially with the size of a specification and thus codebase. So the larger the insurance policy the larger the amount of bugs in its implementation. But the problem has just started here: The so-called <em>truth machine </em>is a system that distributes, stores and executes code in hundreds of separate places to disable tampering or censorship. So by its very design you cannot fix bugs because every piece of code and data stays immutable.</p><p>From my own experience I can tell that the domain model of transfers in retail banking is comparably simple: All you have is accounts holding a balance and transfers between the prior changing the latter. Thinking you could easily apply smart contracts in the insurance or any other more complicated domain — because it worked in finance — is naive.</p><h4>Connection</h4><p>Let’s assume you got all the complexity of your accident insurance policy right. All has been put into software without any single bug. (Well, we could already stop here again, honestly!) Imagine now you had a skiing accident and there’s a very important clause in your contract which differentiates between whether you were skiing on a marked slope or somewhere off the grid.</p><p>Well, it’s really nice to theorize about trustlessness and truth, but who would tell the smart contract where the accident exactly happened — eventually why should the truth machine trust input data from the outside world? And yes, there are proof-of-concepts like <a href="http://www.oraclize.it/">http://www.oraclize.it/</a> — I just don’t see such an approach fly.</p><p>Again, cryptocurrencies have an advantage here: Everything that happens just happens in the digital world. There’s no need for any connection to the outside. By contrast to that your skiing accident still happens if the smart contract does not compile without errors, the business logic of the implementation does not prevent you from going anywhere where there’s an an unmet corner case, etc.</p><h4>Credibility</h4><p>With credibility I here mean any system’s property that a critical share of users can sufficiently comprehend what’s going on — this is to have an accurate mental model built up by learning and experiencing how the system (not) works.</p><p>Whereas I have no clue how modern-day combustion engines work in detail I nonetheless thoroughly understand the concept of operating a car and its engine. I’m well acquainted with fuel consumption, re-fueling the tank, the necessity of service intervals, and so on. The reason for having this knowledge is not my ingenuity but purely the fact that I experience so many attributes related to the concept; e.g. I smell the fumes, I pay for gas, I feel the heat and hear the noise.</p><p>However, although being a software guy I could not tell you anything about <a href="https://xkcd.com/2030/">voting software</a> (which I hopefully will never have to use in my whole life!) apart from whether the user interface looks nice or not. Think about it, it’s very scary.</p><p>Blockchain combines a couple of cryptographic concepts that are just hard to grasp and the main benefits are even harder to track for an outsider. I’m making a potentially grotesque statement here but I’m convinced that blockchain is less trustworthy from the perspective of someone who prefers dealing with a living insurance agent rather than a 25,000 lines-of-code implementation of their contract. In short, I doubt the wide-spread adoption of blockchain-based interactions in the real world.</p><h4>Cost</h4><p>If you’ve read my <a href="https://medium.com/@mathias.c.frey/what-is-a-blockchain-actually-fcd7f9721bd1">introduction</a> carefully I made a point about blockchain’s ability to bring cheap(er) trust. So it might look irritating that I’m listing <em>cost</em> as the fourth downside here. However potential savings of an upcoming technology must be compared to current realities. This very calculation looks compelling for — again! — the world of wiring money. A Bitcoin transaction between two addresses is tremendously cheap compared to an international transfer between at least two banks in potentially different currencies, timezones or legal territory.</p><p>When it comes to storing your gigabytes of family photos, a company’s documents or the orders of the Pizza delivery service around the corner though, the technology is simply not made for it. Most stuff we do with computers today needs a lot of storage capacity or code to be executed. (No joke: I had to pay 45 US cents in Ether to store a smart contract that just saves the following value until the end of time: <em>4fe82ae4606e2137a0e2e03dd691d6ccd7b59957</em>)</p><p>Blockchain is a very expensive means to store data and execute logic — or in other words: infinity is expensive! Transferring money needs little data storage and only a few computational cycles. Therefore blockchain can beat the old technology of wiring money easily.</p><h3>So why IT security then?</h3><p>At <a href="https://vchain.us/">vChain</a> we’re on a mission to make software distribution bullet-proof and verifiable by anyone. The key merits of blockchain just make a lot of sense for IT security and therefore for us:</p><ol><li>Immutability ensures that no one including ourselves can tamper with your data.</li><li>Decentralization ensures that no single party can trick you into seeing or doing wrong things.</li><li>The cryptographic batteries included ensure authenticity of code, machines, configuration, whatever dependencies you have.</li></ol><p>So let’s simply recap on my four above mentioned problems which impede blockchain application and set them into the context of IT security:</p><h4>Complexity ☑️</h4><p>IT security is a highly challenging field of engineering. But the fact that it takes the real whizz kids to contribute here does not necessarily imply that the domain model has to be hard to understand. By contrast: Good software, seal of approval received from an auditor, malicious code, many bugs found, one evil attack, penetration test executed successfully… that’s an easy-to-understand domain that reminds me of playing cops and robbers with my son.</p><h4>Connection ☑️</h4><p>I stated that transfers are limited to the realm of bits and bytes, and so is IT security. It’s easy to tie the execution of code or deployment of servers to information stored on or emitted by a blockchain. Everything that there is and will be is confined to the digital world.</p><h4>Credibility ☑️</h4><p>Well, the steepness of the learning curve will never go away. Yet it’s not arrogant to say that IT (security) professionals are just more likely to understand the underlying technology. These people are the very adopters of such a paradigm.</p><h4>Cost ☑️</h4><p>Tough one. The high costs per write operation just don’t go away. Thinking of code, logs, configuration, etc. we will need a plethora of data to be stored. The only way out: We’re building upon the independent <a href="https://www.zerotrustconsortium.org/">Zero Trust Consortium</a>’s blockchain — a permissioned blockchain for the software industry operated by the software industry. vChain is a proud member amongst other software vendors, enterprises and academia.</p><h3>tldr;</h3><p>Blockchain is a game-changing paradigm for the IT industry, yet there are four issues when it comes to <em>real-world</em> adoption — complexity, connection, credibility and cost. Although there’s a lot of research going on to remedy these — already today the domain of IT security is not fully affected by them. <strong>Thus the IT security space is the next obvious success story of blockchain usage.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a36548c0c17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a blockchain actually?]]></title>
            <link>https://medium.com/@mathias.c.frey/what-is-a-blockchain-actually-fcd7f9721bd1?source=rss-72b513db2f84------2</link>
            <guid isPermaLink="false">https://medium.com/p/fcd7f9721bd1</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Mathias Frey]]></dc:creator>
            <pubDate>Fri, 16 Nov 2018 20:22:19 GMT</pubDate>
            <atom:updated>2018-11-16T22:17:24.704Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>If you can’t explain it simply, you don’t understand it well enough. (Albert Einstein)</blockquote><p>As I’ve recently joined <a href="http://vchain.us/">vChain</a>, a startup in the IT security space, that leverages its main selling point from building upon blockchain I should actually know what this technology is and how it really works. Openly, I needed to invest quite some time to thoroughly understand the concepts involved. Most of the time I found it very hard to locate useful information that neither was half-baked <em>blah blah</em> flooding the media nor academic papers I would have only understood once I carried a PhD in cryptography.</p><p>So here comes my attempt to explain blockchain to someone who’s <br>a bit familiar with IT, wants to look beyond the hype but does<br>not want to invest a lot of time to dive into the topic deeply (like I did).</p><p><em>One more thing: I’m not going to deal with cryptocurrencies as I believe they’re a ghastly stupid application of the underlying technology — fiat money is still one of the best inventions of mankind!</em></p><h3>It’s all about (cheap) trust</h3><p>Forget everything you heard so far about blockchain. The whole thing is just about trust and achieving it cheap(er) — <strong>NOTHING</strong> else.</p><p>For example, I trust my bank to correctly do the bookings on my current account. I don’t really care about the technology they’re using to ensure that my account balance is summed up correctly and that transactions are immutable or kept private from the looks of outsiders.</p><p>However, having worked in a bank myself I know the effort — technical and organizational, thus financial — it takes to ensure this level of trust that is a result from correctness, immutability and secrecy and — above all — literally billions spent over decades on legal and organizational ceremonies to eventually shout all of this proudly out to potential customers.</p><h3>Is it now trust or no trust?</h3><p>The above example shows that — traditionally — trust is achieved by relying on someone that has enough resources to both ensure and show they’re trustworthy. Hence trust is merely a result from reputation which is built up at high cost over a long period of time.</p><p>Further elaborating on the example, let’s suppose I need to transfer money to someone. Today, I need a bank for that — an organization that sits between me and the beneficiary to ensure a correctly executed credit transfer.</p><p>Now, the blockchain is a technological innovation that renders such intermediaries obsolete.</p><p>By using blockchains you can skip intermediaries which — today — bear high costs to ensure trust, costs they eventually pass on to their customers. As blockchain does not require anyone you needed to trust two often-used terms are <em>trustless</em> and <em>zero-trust</em>. I know, it can be confusing to talk about creating trust by being trustless. But compare the concept to a vaccination: You’ve become immune to a virus because you had been intentionally infected with a (weakened) version of that very virus. The blockchain protocols are all built around dealing with infected members, aka faulty or malicious nodes. So trust is created because you can be sure all of this works even though members could potentially be infected — that is breaking the rules erroneously or intentionally.</p><h3>Understanding the economics</h3><p>Let’s summarize the economical part of the whole story:</p><ul><li>trust is no more a result of expensive reputation</li><li>trust is ensured by the design of the blockchain protocol</li><li>once you achieve “technical” trust you can skip intermediaries</li><li>this makes a lot of transactional scenarios much cheaper</li><li>which is the reason why blockchain will a key technology<br>throughout the next years</li></ul><h3>But how does it work?</h3><p>Let’s start with its very name: The blockchain’s chaining of blocks. A block is a data structure (imagine a simple text file) that consists of a couple of transactions, a random number and a reference to the previous block, therefore making up a chained structure because every block points to its predecessor. (The first block is called the genesis block and has no parent.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AknlWEHZDMRZSIMTo6ni4A.jpeg" /><figcaption>A chain of blocks: Imagine a sorted list of documents, each containing a table with transaction data, a signature below and the name of the previous document; hence building up a chain.</figcaption></figure><p>All members of a blockchain, the so-called nodes, store all of these chained blocks. Therefore one of the blockchain’s key properties is (global) distribution and this implicitly means 24/7 availability — because any single node can fail and the data will still be available in abundance in many other places.</p><p>The blockchain also ensures its tolerance towards partitioning, i.e. when a network connection breaks down, a node malfunctions, etc. as the core communication protocol — the servers’ gossip — is robust against such foreseeable breakdowns.</p><p>So far we have availability and partitioning resistance. The third and missing piece now is consistency — being sure that all nodes carry the same state of information. Acccording to the so-called <a href="https://en.wikipedia.org/wiki/CAP_theorem">CAP theorem</a> you can never achieve all three in a distributed system once the network somehow fails. (And this is easy to imagine: Let’s say your system is tolerant to partitions. After a while one of your nodes breaks apart due to a network outage. If the node now won’t accept any further write operations it becomes unavailable. However if it still accepts these it will implicitly turn inconsistent with the rest of the unreachable network…)</p><p>But somehow Satoshi Nakamoto, the <a href="https://blockonomi.com/who-is-satoshi-nakamoto/">mysterious</a> inventor of Bitcoin, solved the CAP theorem’s conundrum. (Not really though, but here’s the trick that lead to the revolution.)</p><h3>Consensus</h3><p>Let’s dive into the above mentioned write operations, e.g. a Bitcoin transaction from my address (account) to yours. Such operations are broadcasted throughout the network and eventually a bundle of them will be written into a new block.</p><p>The (public) blockchain is fully decentralized, thus there is no central logic that would control the writing of new data. This property is extremely important as it prevents any kind of censorship and guarantees full transparency. We’re close to reaching the core of it: <em>Trust by design</em>.</p><p>Imagine you’re on a telephone conversation and whenever the other person on the line talks (e.g. the write operation) you’d have to listen. When you speak though, your counterpart needs to remain silent. This way of doing telephone calls — the protocol — works because of invisible social rules (it’s just impolite to interrupt) and the low number of participants.</p><p>Ever been in a <a href="https://www.youtube.com/watch?v=z_tiqlBFjbk">telco at work</a>? You see, the protocol is not built for larger networks. So what we need is a selection process which ensures that only one person will be talking for a given period of time. Then you run the next selection process and the next person would be allowed to talk.</p><p>Although it’s a horrible idea to do your next telco like this, suprisingly the blockchain consensus algorithms follow such a concept.</p><h3>Proof of Work, aka mining</h3><p>There’s a growing array of different consensus algorithms as two things depend on this very choice:</p><ol><li>The blockchains key properties like transaction throughput, speed or trust level</li><li>The economic or social incentive model to join the blockchain as a node that writes into the chain (i.e. mining nodes in Bitcoin and related blockchains involving cryptocurrencies)</li></ol><p>Bitcoin uses a proof of work algorithm. You for sure have already heard the <a href="https://digiconomist.net/bitcoin-energy-consumption">horror stories</a> about energy consumption resulting from the necessity to solve puzzles that require incredible amounts of computational power.</p><p>This computational puzzle is easily explained on a high level: The node knows the current block and all transactions that have been broadcasted in the meantime and thus should be written into the next block. It will now invent a random number and create one hash over all of this input data and hope that the output string matches an agreed pattern.</p><p>As hashes are one-way functions you can only solve this puzzle by trying with ever newly generated random numbers. If you’re lucky and find a matching output pattern then you’ve just created a new block which you will broadcast. The other nodes will now verify that you did not cheat: They will quickly hash the data and accept if the output matches, then they move on trying to win the next race to successfully mine a block.</p><p>There are two more things to mention when it comes to mining:</p><p>First, a newly generated block also frees up some coins which will go to the miners as reward. So much about the economic incentive and why it makes sense to verify and write the data of others.</p><p>Second, let’s revisit the node(s) lost due to a network outage I mentioned earlier explaining partitioning. Yes it’s thinkable that two nodes will mine a block simultaneously. But there’s an agreed mechanism which of the shortly separated chains will prevail (it depends on the hash function’s complexity which can never be equally complex). Although such orphaned blocks will be forgotten eventually, they are one of the reasons why it takes comparably long to be really sure that a transaction has been successfully written to the blockchain.</p><p>This selection process ensures consistency after a while. Such a mechanism therefore is called eventual consistency.</p><h3>Revisit cryptography</h3><p>I mentioned the verification done by all nodes already. This is not only important when a node needs to decide whether to include a newly generated block into its local copy of the data. It’s also a means to ensure that older data is correct. As all of the transactions make up the block together with the random number and a reference to the previous block you can verify this data easily. So finally we reach the point why the blockchain is immutable: If you wanted to do changes in a given block you would have to redo all the mining operations in all its ancestor blocks to fake a blockchain that meets this integrity criterion… good luck paying your next energy bill!</p><h3>Smart Contracts?</h3><p>For the sake of completeness let me finish by briefly mentioning smart contracts. I’ve already been using the word transaction quite often and so far, we’ve been thinking here about banking-like transfers only. But transactions in blockchains that came after Bitcoin, e.g. Ethereum, can be of any type of write operation, and this includes the storing of computer programs and execution thereof. Think of it as distributing code to hundreds of thousands of computers via the blockchain with the goal that every node will execute your algorithm storing the output data with the same properties we’ve already seen: no-censorship, immutable, always available… Once you got your head around this you might realize why so many think this is a true revolution.</p><h3>Finish line</h3><p>I know this probably was a tough read. Trust me — <em>or don’t if you’ve already switched to trustless</em>— it was even tougher for me to reach a point<br>where I would feel comfortable enough to (at least try to) explain blockchain. I hope it helped; happy to receive feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcd7f9721bd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>