<?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 Storecoin Team on Medium]]></title>
        <description><![CDATA[Stories by Storecoin Team on Medium]]></description>
        <link>https://medium.com/@storecoin?source=rss-6e2927e20087------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FOkDpXzFGzRO--FA5rE19g.png</url>
            <title>Stories by Storecoin Team on Medium</title>
            <link>https://medium.com/@storecoin?source=rss-6e2927e20087------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 21:54:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@storecoin/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[BlockFin: Proof-of-Stake Protocol with Security that Rivals Proof-of-Work]]></title>
            <link>https://medium.com/@storecoin/blockfin-proof-of-stake-protocol-with-security-that-rivals-proof-of-work-728cb9f85113?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/728cb9f85113</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Wed, 09 Jan 2019 21:51:04 GMT</pubDate>
            <atom:updated>2019-01-09T21:51:04.944Z</atom:updated>
            <content:encoded><![CDATA[<p>The Proof-of-Work (PoW) algorithm was the first consensus protocol to power public blockchains. As a result, proponents of PoW-based blockchains claim they are more secure than Proof-of-Stake-based (PoS) blockchains. BlockFin, Storecoin’s PoS consensus algorithm, provides security that rivals traditional PoW blockchains.</p><h3>Introduction</h3><p><strong>Security is the most important attribute of any public blockchain</strong>. Central to a blockchain’s security protocol is its consensus algorithm, because it can be a known security vulnerability as well as the first line of defense in an attack. Because PoW is the oldest and best understood consensus algorithm, proponents of PoW have argued that PoS-based blockchains are less secure.</p><p>Hugo Nguyen, a developer for the Litecoin blockchain, a network using a PoW consensus protocol, writes in <a href="https://medium.com/@hugonguyen/proof-of-stake-the-wrong-engineering-mindset-15e641ab65a2">part 1</a> of a two-part blog post that securing against worst-case scenarios is “an absolute must when dealing with critical systems,” whether they are responsible for operating an airplane, spaceship, nuclear power plant or cryptocurrency network.</p><p>Nguyen argues that the better-known and tested PoW-based blockchain has built a reputation for resiliency that PoW-based blockchains do not have.</p><h3>Jameson Lopp on Twitter</h3><p>In high stakes adversarial environments you must defend against the impossible because the impossible will happen. H/T @hugohanoi https://t.co/2vB2Z8lYdo</p><p>At Storecoin, we believe that just because no PoS consensus algorithm has proven itself comparable (or superior) to PoW doesn’t mean it can’t happen.</p><h3>Chris McCoy on Twitter</h3><p>@hugohanoi Good points for leader-based PoS systems. On security, every protocol needs its own version of Fort Knox for private keys, code bases, device, and personal security. At @storecoin, we&#39;re working close w/partners including the Amazon blockchain strategy group for our Fort Knox.</p><p><strong>BlockFin, Storecoin’s PoS consensus algorithm, has comparable security characteristics to a PoW-based blockchain</strong>. In this post, we explain how BlockFin running a PoS consensus algorithm addresses the types of worst-case scenarios and attacks introduced in Nguyen’s post.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*yA8gxq3a8VyxWvmzlJgApA.jpeg" /><figcaption>When The Challenger space shuttle exploded during launch in 1986, NASA engineers believed the odds of such a disaster were 1 in 100,000. An investigation showed a flaw in a small part called an “o ring” that lowered such odds to roughly 1 in 100, a deadly miscalculation. Nguyen argues, and we agree, that blockchain engineers must be able to predict any number of catastrophic events and create protocols to avoid or recover from them.</figcaption></figure><h4>PoS vs. PoW</h4><p>PoS is a category of consensus algorithms for public blockchains that depends on a validator’s economic stake in the network. With public blockchains using PoW consensus, the algorithm rewards participants that solve complex cryptographic puzzles to validate transactions and create new blocks. In contrast, in PoS-based blockchains, a set of validators propose and vote on the next block as defined in the underlying protocol.</p><p>Nguyen argues in part 1 of his post that<strong> </strong>PoS-based systems are less resilient in dealing with worst-case scenarios<strong>.</strong> He concludes:</p><ol><li><strong>PoW protects the future:</strong> When there’s a chain split, it gives an objective mechanism, automatable way of resolving conflicts, without requiring manual human intervention or trusted third parties.</li><li><strong>PoW protects the past</strong>: Getting control of majority hash rate still costs an attacker an enormous amount of time and money to rewrite history, so the balances are somewhat safe.</li></ol><p>In<a href="https://medium.com/@hugonguyen/proof-of-stake-private-keys-attacks-and-unforgeable-costliness-the-unsung-hero-5caca70b01cb"> part 2</a> of the post, the author describes a property he argues is unique to PoW: resiliency to old private key attacks. We believe such characteristics apply to networks running PoS consensus algorithms as well.</p><h3>BlockFin Summary</h3><p><strong>BlockFin subscribes to the ‘<em>correct by design’</em> philosophy. It sacrifices <em>throughput</em> and in some catastrophic events, <em>liveness,</em> to guarantee <em>correctness</em></strong>. The Storecoin blockchain, under no circumstances, will be in a indeterministic state.</p><p>Throughput is defined here as the number of transactions processed by a blockchain network per second. Liveness refers to a set of properties of concurrent systems that requires a system to make progress despite the fact that it is currently executing components or processes that may have to “take turns” in critical sections, A liveness guarantee is an important property in distributed systems.</p><p><strong>BlockFin is Storecoin’s PoS BFT consensus protocol. It differs from other PoS protocols in the following ways:</strong></p><ul><li><strong>Leaderless consensus</strong> — Consensus is not leader or delegation-led. All validators are required to participate in the consensus process and approve transactions in blocks using a pipelined, multi-stage validation workflow.</li><li><strong>Fork tolerance</strong> — The protocol permits chain forks natively with a strong guarantee to disallow double-spend attacks. This permits parallel block creation without requiring sharding and other complex approaches, thus dramatically improving consensus throughput.</li><li><strong>Shared state machine replication</strong> — Fork-tolerance is achieved through a collaborative block assembly process whereby all (online) validators come together to build and validate new blocks using shared state machine replication. This is in contrast to the “<em>create the block in the local node privately and publish it to the blockchain</em>” approach in both PoW- and PoS-based blockchains.</li><li><strong>Community-based reward sharing</strong> — All validators earn rewards proportional to their stakes for the blocks they produce. This is in contrast to other PoS protocols where the leader/delegates earn all the rewards. We believe that economics leading to competition leads to centralization, encouraging malicious behaviors</li><li><strong>True decentralization</strong> — Since <em>all</em> validators participate in consensus for <em>all</em> blocks, the network is truly decentralized. The sharing of rewards community-wide discussed earlier encourages maximum up-time and participation. A network with a large number of online participants resists worst-case scenarios and attacks better than a network with fewer large participants.</li><li><strong>Dynamic threat levels</strong> — BlockFin incorporates a dynamic threat-level system that identifies the type of attack (spam, DDoS, private key hijacking, etc.) and responds accordingly, at the protocol level.</li></ul><h3>Worst-case scenarios and attacks</h3><p>In this sections, we describe how BlockFin addresses each of the worst-case scenarios and attacks described in Nguyen’s blog post.</p><h4>Scenario 1: The entire network is forced offline for some period, then rebooted.</h4><p>In this scenario, the entire network is forced offline as happened during the Arab Spring movement, when the Turkish government successfully performed<a href="https://bgpmon.net/turkey-hijacking-ip-addresses-for-popular-global-dns-providers"> BGP hijacking</a> to block Twitter traffic from Turkish citizens. Nodes come back online at different times based on their recovery rate. In this scenario, the question is with PoS, will the nodes automatically self-organize, eventually gravitating towards one single chain, the longest chain, and the most secure, or some other chain”</p><p><strong>BlockFin’s <em>shared state machine replication</em> allows for nodes to self-organize, eventually gravitating toward a single chain.</strong> When nodes come back online at different times, they start receiving transactions immediately but will not start building blocks until at least one node is part of the <em>shared state machine</em>.</p><p>As nodes from the <em>shared state machine</em> group come online, they sync with existing nodes, replicating the block data among them. The following behaviors can be observed.</p><ol><li>The validator nodes never produce <em>private</em> chains — they only produce blocks on the main blockchain. If all the nodes forming the <em>shared state machine</em> are forced offline, no blocks will be created. In this catastrophic situation, <em>liveness</em> is sacrificed for <em>correctness</em>.</li><li>The transaction approval throughput initially will be low after being forced offline. As more nodes come online, throughput improves.</li><li>The nodes don’t misbehave (except for Byzantine behavior, which the protocol is designed to handle) and never create a subchain that requires <em>repair</em>.</li></ol><p>What happens in the event that all the nodes forming a shared state machine are forced offline and come back online at different times? As the nodes come back online, how they self-organize and eventually gravitate toward one single chain depends on which node came online first and started producing new blocks.</p><p>In a PoW consensus protocol, some transactions may be lost if they are added to a shorter chain. Additionally, as nodes come back online, those transactions that were approved and added to a chain while the node in question was offline, may also be lost. While nodes will <em>eventually gravitate toward one single chain,</em> PoW offers no guarantee that previously approved transactions will remain so after being forced offline. This is because a peer-to-peer network is <em>eventually consistent</em>.</p><p>We can draw parallels between the behaviors between the <em>shared state machine</em> nodes and PoW nodes. Depending on which of the <em>shared state machine</em> nodes come online first, the block validation process continues accordingly. Regardless of which nodes come online first, the results are the same. The network will still <em>gravitate toward one single chain</em>.</p><h4>Scenario 2: Some portions of the network are partitioned from the main network.</h4><p>This is a special case of scenario 1 where certain nodes are partitioned from the main network. In this case, if the partitioned network doesn’t contain any nodes from the <em>shared state machine</em> group, the network doesn’t participate in the block assembly and validation process.</p><p>At some point, the nodes in the partitioned BlockFin network start rejecting incoming transactions, since they cannot process them anymore. For the larger network this looks like a Byzantine fault. If the partitioned network is large enough (greater than ⅓ of total nodes), the block assembly and validation process will halt momentarily triggering <em>dynamic threat-level</em> logic<strong>, </strong>rebalancing the BlockFin network by excluding the nodes in the partitioned network. After rebalancing, the block assembly and validation process continues unabated.</p><p>It should be observed that subchains are not created and the main blockchain is in no way affected. As the partitioned BlockFin network stabilizes (nodes from <em>shared state machine</em> group are up and synchronized to their peers, etc.) they rejoin the larger network and the block assembly and validation process is restored to its original capacity.</p><h4>Scenario 3: “PoS fares worse in other worst-case scenarios, such as stolen private keys.”</h4><p>Nguyen makes the claim that PoS fares poorly when attackers gain access to the private keys of old validator nodes, using them to get sufficient <em>majority</em> to perform malicious acts.</p><p>BlockFin, a PoS blockchain will respond in the following ways:</p><ol><li>The block validation process in BlockFin involves a <em>sealing phase</em>, creating checkpoints of committed blocks. The sealing process is <em>decentralized</em>, because validators will seal and sign the blocks, just like in the block validation process. All <em>write</em> operations on the sealed block are rejected. A malicious node cannot override this behavior because of the <em>shared state machine replication </em>used in BlockFin. All the nodes in the <em>shared state machine</em> group must be compromised to mount such an attack. As a result, long-range attacks like a history rewrite attack and other similar types of attacks are not feasible in BlockFin. Additionally, any attempt to write to the sealed blocks will be noticed by honest validators who will initiate protocol-defined punitive measures such as slashing.</li><li>All validators must meet KYC/AML (know-your-customer/anti-money-laundering) and minimum staking requirements in BlockFin. Once a validator decides to retire or move out of the network, their private keys are no longer useful in the block assembly and validation process. If a malicious node uses stolen private keys to sign the blocks, it will be noticed by other honest validators since the private keys are not longer showing as valid within the network.</li></ol><p>To summarize:</p><ol><li><em>BlockFin protects the future</em>: Catastrophic events such as being forced offline will not result in chain forks because by design, BlockFin is fork-tolerant. Throughput may suffer for the duration of the catastrophic event, but the blockchain will gravitate towards a steady state. In attacks such as the one where malicious actors obtain retired private keys, the attack will not succeed because the network will recognize that the keys trying to be used by the malicious actor have previously, been retired.</li><li><em>BlockFin protects the past</em>: Getting control of the majority of nodes by buying or stealing old private keys will not work in BlockFin because sealed blocks cannot be modified. Additionally, the status of retired or stolen private keys will be immediately recognized by the network and shut down.</li></ol><h4>Scenario 4: New and long dormant nodes</h4><p>In the fourth scenario, a new node joins the network or a node that was previously offline for a long time comes back online. The question becomes who this node should <em>trust.</em> In BlockFin, the answer is straightforward. Since the validator nodes use <em>shared state machine replication</em>, the new or long dormant node simply needs to connect to one of the nodes in the <em>shared state machine</em> group to get up and running <em>instantly</em>. <strong>The new or dormant node needs to trust the network itself and not individual nodes.</strong></p><h4>Scenario 5: Current private key attack</h4><p>In the fifth scenario, the private keys of more than ⅓ nodes are compromised. In other words, a Byzantine fault occurred resulting in a <em>stalled</em> network. BlockFin’s dynamic threat detection reconfigures the blockchain by excluding the affected validators from the block assembly and validation process, ensuring <em>liveliness. </em><strong>The network recognizes the stolen private keys as the result of an offline <em>governance</em> process.</strong></p><h3>Conclusion</h3><p>Security is a critical ingredient for any blockchain project. BlockFin’s ‘<em>correct by design’</em> philosophy enables it to address some of the shortcomings found on public blockchains running traditional proof-of-stake consensus algorithms.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=728cb9f85113" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Closer Look at BlockFin and Finality]]></title>
            <link>https://medium.com/@storecoin/a-closer-look-at-blockfin-and-finality-b7561a3980be?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7561a3980be</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Tue, 04 Sep 2018 21:31:10 GMT</pubDate>
            <atom:updated>2018-09-04T21:31:10.271Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>In Storecoin, </strong>BlockFin’s finality is a combination of absolute and probabilistic finalities. Once more than 2/3 of validators validate and sign the block containing the transactions, the block has <em>absolute finality,</em> hence the transactions included the blocks also have absolute finality. There is no need to wait for a predefined number of block confirmations as in Nakamoto consensus. However, BlockFin uses an <em>asynchronous</em> consensus algorithm and by definition, it doesn’t make any timing assumptions. So, as the number of signatures reaches the threshhold of &gt; 2/3 of the total number of validators, the probability of finality reaches 1.</p><h3>StorecoinDev on Twitter</h3><p>1/ &quot;Finality in Blockchain Consensus&quot; -- https://t.co/KGbiCmqqpD -- discusses 3 finality types. 1) Probabilistic Finality, 2) Absolute Finality, and 3) Economic Finality.</p><h3>StorecoinDev on Twitter</h3><p>2/ Depending on the underlying consensus algorithm, blockchain fall into one or more of these types. For example, Bitcoin has &quot;probabilistic finality&quot; because the recipient must for certain number of block confirmations before accepting the payment.</p><h3>StorecoinDev on Twitter</h3><p>3/ &quot;Finality&quot; implies irreversibility of the transactions. In real world cases the transactions are always reversible. For example, a fraudulent charge on a credit card is always reversible.</p><h3>StorecoinDev on Twitter</h3><p>4/ So, &quot;absolute finality&quot; in blockchains is its ability to resist illegal reversal of transactions. This is because any legal reversal would work just like in real world cases -- a *new* transaction that reverses the effect of *old* transaction.</p><h3>StorecoinDev on Twitter</h3><p>5/ Transaction finality with BlockFin, @storecoin&#39;s BFT consensus algorithm is a bit of all the 3 types of finalities. The transactions have &quot;absolute finality&quot; because once more than 2/3 of the validators validate and commit the block, the block and</p><h3>StorecoinDev on Twitter</h3><p>5.a/ hence the transactions included in the committed block are irreversible. There is no need to wait for certain number of block confirmations or any such thing.</p><h3>StorecoinDev on Twitter</h3><p>6/ BlockFin consensus algorithm is asynchronous in nature. By definition, it doesn&#39;t make any timing assumptions. This means, there is no fixed window of time in which all the validators sign and commit the blocks.</p><h3>StorecoinDev on Twitter</h3><p>7/ This makes the finality &quot;probabilistic&quot; (although not by the definition used in the above article). As the validators commit the block with their signatures, the finality reaches the probability of 1.</p><h3>StorecoinDev on Twitter</h3><p>8/ While the incentive model encourages validator up-time and in practice, the probability of 1 is reached in a predictable window of time, in theory, the algorithm results in &quot;probabilistic finality&quot;.</p><h3>StorecoinDev on Twitter</h3><p>9/ Finally, BlockFin institutes punishment for misbehaving nodes, like in most PoS-based systems. So, the cost of reversing the block (and hence transactions) is economically expensive.</p><h3>StorecoinDev on Twitter</h3><p>10/ Such reversals require more than 2/3 of *current* validators to collude. This makes BlockFin&#39;s finality also an &quot;economic finality&quot;.</p><h3>StorecoinDev on Twitter</h3><p>11/ These qualifications should be examined in their own contexts. Absolute finality is critical for merchants because once they learn that a block is committed, they don&#39;t need to wait any longer to accept the payments.</p><h3>StorecoinDev on Twitter</h3><p>12/ Probabilistic finality is the side effect of asynchronous nature of block finalization process. A synchronous network is impractical because of strict timing assumptions. So, while such algorithms &quot;terminate&quot; on paper, they rarely do so in practice.</p><h3>StorecoinDev on Twitter</h3><p>13/ Economic finality should be viewed in the context of the security of the network. It demonstrates the cost to mount any malicious acts to reverse a block.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7561a3980be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The History of Storecoin]]></title>
            <link>https://medium.com/@storecoin/the-history-of-storecoin-a3bf5ee4258c?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3bf5ee4258c</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Wed, 29 Aug 2018 20:51:46 GMT</pubDate>
            <atom:updated>2018-08-29T20:51:46.660Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Storecoin Creator Chris McCoy</em></p><p>I started out with a plan to create a chat network for franchise and chain stores. It has grown into an ambitious project to create a fee-free, decentralized, high-throughput p2p payments infrastructure for the internet.</p><p>Here’s how it evolved:</p><h3>Chris McCoy on Twitter</h3><p>@mdudas @nic__carter @StartupLJackson Back in 13/14, I was convinced BTC would be used as an in-app, censorship resistant, API-driven new currency. I even tried to build a complex, API-based payment network for it. It didn&#39;t work. Finally, accepted Bitcoin&#39;s limitations as &quot;p2p e-cash&quot;. Then met Vitalik/Anthony/EF.</p><p>Skeptical about how you could “print new money” on top of new, speculative money, I was a contrarian on the issue. Most of my SV “platform” friends loved it.</p><p>Instead of building on Ethereum, I took a bet and put some BTC into the pre-sale, then left the crypto space (out of frustration with Bitcoin). But I jumped back in when I realized zero-fee, in-app, API-based, and censorship-resistant payments still was a problem needing a solution.</p><p>At the time, was building a new company: headquarter-to-location chat for franchise and chain stores. I saw two things:</p><ol><li>Stores hated the 2.5%-3.5% transaction fee from traditional payment rails</li><li>The 4% fee that locations pay HQ as part of the franchise agreement could be a smart contract (that’s 4% of <em>every single transaction</em> at the cash register)</li></ol><p>I studied the Ethereum dApp ecosystem, but realized that “gas” was an economic primitive for gamified banks — not a world computer. Bitcoin was on its way to becoming joule-backed digital gold.</p><p>As I went deeper into research, it was clear “the smart contract wars” were about to start. I still didn’t buy into new money being created on top of new, speculative money. And there were no plausible zero-fee models for the merchant (or app developer).</p><p>After coming out of a 3-month research cave, I realized that inflationary rewards could incentivize a p2p consensus to not only validate transactions but to secure, govern, and scale them as well. Along the way, we spun out <a href="http://twitter.com/storecoin">@storecoin</a> as a new blockchain for franchise and chain stores.</p><p>But as our research evolved, my business partner Rag Bhagavatha and I realized that we were solving a much larger problem than zero-fee payments for the franchise and chain store vertical. We were building zero-fee, p2p, highly programmable payments infrastructure for the centralized internet (apps not dApps).</p><p>We’re making progress 24/7 with a team spread around the world. It’s still early but we’re shipping on the technology, security, community, treasury management, legal, and ecosystem fronts daily.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3bf5ee4258c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Storecoin Pioneers Lining Up to Host Meet-Ups in Cities Around the World]]></title>
            <link>https://medium.com/@storecoin/storecoin-pioneers-lining-up-to-host-meet-ups-in-cities-around-the-world-b59113320bca?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/b59113320bca</guid>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 23:08:57 GMT</pubDate>
            <atom:updated>2018-08-13T23:08:57.673Z</atom:updated>
            <content:encoded><![CDATA[<h3>Storecoin [$STORE] on Twitter</h3><p>1/ The 64 Cities Across 39 Countries that $STORE Community Members want to host @Storecoin Meet-ups - Alicante, Spain - Amersfoort, Netherlands - Amsterdam, Netherlands - Rotterdam, Netherlands - Astana, Kazakhstan - Baku, Azerbaijan - Bangalore, India - Beijing, China</p><h3>Storecoin [$STORE] on Twitter</h3><p>2/ - Boston, MA (USA) - Brussels, Belgium - Bucharest, Romania - Buenos Aires, Argentina - Busan, Korea - Cambridge, MA (USA) - Chicago, IL (USA) - Clearwater, FL (USA) - Copenhagen, Sweden - Dubai, United Arab Emirates - Dublin, Ireland - Edmonton, Canada - Hong Kong</p><h3>Storecoin [$STORE] on Twitter</h3><p>3/ - Houston, TX (USA) - Irvine, CA (USA) - Islamabad, Pakistan - Istanbul, Turkey - Izmir, Turkey - Jakarta, Indonesia - Kyiv, Ukraine - Las Vegas, NV (USA) - London, UK - Malta - Manila, Philippines - Melbourne, Australia - Milan, Italy - Minsk, Belarus - Moscow, Russia</p><h3>Storecoin [$STORE] on Twitter</h3><p>4/ - Mumbai, India - Nauru, Oceania - New Delhi, India - New York, NY (US) - North New Jersey, NH (USA) - Orlando, FL (USA) - Paris, France - Philadelphia, PA (USA) - Phoenix, AZ (USA) - Raleigh, NC (USA) - Riga, Latvia - Saint Petersburg, Russia - San Diego, CA (USA)</p><h3>Storecoin [$STORE] on Twitter</h3><p>5/ - San Francisco, CA (USA) - San Jose, CA (USA) - San Jose, Costa Rica - Shanghai, China - Sofia, Bulgaria - Split, Croatia - Stockholm, Sweden - Sydney, Austrailia - Taiwan - The Hague, Netherlands - Toronto, CA - Utrecht, Netherlands - Valencia, Spain - Vancouver, Canada</p><h3>Storecoin [$STORE] on Twitter</h3><p>6/ - Washington DC (USA) - Wiesbaden, Germany</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b59113320bca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yes, We Counted! 40 Ways Our Community Learned about Storecoin]]></title>
            <link>https://medium.com/@storecoin/yes-we-counted-40-ways-our-community-learned-about-storecoin-447dc76efe8c?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/447dc76efe8c</guid>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 23:02:22 GMT</pubDate>
            <atom:updated>2018-08-13T23:02:22.408Z</atom:updated>
            <content:encoded><![CDATA[<h3>Storecoin [$STORE] on Twitter</h3><p>1/ The 40 Ways Our Community Has Learned about @Storecoin: - @Curt_Shilling on Twitter - @Cyrptotherappy on Twitter - @JerominoMCrypto on Twitter - @M_Povolotski on Twitter - @Pomp on Twitter - @chrisamccoy on Twitter - A Crypto Event In Stockholm, Sweden - A Footprint Investor</p><h3>Storecoin [$STORE] on Twitter</h3><p>2/ - A Friend DM&#39;d me on Twitter - A Friend invited me on Telegram - A Friend Shared a Link - A Friend told me in person - A User told me in Discord - Added on Telegram - At &#39;To The Moon Bockchain Event&#39; - Bitcoin Bravado Discord Group - https://t.co/QiTdsJnWXu article</p><h3>Storecoin [$STORE] on Twitter</h3><p>3/ - Chris McCoy by Email - Chris McCoy on Telegram - Coin Crunch Discord - Coin Crunch YouTube Review - Comment On Reddit - Cryptodiffer - Donna Capodelupo in Person - Found It In A &quot;Blockchains Built From Scratch&quot; Google Table: https://t.co/6HROfdZiEv - Github - Google Search</p><h3>Storecoin [$STORE] on Twitter</h3><p>4/ - ICO Drops - Jff ICO Group on Telegram - Money Master Mind Group - Monoico Telegram Group - My Brother - My Dad - My Friends - Online Community Members - Open Token - My Partner - Private Crypto Group - Self Research About Storecoin - Social Media - Some Guy On Twitter #💰</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=447dc76efe8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nathaniel Whittemore’s Comprehensive View of the Past Week in Cryptocurrency]]></title>
            <link>https://medium.com/@storecoin/nathaniel-whittemores-comprehensive-view-of-the-past-week-in-cryptocurrency-11eec2d82801?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/11eec2d82801</guid>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 15:50:19 GMT</pubDate>
            <atom:updated>2018-08-13T15:50:19.348Z</atom:updated>
            <content:encoded><![CDATA[<h3>Nathaniel Whittemore on Twitter</h3><p>1/ Long Reads Sunday #7. Remember how last week we were hovering above BTC @ $8k and talking about what market narratives will drive the next bull run? Oops. Luckily, bear markets are for big ideas and building. Thread 👇</p><h3>Nathaniel Whittemore on Twitter</h3><p>2/ From a market price perspective, this week has been a brutal. With BTC circling around the low-mid $6k range, we&#39;re now asking &quot;why the selloff?&quot; @brucefenton argued it&#39;s *not* about the SEC delaying a much anticipated ETF decision https://t.co/ouwUNgp0w2</p><h3>Nathaniel Whittemore on Twitter</h3><p>3/ Speaking of ETFs, @Crypto_Macro wrote this fantastic overview of the Bitcoin ETF process and implications. It&#39;s the best single source I&#39;ve seen to get the background on this financial instrument which so many are looking to to expand the crypto markets https://t.co/3fy1kyrvRn</p><h3>Nathaniel Whittemore on Twitter</h3><p>4/ Brad captured a phenomenon quietly (or perhaps not so quietly) shaping the market, which is the addt&#39;l pain caused by the concentration of ICO war chests on ETH. In short, w/ ETH at ~20% of its ATH, projects are panic selling as their resources dwindle. https://t.co/dkBCMLLIoD</p><h3>Nathaniel Whittemore on Twitter</h3><p>5/ Fred Wilson wonders if we&#39;re finally seeing the end of &quot;HODL&quot; and the beginning of capitulation. He argues that getting capital resources freed up and back into the market would actually be long term beneficial https://t.co/1X8iA3FFvq</p><h3>Nathaniel Whittemore on Twitter</h3><p>6/ Whatever the case, it&#39;s undeniable that what optimism exists focus on the institutional capital circling on the sidelines. @DavidJN79 suggests that institutional interest is as much about what&#39;s going on outside crypto than inside https://t.co/OQsBEPbtZi</p><h3>Nathaniel Whittemore on Twitter</h3><p>7/ @burniske provided some comparative historical context about downturns, and articulated a perspective that I share that for all the pain they cause, bear markets are good times for building https://t.co/7HYnf2HUTK</p><h3>Nathaniel Whittemore on Twitter</h3><p>8/ With that in mind, check out this announcement from @AragonProject about the Aragon DAC, a &quot;decentralized altruistic community.&quot; If we&#39;re actually going to experiment with non firm models of organizing, we need these sort of examples https://t.co/uDTT9NkQ3b</p><h3>Nathaniel Whittemore on Twitter</h3><p>9/ Of course, it&#39;s not like cryptos are the only currencies in the toilet. With the Turkish Lira tanking, Nic asked this choice question: https://t.co/yUU0Zj6CUz</p><h3>Nathaniel Whittemore on Twitter</h3><p>10/ Situations like Turkey &amp;amp; Venezuela are part of why many are so focused on the creation of a global digital money and find the Dapp conversation distracting. @stephanlivera&#39;s podcast with @MustStopMurad is a masterclass in this perspective https://t.co/xmA9ZK6yLM</p><h3>Nathaniel Whittemore on Twitter</h3><p>11/ In &quot;Money Crypto vs. Tech Crypto&quot; @eriktorenberg articulates the differences b/n two perspectives in the crypto community in order to make it easier for us to understand where they&#39;re in competition vs. where they just care about different things. https://t.co/gOMcNluiMJ</p><h3>Nathaniel Whittemore on Twitter</h3><p>12/ This intellectual division is clearly on people&#39;s minds right now. @BenDiFrancesco wrote a similar piece, labeling one side &quot;Sound Money&quot; and the other &quot;World Computer.&quot; https://t.co/YMYjcrMUxi</p><h3>Nathaniel Whittemore on Twitter</h3><p>13/ This thread from @DFINITY&#39;s @dominic_w captures the passion on the tech crypto/world computer side of the coin. The internet started open, swung towards network effect-driven monopoly, and now needs to swing back towards decentralization. https://t.co/jp39bP99Md</p><h3>Nathaniel Whittemore on Twitter</h3><p>14/ In &quot;Evangelizing Bitcoin,&quot; @hasufly eloquently makes the point that the money crypto/sound money crowd should be making the Bitcoin tent large and about the big point: &quot;monetary freedom for everyone.&quot; https://t.co/BFB3zVb8Oa</p><h3>Nathaniel Whittemore on Twitter</h3><p>15/ These sorts of conversations are one of the benefits of a less congested market. We have space for discourse about what we actually want to build. In that spirit, I wrote an essay for @21Cryptos about alternatives to accredited investor rules https://t.co/xthyxOkGr3</p><h3>Nathaniel Whittemore on Twitter</h3><p>16/ Vitalik clarified his position and simultaneously affirmed that the old adage that a picture is worth a thousand words (Good luck unseeing that, btw). https://t.co/W32ckZ4bEe</p><h3>Nathaniel Whittemore on Twitter</h3><p>17/ @coinfund_ai wrote a great follow up thread. Money line: &quot;the goal here is not to protect the individual from losses. It is to reduce the loss-likelihood of the entire market.&quot; https://t.co/Potmsv4M10</p><h3>Nathaniel Whittemore on Twitter</h3><p>18/ In the context of crypto networks, with their new ways of capturing and distributing value, the role of investors is going to evolve. @jbrukh has written about this recently, and @pjkershawnz captures many of these ideas in this great thread: https://t.co/hxLZuYvXXD</p><h3>Nathaniel Whittemore on Twitter</h3><p>19/ One of the most interesting questions for investors is where value will accrue in the context of protocols, and whether an MOE-first or SOV-first coin will ultimately become a digital reserve currency. @KyleSamani adds some great thinking to that here: https://t.co/YRKy2pRXB4</p><h3>Nathaniel Whittemore on Twitter</h3><p>20/ If there&#39;s not enough big thinking in the links above to keep you busy, here are a few more choice pieces.</p><h3>Nathaniel Whittemore on Twitter</h3><p>21/ One of the most important/misunderstood concepts in crypto is blockchain interoperability. As we let thousands of flowers bloom, will they be stuck in their own walled gardens or free to interact? Choice thread kicked off by Meltem: https://t.co/sWE68loJKd</p><h3>Nathaniel Whittemore on Twitter</h3><p>22/ @maxrogo notes the significance of the Bitmain IPO with historical analogy to Levis - noting both the impressiveness of the company&#39;s achievements while also wondering what it will take to stay ahead. https://t.co/Kj35WGQzeV</p><h3>Nathaniel Whittemore on Twitter</h3><p>23/ With characteristic precision, @timevalueofbtc published this look at the concept of &quot;layered money&quot; as a way to explain Lightning in the context of the larger Bitcoin ecosystem. https://t.co/IwlC62IJK6 This thread briefly sums up his recent writing: https://t.co/LRWS05cU3U</p><h3>Nathaniel Whittemore on Twitter</h3><p>24/ From the &quot;sick burn&quot; files come: + @CantHardyWait&#39;s tête-à-tête with Krugman&#39;s latest boring anti-bitcoin piece + @nic__carter&#39;s vicious WaPo rebuttal: https://t.co/264S4P5RkP</p><h3>Nathaniel Whittemore on Twitter</h3><p>25/ For those keeping track of ICE and the Wall Street entrance into crypto, @CaitlinLong_ published part 3 of 3 of her series on @ForbesCrypto. Key line: &quot;ICE&#39;s entry into cryptocurrencies changes the conversation about how Wall Street really works&quot; https://t.co/M6Ec2hKpZ8</p><h3>Nathaniel Whittemore on Twitter</h3><p>26/ If you&#39;re interested in industries that actually need blockchains, check out this piece from @Fantasmo about the importance of blockchain for 3D data and geospatial applications. https://t.co/g0ZmND1BXU</p><h3>Nathaniel Whittemore on Twitter</h3><p>27/ @max_bronstein published this ecosystem primer on Token Economy that is essential reading especially for new people entering the space. https://t.co/u3F1dhVi22</p><h3>Nathaniel Whittemore on Twitter</h3><p>28/ Finally, here&#39;s a provocative little gem. People are noticing and wondering about the seemingly significant recent shift among fund managers away from the &quot;Fat Protocol&quot; thesis. What do you think? Is it it a real phenomena or overblown?</p><h3>Nathaniel Whittemore on Twitter</h3><p>29/ And with that, we wrap. What else was great this week? What did I miss?</p><h3>Nathaniel Whittemore on Twitter</h3><p>One more: this is a conversation I&#39;m tracking closely and will be writing about in the coming week or so: https://t.co/njBkU7Syii</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11eec2d82801" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Storecoin Addresses “Rich Get Gradually Richer” Concern with its Leaderless Protocol and…]]></title>
            <link>https://medium.com/@storecoin/storecoin-addresses-rich-get-gradually-richer-concern-with-its-leaderless-protocol-and-a97609061635?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/a97609061635</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 20:00:13 GMT</pubDate>
            <atom:updated>2018-07-31T20:00:13.089Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Storecoin Addresses “Rich Get Gradually Richer” Concern with its Leaderless Protocol and Decentralized Economics</strong></h3><p>A blog post on <a href="https://cointelegraph.com/news/the-inevitable-failure-of-proof-of-stake-blockchains-and-why-a-new-algorithm-is-needed">cointelegraph.com</a> contends Proof of Stake blockchains create a “rich get richer” scenario for participants on the network. But <a href="http://storeco.in/">Storecoin</a>’s Chief Technology Officer Rag Bhagavatha argues Proof of Stake itself is not to blame.</p><p>Instead, it is the leader-based block production design used by Proof of Stake <em>and </em>Proof of Work protocols that creates a “winner take all” environment, skewing toward miners or stakers who have available resources to invest to try to “beat the system.”</p><p>BlockFin, Storecoin’s leaderless consensus algorithm with a decentralized economic model for block rewards, offers a more democratic process in which all validators have a chance to share the rewards of block production.</p><p>Bhagavatha shared this series of tweets recently to make his point:</p><h3>StorecoinDev on Twitter</h3><p>1/ &quot;In Proof-of-stake, the rich get gradually richer&quot; says this blog post -- https://t.co/pA0wJc3RnW</p><h3>StorecoinDev on Twitter</h3><p>2/ This argument is partially correct and partially flawed. It is actually not a problem with Proof-of-Stake (PoS) itself, but because PoS is modeled after Proof-of-Work (PoW).</p><h3>StorecoinDev on Twitter</h3><p>3/ In PoW, one miner emerges as the winner of solving the cryptographic puzzle and the winning miner gets to add the new block to the blockchain and win the resulting block reward.</p><h3>StorecoinDev on Twitter</h3><p>4/ In other words, the winning miner was the *elected leader* to produce the new block. The election was *random* because of the nature of the underlying cryptographic puzzle.</p><h3>StorecoinDev on Twitter</h3><p>5/ First generation PoS algorithms mimicked this model. But instead of solving an energy-intensive cryptographic puzzle, the PoS algorithms opted for some type of *randomization* to elect the leader to produce the next block.</p><h3>StorecoinDev on Twitter</h3><p>6/ To secure the network against attacks such 51% attack, Sybil attack, etc., a &quot;stake&quot; or &quot;deposit&quot; is mandated, so the offender can be punished with slashing or burning the deposit for any malicious acts by the offender.</p><h3>StorecoinDev on Twitter</h3><p>7/ In PoW this is not necessary because solving cryptographic puzzle itself is very energy-intensive, so a malicious actor would pay the *price* first before committing the crime.</p><h3>StorecoinDev on Twitter</h3><p>8/ So, it is the &quot;leader-based block production design&quot; that makes the rich, richer. We can find evidence of this argument in PoW itself. The biggest mining pools are the ones who are getting richer, because they force themselves to be elected using their sheer hashing power.</p><h3>StorecoinDev on Twitter</h3><p>9/ So, what part of this argument is right? -- &quot;A new algorithm is needed&quot;. Or better, as we believe at @storecoin, a new &quot;mindset&quot; is needed.</p><h3>StorecoinDev on Twitter</h3><p>10/ A mindset away from leader or delegation-based protocols because they are easier to design. A mindset away from &quot;winner takes it all&quot; design for block rewards. A mindset where governance is off-the-chain or not specified or thought about at all.</p><h3>StorecoinDev on Twitter</h3><p>11/ @storecoin&#39;s BlockFin leaderless BFT consensus protocol attempts to address centralization and low throughput issues head on. We believe that if the network is not truly decentralized, it is not a blockchain at all.</p><h3>StorecoinDev on Twitter</h3><p>12/ Decentralization is not just about algorithm design. It must include the economics as well. Because a &quot;true decentralization&quot; is where *everyone* participates -- in validating the blocks, earning block rewards, and securing the network.</p><h3>StorecoinDev on Twitter</h3><p>13/ In BlockFin, all validator nodes participate in block validation. They may go offline from time to time, but they are *mostly* &quot;online and doing their job&quot;. They are incentivized to stay online and do their job via a decentralized block reward structure.</p><h3>StorecoinDev on Twitter</h3><p>14/ So, every participating validator node earns a portion of the block reward. So, validators &quot;work to earn&quot; rather than waiting for the lottery to get elected and earn the rewards.</p><h3>StorecoinDev on Twitter</h3><p>15/ So, rich get *marginally* richer only by ensuring their up-time and validating as many blocks in a day as they can. A validator node will fall back only with sloppy up-time.</p><h3>StorecoinDev on Twitter</h3><p>16/ Designing such a system is not easy, because we need to maintain a lot more data to be able to pay block rewards for all the participating validator nodes. When the protocol depends on a large number of nodes, it cannot be &quot;synchronous&quot; or assume any timing constraints.</p><h3>StorecoinDev on Twitter</h3><p>17/ But these challenges are exactly why @storecoin exists. It is important to believe in &quot;true decentralization&quot;, because otherwise, we will not be building a blockchain, but a centralized service like millions of cloud-based services all around us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a97609061635" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Storecoin?]]></title>
            <link>https://medium.com/@storecoin/what-is-storecoin-46e58e978833?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/46e58e978833</guid>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Sun, 03 Jun 2018 21:41:21 GMT</pubDate>
            <atom:updated>2018-06-03T21:41:21.193Z</atom:updated>
            <content:encoded><![CDATA[<h3>Storecoin on Twitter</h3><p>1/ Storecoin is a new public blockchain with high-throughput, true decentralization, and zero transaction fees. The project has eyes on taking on VISA with a faster, zero-fee, programmable, p2p payment system. If Ripple is taking on SWIFT, Storecoin is taking on ACH payments.</p><h3>Storecoin on Twitter</h3><p>2/ Storecoin&#39;s native currency, STORE, uses a sustainable inflationary monetary policy to achieve zero-fee transaction fees for merchants, developers, and end users.</p><h3>Storecoin on Twitter</h3><p>3/ Inflation is dynamically pegged to the number of tokens staked by dWorkers, who are in turn rewarded for contributing resources to the protocol&#39;s validation, governance, security, and scalability mechanisms.</p><h3>Storecoin on Twitter</h3><p>4/ The rate of inflation grows proportionally to the growth of total value staked, reaching a hard cap at 51% of total supply staked: at this limit, annual token inflation flatlines at 4%.</p><h3>Storecoin on Twitter</h3><p>5/ @Storecoin strives to take the Web 3.0 ethos one step further, leveraging a unique on-chain governance model inspired by the U.S. Constitution&#39;s checks and balances system.</p><h3>Storecoin on Twitter</h3><p>6/ This additional layer of trust and enforceability provides Storecoin with the necessary security and censorship resistance required to attract Fortune 500 companies to its zero-fee, p2p, programmable payments platform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46e58e978833" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Storecoin Begins Testing on BlockFin’s ‘Feed & Follow’ Design]]></title>
            <link>https://medium.com/@storecoin/storecoin-begins-testing-on-blockfins-feed-follow-design-492faec7ee84?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/492faec7ee84</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Sun, 27 May 2018 15:27:06 GMT</pubDate>
            <atom:updated>2018-05-27T15:27:06.530Z</atom:updated>
            <content:encoded><![CDATA[<h4>Goal is to overcome latency, up-time issues in global network</h4><p><strong>Highlights</strong></p><p>BlockFin Consensus Engine consists of a two-tier peer-to-peer network</p><p>Only nodes with proof of stake and KYC/AML verification are recognized by the network</p><p>Validators participate in the transaction and block validation process and Messagenodes provide storage and bandwidth services.</p><p>Nodes use the familiar “follow” model to get the information they need during the transaction and block validation process</p><p>The design can be compared with the function of a social media network</p><h3>StorecoinDev on Twitter</h3><p>We started testing a version of BlockFin peer-to-peer (p2p) core built using &quot;feeds&quot; and &quot;follow&quot; model of data replication. The design motivation is discussed here -- https://t.co/f909yXjEld</p><h3>StorecoinDev on Twitter</h3><p>BlockFin, @storecoin&#39;s Dynamic Proof-of-Stake (DyPoS) consensus engine consists of 2 cooperating p2p networks. One is a larger network of validators and second, smaller network of Messagenodes.</p><h3>StorecoinDev on Twitter</h3><p>The validators, as the name suggests, validate transactions and blocks and the Messagenodes provide storage and bandwidth services to validators. But how do you bring *trust* between the participating nodes?</p><h3>StorecoinDev on Twitter</h3><p>We want something like, &quot;trust, but double-check&quot; model where cryptographic signatures bring *trust* so a *signed* message can be verified by anyone, but how do we double check that a message is relayed correctly?</p><h3>StorecoinDev on Twitter</h3><p>In the &quot;feeds&quot; and &quot;follow&quot; model, each node creates its messages as its own private &quot;feed&quot; and let other nodes &quot;follow&quot; the feed. For example, Messagenodes follow validators for transactions received by them.</p><h3>StorecoinDev on Twitter</h3><p>When Messagenodes in turn follow each other, the transactions are replicated among them. Messagenodes cannot censor, alter, or perform any malicious activities because validators will be watching over them.</p><h3>StorecoinDev on Twitter</h3><p>So, unless a majority of nodes collude to breach the BFT threshold, the network is secure without incurring the overhead of traditional blockchains with O(n**2) complexity.</p><h3>StorecoinDev on Twitter</h3><p>The &quot;feeds&quot; and &quot;follow&quot; model works best in asynchronous environments where network connectivity and quality cannot be guaranteed. This is the exact setup @storecoin envisions for its public blockchain.</p><h3>StorecoinDev on Twitter</h3><p>In a globally distributed network, the latency and up-time cannot be guaranteed. So, BlockFin cannot make any timing assumptions.</p><h3>StorecoinDev on Twitter</h3><p>For example, we cannot say that a block will be produced every N seconds because that makes BlockFin fully *synchronous*. That in turn results in eventual centralization. Why?</p><h3>StorecoinDev on Twitter</h3><p>Strong timing assumptions eventually force a leader or delegate selection because you can guarantee connectivity or latency only when the number of participants is small.</p><h3>StorecoinDev on Twitter</h3><p>So nodes with poor up-time or latency will eventually be ignored/down-voted by others resulting in possible centralization. In BlockFin, nodes make progress asynchronously.</p><h3>StorecoinDev on Twitter</h3><p>So, BlockFin favors &quot;C&quot;onsistency over &quot;A&quot;vailability. Availability is addressed via economic rewards where *all* participating validators and Messagenodes earn a portion of the block reward for the blocks they helped validate.</p><h3>StorecoinDev on Twitter</h3><p>Stronger consistency is important because, remember, blockchains are supposed to be *immutable*? A weaker consistency makes immutability meaningless.</p><h3>StorecoinDev on Twitter</h3><p>Now, back to the testing. In the next few weeks, our goal is to test the &quot;feeds&quot; and &quot;follow&quot; model in a network consisting of 220 validators and 44 Messagenodes. These nodes are globally distributed around the world.</p><h3>StorecoinDev on Twitter</h3><p>We want to measure the performance characteristics of the model to ensure that the a) desire for stronger consistency is achieved and b) network makes progress in unreliable environments.</p><h3>StorecoinDev on Twitter</h3><p>The &quot;feeds&quot; and &quot;follow&quot; model is built using https://t.co/GviCF2wnyd. SSBC&#39;s focus on decentralization matches @storecoin&#39;s so we want to evaluate it to see how far we can go with it.</p><h3>StorecoinDev on Twitter</h3><p>In the event of network partitions, our desire is for individual nodes to continue to make *local* progress and *eventually* converge their work with the larger network without sacrificing consistency.</p><h3>StorecoinDev on Twitter</h3><p>So, any reliance on one or more nodes for *entire* blockchain is undesirable, because the *continuity* of the chain after the partition depends on the *views* of the connected nodes.</p><h3>StorecoinDev on Twitter</h3><p>So, we want to experiment if a global distribution of a large number of nodes provides better security in the event of network partition. We&#39;ll update our findings here after the test.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=492faec7ee84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open-Source Proposal has Potential to Raise Tendermint’s Consensus Throughput]]></title>
            <link>https://medium.com/@storecoin/open-source-proposal-has-potential-to-raise-tendermints-consensus-throughput-11fd44f7d537?source=rss-6e2927e20087------2</link>
            <guid isPermaLink="false">https://medium.com/p/11fd44f7d537</guid>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Storecoin Team]]></dc:creator>
            <pubDate>Fri, 20 Apr 2018 22:18:44 GMT</pubDate>
            <atom:updated>2018-06-22T00:50:16.462Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Storecoin’s idea would improve software’s ability to run consensus with constant time, even when many validators participate in the process</em></h4><h4>Highlights</h4><ul><li>Storecoin opens an issue with Tendermint on <a href="https://github.com/tendermint/tendermint/issues/1426">GitHub</a>, suggesting an improvement to “minimize peer-to-peer communication overload.”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/0*m39cjkYFX4GYAnCo." /><figcaption><strong>Image 1 — Submission of Project Basil by Storecoin on GitHub.</strong></figcaption></figure><ul><li>Novel idea results in throughput unaffected by the size of the network.</li><li>Proposal eliminates replication of a “holding area” for transactions on each individual peer’s system.</li><li>Shared transaction repository solves problem of peer-to-peer communication and opens the possibility of parallel consensus rounds by multiple block producers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rOKE_MStVyM-qSZj179BHg.png" /><figcaption><strong>Figure 1 — The outcome of the Project Basil proposal. Transactions are taken from a shared mempool.</strong></figcaption></figure><h4><strong>Background</strong></h4><p>While Storecoin’s engineering team worked on developing BlockFin, its dynamic, fork-tolerant, and auditable consensus algorithm, early versions of the Dynamic Proof of Stake (DyPoS) protocol were built and tested on top of Tendermint.</p><p>Open-source software, Tendermint core implements the blockchain consensus engine, which ensures that the same transactions are recorded on every machine in the same order. However, when a large number of machines are involved in the consensus, Tendermint is unable to handle the burden, making it unsuitable for large deployments with thousands of peers, a situation that Storecoin expects to encounter when it achieves its mission of becoming zero-fee payment infrastructure for users around the globe.</p><p><strong>Project Basil</strong></p><p>After studying its research results, Storecoin was able to propose an open-source idea, called <a href="https://github.com/StorecoinProject/Basil">Project Basil</a>, to ensure that throughput is not affected by the size of the network.</p><p>Specifically, Storecoin proposes two enhancements to Tendermint core:</p><ol><li>Eliminate the need for relaying the incoming transactions to other peers by devising a shared mempool that guarantees total order of transactions</li><li>Use the shared mempool to build the new block during consensus round</li></ol><p>Since peer-to-peer communication is eliminated by this proposal, the consensus throughput remains unaffected by the number of peers.</p><p>Tendermint is designed so that validators pick transactions from a storage area called a mempool. Each validator has a mempool. The elected block proposer takes the transactions from its local mempool to build the new block and proposes the new block for voting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2jjE_2byBTKegNQy." /><figcaption><strong>Figure 2— Traditional interaction between Tendermint core and its associated ABCI app.</strong></figcaption></figure><p>The proposer needs to grab a list of <em>validated</em> transactions to propose the new block for voting. Since transaction validation is offloaded to the ABCI app, maintaining the list of validated transactions can be too, calling for a <strong><em>shared</em> </strong>mempool with the following properties.</p><ol><li>Transaction order must be guaranteed as multiple peers submit validated transactions to the shared mempool</li><li>It must be secure, so the peers can trust the entries in the shared mempool during consensus rounds</li><li>The entries in the shared mempool must be consistent, so it offers the same view to all the peers</li><li>The shared mempool must have high availability because the progress of consensus rounds depends on it</li></ol><p>The creation of a shared mempool means that the peers:</p><ul><li>don’t add the transaction to their local mempool, but use SequenceTx() to store the <em>signed</em> transaction in the shared mempool</li><li>don’t relay it to other peers</li></ul><p>Since the transactions are ordered in the shared mempool, multiple block producers can propose multiple blocks for voting. The prevote and pre-commit phases of multiple proposed blocks can be pipelined, so the voting happens in parallel. Only the commit phase needs to be serial, so the block proposed by the <em>current</em> block producer is committed first, followed by the block proposed by the <em>next</em> producer, and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0GVkS5NT8tLyCF3g." /><figcaption><strong>Figure 3 — Validators take signed transactions from a shared mempool.</strong></figcaption></figure><p>Maintaining a shared mempool of ordered transactions eliminates the need for relaying the incoming transactions to all the peers. This approach adds 3 APIs to the ABCI interface and offloads the consistency and availability responsibilities to the ABCI app. This should not be perceived as a weakness, because the Tendermint core is not a standalone consensus engine and is always used in association with an ABCI app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11fd44f7d537" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>