<?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 Luke Parker on Medium]]></title>
        <description><![CDATA[Stories by Luke Parker on Medium]]></description>
        <link>https://medium.com/@Coinosphere?source=rss-61c943aa0227------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tVmbgD6H1Rlq_jsJ.png</url>
            <title>Stories by Luke Parker on Medium</title>
            <link>https://medium.com/@Coinosphere?source=rss-61c943aa0227------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:06:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Coinosphere/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[SWATH boats will be too expensive for Seasteaders.]]></title>
            <link>https://medium.com/@Coinosphere/swath-boats-will-be-too-expensive-for-seasteaders-601efbef39ff?source=rss-61c943aa0227------2</link>
            <guid isPermaLink="false">https://medium.com/p/601efbef39ff</guid>
            <category><![CDATA[ocean-builders]]></category>
            <category><![CDATA[floating-walkways]]></category>
            <category><![CDATA[seasteading]]></category>
            <category><![CDATA[aquapod]]></category>
            <dc:creator><![CDATA[Luke Parker]]></dc:creator>
            <pubDate>Sat, 08 Aug 2020 06:01:44 GMT</pubDate>
            <atom:updated>2020-08-08T06:01:44.071Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>SWATH boats will be too expensive for Seasteaders. Here’s a cheap alternative using floating walkways</strong></h3><p>I’ve been thinking hard about the current solution to the problem of boarding and departing from an <a href="https://www.youtube.com/watch?v=aIo6usoRvqo">Ocean Builders’ AquaPod</a>. The tall pods have a balcony that comes nowhere near the deck of most boats, so <a href="https://www.youtube.com/watch?v=L-Ee8StT4LM">the current thinking</a> is to build a custom boat of the SWATH design to scale, which would have a tall-enough deck and can be moored directly beside the seastead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I0hYIs2T6OvOiToKM8mMIg.png" /><figcaption>Ocean Builder’s SWATH scale prototype</figcaption></figure><p>Seatoshi, Chad, and the team have even built a scaled-down prototype of the boat’s frame, (pictured) which looks beautiful. However, SWATH boats have a few serious issues that might make it unaffordable to most seasteaders.</p><p><strong>Swath issues:</strong></p><ul><li><strong>It’s a really huge friggin’ boat! </strong>(At scale it will be massive. Perhaps a million-dollar boat.)</li><li><strong>There is no industry making these regularly now… Would each be a custom make? </strong>(Long wait time.)</li><li><strong>This system makes seasteading incompatible with most boats!</strong> (No visitors, sell your existing boats, sorry!)</li><li><strong>SWATH boats are untested for our needs anyway. We should certainly have a backup plan by this point.</strong></li></ul><p>The smallest SWATH boat I could find on youtube is this 27-meter ferry:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/1*fl4mcl3pZSY8SQjt46VW2g.png" /><figcaption>Danish commercial Swath ferry @ 27 Meters.</figcaption></figure><p>Needless to say, a boat even half that size is going to cost much more than an AquaPod will. Sure, a SWATH is a dream to ride, but port fees &amp; fuel just can’t be cheap with these monsters.</p><h3>Solution: Floating Walkways around the Spar</h3><p>Luckily, a much cheaper alternative to the SWATH system comes with many additional benefits. (And allows guests!) A ‘softdeck’ made of some kind of sturdy, marine-grade floating walkway (there are multiple types in mass production now) could be installed around the base of the AquaPod, and a naval-grade hatch in the middle of the spar, just above water’s highest planned level, will let people step out onto the softdeck, stroll down a gangplank and walk to their boat docked nearby. (Among other activites.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*C2euwNzE-mQ4J1AkQ7hebw.png" /></figure><p>Floating walkways come in many different designs, and size is generally no constraint. Tokyo bay once had an entire airstrip floating in it. The “mega float” was 100% constructed on a floating platform, and military planes used it successfully during the war. Naturally, testing will need to be done to see which design and materials will be best for the conditions that AquaPods are installed in. Some more modern projects made with floating walkways are absolutely massive:</p><p>Floating walkways on a lake in Italy:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FfJ20p1IXG4A%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DfJ20p1IXG4A&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FfJ20p1IXG4A%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/78bcebd42549d7ff0d2f25bb5c4f8ba9/href">https://medium.com/media/78bcebd42549d7ff0d2f25bb5c4f8ba9/href</a></iframe><p>Floating walkways on a river in China:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FwNW6bHtLiHQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwNW6bHtLiHQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FwNW6bHtLiHQ%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/43d78fd025266f10aec1dcecbd9ac809/href">https://medium.com/media/43d78fd025266f10aec1dcecbd9ac809/href</a></iframe><p>An interesting modular dock system at sea:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fq5m6Ft4fqsY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dq5m6Ft4fqsY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fq5m6Ft4fqsY%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/deea059736ba9cfdc30b8ae42fa4fb42/href">https://medium.com/media/deea059736ba9cfdc30b8ae42fa4fb42/href</a></iframe><p>Another thing that will need testing is how this softdeck is connected to the spar. The repetitive movement of the waves rising an dropping the softdeck around the spar’s shaft could wear down all concerned parts over the years. However, by simply placing wheels on the end of a gangplank, occupants can step outside with ease, even on days with higher waves.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pHV0vV8hHbTMcNX-e_u43w.png" /><figcaption>Green: Softdeck floating walkway around AquaPod’s Spar. The gangplank has wheels underneath it to ride the waves up and down. — But now there’s a place to dock normal boats!</figcaption></figure><p>If putting a hatch in the spar is too structurally damaging to an AquaPod, then an elevator could be added to the side of the unit instead, although something would have to be rigged to allow the bottom floor of the elevator to float up and down with the waves.</p><p>A wonderful benefit from installing a softdeck is that our lone cabins on the water will be able to be connected, and even have yards to play on. Pathways between neighbors or one pathway each to a central hub would make for an ideal neighborhood linkage when forming the first seastead communities.</p><p>Add a few more square meters to the softdeck around your house and suddenly you have a yard to stretch your legs on, place some potted plants or trees, host a community barbecue on, or even let the kids play ball.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nNVy54OkVCsn1VsG2VrmMw.png" /><figcaption>A typical arm of one of the first seasteading communities at sunset. BYOBoat!</figcaption></figure><p>Other design challenges include fortifying the mooring posts, placing railings wherever needed, and safeguarding the Spar’s opening from getting hands stuck in it during any wave action. (Basically, leaning against the spar will be dangerous.) The hatchway security may also pose a problem because it must be fully water-tight during stormy weather yet still have a security system such as a keypad and camera.</p><p>SWATH boats can still approach the balcony as planned even with the softdeck in place, as long as the walkway stays on the opposite side of the AquaPod from the balcony. Otherwise, your own boat should be fine!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=601efbef39ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to pull off a Hard Fork in Bitcoin]]></title>
            <link>https://medium.com/@Coinosphere/how-to-pull-off-a-hard-fork-in-bitcoin-98e756115721?source=rss-61c943aa0227------2</link>
            <guid isPermaLink="false">https://medium.com/p/98e756115721</guid>
            <category><![CDATA[segwit]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[bitcoin-unlimited]]></category>
            <category><![CDATA[bitcoin-mining]]></category>
            <category><![CDATA[hard-fork]]></category>
            <dc:creator><![CDATA[Luke Parker]]></dc:creator>
            <pubDate>Thu, 18 May 2017 07:09:29 GMT</pubDate>
            <atom:updated>2017-05-18T07:09:29.036Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Using game theory to tackle the biggest problem in Bitcoin today</em></p><h3>The problem</h3><p>Bitcoin’s market cap is closing in on $30 Billion, which is more than enough incentive for _<em>insert_any_bad_guys_name_here</em>_ to harm the network.</p><p>Ethereum’s market cap was only around $800 million <a href="https://blog.ethereum.org/2016/07/20/hard-fork-completed/">last July</a> when they found out <a href="https://blog.ethereum.org/2016/07/26/onward_from_the_hard_fork/">the hard way</a> that contention, even when not announced so loudly, splits your blockchain in two.</p><p>Although exchanges assure us that a split of bitcoin’s blockchain today would result in Bitcoin Core’s existing coin and an altcoin named BTU, the effects of a split could be completely devastating to bitcoin’s price and market share. Many feel that it would be the end of bitcoin’s entire value proposition and the end of digital scarcity as we know it. (Investors really won’t enjoy hearing the media refer to Bitcoin as a ‘stock split’ which doubled the supply to 42 million bitcoins!)</p><p>So now that Bitcoin is more than incentivized and contentious enough to make a hard fork too risky anymore, any number of a hundred different conspiracy theories and even a few perfectly rational reasons are stopping Bitcoin’s developers from even <em>considering</em> a risky hard fork of the blockchain. And thank goodness for their carefulness, but it does come at a price.</p><h3>The Roadblock</h3><p>A hard fork appears to be required now to raise Bitcoin’s inadequate block size directly. Not for technical reasons, but for egos, apparently. Soft Forks, like the current one planned for Segwit, does in fact raise the block size while avoiding the risk of a chain split. Sadly, they have somehow become extremely confrontational lately, thanks to any number of reasons that is really still up to speculation.</p><p>All we know for sure is that the largest miners tell us that they will only move forward with a hard fork proposal like they agreed to at the infamous <a href="https://medium.com/@bitcoinroundtable/bitcoin-roundtable-consensus-266d475a61ff#.xkmfcmn7c">HK roundtable agreement</a>, which somehow they feel Core devs backed out of, despite miners not signaling for Segwit first like they clearly agreed to do… Clearly, such agreements are open to interpretation and not sufficient.</p><p>If, to come to a compromise, their egos must be stroked a bit, the alternative is still worse… But we just can’t risk splitting the chain while doing so.</p><p>If the miners and other people standing against passing Segwit require a hard fork, and we still have no reason to believe that it won’t be without contention from them or some third party, it is clear that a new option is needed; one that ensures there is no contention by other means.</p><p>After much thought, I think there may be a way to avoid contention in hard forks which even Core Devs might agree to. It won’t be loved by everyone, but it will hold everyone accountable and vastly reduce the possibility of contention during a hard fork.</p><p>This may, in fact, be the only way to do a hard fork in high-value blockchain systems going forwards. It even assumes that bad actors currently exist that won’t do what they agree to do.</p><h3>The plan</h3><p>First, we find everyone →<strong>who has a realistic chance of blocking</strong>← adoption of whatever it is we’re forking for. Both with mining power and power over the economic majority. An example might be all economic nodes, plus all major wallet providers, all exchanges with 100 btc/day volume, and all miners with over one petahash mining sha256. -I’ll leave it up to developers to figure out the proper makeup, but the number shouldn’t be small nor should any of these players be of humble means.</p><p>Second, we define two desirable outcomes, the second one approached from a separate direction where large amounts of money can solve the problem. <strong><em>Example: </em></strong>A) We hard fork to raise the blocksize to 2MB, and B) We collectively buy enough mining power to signal segwit for two weeks overcoming any opposition, getting it passed easily.</p><p>The goal in this step is that if the A outcome fails, those who make it fail will be forced to pay for the B outcome, which would strongly be against their best interest. Game theory at it’s finest.</p><p>Third, we have to figure out how many bitcoins it will take to realistically make outcome B happen. Yes, it may be huge, but bear with me.</p><p>Fourth, we set up a panel of judges made of prominent members of the community that we vote in; A miner, a dev, and at least three executives from well-respected companies in the industry that are not economic nodes themselves. This group’s only job will be to hold onto a multisig key that controls the outcome B trust fund and either reverse the payments in the case of outcome A, or go forward with the payment in outcome B. The group is disbanded immediately after that duty.</p><p>Fifth, all found who have a chance of blocking are given an agreement to sign, but only under the stipulation that they put up their share of bitcoins into the trust fund. They can’t sign without the deposit, but they’ll get the deposit back if there is no contention that splits the chain.</p><p>Sixth, the rising mempool and basically everyone in the whole community pressures these people into signing. Until they do, there simply is no chance for a hard fork. <strong><em>Ever.</em></strong> Only through signing, do we allow the hard fork, and a huge bonus of doing it this way is that the fork can happen within hours or days, not months or years. This could literally raise the block size in safety in mere days from now.</p><p>Seventh, once all signatures are gathered and the trust fund is full, the fork is executed. We all bite our nails. If there is a bad actor who wants to split a chain, this is where they’d do it.</p><p>Eighth, After enough time has passed, (a day? two weeks?) the judges decide if the chain has been split, and if so, if anyone backed out on their promise when they signed. If they did, the money is used to pay for outcome B, which the developers who created the code for that outcome will carry out immediately. Otherwise, the money simply is reversed back to their original owners and we enjoy the safely-forked new blockchain and the benefits that come with forking it.</p><h3>The spoils of war</h3><p>Sure there are a lot of details to mop up, but if this can be done and the game theory element preserved at its heart, then we’ll have successfully defeated… Contention itself.</p><p>If the job of finding all the people who have the power to block the fork is done properly, there will be no one left who doesn’t sign the agreement and put up some serious coins to ensure a solution is enacted soon.</p><p>Hard forks can happen every year if we need them to this way, although the people who put themselves in place of power in the bitcoin community will be inconvenienced, for sure. At least while the scaling debate still roars along.</p><p>Still, if there is no pending doom like we currently face, there is no way to twist these people’s arms into signing, either. This is an emergency measure only, but one that is desperately needed these days.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98e756115721" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Minimalist approach to Scaling Bitcoin]]></title>
            <link>https://medium.com/startup-grind/the-minimalist-approach-to-scaling-bitcoin-fa8e1f592b4d?source=rss-61c943aa0227------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa8e1f592b4d</guid>
            <category><![CDATA[minimalism]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[future]]></category>
            <dc:creator><![CDATA[Luke Parker]]></dc:creator>
            <pubDate>Wed, 12 Apr 2017 21:04:11 GMT</pubDate>
            <atom:updated>2017-04-20T23:57:53.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LOjzB19bMJtMr7H7NjFwJQ.png" /><figcaption>Packing as little as possible is often the best solution</figcaption></figure><p>The divided houses of Bitcoin users are often convinced by loudmouths and trolls that they no longer have much in common, and many Bitcoiners today would even like to fork off into a separate coin. But as <a href="https://bitcoin.org/en/posts/hard-fork-policy">several</a> <a href="https://medium.com/@nicolasdorier/the-real-root-of-all-evil-in-bitcoin-f34f3d3a096e">bright</a> <a href="https://www.quora.com/Why-does-a-hard-fork-in-Bitcoin-threaten-Bitcoins-value">minds</a> <a href="https://www.cryptocoinsnews.com/bitcoin-fork-avoided-costs/">have</a> <a href="https://vinnylingham.com/a-fork-in-the-road-70288fd3c046">pointed out</a>, splitting Bitcoin up could be extremely damaging, if not fatal, to Bitcoin’s price and adoption.</p><p>In fact, all cryptocurrencies could suffer greatly at the loss of trust that would result at the fallout from the public seeing 42 million bitcoins! Satoshi would have lied to them about digital scarcity.</p><p>Since <em>not</em> scaling bitcoin is a certain way to ensure other altcoins overtake Bitcoin’s network effect, and big packages like SegWit, which have lots of needed, if not crucial, upgrades in them, will never see 75% (much less 95%) of the mining power vote for them again, what options do we have to scale at all?</p><h3>Bitcoin’s <a href="https://en.wikipedia.org/wiki/Bay_of_Pigs_Invasion">Bay of Pigs</a> Imminent</h3><p>Bitcoin Unlimited has <a href="https://coin.dance/nodes/unlimited">lost its steam</a>, bcoin never took off, and many Core supporters are <a href="http://uasf.saltylemon.org/">pushing</a> for a miner-ignoring fork called <a href="https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki">UASF</a>, which sounds good on the surface but is not as neat and tidy as they’d have you believe.</p><p>Several core developers have <a href="https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-March/013772.html">explained</a> the <a href="https://github.com/bitcoin-dot-org/bitcoin.org/pull/1564">dangers</a> of going up against majority hashing power, and Bitcoin Unlimited developer Peter Rizun has outrageously <a href="https://medium.com/@peter_r/on-the-emerging-consensus-regarding-bitcoins-block-size-limit-insights-from-my-visit-with-2348878a16d8">already suggested using this nuclear tactic</a>. In a nutshell, pissed-off miners can attack and even destroy your blockchain if they have enough hashes.</p><p>It’s just a matter of piling on enough orphaned, empty blocks onto your chain.</p><p><a href="http://www.uasf.co/">UASF</a> is a major threat to miners like Jihan Wu today, and the threat is made impossible to ignore by them when we announce the date and time that all nodes are supposed to sync together and upgrade on. (Flag day.) It’s best to think of UASF as holding up a big sign that says to the opposing team:</p><blockquote>‘On day X we are going to deploy nukes on you. So you‘d be an idiot not to nuke us first.’</blockquote><h3>The Proposition</h3><p>Meanwhile, our current situation kinda sucks too. We lose new Bitcoin users and businesses every day when we should be attracting them at a record pace. But if we cannot use UASF to fix this, what option does that leave? The strong controversy between the two sides seems to make all options we have today useless. There is one way to bypass controversy, however.</p><p>Allow me to make a humble suggestion:</p><blockquote>In an effort to eliminate all controversy from blocking non-controversial upgrades, I propose developers break up SegWit and all future upgrades into their component parts. Small chunks of code, singular in purpose, each to be upgraded <em>one at a time… Minimalist packing.</em></blockquote><p>We would see close to zero controversy to reach consensus on a single-feature-basis. For example, take a recent feature in 0.14.0, such as Improved Block Downloading (IBD). Compare deploying only that feature in Bitcoin to the controversy around getting SegWit upgraded with it’s <a href="https://bitcoincore.org/en/2016/01/26/segwit-benefits/">many functionalities</a> packed inside.</p><p>Everyone wants their blocks to download faster, right? They couldn’t put up much of a fight against getting faster block downloads if they have no reason to suspect something else that they don’t want is included in the upgrade. It’s that simple.</p><p>The current process reminds me a lot of riders on a Bill in the legislative process of many countries, in fact… Who wants to have a Bill made up of mostly riders? Is Bitcoin run by it’s lobbyists too?</p><p>Developers can create and review code far faster when it is nice, neat little packages of one. Arguing against code that is simple is much harder, too.</p><p>Another positive side effect is that it should greatly help to destroy the unfounded ideology of Bitcoin Core as being a monolithic thing… As the layman sees it today, Core might as well be a corporation with a president… But if every little upgrade came with different developer’s names attached, Core’s role is lessened and the developer’s role is highlighted.</p><h3>The Drawback</h3><p>Of course the flipside of breaking up the functionality into single chunks means that we have to upgrade Bitcoin far more often to meaningfully scale. A six-month upgrade period is probably too long now, and running a node will indeed become more of a hassle with all of the smaller upgrades.</p><p>If node operators have to review the terms and upgrade their code twenty times over the course of the next 3 years just to upgrade the alternative of SegWit, however, then<em> so be it.</em> At least Bitcoin avoids certain destruction. It will, at the very least, be able to improve itself slowly. We’ll still have Bitcoin, we’ll still be in the lead of the network effect, and we will indeed be able to reach consensus on most of these individual parts.</p><p>The unfortunate parts that do not reach consensus will simply have to be upgraded off-chain, where it is permissionless to do so. I’d be thrilled to see networks a thousand layers deep running on top of Bitcoin. Talk about decentralization! Imagine your government trying to track your payment across one of a thousand different lightning networks or sidechains… Or a hundred of them.</p><h3><strong>Onwards</strong></h3><p>One excellent step towards compartmentalizing these functionalities would be adding the <a href="https://medium.com/@nicolasdorier/the-real-root-of-all-evil-in-bitcoin-f34f3d3a096e">Consuensus Rules</a> that Core Developer Nicolas Dorier’s planned last month. This would make it so that we don’t have to wait for each of the tiny upgrades to be fully passed before starting the next.</p><p>In closing, I’d like to point out that there are currently zero options on the table that appeal to both sides of the debate, and I hope this plan offers something closer to a real compromise. It still needs work, and I need your help to convince developers to start working in this direction at all.</p><p>If you like the proposal you’ve seen here today, please tell your local bitcoin developer to check out Nicolas’ Consensus Rules and maybe even this post too. Thanks for your consideration.</p><figure><a href="http://eepurl.com/bBbrFX"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*iq0EKuOUS52AtOW_RSKNxA.jpeg" /></a></figure><figure><a href="https://europe2017.eventbrite.com/?aff=mediumfooter"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*sg1PGrUIRQvIDH7bb2OY0A.jpeg" /></a></figure><figure><a href="http://startupgrind.com/chapters"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*N1UpkDFpA5UrRxen2NHxtw.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa8e1f592b4d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/the-minimalist-approach-to-scaling-bitcoin-fa8e1f592b4d">The Minimalist approach to Scaling Bitcoin</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bitcoin’s Latest Scandal: How to Analyze the ASICBoost Mining Debate]]></title>
            <link>https://medium.com/startup-grind/jihans-specific-sins-11c5c63d1b9f?source=rss-61c943aa0227------2</link>
            <guid isPermaLink="false">https://medium.com/p/11c5c63d1b9f</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Luke Parker]]></dc:creator>
            <pubDate>Mon, 10 Apr 2017 16:52:09 GMT</pubDate>
            <atom:updated>2017-04-14T23:02:35.939Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*so19R7uSgDASlp_oSQQmTg.jpeg" /></figure><p>Too many strawman arguments are flying around the Bitcoin space right now about how Jihan Wu, with his alleged <a href="https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/013996.html">covert ASICBoost</a> modification, is mining selfishly but not really doing anything wrong since we can expect miners to seek maximum profits. This harmful behavior must end now.</p><p>Jihan’s unfair earnings have been <a href="https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014042.html">calculated by two different developers</a> now to be in the neighborhood of $100 million per year. If his sin was only making a better product that earned that much money, I’d be trying to cozy up to him and get him on my good side today. I’ve got no problem with winners.</p><p>But that’s not his crime. If Greg is correct in his <a href="https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/013996.html">accusation</a>, Jihan was causing unimaginable amounts of harm to Bitcoin, which if left unchecked, may even lead to it’s doom.</p><p>There may be other sins, but these are top three problems I can see covertly mining ASICboost in the way Greg describes:</p><h3><strong>Sin #1: Community splitting, i.e. Divide &amp; Conquer.</strong></h3><p>If Greg is correct, the entire blocksize debate since ~2014 was little but Jihan’s way to keep us fighting against each other so that Bitcoin will not scale up in a way that blocks Jihan’s edge. It appears that SegWit and many other scaling upgrades with a similar solution are upgrades that Jihan <em>cannot allow to ever happen</em> since he got his ASICBoost tech deployed.</p><p>Since that time, early 2015, this community has split into two communities at each other’s throats and there has been wave after wave of challengers to the Core devs… (Bitcoin Classic, BitcoinXT, BU, and now Extension Blocks) — All that do not use the upgrade that nullifies the gains from ASICboost.</p><p>If Greg is right, Bitmain signaling for BU and all of its efforts to oppose SegWit were never for ideological reasons, just financial. It means that our fight was a delay tactic, so he could earn more money, plain and simple.</p><p><em>So many friendships lost, so much time and effort wasted…</em></p><p>Think of all the energy that developers could have been put into scaling bitcoin that was instead spent on defending themselves from attack; it’s unfathomable.</p><p>As to how anyone would be able to force us to fight each other, I’ll simply link readers to explanations of the well-established concepts of <a href="https://en.wikipedia.org/wiki/Sockpuppet_(Internet)">sockpuppetry</a> and <a href="https://en.wikipedia.org/wiki/Agent_provocateur">agent provocateurs</a>, and allow your imagination to go wild with how much strife Jihan would be able to accomplish using those two methods with his war chest of up to $100 million per year.</p><p>Because of this strife, many have <a href="http://coinmarketcap.com/charts/">turned to altcoins</a>, and many people and businesses outside of bitcoin did not join us that would have otherwise. Because of this strife, we haven’t scaled Bitcoin in any meaningful way yet, and that has stopped many desirable use cases that depend on micropayments from being completed, including Code Valley, Yours, MegaUpload2, and tons of other projects and infrastructure… Which again, turns businesses away from embracing bitcoin. (And startups from starting up.)</p><p>Today’s price would likely be $6,000 or higher, IMHO, if it weren’t for that loss of our cohesion that it appears Jihan personally created sometime before 2015.</p><h3>Sin #2: ‘Merklegrinding’ makes Bitcoin less safe.</h3><p>Bitcoin’s cryptographic security relies on creating as much hard work for a would-be attacker as possible, as measured in the number of operations a task requires to be computed. As Greg Maxwell has explained on the Devlist, the attack is highly technical in nature so it’s hard for most to understand the significance, even among other devs. “While talking about it privately for the last month I ran into many experts that kept lapsing into thinking that the collision required 2³² work, and other misunderstandings,” he said.</p><p>A great, recent <a href="http://www.mit.edu/~jlrubin//public/pdfs/Asicboost.pdf">writeup by MIT’s Jeremy Reubin is here</a>, but Greg was correct to describe it as difficult to understand. What follows is my imperfect summary, for those who won’t take the time to read it for themselves.</p><p>Apparently, the SHA2–256 cryptography behind Bitcoin’s mining function uses a “merkle damgard hash function” that all miners have to perform in order to keep looking for those special numbers to submit like lotto tickets every ten minutes.</p><p>Without using the covert version of ASICBoost, the odds of winning were equal for all miners, in relation to their hashing power, because the amount of work was equal for everyone.</p><p>In this case, Greg has accused Bitmain of changing his process, deep inside the hardware where you can’t look at the code, to make a big shortcut in the merkle damgard hash function so that it ‘grinds on the version bits’ of the Merkle root, which cheats the process by shuffling transactions that it processes. Detecting actual usage of this is impossible, only statistical evidence of the output can be detected.</p><p>Meanwhile, the process of making bitcoin secure with mining has been compromised. Instead of all miners competing on a level playing field, Jihan’s miners have allegedly been taking the shortcut, doing less work to win more blocks. That’s textbook bypassing of a basic security in Bitcoin.</p><p>This process cannot be done mistakenly, because doing it this way would normally be very wasteful, since the process trades away system RAM and extra SHA256 calculations in order to shuffle the transactions in a different order to pull this off. It’s a very blatant cheat and serves no other purpose but trading away security for extra money, and only in a very certain set of circumstances does it pay off. Jihan’s exact circumstances.</p><p>Use of this process also explains all of the empty blocks that Jihan has been <a href="https://twitter.com/JihanWu/status/704476839566135298">defending the right to create</a>, despite how much we all need more space in our Blocks due to the high number of transactions these days.</p><p>Bitmain has <a href="https://blog.bitmain.com/en/regarding-recent-allegations-smear-campaigns/">officially denied</a> USING this process on Bitcoin’s mainnet, and that is now 100% of the point of contention we need investigated thoroughly.</p><p>This merklegrinding is the part that Core developers are calling the “attack,” just as they would anything else that tries to bypass Bitcoin’s security defenses. If Greg is correct, bitcoin has been far less safe than it should be for as long as Jihan has been doing this covertly. That could be as far back as 2014.</p><h3><strong>Sin #3: Miner centralization.</strong></h3><p>If he is using this unfair advantage, Jihan has already put at least two competitors out of business that couldn’t figure out why they failed. In May 2016, Now-bankrupt KNC Miner’s CEO Sam Cole <a href="http://digital.di.se/artikel/knc-miner-grundaren-kina-har-fordelar-som-vi-inte-kanner-till">was interviewed</a> and said a few things about Bitmain that explain a lot today if Greg is correct.</p><blockquote>“<strong>The competition has increased more than we could ever anticipate. When we crunch the numbers it amounts to hundreds of millions of dollars that have been invested only in the past six months… Even if they have free electricity we can’t understand how they can make a profit</strong>” — Cole</blockquote><p>KNC was only the most recent Bitcoin mining company to go under since Jihan got his ASICBoost patent. The Israeli <a href="https://www.cryptocoinsnews.com/bitcoin-mining-developer-spondoolies-shuts/">Spoondoolies tech</a> was another, and they suffered a very similar fate. Despite revenues of $28 million in 2015, the company went bankrupt early the following year after multiple fundraising attempts. It too said that the only reason for their failure to stay profitable was competition with a China-based bitcoin hardware developer.</p><p>If all mining manufacturers were in China, then Bitmain’s Chinese patent on ASICBoost tech would have allowed him to keep down the competitors and all of this would have been transparent. Spoondoolies and KNC were in Israel and Sweden, however, where Jihan’s patent are meaningless, so it best serves Jihan to stay quiet about the reason. This appears to be a lack of communication in the industry, however, because even some Core developers knew about Jihan’s 2015 patent on ASICBoost <a href="https://twitter.com/olivierjanss/status/731198742968291329">since May 2016.</a></p><p>Imagine how many other mining manufacturers would have started up on level playing field… Maybe we’d have 20 different chip makers today instead of the 2–3 we have now? Now, imagine how hard it must be for a new chip manufacturer to launch today… No matter how awesome your fabrication process, now matter how much capital you have access to, someone else out there will still make a product that is 20%-30% more efficient than yours and sell it worldwide. That’s an insurmountable profit margin. Zero investors out there would be willing to loan to such a startup today.</p><p>Meanwhile, mining centralization has been a top-5 threat on the Core dev’s list of bitcoin-killers since the very day ASIC manufacturing was announced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*OWNku-oXyJosIhUlcngvWg.jpeg" /><figcaption>We’ve kinda been here before, but last time everyone begged Core devs to stop the mining monopoly!</figcaption></figure><p>Who in the community during the summer of 2014 can forget the defcon-5-level of panic when pool <a href="http://www.businessinsider.com/today-bitcoins-doomsday-scenario-arrived-2014-6">Ghash.io attained 51% of the mining hashrate?</a> Conspiracy theories were everywhere and many were demanding that the Core devs find a way to stop Ghash forcefully, so they couldn’t do a 51% attack against the network.</p><p>Thankfully, Ghash was a good neighbor and broke up their own monopoly voluntarily. ‘Good guy Ghash’ — I think some T-shirts were printed with the slogan.</p><p>Bitmain doesn’t appear to want to take the same paycut, since they are busy <a href="https://blog.bitmain.com/en/regarding-recent-allegations-smear-campaigns/">defending their innocence</a>. If the allegations are correct, anyone using their chips or mining in their pools should be eyed with even greater panic and disdain than Ghash was; If, again, the charges are founded. Siding with centralization is siding against Bitcoin, plain and simple.</p><p>Let me make this point clear:<em> It does not matter</em> that Jihan has <a href="https://blog.bitmain.com/en/regarding-recent-allegations-smear-campaigns/">admitted to Building</a> ASICBoost into his chips. As long as he says he did not <em>use</em> it, he is claiming innocence, and that creates problems.</p><p>The difference is very important; If developers simply try to block covert ASICBoost without holding Jihan accountable for these crimes, then Jihan is not only free to commit more crimes, but he will in fact GROW his following of supporters who feel that he is being attacked by “Core devs” unfairly.</p><p>It is the followers, not Jihan, who need to be shown indisputable evidence of Jihan’s wrongdoing. Any attempt to upgrade the network to fight Jihan may very well come down to their support.</p><h3><strong>So, what to do? Who to Believe?</strong></h3><p>We have to let science decide, of course. We must encourage many peer review teams, hopefully some from outside the community too for unbiased opinions, to review Greg’s evidence and redo the tests for themselves. We may even need to do some crowdfunding in order to afford these tests.</p><p>Although direct proof of Jihan’s covert usage may be impossible, incontestable evidence could still be gathered that is too strong for anyone to reject. (i.e. Compute the probability of his actual results matching a set of ASICBoost-derived results.) If the claims cannot be disproved, then Greg will be more and more shamed over time by much of the community, and perhaps even unemployable in the long run. Instead of being a hero to all Bitcoiners, he stands to lose most of the remaining respect he had in the community if <a href="https://www.reddit.com/r/btc/comments/64czhc/asicboost_is_an_invented_nonissue_to_divert_your/">current trends</a> persist. Not to mention, SegWit becomes far less likely to pass.</p><p>However, no matter how much Greg’s detractors feel that he gets on their nerves with his occasional trolling and less-than-humble attitude, he’s also a PhD with some incredible development skills that are well respected across several industries. He’s no dummy.</p><p>I cannot in good faith proclaim that he is absolutely correct yet, but I expect that we could do so definitively if the evidence is pursued. Only once it has, will we be able to act on one course or another immediately to stop these major problems already occurring in Bitcoin now. Calls for UASF or forks of any kind to enable Segwit are too drastic until we have this key evidence.</p><p>After proving Jihan’s usage, the next step would then be to decide if we just want to do Greg’s latest BIP that only targets Covert ASICboost usage, or do we want to disable All ASICBoost usage, like Peter Todd promotes. Surely there would be more support on the former but added advantages on the latter.</p><p>Every day we waste allowing the idea to flourish that Jihan did not commit these crimes to the community, we allow his following and SegWit resistance to grow stronger.</p><figure><a href="http://eepurl.com/bBbrFX"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*iq0EKuOUS52AtOW_RSKNxA.jpeg" /></a></figure><figure><a href="https://europe2017.eventbrite.com/?aff=mediumfooter"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*sg1PGrUIRQvIDH7bb2OY0A.jpeg" /></a></figure><figure><a href="http://startupgrind.com/chapters"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*N1UpkDFpA5UrRxen2NHxtw.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11c5c63d1b9f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/jihans-specific-sins-11c5c63d1b9f">Bitcoin’s Latest Scandal: How to Analyze the ASICBoost Mining Debate</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Bitcoin Unlimited should be correctly classified as an ‘attempted robbery’ of Bitcoin, not a…]]></title>
            <link>https://medium.com/@Coinosphere/why-bitcoin-unlimited-should-be-correctly-classified-as-an-attempted-robbery-of-bitcoin-not-a-9355d075763c?source=rss-61c943aa0227------2</link>
            <guid isPermaLink="false">https://medium.com/p/9355d075763c</guid>
            <category><![CDATA[bitcoin-mining]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[bitcoin-unlimited]]></category>
            <dc:creator><![CDATA[Luke Parker]]></dc:creator>
            <pubDate>Thu, 16 Mar 2017 00:58:30 GMT</pubDate>
            <atom:updated>2017-03-16T13:37:36.475Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Bitcoin Unlimited should be correctly classified as an ‘attempted robbery’ of Bitcoin, not a fork</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*amokD1twNrpVT6vuPpqx9g.jpeg" /><figcaption>Here we see a Bitcoin Unlimited Dev in his natural habitat</figcaption></figure><p>Looking into the history of open source project forks, I finally figured out (I can’t claim to be the first, but I haven’t seen others say it) that <strong>forks do not try to steal the names of their parents.</strong></p><p>Firefox is a fork of Mozilla which is a fork of Netscape. Why aren’t they all named Netscape? Because two are project forks.</p><p>Forks are new entities with new developers that start off with the same code as their parent, but then make the code their own. They do not say <em>“Give up control, we’re taking over.”</em> That is called theft.</p><p>Not applicable to Bitcoin Unlimited, you say? Bitcoin Core is compromised, you believe?</p><p>The open source CMS <a href="http://www.joomla.org/">Joomla!</a> is a fork of Mambo. In 2005-ish the employees and community at Mambo felt the company was controlled a bit too tightly by their primary investor, Miro. The entire core development team at Mambo (and the community) left to create Joomla! in a major walk-out together. Even with such ill feelings for their former employer, nobody stole anything worse than a red stapler from their former employer.</p><p>They just took some code.</p><p>I’ve looked at tons of forked projects to see if this holds true across the board… The torrents apps, the blogging platforms, chat apps, database platforms, all kinds of CMSs, and of course Linux. Some forks went on to be far better than their parents, others were complete crap and never heard from again. Still, they didn’t steal the sign on the way out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*9ZL3kTVpiTiMGI8A5yAHBw.png" /></figure><p>No project seems to have any history of the forkers stealing the forkee’s name nor property, no matter the circumstance. Yes, even when large amounts of funding were involved.</p><p>The history of Linux forks is an extremely large pool, too. Check out this chart to the left; those are all the linux distributions, pretty much up to date. (You may want to <a href="https://upload.wikimedia.org/wikipedia/commons/thumb/1/1b/Linux_Distribution_Timeline.svg/170px-Linux_Distribution_Timeline.svg.png">click here to see it in full resolution</a>.)Notice how they all have different names?</p><p>Look at how the lines connecting parents to forks… Not a one of them loops back to it’s parent.</p><p>Good example: <a href="https://en.wikipedia.org/wiki/Red_Hat_Linux">Red Hat linux</a> was a corporation, which was profitable most of its 19 years of existence. Fedora was its fork, and again, didn’t try to steal the assets of Red Hat. Eventually the corp went out of business and Red Hat’s code was merged into Fedora. Classy way to go out, that.</p><p>Plenty of these projects felt that their parent “sold out” or “lost its way,” just like those who have lost their faith in Bitcoin’s core developers today. Did they impersonate them?</p><p>There is simply no precedence for a fork stealing it’s parents name. When they steal the parent’s marketshare or customer base, it is because they, as separate entities, out perform their parents, <em>not pretend to be them</em>.</p><p>There is no precedence for this attitude anywhere in the world of open source development that I can find.</p><p>Interestingly, Bitcoin already has tons of precedence for being forked properly itself. Since bitcoin is a currency, forking bitcoin creates altcoins.</p><p>Litecoin and namecoin were early Bitcoin forks, and like every other fork in history, they have their own development teams and grabbed a new name.</p><p>Satoshi’s code may allow a way for majority hashrate to steal the project away from one dev team and put it in the hands of others, but that is a ‘might makes right’ argument; it doesn’t make it ethical to take a whole project away from its developers, and it certainly doesn’t mean they get to steal the name too.</p><p><a href="https://www.bitcoinunlimited.info/">Some coders</a> and <a href="http://rogerver.com/">Bitcoin millionaires</a> believe this time-honored system to be not good enough for them. They want more than the next dash or dogecoin.</p><p>They see Bitcoin’s massive market cap and frontrunner status as the things they want to fork, not some code. This is immoral and against the <a href="https://wiki.mises.org/wiki/Principle_of_non-aggression">Non Aggression Principle</a>, to which many Bitcoiners and Bitcoin millionaires subscribe.</p><p>To Bitcoin Unlimited, and all future attempts to steal Bitcoin’s identity and assets: Do the right thing and just fork off.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9355d075763c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>