<?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 Udi Wertheimer on Medium]]></title>
        <description><![CDATA[Stories by Udi Wertheimer on Medium]]></description>
        <link>https://medium.com/@udiwertheimer?source=rss-482473e6a905------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*oDhLkcRuo5rAoSaA.jpeg</url>
            <title>Stories by Udi Wertheimer on Medium</title>
            <link>https://medium.com/@udiwertheimer?source=rss-482473e6a905------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:43:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@udiwertheimer/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[Bancor Unchained: All Your Token Are Belong To Us]]></title>
            <link>https://medium.com/unchained-reports/bancor-unchained-all-your-token-are-belong-to-us-d6bb00871e86?source=rss-482473e6a905------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6bb00871e86</guid>
            <category><![CDATA[ico]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[bancor]]></category>
            <dc:creator><![CDATA[Udi Wertheimer]]></dc:creator>
            <pubDate>Tue, 20 Jun 2017 16:04:38 GMT</pubDate>
            <atom:updated>2019-01-19T17:32:12.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bUxpl1T1IRvs0LJYSrK-1g.jpeg" /></figure><p>This post is the first in a series of<strong> </strong><a href="https://medium.com/unchained-reports"><strong>Unchained Reports</strong></a>, covering the often overlooked details about projects in the current “ICO bubble”.</p><p>Last week, the <a href="http://bancor.network/">Bancor</a> project raised ~$150M. The team stood up an impressive campaign, ending with the largest amount raised in an ICO to date.</p><p>Bancor’s main product is said to be a way to provide liquidity to the “long tail” of tokens, and seems to be an interesting idea, that deserves exploration. It is lead by an accomplished team of entrepreneurs, and already produced some great-looking demos.</p><p>I took some time to read many of the materials published by Bancor, including its smart contract code. I was absolutely astonished by some of the things I found, including what I consider <strong>dangerous backdoors</strong>.</p><p>In this report, I will detail my findings, including the team’s ability to <strong>take anyone’s tokens arbitrarily</strong>. But first, a brief introduction on what smart contracts are, and why it’s so important to read and review them.</p><h3>Did you read your smart contract?</h3><p>“Smart contracts” are at the heart of the Ethereum blockchain. They are written by coders, so some people think of them as “apps”. But in reality, they aim to replace <strong>legal prose</strong>. Smart contracts can describe, for example, a set of <strong>conditions</strong> that will control who gets a pre-deposited amount of money. Or they can describe <strong>who</strong> will get to decide what happens with a pool of coins.</p><p>They are very much like regular legal contracts. But unlike regular contracts, there are no judges to make decisions at their discretion. Instead, blockchain participants will run the <em>smart contract code</em> to decide what’s the outcome of a transaction. There’s only one way to “interpret” a smart contract, and that’s the way a computer would. The <em>intent</em> of the contract writer does not matter, nor does the <em>understanding</em> of any counter party. The only thing that matters is what’s in the code.</p><h3>Reading Bancor’s contracts</h3><p>A lot of ICOs use smart contracts to raise money. Bancor is one of them.</p><p>This report is (at least) as much about the importance of reading contracts as it is about Bancor itself. I won’t be touching the actual details of Bancor’s protocol at all. I recommend reading Bancor’s <a href="https://bancor.network/static/Bancor_Protocol_Whitepaper_en.pdf">whitepaper</a> for that, which is very well written, and also Emin Gün Sirer and Phil Daian’s <a href="http://hackingdistributed.com/2017/06/19/bancor-is-flawed/">breakdown</a> on its potential problems (<em>Edit, 22/06/2017</em>: and Bancor’s very detailed <a href="https://blog.bancor.network/this-analysis-of-bancor-is-flawed-18ab8a000d43">response</a>, which was published after this report).</p><p>Instead, we will look at the contract of the actual <strong>crowdsale:</strong> did the contract code fit the sale terms that were published by the project?</p><p>Then, we’ll look at the contract governing the token created by that crowdsale, BNT, and the dangerous backdoors that contract contains.</p><h3>Crowdsale Unlimited</h3><p>Bancor’s <a href="https://bancor.network/fundraiser">crowdsale</a> went live on June 12th. Prior to its start, in a blog post, the team pubished the sale <a href="https://blog.bancor.network/bancor-network-token-bnt-contribution-token-creation-terms-48cc85a63812">terms</a>, including the following:</p><ul><li>The sale would run for no more than 14 days.</li><li>There would be a “hidden cap” for the amount of funds to be allowed in, which would be revealed when raising 80% of the cap.</li><li>During the first hour, called the “minimum time”, all funds would be allowed in, even if above the “hidden cap”. If the sale goes over the “hidden cap” during the first hour, it would stop immediately at the end of this first hour. Otherwise, it will continue until reaching the “hidden cap”.</li></ul><p>However, the crowdsale contract, <a href="https://etherscan.io/address/0xbbc79794599b19274850492394004087cbf89710#code">viewable here</a>, told a <strong>slightly different story</strong>. I’ll explain what the contract says in words, and add code snippets so you can follow along if you can read contract code.</p><ul><li>The sale will, indeed, run for a maximum of 14 days.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Jxwtf8XM0cD0z-6AZYmUw.png" /><figcaption>The corwdsale duration, in the actual contract code</figcaption></figure><ul><li>There will be a “hidden cap”, and the team will cryptographically commit to it (meaning it’s hidden but can’t be changed after the sale starts). <strong>It will be revealed whenever the team decides to reveal it</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*spgRlyqH97nPl3sMfmJZSw.png" /><figcaption>The “hidden cap” was to be revealed, and set, whenever the contract owner calls this <strong>enableRealCap </strong>function, which sets the <strong>totalEtherCap</strong> variable</figcaption></figure><ul><li>The sale was to have <strong>no limits </strong>(other than a 1,000,000 ETH “safety limit” which equals roughly $400 million dollars, 4 times the “hidden cap” that was later revealed)<strong>, until the team would reveal the “hidden cap”.</strong> Not until 1 hour passed, as the blog post detailing the sale terms promised. In fact, I can think of no reasonable way they could codify this promise into a contract, without revealing the “hidden cap” beforehand.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t2iS6vnvXxh-HSA0JpLi_w.png" /><figcaption>The safety cap is 1,000,000 ETH, until the <strong>enableRealCap</strong> function, from the previous snippet, is called by the contract owner to replace it with the “hidden cap”.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a2_79D7ZOqdDFucvNicBxw.png" /><figcaption>This <strong>etherCapNotReached</strong> modifier is called before every “contribution” to the sale, to assert that the total amount contributed isn’t higher than the current <strong>totalEtherCap</strong>, which is set to 1,000,000 ETH (above) until the contract owner decides to reveal the “hidden cap”.</figcaption></figure><p>As the sale started, people rushed to get their ethers in. The Ethereum network had a hard time processing all those transactions, as it frequently does during high-profile ICOs. As the first hour was approaching its end, about $70M worth of transactions were confirmed by the network, with <strong>tens of millions more</strong> sitting in the backlog, waiting to be confirmed.</p><p>In order to comply with the terms the project published before, they had to stop the “cap-less first hour” at that point, and reveal the “hidden cap” very soon after, once $80M was reached, which was ~80% of the hidden cap.</p><p>Instead, they released <a href="https://blog.bancor.network/critical-update-bnt-fundraiser-minimum-time-extended-5f4584f979fe">this critical update</a>, saying:</p><blockquote>We have decided to extend the minimum time to THREE HOURS in order to allow the Ethereum network to process all PENDING transactions and allow everyone who’s transactions have failed to RETRY. Our intention remains to include all early contributors.</blockquote><p>Many were surprised by this. Some investors were grateful, as they weren’t able to get in during the first hour due to a high load on the network. Yet others were furious — probably the ones that already managed to get in — they were promised that the cap will be enforced after 1 hour, but now that the “minimum time” was expanded to 3 hours, they were effectively being diluted.</p><p>One group wasn’t surprised: those that took the time to read the contract before hand. They <em>always knew</em> this was an option.</p><p>It is hard to tell whether extending the “minimum time” was good or bad. The key takeaway from this ordeal though, is that when a contract gives its owner capabilities that aren’t listed in the official announcements and blog posts, some people who didn’t read the contract might end up being upset.</p><p>But for those who didn’t read the contract, a bigger surprise is in store…</p><h3>A token full of back doors</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hh9RcNm6jms1jITe3eG-3Q.jpeg" /></figure><p>When people think of “cryptocurrencies” or “digital assets”, or whatever the cool kids call them today, they think of decentralized, censorship resistant tokens, that no central party could control for any reason. And while some projects have various degrees of (de)centralization, I have never seen a token as centralized as BNT, that puts so much power in the hands of so few.</p><p>The <a href="https://etherscan.io/address/0x1F573D6Fb3F13d689FF844B4cE37794d79a7FF1C#code">BancorTokenContract</a> controls the actual BNT token and its behavior. It is currently owned by the <a href="https://etherscan.io/address/0xbbc79794599b19274850492394004087cbf89710#code">BancorCrowdsale</a> contract, which is owned in turn by a closed-source contract which is most likely a “multisig” account held by the project and/or its partners.</p><p>These are the powers that the <strong>BancorCrowdsale</strong> contract allows its owners:</p><ul><li><strong>All transactions using the BNT token can be disabled by the team at any time for any reason</strong>. Presumably the capability is there to allow the tokens to be frozen immediately after the crowdsale for about a week, until Bancor’s main product is ready. However, for some reason, after they’ll unfreeze the tokens, the team will retain the option to freeze transactions again at any time.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*73TG29uGnoNAk70vKJgZeg.png" /><figcaption>In <strong>BancorTokenContract</strong>, contract owner (the contract below) is allowed to disable transactions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dyt4XsAk_aeuczdqfA1hgw.png" /><figcaption>In <strong>BancorCrowdsale</strong>, contract owner (the Bancor team) is allowed to use <strong>BancorTokenContract</strong> (above) to disable transactions</figcaption></figure><ul><li><strong>The team can issue new tokens at any time</strong>. Bancor’s “changer” product requires the ability to create tokens programmatically based on a market-making formula distilled in another smart contract, so it must have the ability to create more tokens. However, for some reason, the team has the ability to create new tokens <strong>arbitrarily</strong>, for whatever reason they choose.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gPeUeWc8ohOxdWiPMpAwiw.png" /><figcaption>In <strong>BancorTokenContract</strong>, contract owner (the contract below) is allowed to issue new tokens arbitrarily</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UyRpyaM094DwgMlwGGyFBA.png" /><figcaption>In <strong>BancorCrowdsale</strong>, contract owner (the Bancor team) is allowed to use <strong>BancorTokenContract</strong> (above) to issue new tokens arbitrarily</figcaption></figure><ul><li>Shockingly, <strong>the team can DESTROY any tokens FROM ANY ACCOUNT, at any time</strong>. Once again, Bancor’s “changer” product requires the ability to programmatically destroy tokens sent to its contract, so there <strong>has </strong>to be a functionality to destroy tokens — but it could be easily limited to destroying only tokens sent to that contract. <strong>Instead, the team has the power to pick any account’s tokens and destroy any amount of them, at any time, for any reason</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dwiz0KjA-CfAgDxNe44czw.png" /><figcaption>In <strong>BancorTokenContract</strong>, contract owner (the contract below) is allowed to <strong>destroy anyone’s tokens </strong>arbitrarily</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2M1PB7PAHIU_Th8OzOL4lg.png" /><figcaption>In <strong>BancorCrowdsale</strong>, contract owner (the Bancor team) is allowed to use <strong>BancorTokenContract</strong> (above) to <strong>destroy anyone’s tokens</strong> arbitrarily</figcaption></figure><p>This third point is unheard of. I’ve looked at other high-profile contracts managing other tokens, and couldn’t find anything similar. This puts unprecedented, and worse, <strong>unexpected</strong> power in the hands of the contract owners.</p><h3>How did this go by unnoticed?</h3><p>For anyone who’s been in crypto long enough, this is a big no-no. How come no one noticed this?</p><p>Well, people <em>did</em> notice.</p><p>As noted in this <a href="https://blog.bancor.network/bancor-contracts-audited-and-deployed-54157fcc0a61">blog post</a>, two security auditors were invited by Bancor to inspect the contracts. However, the blog post only refers to the positive points from the audits. The post didn’t list the concerns that both auditors raised, and instead linked to their full reports which are very lengthy and highly technical. I doubt many people took the time to deep dive into the full reports.</p><p>Martin Holst Swende, Security Lead at Ethereum, wrote in his <a href="https://gist.github.com/holiman/d74592af15682f03bce41aad10011a13">report</a>:</p><blockquote>The Bancor protocol implementation has a security model based on centralized trust: the owner of the contracts have (sic), to a large degree, full control over assets traded over the platform… Since the bancor protocol is fairly a complex scheme … it makes sense to have a centralized model, at least initially.</blockquote><p>While Ethereum Foundation’s member Nick Johnson wrote in his own <a href="https://gist.github.com/Arachnid/c65fd1bd61a8e0294aef95a4808edc78">report</a>:</p><blockquote>Participants should note that the contracts as authored for the crowdsale are not trustless, and depend on the good behaviour of Bancor. Bancor have stated that this is intentional, intended to allow them to respond to and remedy any issues that come up during the crowdsale and in early operation, and that manual oversight will be exchanged for more automated operation once they are confident the system is working as intended.</blockquote><p>So, both of these respectable auditors found that the contracts are fully centralized, in an unprecedented way. When they told the Bancor team, Bancor just said “we know, that’s the point”.</p><p>Now, the team’s reasoning seems to be that while their main smart contract is still being tested, they should retain full control in case anything goes wrong. They expand on this approach in a blog post about “<a href="https://blog.bancor.network/learning-from-thedao-fdbeb687000a">learning from the DAO</a>”. That blog post details the team’s control over their main “changer” product, control which they plan to diminish over time, but it doesn’t mention <strong>at all</strong> the backdoors listed above.</p><p>From Wikipedia’s article on <a href="https://en.wikipedia.org/wiki/Backdoor_(computing)">backdoors</a>:</p><blockquote>Although normally surreptitiously installed, in some cases backdoors are deliberate and widely known. These kinds of backdoors might have “legitimate” uses such as providing the manufacturer with a way to restore user passwords.</blockquote><p>I’m pretty sure that the Bancor team has no intention to misuse these backdoors, and that they believe they have “legitimate” uses. I’m not 100% sure of their legitimacy myself, but in any case I would argue that their existence should be clearly communicated to investors.</p><p>People in this space expect the control over tokens to be fully decentralized, and if for some reason they’re not, this should be made very clear.</p><h3>Upgradeability</h3><p>Bancor’s contracts are “upgradeable”, meaning they can replace them with new functionality, giving them more power, or removing power from themselves. They promise on some communications they will gradually remove their control over the system.</p><p>The currently deployed <strong>BancorCrowdsale</strong> contract is planned to be replaced by <a href="https://github.com/bancorprotocol/contracts/blob/master/solidity/contracts/BancorChanger.sol"><strong>BancorChanger</strong></a> in the next few days, however this new contract still retains the 3 backdoors: freezing all transactions, issuing new tokens, and destroying any tokens.</p><h3>The risks</h3><p>As I mentioned before, I trust that Bancor’s team won’t try to misuse this backdoor. However, having so much power concentrated centrally, creates a potential single point of failure. The keys held by the team could be stolen for example. Or, law enforcement could force the project to freeze or destroy tokens if they realize this is possible (and if for some reason they would suspect any wrongdoing).</p><p>It could be argued that BNT investors would be at risk of the team being compromised anyway, so these backdoors don’t add any significant exposure. It could also be argued that if these backdoors are misused, Bancor could always use its reissuance capabilities to restore the state prior to any misuse.</p><p>However, because the existence of these backdoors isn’t properly communicated, this puts many users at risk, and especially <strong>exchanges</strong>.</p><p>Exchanges that list the BNT token, might not be aware that if the team’s keys are compromised, <strong>the exchanges could lose access to deposited tokens</strong>. This could raise regulatory concerns, but also technical risks: exchanges normally don’t “monitor” accounts to check that tokens are “still there”. They assume that once deposited the tokens stay in place, unless they’re moved. If an exchange’s tokens are destroyed (or frozen) while the market is active, this could bring a world of pain to the exchange operator, who might not be able to reverse executed orders.</p><h3>Recommendations and Conclusion</h3><ul><li><strong>For the Bancor project</strong>: I would recommend to immediately restructure the contracts to remove the team’s capability to freeze, issue, or destroy assets arbitrarily. Otherwise, a proper advisory should be given to investors and industry members about the existence of these backdoors, and how to mitigate their risks.</li><li><strong>For exchanges</strong>: The safest route would be to <strong>delay listing BNT tokens</strong> until the team removes the backdoors. If this is not possible, at the very least inform users during the deposit process that their tokens may be frozen or destroyed by Bancor, and adapt the exchange’s system to monitor that tokens remain non-destroyed and liquid.</li><li><strong>For future crowdsales</strong>: In order to be fully transparent with potential investors and users, it would be best if ICO projects share a clear “English translation” of their smart contracts, that explain step-by-step what the contract does. More than anything else, it should focus on <strong>the differences</strong> between the written terms and the contract itself, differences that sometimes have to exist.</li></ul><p>And for users: <strong>always read the contract before you sign</strong>. The security of smart contracts depends on the users reading them. If you can’t read code yourself, find someone who can.</p><p>I’d like to thank <a href="https://twitter.com/yairwein">Yair Weinberger</a> and <a href="https://www.linkedin.com/in/oded-leiba-4884a166/">Oded Leiba</a> for helping with the research on this report.</p><p><strong>Disclosure</strong>: I am an employee at Colu, which develops the Colored Coins protocol and local currency solutions. My employer wasn’t involved in this report in any way, and any research leading up to it was done on my own time. Any and all opinions are my own, and I never owned any Bancor tokens.</p><p><em>Edit (22/06/2017): </em>Bancor published their response to this article, which you may find <a href="https://blog.bancor.network/response-to-bancor-unchained-cdb3bd2ba505">here</a>.</p><p><em>If you liked this post, tap the 👏 below so other people will see it on Medium!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6bb00871e86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/unchained-reports/bancor-unchained-all-your-token-are-belong-to-us-d6bb00871e86">Bancor Unchained: All Your Token Are Belong To Us</a> was originally published in <a href="https://medium.com/unchained-reports">Unchained Reports</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Coins of Color and Forks of Force]]></title>
            <link>https://medium.com/colu/on-coins-of-color-and-forks-of-force-1363f3977170?source=rss-482473e6a905------2</link>
            <guid isPermaLink="false">https://medium.com/p/1363f3977170</guid>
            <category><![CDATA[colored-coins]]></category>
            <category><![CDATA[hard-fork]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Udi Wertheimer]]></dc:creator>
            <pubDate>Mon, 27 Mar 2017 12:48:56 GMT</pubDate>
            <atom:updated>2017-03-27T13:17:16.470Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently there’s been a heated debate regarding a possible fork to the Bitcoin blockchain. A lot has been written on the various risks and difficulties that a contentious hard fork would create for the ecosystem.</p><p>An interesting topic that didn’t yet receive much attention is the subject of bitcoin-based assets, like the ones based on the <a href="http://coloredcoins.org/">ColoredCoins</a> protocol, during a fork.</p><p>At <a href="http://colu.com/">Colu</a>, we are putting a lot of resources into the development of the open ColoredCoins protocol and platform, and we’d like to share our thoughts and guidance regarding this matter.</p><h3>The case for clarity</h3><p>There are a lot of different digital assets on the Bitcoin blockchain, using different protocols like ColoredCoins and others. On ColoredCoins alone, we have projects issuing currency, stocks, property rights, and many other types of assets.</p><p>When a cryptocurrency like Bitcoin (which behaves as a <em>bearer asset</em>) forks, it makes sense to expect that its value will split in some way between the two forked coins. Perhaps 30% will go into one, and 70% into the other. Perhaps 0% will go into one side, and 100% into another. Maybe the total value of both coins will be lower than pre-fork, or maybe the total value will be higher. But what we can be sure of, is that when two parties transact on one of the chains, the sender and receiver have the power to decide what they believe the value of that transaction is, and act accordingly.</p><p>When a digital asset is involved that is backed by real-word value, like a USD-backed token for example, there’s another complexity. The two parties of the transaction, the sender and receiver, are not the only ones that should agree on its value. There’s a third party, the issuer, that’s involved. The issuer must be willing to eventually accept the transacted assets and give their backed assets in return. In the case of a USD-backed token, the issuer must be willing to accept a payment in that token, as a “withdrawal”, and release real cash in return. This is not a problem when there’s only one chain, but if the blockchain forks, there are now double the tokens, and the issuer can’t respect all of them. So the issuer <strong>must decide</strong>, and <strong>communicate clearly</strong>, which of the chains will be considered valid.</p><p>If this isn’t made clear prior to the fork, some users might try to transact on the wrong chain after a fork happens, and later discover these transactions aren’t considered valid by the issuer, thus losing value.</p><h3>The case for stability</h3><p>We established that digital assets <strong>must</strong> choose one of the chains, and can’t “let the market decide” like some people claim might be possible with Bitcoin. If that’s the case, which chain should they choose? In general, that’s the issuer’s choice, however, we have some thoughts on that matter. Other Bitcoin companies like <a href="https://blog.bitgo.com/bitgos-approach-to-handling-a-hard-fork-71e572506d7d">BitGo</a> and <a href="https://medium.com/@bitrated/bitrateds-position-on-network-splits-and-bitcoin-unlimited-4685c5c3f8e8">Bitrated</a> provide reasons why they consider the Bitcoin Unlimited proposal unsafe and unstable, as it currently stands. This is how we believe they affect ColoredCoins issuers:</p><ol><li>There’s no <strong>activation mechanism</strong> or <strong>grace period</strong> for activating the fork. This makes it impractical for issuers to try and plan for supporting Bitcoin Unlimited safely.</li><li>There’s no <strong>wipeout protection</strong>, meaning that the chain could eventually, under some circumstances, reorg and rollback completely to the original chain, losing all transactions that ever occurred on the Bitcoin Unlimited fork.</li><li>The last point is a special case of a larger theme in Bitcoin Unlimited, that non-trivial parts of the chain are <strong>at a constant risk of being reorged</strong> due to incompatible block size parameters between nodes and/or miners. This is <em>expected behavior</em> with Bitcoin Unlimited. Again, this means that at any point customer funds might be lost.</li></ol><p>In addition to that, the Bitcoin Unlimited software has been shown to be unstable, and we believe it needs more development time and better development processes before it’s ready for prime time.</p><h3>The case for scalability</h3><p>Users of any sort of “digital assets protocol” on top of Bitcoin, like ColoredCoins, are well aware of rising fees and confirmation times. It is natural to assume that allowing blocks to get larger will relieve some of that stress. However, we believe that we must respect the shared resource that is the Bitcoin blockchain, and do as much as we can to reduce our footprint, instead of pushing for more and more bloat on the system.</p><p>We are also confident that “scaling” can’t be achieved by merely raising the block size, and right now the only viable solution we see for true scalability, while keeping Bitcoin’s features of <em>censorship resistance</em>, is by moving transactions off-chain.</p><p>This is why we support SegWit, both as an immediate yet cautious increase in block size, and as a first step for solutions like Lightning, which we are <a href="https://medium.com/colu/announcing-colored-coins-and-lightning-integration-8e54d5dbfd0e">already building on</a>.</p><h3>The case for choice</h3><h3>Colored Coins on Twitter</h3><p>If Bitcoin forks, users of ColoredCoins can make adjustments to use Unlimited, like any other altcoin. We don&#39;t recommend it though.</p><p>That being said, ColoredCoins is an open platform. All issuers and users are free to run their own full ColoredCoins node, supported by any Bitcoin-based full node they wish, be it Litecoin, Dogecoin, or Bitcoin Unlimited.</p><p>We clearly recommend that issuers choose Bitcoin Core, as we believe it’s the safest option. For this reason, all hosted infrastructure supplied by us will continue to use Bitcoin Core. We also won’t be able to provide support for other forks. However, issuers are free to choose any node software they wish.</p><h3>Summary and next steps</h3><h4>What’s next for issuers?</h4><p>Please take the time to research how a Bitcoin hard fork affects you and your customers. You can reach out to the rest of <a href="http://slack.coloredcoins.org/">the ColoredCoins community</a> to discuss this. We urge you to make a decision, as “letting the market decide” is in most cases not the right choice for issuers.</p><p>We recommend continuing to use Bitcoin Core, but if you choose otherwise be aware that you will have to run your own ColoredCoins node and won’t be able to use our hosted infrastructure.</p><p>Please make sure to provide clear guidance to your users as soon as you can.</p><h4>What’s next for users?</h4><p>If you’re using an asset issued by someone else, please contact your issuer and ask about their plans in case of a fork. Feel free to attach this post. If you’re not sure, a safe approach immediately after a fork might be to avoid making transactions with your assets until you receive proper guidance from the issuer.</p><p>Please feel free to drop by the <a href="http://slack.coloredcoins.org/">ColoredCoins Slack team</a> if you have any questions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1363f3977170" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colu/on-coins-of-color-and-forks-of-force-1363f3977170">On Coins of Color and Forks of Force</a> was originally published in <a href="https://medium.com/colu">Colu Local Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full Nodes and Fake News: A Bitcoin Primer for Bitcoiners]]></title>
            <link>https://medium.com/colu/full-nodes-and-fake-news-a-bitcoin-primer-for-bitcoiners-47120b1a97bf?source=rss-482473e6a905------2</link>
            <guid isPermaLink="false">https://medium.com/p/47120b1a97bf</guid>
            <category><![CDATA[game-theory]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[segwit]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[fake-news]]></category>
            <dc:creator><![CDATA[Udi Wertheimer]]></dc:creator>
            <pubDate>Tue, 21 Feb 2017 06:37:01 GMT</pubDate>
            <atom:updated>2017-02-22T08:28:48.239Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aBlzgM6C2rplL5Lx89eA5w.jpeg" /><figcaption>So how many people really attended Trump’s inauguration speech?</figcaption></figure><p>In my <a href="https://medium.com/colu/reaching-affordable-consensus-what-made-scaling-bitcoin-awesome-1d029babbcf8#.c4gu7pkno">previous post</a>, there was a hidden confession. I’ve been active in the Bitcoin space for quite a while now, and always felt well-versed in its technicalities. But I only recently realized <strong>what it actually was</strong>.</p><p>With the community locked in a tiring debate for a while now, we failed to notice an important milestone. We finally grew out of our old explanations, meant to introduce newcomers. Things like “Bitcoin is a digital currency”, or “A decentralized ledger”. We are now a more mature community, with many more members than before. And it might be the time to put more emphasis on educating long-time bitcoiners, than newbies. Because if we’re not all clear on the details of how (and why) things work, it’s going to be hard to consolidate on a single path forwards.</p><h3>Neil deGrasse Tyson on Twitter</h3><p>Almost all armed conflict in the history of the world came about because opposing sides believed different things to be true.</p><p>The problem with understanding Bitcoin is, it’s too easy to get obsessed with the tech. We keep getting told that the <strong>technology</strong> behind bitcoin “secures” our coins somehow. That it uses “cryptographic proofs” and “algorithms” to make things “decentralized”. Actually, the biggest innovation in Bitcoin is a social, game-theoretic one. Signing transactions with cryptographic keys to prove ownership isn’t a new idea. The thing that <em>is</em> new, is the aligning of incentives so that everyone profits by doing their part.</p><p>But just like in politics, in order for this system of <em>checks and balances</em> to work, people must be aware of it. In this post I will try to explain the balance of power between miners, users, and node operators. There are many other subjects to cover, and if this post is useful (let me know by clicking the 💚 at the bottom of this post!), I’d love to make this “primer” a series.</p><h3>The power of miners</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/1*P5G4uYH0JNIW5BB5Be3ssw.jpeg" /><figcaption>These miners seem ready to jump into a pool. From the 2015 film “The 33”</figcaption></figure><p>We all know what incentivizes miners to mine: the block reward, currently at 12.5 BTC per block, and the miner fees.</p><p>But what incentivizes miners to <em>follow the rules?</em></p><p>There’s a popular belief that miners are somehow “forced” by the “power of math” to follow the “laws of bitcoin”. This is false. The rules that make bitcoin what it is, its <em>consensus rules</em>, are hard-coded into node software like Bitcoin Core. And there’s nothing special about them! They’re just lines of code, which <strong>mean</strong> things like “the block reward halves every 4 years”, and “coins can’t be created out of thin air”. There’s also one that says “blocks must not contain more than 1 MB of data”</p><p>But what’s enforcing those rules? If they’re nothing but lines of code on a miner’s (or miner pool’s) client, what’s to stop them from changing them? What’s to stop a miner from producing a block that awards her with 25 bitcoins, instead of 12.5? Well, it’s not the “magic of cryptography”. In theory, any miner could do that. What’s stopping them, is that they’ll get punished — their peers will reject the block, and the block’s miner will lose its reward altogether.</p><p>Some think that what keeps miners in check are the other miners. If one miner will build an invalid block, the rest of the miners will ignore it, and the attacker will lose out. It’s true to an extent, but what if a lot of miners collude to change the rules? Popular belief says that if miners try to change critical rules, like the 21 million cap, bitcoin will lose its value. Due to this, it is assumed, it’s in the best interest of miners to avoid doing so. This isn’t always correct, though. Here’s an example:</p><p>Let’s say 75% of miners decide they wish to bring the block reward back to 25 bitcoins. They get the best analysts they can find, and get a prediction that doing so will cause many users to lose trust in the system. The value of bitcoin would be expected plummet from $1000 USD, to $600. The thing is, this still leaves the scheming miners in profit — the price of bitcoin took a 40% hit, but the miner reward doubled. Instead of 12.5 * $1000 = $12,500, they’d be making 25 * $600 = $15000. That’s a <strong>20% increase</strong> in revenue!</p><p>So we see that under <strong>some circumstances</strong>, it could <strong>make sense</strong> for the miners to disobey the rules. And these days we are finding ourselves in a similar situation, in fact — some miners wish to change the rules and mine bigger blocks. Everyone agrees that bigger blocks will hurt decentralization to a certain extent. But some users and developers believe this is a huge risk, while many miners and other users calculate that this risk is negligible. The miners’ incentives to make bigger blocks are big enough to make them want to force changing the rules, yet the opponents are strong enough to make that an issue.</p><p>So what’s stopping miners from making changes, even though they are sometimes incentivized, as a group, to do so? The answer is: full nodes. But bitcoin is kind of difficult to explain. So allow me instead to use the metaphor of <strong>fake news</strong>.</p><h3>Enforcing rules in a post-truth era</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-WkWAZnfwlRz-1Hn8gWe-A.png" /><figcaption><a href="https://www.youtube.com/watch?v=3xcW7Tg5E34">True story</a>.</figcaption></figure><p>During the last presidential campaign, liberals and parts of the mainstream media were blaming social networks, mostly Facebook, for allowing “fake news” to spread — mainly stories that were plain lies, describing events that never happened. They claimed Facebook has a responsibility to make sure lies aren’t represented as truth on their platform. Perhaps unsurprisingly, the use of that term has since been turned on its head, and is used mostly by Trump supporters to describe supposedly unfair representation by the media. The problem of “figuring out the truth” is what bitcoin set out to solve. Allow me to explain.</p><p>So let’s consider an imaginary parliament in the future Republic of <a href="https://en.wikipedia.org/wiki/Liberland">Liberland</a>. The members of that parliament are elected by the citizens of Liberland, in order to represent them in making the laws that everyone should live by. These laws are what makes modern society tick, so this is important. So laws are passed, and they are open for everyone to review and comment on, and everyone is happy.</p><p>But what happens when a powerful member of parliament decides to avoid paying his taxes? The agreed upon laws are very clear on the subject of taxes, but what’s to stop politicians from cheating? Citizens can’t go over each other’s tax forms just to make sure they are correct.</p><p>So citizens have two mechanisms that can help here. The first is that other politicians, which are also powerful, would love to see their rivals fail. So if they happen to stumble upon information that proves that another member of parliament is breaking the law, they are likely to do something about it. This is like miners that are expected to ignore invalid blocks, increasing their own chances to find a valid block.</p><p>But revealing the wrongdoings of colleagues is not always in the best interest of politicians! Sometimes they make deals that would make it worth it for them to keep their mouths shut. As we discussed before, this could also be true for miners, under certain circumstances.</p><p>The second mechanism to protect the citizens, is the media. The media is (supposedly) incentivized to always seek the truth. They are able to parse and understand all of society’s laws, and then reveal anyone not following them. This can work well, but as we all know it is proving more and more difficult to tell if media outlets (and which ones) are truly “seeking the truth”. Some are claiming that the media is giving a hard time to some politicians, not because these politicians are breaking the law, but because it’s in the best interest of some news conglomerates to take them down. So how can an honest citizen figure out the truth anymore?</p><h3>The Bitcoin Solution</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3CWGRUsdd8Q6eBTcfGB_Bw.jpeg" /></figure><p>Bitcoin solves this problem in a different way. It gives up the notion that some group, like “the media”, can be somehow incentivized to <em>seek the truth </em>for users. Instead, it’s the users’ job to seek the truth for themselves. They do this by becoming <em>validating full nodes</em>.</p><p>The laws of bitcoin, unlike the laws of <em>Liberland</em>, are extremely simplified. There’s a very small set of things that’s possible to do at all in <em>Bitcoinland</em>. And that’s a good thing, because that makes it easy for computers to validate them automatically. So now a <em>full node</em> can validate the entire history of all things that ever happened in <em>Bitcoinland</em>. If it finds something illegal along the way, it will refuse to trust that version of reality, and everything that supposedly occurred later.</p><p>It will <strong>ignore that chain</strong>, and will find another one that <strong>is</strong> valid. And that’ll be the only one that’s considered <strong>the truth</strong> for that node, even if there’s another, <strong>illegal chain</strong>, that has more mining power backing it.</p><p>And that’s what’s keeping miners honest. They understand that people with vested economic interest in the Bitcoin project, will be validating <strong>their incoming transactions</strong> with their own full nodes. If a miner tries to cheat along the way, he’ll be ignored — even if other miners try to support him. And they all risk losing their mining rewards — which is why they’ll avoid trying to cheat altogether.</p><h3>But running a node is difficult!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bsWnPueQ5oPHPA0TT86VfQ.jpeg" /></figure><p>Some people feel that running a full node is too hard. So they use block explorers like blockchain.info (or wallets that use such block explorers) as their <em>source of truth.</em> This is kind of similar to trusting the media for everything you think about the world. It might be easier when there’s not a lot at stake, but I think it’s irresponsible. Especially when transacting significant amounts. Ask <strong>any cryptocurrency exchange</strong> if they’re OK with trusting someone else as their <em>source of truth</em>, or if they prefer to be running their own full nodes. If the big players don’t trust centralized block explorers, why should you?</p><p>There’s also the misconception that you have to accept incoming connections on your full node (the famous “more than 8 connections” rule) in order to be useful to the network. If you accept incoming connections, you’ll help with distributing the block chain to other nodes. But it turns out this isn’t very important, as it’s trivial for others to do so, and it’s not really required that home users help. What’s important is that as many users as possible will use <em>their own nodes</em> to validate <em>their own incoming transactions</em>, in order to keep the balance of power in bitcoin. You don’t even need to use Bitcoin Core’s wallet for that — some mobile wallets, like <a href="https://play.google.com/store/apps/details?id=com.greenaddress.greenbits_android_wallet&amp;hl=en">GreenBits</a>, can securely connect to your full node at home and use it to validate your transactions.</p><h3>Full Nodes and Colu</h3><p>In <a href="http://colu.com/">Colu</a>, we are helping to build the community around <a href="http://coloredcoins.org/">Colored Coins</a>, an open protocol built on top of Bitcoin for issuing and transferring digital currencies. Colored Coins differ from Bitcoin in that full nodes have <strong>even more power</strong> — Bitcoin miners don’t validate Colored Coins transactions at all, and it’s solely the job of full nodes to do that — making the Colored Coins protocol even more decentralized than Bitcoin in some respects.</p><p>While it’s already possible to run your own <a href="https://github.com/Colored-Coins/colored-coins-docker-node">Colored Coins full node</a>, it’s not yet as easy as we would like it to be. We want to make sure that there are as many people as possible that run their own nodes and secure the network — and as a bonus, a full Colored Coins node is a full Bitcoin node as well! This is why we’re making running a Colored Coins full node much simpler and much less resource-intensive than it was in the past.</p><p>In the past, Colored Coins was a generic offering for “digital assets” on the blockchain, but we are gearing up to release more details about our updated vision for Colored Coins, as the backend allowing economies of all sizes to issue their own currencies. You’ll be hearing more about our updated <em>full node</em> and how it fits into this larger idea in the near future.</p><p>We also believe that Bitcoin Core, as the reference implementation of the Bitcoin full node and consensus rules, is extremely important for the ecosystem. We think that companies in the space should be doing more to support it. We’ll be sharing more information on how we‘re going to contribute to Bitcoin Core very soon.</p><p><em>If you liked this post, click the💚 below so other people will see it on Medium!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*dar4TOetHIOwWBU_NPUqBA.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47120b1a97bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colu/full-nodes-and-fake-news-a-bitcoin-primer-for-bitcoiners-47120b1a97bf">Full Nodes and Fake News: A Bitcoin Primer for Bitcoiners</a> was originally published in <a href="https://medium.com/colu">Colu Local Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reaching affordable consensus: What made “Scaling Bitcoin” awesome?]]></title>
            <link>https://medium.com/colu/reaching-affordable-consensus-what-made-scaling-bitcoin-awesome-1d029babbcf8?source=rss-482473e6a905------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d029babbcf8</guid>
            <category><![CDATA[digital-currency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[central-banking]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[payments]]></category>
            <dc:creator><![CDATA[Udi Wertheimer]]></dc:creator>
            <pubDate>Thu, 20 Oct 2016 08:16:29 GMT</pubDate>
            <atom:updated>2016-10-22T10:19:39.908Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7VerS37xHWyPz066j94rig.png" /><figcaption>The 1957 feature film “12 Angry Men” is all about the difficulties of reaching consensus. Oh, and if the number of women in this picture bothers you too, you should google “12 Angry Men Inside Amy Schumer”</figcaption></figure><p>How do you explain Bitcoin? What is a blockchain? What’s so great about it and if it is that great why hasn’t it take over the world yet? <strong>You think that you know</strong>? I thought so too.</p><p>I’ve been surrounded with Bitcoin for 4 years now. I’m an experienced software developer and consider myself an advanced Bitcoin enthusiast. And I recently joined <a href="http://colu.com/">Colu</a>, a company that is building the <a href="https://www.colu.com/technology">digital equivalent of physical cash</a>.</p><p>So, I work with Bitcoin full-time. And I’ve been explaining it to friends and family for years. But it wasn’t until I attended the <strong>Scaling Bitcoin </strong>conference that I finally understood <strong>what it is</strong>.</p><p>It is hard to explain Bitcoin to newcomers. But last week I learned it’s even harder to explain Bitcoin to bitcoiners. Allow me to try.</p><h3>It’s all about consensus, stupid</h3><p>The best feature of the bitcoin blockchain is reaching and maintaining <strong>consensus</strong>. All nodes can come to an agreement on <strong>what happened</strong>, and just as important, on what <strong>didn’t happen</strong>.</p><p>The most common application of this is the bitcoin currency itself. It allows all nodes to agree that a certain amount of coins were sent to Alice. They can also agree that Alice spent some part of that amount. Finally they can agree that she <strong>did not</strong> spend another part.</p><p>It is by being able to agree on what Alice <strong>did not</strong> spend, that we are able to prevent <strong>double spend</strong> attacks.</p><p>You can also put <a href="http://blockstack.org/">DNS records</a> on the bitcoin blockchain. You can prove that a domain name belongs to Bob, but also that another domain name <strong>doesn’t</strong> yet belong to anyone.</p><h3>Affordable consensus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*z-4MDQJr_V0M9iRRAI-sJw.jpeg" /><figcaption>Did he though? Well, that depends on who you ask.</figcaption></figure><p>Agreeing on what happened, and what didn’t happen, is hard. Look at this election season. Did Trump say Obama wasn’t American, or didn’t he? Did Clinton? And who said it <em>first</em>? That probably depends on who you ask.</p><p>So the problem with having everyone in consensus, is that they all need to know <strong>everything</strong>. To agree on who owns which bitcoin, the network requires all nodes to be aware of <strong>all the transactions ever made</strong>. It turns out that this is a lot of data to handle, so it takes a long time, and it’s expensive.</p><p>And remember, Bitcoin is not really a payment network. It’s a tool that helps us (faulty) humans reach consensus. So what do we really mean when looking for ways to “scale bitcoin?” What we are looking for is ways to <strong>make reaching consensus affordable</strong>.</p><p>Here are 3 ways to do that, that were mentioned out at Scaling Bitcoin:</p><h4>1. Bitcoin fungibility: how about some privacy?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*nUIbLz56yGELP3Fdvt6NyQ.jpeg" /></figure><p>According to Wikipedia:</p><blockquote><strong>Fungibility</strong> is the property of a good or a commodity whose individual units are capable of mutual substitution.</blockquote><p>So for Bitcoin to be fungible, one bitcoin must be completely identical to any other bitcoin. Currently that’s not the case, as all bitcoins have a <strong>public history.</strong> One bitcoin could conceivably be worth less than another, if it is known to have “dubious” history.</p><p>I won’t get into the influence of this on bitcoin economics here, but it’s important to note how privacy and anonymity in bitcoin go hand in hand with making it fungible.</p><p>How is all this related to <strong>making consensus affordable </strong>(or “scaling bitcoin”)? Well, turns out that the most efficient way to maintain your privacy is to just <strong>keep some things to yourself</strong>, and limit the things we must all agree on.</p><p>One interesting idea presented at Scaling Bitcoin is <strong>MimbleWimble. </strong>MimbleWimble is a design for a new blockchain. Instead of agreeing on the history of all transactions, let’s only agree on <strong>the current state!</strong></p><p>A few months ago, an anonymous author published the <a href="https://download.wpsoftware.net/bitcoin/wizardry/mimblewimble.txt">whitepaper</a> detailing the crypto magic required to make this work. Once miners process transactions, the entire blockchain history can be compressed to only the current state. And so the entire blockchain that weighs 100GB today could be compressed to less than 1MB, and you won’t be able to tell who sent how much to who. For more on MimbleWimble, check out the <a href="https://youtu.be/8BLWUUPfh2Q?t=1h29m29s">Scaling Bitcoin presentation</a> or the less technical <a href="https://soundcloud.com/heryptohow/mimblewimble-andrew-poelstra-peter-wuille-brian-deery-and-chris-odom">Crypto Show podcast</a>.</p><p>Another idea is using the Lightning Network for privacy…</p><h4>2. Lightning Network: Need-to-know basis</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pa3RYnIWBBx_6DF5dan_HQ.jpeg" /></figure><p>A lot has been said about Lightning. It’s a second-layer network that should enable bitcoin users to transact <strong>without</strong> writing to the blockchain, that is, without reaching worldwide consensus. It’s helpful for privacy and fungibility, but also much more.</p><p>Instead of registering transactions on blockchains, users transact with <em>cryptographic proofs</em> (think of them as IOUs). These show that they intend (and are able) to settle the payment in the future. Whenever Alice wants to convert the IOUs she received to bitcoins registered on the blockchain, she can ask Bob to pay up.</p><p>If he refuses, Alice can submit these IOUs to the blockchain, which will act as a “judge” and automatically make sure Bob pays and Alice gets her fair share.</p><p>But the trick is, Alice only has to do this if for some reason she wants everyone to have <strong>global consensus</strong> about her ownership of these coins. If she doesn’t want (or care for) everyone to know, she might very well <em>never</em> register that transaction on the blockchain.</p><p>She can continue to transact with other users on the Lightning Network and perhaps neither of them will ever cash out!</p><p>(Some of you probably noticed that I’m oversimplifying. But you can’t really explain how Lightning works in a few paragraph<em>s. </em>Bitcoin Magazine has a great three-parter on this subject: <a href="https://bitcoinmagazine.com/articles/understanding-the-lightning-network-part-building-a-bidirectional-payment-channel-1464710791">Part 1</a>, <a href="https://bitcoinmagazine.com/articles/understanding-the-lightning-network-part-creating-the-network-1465326903">Part 2</a>, <a href="https://bitcoinmagazine.com/articles/understanding-the-lightning-network-part-completing-the-puzzle-and-closing-the-channel-1466178980">Part 3</a>)</p><p>The Lightning protocol still needs a lot of work, and the 3 related presentations at the conference (I recommend watching them all) raised a lot of questions.</p><p>At Colu, we will provide our users the benefits of the Lightning network as soon as it launches. Expect to hear more very soon!</p><h4>3. Client side validation</h4><p>The <a href="https://youtu.be/uO-1rQbdZuk?t=1h43m18s">final presentation</a> was given by Peter Todd, who, for me, finally drove the point home.</p><p>He named the most revolutionary blockchain feature for consensus <a href="https://petertodd.org/2014/setting-the-record-proof-of-publication">Proof of Publication</a> (remember? That’s agreeing on what happened, and on what <strong>didn’t</strong> happen). Then he asked the surprising question:</p><blockquote>If miners are validating blocks, what are full nodes doing?</blockquote><p>or in other words:</p><blockquote>Do miners need to validate blocks?</blockquote><p>Protocols like Colu’s <a href="http://coloredcoins.org/">Colored Coins</a> take care of all validation on the <strong>client-side</strong>, on full nodes. Miners don’t care about the transaction data created by colored coins implementations. We pay them in bitcoins to put the data in the blockchain and they are happy to take the deal.</p><p>The idea of client-side validation for bitcoin is: <em>why do miners need to even validate bitcoin transactions at all?</em> Bitcoin could be transitioned to become an asset in a future protocol like Colored Coins. Miners could ignore all transactions and their validity (except for transaction that pay them directly).</p><p>They can dump all data they receive in blocks, as long as they are being paid enough. The upside is that miners don’t even need to be <em>able</em> to read the data! That allows all sorts of tricks with encryption, compression, aggregation, etc.</p><p>Full nodes will take care of validations and ignore all data that is invalid. And if they want to go for a new set of rules or features, they don’t need to seek approval from miners!</p><p>Today, Bitcoin as an ecosystem is deeply rooted in the idea of miners validating blocks. But going forward, I think discussions on the notion of client-only validations could be very interesting.</p><h3>Final thoughts: the inefficient blockchain</h3><p>People keep saying “Blockchains provide an efficient way to make payments”. This couldn’t be further from the truth, and Scaling Bitcoin was unapologetic about this. <strong>Blockchains are inherently inefficient.</strong> They are slow and expensive by design. And their capacity for growth is, compared to other data structures, limited. The reason they were made this way, was because their only true goal is to <strong>reach consensus</strong>.</p><p>The way to scale bitcoin, isn’t to make it faster or easier to agree on everything. It’s using non-blockchain, second layer protocols, to limit what we must agree on.</p><p>During the coming weeks, expect to hear more from us at Colu on our plans for the world’s first network of digital fiat currencies — using the blockchain for consensus where it makes sense, and second layer protocols where it doesn’t. Stay tuned…</p><p><em>If you liked this post, click the💚 below so other people will see it on Medium!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*fQKZqy6cvL2di9vsX0wLIw.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d029babbcf8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/colu/reaching-affordable-consensus-what-made-scaling-bitcoin-awesome-1d029babbcf8">Reaching affordable consensus: What made “Scaling Bitcoin” awesome?</a> was originally published in <a href="https://medium.com/colu">Colu Local Network</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>