<?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 Kevin Sekniqi on Medium]]></title>
        <description><![CDATA[Stories by Kevin Sekniqi on Medium]]></description>
        <link>https://medium.com/@kevinsekniqi?source=rss-4fc0ad42ffa8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*MyfCoMXdbh7XtnXVwdFHVA.jpeg</url>
            <title>Stories by Kevin Sekniqi on Medium</title>
            <link>https://medium.com/@kevinsekniqi?source=rss-4fc0ad42ffa8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:19:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kevinsekniqi/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[A 10-Minute Guide to Consensus Protocols, by Analogy to an Imaginary Senate]]></title>
            <link>https://medium.com/@kevinsekniqi/a-10-minute-guide-to-consensus-protocols-by-analogy-to-an-imaginary-senate-5caf273af801?source=rss-4fc0ad42ffa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5caf273af801</guid>
            <dc:creator><![CDATA[Kevin Sekniqi]]></dc:creator>
            <pubDate>Sun, 27 Sep 2020 02:07:16 GMT</pubDate>
            <atom:updated>2020-09-27T14:12:49.014Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/992/0*vyz5IDb0O3HkIhrR.jpg" /></figure><h4>Or, how to explain consensus to my dad.</h4><p>With the launch of Avalanche, it seems like work has only amplified. Projects after projects, integrations after integrations. Still, among the craziness, I wanted to take a bit of time to do something I haven’t done in a very long time: write concisely about topics that I happen to know a thing or two about.</p><p>Today’s topic is consensus. There’s been at this point probably hundreds if not thousands of blog posts written about this topic. I’ve read a bunch myself, and wasn’t impressed.</p><p>“<em>Everything should be as simple as possible, but not simpler</em>”. The blog posts, tweet-storms, etc., I’ve read have been jumbles of ideas, trying to juggle multiple designs without a cohesive — or “unifying” theory — of consensus. There’s far too much complexity, likely due to a lack of subject mastery. To that end, I shall create a “unifying” theory of consensus through a simple, yet arguably pretty accurate, metaphor: that of a bunch of senators trying to pass a bill in a parliament. And I shall choose the clearly superior method of publishing to academic papers: a blog post on Medium. In this guide I’ll cover PoW, PoS, sharding, and whatever comes along. If my dad can understand this post, while remaining scientifically accurate, I will have achieved my goal.</p><h3>1. Setting the Stage</h3><p>Because we want to keep it really simple, we’re going to learn about consensus by now <strong>never saying the word consensus ever again</strong>. We can’t define a word by using the word itself in the definition.</p><p>Instead, we’re going to focus on the following task at hand: getting a bunch of senators to pass a bill. First, we need a few ground rules, which are artificially imposed on the senators a) for simplicity and b) out of a need to make them “behave” like computers.</p><ol><li>Rule #1: Each senator must vote yay or nay to a bill. Also, each senator has exactly 1 vote.</li><li>Rule #2. A senator <strong>must be present</strong> on the senate building in order to vote. If they aren’t there, they can’t vote for or against the bill. It’s show up or gtfo.</li><li>Rule #3: There’s at most 100 senators. This is random, but I chose it because it makes the math simple.</li><li>Rule #4: Whenever a bill is proposed, there’s at least 1 senator on the floor available to vote on the bill, AND that senator is willing to vote yay or nay on it.</li></ol><p>Now, through this setup, we’re going to do the following: <strong><em>get a bill through the floor</em></strong>. That’s the goal. How we get there will be <strong><em>subject to the specific design of each algorithm</em></strong>. Naturally, there are three outcomes:</p><ol><li>The bill is approved.</li><li>The bill is rejected.</li><li>There’s no decision, and we just filibuster. At that point, we pack our bags and try again tomorrow.</li></ol><p>In my words above there is a few subtle, but deeply consequential, implications:</p><ol><li>I never said anything about what either “approved”, “rejected”, or “no decision” means. Why? because it is <strong>subject to interpretation. </strong>Said in nerd lingo, it is subject to the specific definition that the target algorithm uses. <strong><em>This is quite important to understand right now</em></strong>. Those that aren’t experts in this area typically understand each of those as having unique and universal definitions (typically those subsumed by Satoshi). However, this is clearly not the case, as there are other definitions. For example, the algorithm that the U.S. government chooses to pass bills (very roughly <a href="https://www.carper.senate.gov/public/index.cfm/how-a-bill-becomes-a-law">[1]</a>) says that if 2/3 of the senate (in this case 67 of the 100 senators) votes for a bill, they can overwrite the President even if he or she vetoes it. In that sense, “approve” means that 2/3 of the senate wants to pass the bill. Furthermore, unlike in Bitcoin, it is also perfectly normal and acceptable for the bill to be filibustered. Weird, right?</li><li>The framework above is universal. This means that the simple process I’ve outlined above is sufficient to describe every single consensus protocol, including L1’s and L2’s. Pretty neat.</li></ol><p>Ok, so let’s get started.</p><h3>2. Synchronous protocols, proof-of-work, Bitcoin, Ethereum, and much ado about nothing.</h3><p>Here’s how Bitcoin works:</p><ol><li><strong>Step 1:</strong> A bill is proposed.</li><li><strong>Step 2:</strong> Senators have 10 minutes to vote on the bill.</li><li><strong>Step 3:</strong> At the end of the 10 minutes, there’s 3 outcomes:</li></ol><ul><li>Approve: <strong><em>pass the bill as long as 51% of</em></strong> <strong><em>whoever is on the senate floor at the time of the bill being proposed votes “yay”</em></strong><em>.</em></li><li>Reject: <strong><em>reject the bill as long as 51% of</em></strong> <strong><em>whoever is on the senate floor at the time of the bill being proposed votes “nay”</em></strong><em>.</em></li><li>Filibuster: <strong>not possible. </strong>Why is filibuster not possible in Bitcoin’s senate? Because of one key part: “<strong><em>51% of</em></strong> <strong><em>whoever is on the senate floor at the time of the bill being proposed votes”. </em></strong>So, as long as at least 1 senator is on the floor to vote, which is something that we assumed per the rules above, we will have a vote.</li></ul><p>4. <strong>Step 4: </strong>Go back to step 2, and consider the bill irrevocable once you go through steps 2 and 3 for a minimum of 6 times.</p><p>That’s literally Bitcoin. Don’t @ me on Twitter, this is how it works. For Ethereum, change the 10 minutes to 15 seconds, and the 6 to like 35. Something like that.</p><p>A few observations:</p><p><strong>Observation #1. </strong>So where does the proof-of-work come into play? Irrelevant for any of this. Truly, it is. Proof-of-work becomes relevant in the pre-processing step, in the part where we define on who a senator is. In PoW-case, it’s someone with a bunch of hashpower. The more hashpower, the more the voting power.</p><p><strong>Observation #2</strong>. This one’s a doozy, but it’s one of the most interesting outcomes from distributed systems. Synchronous protocols, such as Bitcoin and Ethereum, <strong>always make progress. </strong>But, they do so at a massive tradeoff: safety. Remember that when I said there’s really 100 senators, but Bitcoin could make progress with a single one being present every 10 minutes?</p><p>That’s pretty bad. Here’s how: only one senator is on the floor; bill arrives; senator keeps voting “yay” every 10 minutes; an hour goes by, bill passes; next day 99 other senators come in, they can easily overwrite the 1 senator.</p><p>Pretty bad. This is what’s know in literature as a partitioning attack, which is what happens when synchronicity is violated. Bitcoin is only safe if it is guarantee that all miners in the network are connected by at worse a 10 minute delay.</p><h3>3. Asynchronous protocols, PoS, and why a filibuster is good.</h3><p>I’m going to disappoint a whole lot of you. There’s nothing special about this class of protocols besides the fact that instead of there being <em>any </em>majority of senators to there being <em>the </em>majority of senators. In particular, in these protocols, we will ONLY make progress if some large majority of the 100 senators are actually voting on the bill. That’s it. The PoS component doesn’t matter.</p><p>Here’s how, for example, PBFT works:</p><ol><li><strong>Step 1:</strong> A bill is proposed.</li><li><strong>Step 2:</strong> Senators can vote as soon as they want to.</li><li><strong>Step 3:</strong> As soon as a supermajority of the votes come in, there’s three outcomes:</li></ol><ul><li>Approve: <strong><em>pass the bill as long as a supermajority of the 100 senators vote “yay”</em></strong><em>.</em></li><li>Reject: <strong><em>reject the bill as long as a supermajority of the 100 senators vote “nay”</em></strong><em>.</em></li><li>Filibuster: <strong>possible. </strong>Why? We could be waiting for quite a while until the supermajority of senators vote. But here’s the important part: eventually, the senators will vote. Eventually.</li></ul><p>4. <strong>Step 4: </strong>Nothing to do. Get an espresso and hang out. Just keep waiting until senators vote. Trust me, dude, it’s better for everyone. We need <strong>assurance</strong> here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*E6XwFIXR80TP4ivR.jpg" /><figcaption>Please vote this November</figcaption></figure><p>Most important observation: asynchronous protocols typically value safety over liveness. These protocols make no assumptions about how long it will take for communication to happen, and so it is required that a supermajority of senators must vote.</p><p>Is this supermajority property a requirement? Can we make PoS protocols work in the synchronous case? Absolutely. And there’s a bunch of them out there.</p><p>What about Avalanche? Avalanche is an elegant protocol, but it’s not so special that it won’t fit within this universal framework. It’s — in fact — squarely in this domain. Avalanche is a (probabilistically) safe asynchronous protocol.</p><h3>4. L2s on Ethereum</h3><p>Simple:</p><ol><li><strong>Step 1:</strong> A bunch of bills are proposed all at once in a building next to the senate, and are approved or rejected by a “pseudo senate”.</li><li><strong>Step 2:</strong> At some point, the pseudo senate sends the set of bills to the actual real senators, who have 10 minutes to vote on the set of bills.</li><li><strong>Step 3:</strong> At the end of the 10 minutes, there’s 3 outcomes:</li></ol><ul><li>Approve: <strong><em>pass the bills as long as 51% of</em></strong> <strong><em>whoever is on the senate floor at the time of the bills being proposed votes “yay”</em></strong><em>.</em></li><li>Reject: <strong><em>reject the bills as long as 51% of</em></strong> <strong><em>whoever is on the senate floor at the time of the bills being proposed votes “nay”</em></strong><em>.</em></li><li>Filibuster: <strong>not possible.</strong></li></ul><p>4. <strong>Step 4: </strong>Go back to step 2, and consider the set of bills irrevocable once you go through steps 2 and 3 for a minimum of 6 times.</p><p>Basically, L2s “process” a bunch of bills offline first, then show them all at once in a “condensed” form to the senate. <strong>Senate must still vote on these bills, so L2s are as slow as the underlying L1</strong>. Also, it’s possible the senators are going to reject all those bills, even though the pseudo-senate approved them. The pseudo-senate is irrelevant. Only the real senate can set the law. L2s are trusted off-chain accumulators.</p><h3>5. Sharding (the asynchronous version)</h3><p>Gets a bit more complicated. I’ve seen two major classes of sharded blockchains.</p><p><strong>Class 1</strong>: The basic principle is that instead of having a single big senate, we divide the senate into multiple mini-senates, where each mini-senate votes on bills in parallel, and then sends them out to the larger senate to vote in batches. I’m grossly oversimplifying, but ultimately that’s the gist. The astute reader will notice that the latencies here — in theory and in practice — will be as high as the slowest mini-senate.</p><p><strong>Class 2: </strong>The basic principle is that we divide senators into mini-senates and then each of those acts as a single unit of vote. It’s basically just a way to reduce the raw number of senators voting on a bill down linearly by the number of shards. Again, latencies here could be huge.</p><h3><strong>6. Concluding remarks.</strong></h3><p>If you are now thinking to yourself: “is this it, is this all the fuss is about?”, the answer is a resounding “yes”. This is really it. It’s not that much more complicated. I got kind of lazy towards the latter parts of the article, especially with L2s and sharding because frankly the article started getting kind of long, but there isn’t much more to this space.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5caf273af801" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Update on Avalanche Mainnet: Setting Up for a Successful Launch]]></title>
            <link>https://medium.com/avalancheavax/an-update-on-avalanche-mainnet-setting-up-for-a-successful-launch-7ea9b139ba09?source=rss-4fc0ad42ffa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ea9b139ba09</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[avalanche]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Kevin Sekniqi]]></dc:creator>
            <pubDate>Thu, 27 Aug 2020 16:41:19 GMT</pubDate>
            <atom:updated>2020-09-19T15:26:21.665Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The fun is just about to begin, and we’re excited to start making history with you very soon.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f5kZnpk3PRuszGP7ySzBAA.png" /></figure><p>Avalanche’s mainnet release candidate, codenamed Everest, has been outstanding thus far. Over <a href="https://explorer.avax.network/">650 full, block-producing validators</a> are participating on the platform, we’re seeing awesome development activity, and making great strides in improving the user experience you’ll have at launch.</p><p>For a mature ecosystem to develop around Avalanche, we need to complete critical third-party integrations.</p><p><em>To that end, we are waiting to launch Avalanche’s mainnet until users can access, hold, and store AVAX with reputable third-parties. The Avalanche community should expect mainnet and exchange liquidity around mid-September.</em></p><p>Along with mainnet and exchange liquidity, the community should expect other major infrastructure integrations like custodians, wallets — including Ledger hardware — and staking providers. These integrations, scheduled synchronously, will support our existing users and open doors for new entrants in highly efficient ways.</p><h3><strong>Progress Since the Avalanche Token (AVAX) Public Sale</strong></h3><p>Since the Avalanche token (AVAX) public sale on July 15, 2020, the Avalanche team set its undivided attention towards mainnet launch. The Everest mainnet release candidate enabled the development team to have full clarity and confidence with the platform prior to fully committing to mainnet. Our focus did not stop here.</p><p>In parallel to improvements to Avalanche’s performance and security, we’ve secured many integrations and ecosystem collaborations, including:</p><ul><li>Expanding the Avalanche-X grants program</li><li><a href="https://medium.com/avalabs/bringing-one-click-google-logins-to-the-avalanche-wallet-57227ab25673?source=collection_home---4------11-----------------------">Integrating one-click Google Logins to the Avalanche Wallet</a></li><li><a href="https://medium.com/avalabs/polyient-games-to-bring-nft-focused-decentralized-exchange-to-ava-labs-avalanche-2f7c3c6e738d">Polyient Games committing to launch an NFT-focused decentralized exchange (DEX) on Avalanche</a></li><li><a href="https://medium.com/avalabs/avalanche-partners-with-whiteblock-to-optimize-blockchain-security-and-performance-8d6b8a383365">Leveraging Whiteblock’s Genesis platform to optimize Avalanche’s security</a></li><li><a href="https://medium.com/avalabs/ava-labs-joins-lacchain-alliance-led-by-the-interamerican-development-bank-131df4065839">Ava Labs’ joining LACChain Alliance to accelerate the development of blockchain technology in Latin America and the Caribbean region</a></li><li><a href="https://medium.com/avalabs/quantstamp-optimizing-security-for-avalanche-2c2129a63795">Quantstamp enhancing Avalanche’s security for mainnet launch</a></li><li>And more underway!</li></ul><p>Our team is finalizing third-party security audits, enhancing core staking and minting functionalities, aggressively testing the network to optimize performance, and developing major ecosystem collaborations that bring more applications on Avalanche. If you’re not doing so already, we encourage you to explore the new features on Everest with our community of <a href="https://chat.avax.network/">devs on Discord</a> or jump into the <a href="https://medium.com/avalabs/how-to-join-avalanche-everest-release-a40cd20aa654">quickstart guide</a>.</p><p>A big set of events and growth initiatives are scheduled for shortly after mainnet. As always, make sure to stay tuned for all our post-mainnet announcements. The fun is just getting started.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2Fxnitey%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fxnitey&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b8a596544f943e3618682869c7e2f97a/href">https://medium.com/media/b8a596544f943e3618682869c7e2f97a/href</a></iframe><h3>About Avalanche</h3><p>Avalanche is an open-source platform for launching decentralized finance applications and enterprise blockchain deployments in one interoperable, highly scalable ecosystem. Developers who build on Avalanche can easily create powerful, reliable, and secure applications and custom blockchain networks with complex rulesets or build on existing private or public subnets.</p><p><a href="https://avax.network/">Website</a> | <a href="https://avalabs.org/whitepapers">Whitepapers</a> | <a href="https://twitter.com/avalancheavax">Twitter</a> | <a href="https://chat.avalabs.org/">Discord</a> | <a href="https://github.com/ava-labs">GitHub</a> | <a href="https://docs.avax.network/">Documentation</a> | <a href="https://explorer.avax.network/">Explorer</a> | <a href="https://avalabs.org/avalanche-x">Avalanche-X </a>| <a href="https://t.me/avalancheavax">Telegram</a> | <a href="https://facebook.com/avalancheavax">Facebook</a> | <a href="https://linkedin.com/company/avalancheavax">LinkedIn</a> | <a href="https://reddit.com/r/avax">Reddit</a> | <a href="http://www.youtube.com/c/AVALabsOfficial">YouTube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ea9b139ba09" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avalancheavax/an-update-on-avalanche-mainnet-setting-up-for-a-successful-launch-7ea9b139ba09">An Update on Avalanche Mainnet: Setting Up for a Successful Launch</a> was originally published in <a href="https://medium.com/avalancheavax">Avalanche</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Updates to Avalanche (AVAX) Public Sale]]></title>
            <link>https://medium.com/avalancheavax/updates-to-avalanche-avax-public-sale-122da45bba5b?source=rss-4fc0ad42ffa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/122da45bba5b</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[public-sale]]></category>
            <category><![CDATA[avalanche]]></category>
            <category><![CDATA[ico]]></category>
            <dc:creator><![CDATA[Kevin Sekniqi]]></dc:creator>
            <pubDate>Tue, 30 Jun 2020 12:56:19 GMT</pubDate>
            <atom:updated>2020-07-23T13:13:51.529Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>To the Avalanche community: thank you for your feedback last week.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1a710P8s3FZAC5jF" /></figure><p>When we started the journey to bring Avalanche to the world, we outlined core principles that would define every decision that would push the project closer to reaching its potential. Principles that would ensure we are good stewards of the Avalanche community, while also rejecting the status quo of projects that promise much and deliver little at the expense of their most avid supporters.</p><p>From the start, we’ve committed to being:</p><ul><li><strong>Community-driven</strong>: we’ve always been dedicated to fostering an equal, open, and productive community around Avalanche and sharing our successes together.</li><li><strong>Long-term</strong>: we’re in this for a new era, not just a flash in the pan fad. We’re committed to delivering on our promises and building the internet of finance.</li><li><strong>Egalitarian</strong>: we’ve deliberately structured the Avalanche distribution to ensure fair and open access to the widest set of value-providing users and builders on the network.</li></ul><p>In light of our commitment to these principles, we’re making some updates to our public sale that incorporate the feedback you’ve shared in recent days while sharpening our long-term positioning for sustainable growth. View all changes in our public sale info page <a href="https://info.avax.network/">here</a>. We also wanted to take the time to clarify some points of confusion that we witnessed. For all other frequently asked questions, always refer to our FAQ found <a href="https://support.avalabs.org/en/collections/2413660-ava-token-sale">here</a>.</p><h3>Sale Updates</h3><blockquote><strong>1. The total public sale allocation is increasing, and allocations are being capped to allow for a fairer and broader distribution.</strong></blockquote><p>Much of the community’s concern for the original Option A was that a select few whales could enter and consume the allotment. This sale should naturally be about maximizing a fair and broad distribution. To remedy this, the following three options are now available to public sale participants:</p><p>- <strong>Option A1</strong>: This option is for $0.50/token, with 1 year vesting, and with a maximum check size of $25K USD per participant. <br>- <strong>Option A2</strong>: This option is for $0.50/token, with 1.5 years vesting, and with no maximum check size per participant.<br>- <strong>Option B</strong>: This option is for $0.85/token, fully unlocked, and with a maximum check size of $5K USD per participant.</p><p>Option A1 and B are allocated a total of 12M tokens, borrowed from the same pool. Both options have low maximum check sizes to ensure distribution. Additionally, we are assigning a dedicated pool of 5M tokens for Option A2, which has no maximum check size. This brings the total public sale allocation to 17M tokens.</p><p>On July 21st, at 10AM ET (UTC-4), all unsold tokens from Option A1 and B are sent to Option A2. On July 22nd, 24 hours later at 10AM ET (UTC-4), all unsold tokens from Option A2 will be sent to the Community and Developer Endowment.</p><blockquote><strong>2. We’ve greatly simplified participation restrictions for persons outside the U.S.</strong></blockquote><p>In the U.S., participation is clearly defined and limited to accredited investors, but outside the U.S., there were substantial questions about who could participate. We’ve simplified the descriptions to more clearly outline ineligible participants. More details on participation for non-U.S. persons, visit our dedicated FAQ section <a href="https://support.avalabs.org/en/articles/4196735-who-can-participate-in-the-avalanche-avax-public-sale">here</a>.</p><h3>Clarifications</h3><blockquote><strong>1. All locked tokens, including those distributed in Option A1 and A2, are eligible for staking. </strong>Furthermore, all tokens minted through staking are not subject to any vesting term.</blockquote><p>Many of you asked whether locked tokens could be staked, and if so, what terms would be placed on rewards. The full amount of tokens acquired through Option A1 and A2 are eligible for staking, and there is no vesting schedule for staking rewards. In fact, this is how we envision (and hope) the vast majority of participants in Option A1 and A2 will use their tokens.</p><p>We believe network participation shouldn’t be limited to delegated staking or expensive mining rigs. Avalanche really showcases its power when individuals participate at the highest level, and is designed to be as easy as possible with low hardware requirements.</p><blockquote><strong>2. The set of available payment options are ETH, BTC, USDC, USDT, as well as wire transfers.</strong></blockquote><p>and, finally,</p><blockquote><strong>3. There have been questions regarding the fee structure of Avalanche, and how this fee structure affects the burning and overall economics of the system.</strong></blockquote><p>We are putting together a blog post describing various scenarios under which Avalanche may undergo for the first year. These scenarios will inform how fees will affect supply. Please stay tuned for the announcement on our social channels.</p><p>These decisions have not been made lightly, requiring a careful balance of Avalanche’s immediate goal of a broad distribution with the realities of growing a network through builders.</p><p>As with our private sale, this will require leaving “easy” participation on the table that would come in from speculators looking to turn a profit, and instead favoring individuals committed to the further development and decentralization of Avalanche. That is a tradeoff we will happily make now to enable long-term, community-driven growth in the future.</p><p><em>For more information on the AVAX token, go to: </em><a href="https://info.avax.network/"><em>https://info.avax.network/</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2Fxnitey%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fxnitey&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b8a596544f943e3618682869c7e2f97a/href">https://medium.com/media/b8a596544f943e3618682869c7e2f97a/href</a></iframe><h3>About Avalanche</h3><p>Avalanche is an open-source platform for launching decentralized finance applications and enterprise blockchain deployments in one interoperable, highly scalable ecosystem. Developers who build on Avalanche can easily create powerful, reliable, and secure applications and custom blockchain networks with complex rulesets or build on existing private or public subnets.</p><p><a href="https://avax.network/">Website</a> | <a href="https://avalabs.org/whitepapers">Whitepapers</a> | <a href="https://twitter.com/avalancheavax">Twitter</a> | <a href="https://chat.avalabs.org/">Discord</a> | <a href="https://github.com/ava-labs">GitHub</a> | <a href="https://docs.avax.network/">Documentation</a> | <a href="https://explorer.avax.network/">Explorer</a> | <a href="https://avalabs.org/avalanche-x">Avalanche-X </a>| <a href="https://t.me/avalancheavax">Telegram</a> | <a href="https://facebook.com/avalancheavax">Facebook</a> | <a href="https://linkedin.com/company/avalancheavax">LinkedIn</a> | <a href="https://reddit.com/r/avax">Reddit</a> | <a href="http://www.youtube.com/c/AVALabsOfficial">YouTube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=122da45bba5b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avalancheavax/updates-to-avalanche-avax-public-sale-122da45bba5b">Updates to Avalanche (AVAX) Public Sale</a> was originally published in <a href="https://medium.com/avalancheavax">Avalanche</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Consolidating Our Identity: Ava Labs, Avalanche, and AVAX]]></title>
            <link>https://medium.com/avalancheavax/consolidating-our-identity-avalanche-and-avax-6c97e7968599?source=rss-4fc0ad42ffa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c97e7968599</guid>
            <category><![CDATA[avax]]></category>
            <category><![CDATA[ava-labs]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[avalanche]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Kevin Sekniqi]]></dc:creator>
            <pubDate>Wed, 24 Jun 2020 21:03:16 GMT</pubDate>
            <atom:updated>2020-07-28T13:24:18.277Z</atom:updated>
            <content:encoded><![CDATA[<p><em>We have come a long way since the Team Rocket whitepaper. Today, we are excited to move forward with our consolidated direction.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_mu-L9dW00nRa1mVJqNsQ.gif" /></figure><p>A lot has changed in the two years since Team Rocket shared a whitepaper outlining Avalanche. A few of us at Cornell moved the paper and its ideas forward with Team Rocket to <a href="https://files.avalabs.org/papers/consensus.pdf">formally introduce our family of consensus protocols</a>. In the early days of our research, we were just a small group. Today, there’s a global team and community building the protocol and promise detailed in those pages.</p><p>Over the last year, the project has grown tremendously. From a community that spans a countless number of countries to a testnet that achieved over a thousand validators, we can feel the excitement across all facets of the project. As we complete the final preparations for mainnet launch, we’ve realized that this community growth will soon outpace the rails that we’ve built for our brand. It became very apparent that we needed to simplify the brand to what we’ve always been.</p><p><em>We are Avalanche</em>. $AVAX, Avalanche’s native token, memorializes the many ideas and realities that continue to converge around the project and the intersections within it. The X, a symbol and constant reminder that the network, while decentralized and global, is only as valuable as the connections it’s able to forge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*etvrHBLPxv8JyhnL" /></figure><h3><strong>The Journey That Brought Us Here</strong></h3><p>In the process of growing rapidly, we created different sub-brands and vehicles to bring Avalanche to the masses, often relying on the short-hand “AVA” — a habit we all fell into after typing Avalanche a few hundred times per week alongside thousands of lines of code.</p><p>Compound that with character limits across social channels, and you’ve got a recipe for naming initiatives with the short-hand (a perfect example is our community growth platform <a href="https://community.avax.network/">Avalanche Hub</a>).</p><p>This nomenclature was fine for a smaller community, but as Avalanche picked up momentum and rapidly grew across the world, we found that too often the connection to AVA was being lost in communication.</p><p>A few weeks ago, as more than one thousand developers were concurrently participating as full block-producing nodes on the Denali Testnet, we went back to the drawing board for the project’s brand. We filled it with research into ticker names, domains, social handles, and symbols with one goal in mind: make it clear to anyone in the world what our community is rallying behind and what the network achieves.</p><p>Through discussion, debate, and careful weighing of pros and cons, we kept finding ourselves back to our roots and what the next phase will achieve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*glzEBEN7d_KBqnTa" /></figure><h3><strong>Moving Forward with Avalanche and $AVAX.</strong></h3><p>A network built by and for its community. A token and internet of finance defined by velocity, efficiency, and innovation in new products and services. This is what Avalanche is all about. Just like the occurrence in nature, we hope to build a project driven by compounding momentum that will, someday, be unstoppable.</p><p>Thank you to everyone who participated in Avalanche’s progress thus far, and we welcome anyone who wants to be the next contributor. We’re on the precipice of making history together, and I couldn’t be more excited for what lies ahead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9zg15SaixDOdqqeMNa8i1g.png" /></figure><p><em>Note: AVA Labs, the team supporting the development of Avalanche, will stay the same.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2Fxnitey%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fxnitey&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b8a596544f943e3618682869c7e2f97a/href">https://medium.com/media/b8a596544f943e3618682869c7e2f97a/href</a></iframe><h3>About Avalanche:</h3><p>Avalanche is an open-source platform for launching decentralized finance applications and enterprise blockchain deployments in one interoperable, highly scalable ecosystem. Developers who build on Avalanche can easily create powerful, reliable, and secure applications and custom blockchain networks with complex rulesets or build on existing private or public subnets.</p><p><a href="https://avax.network/">Website</a> | <a href="https://avalabs.org/whitepapers">Whitepapers</a> | <a href="https://twitter.com/avalancheavax">Twitter</a> | <a href="https://chat.avalabs.org/">Discord</a> | <a href="https://github.com/ava-labs">GitHub</a> | <a href="https://docs.avax.network/">Documentation</a> | <a href="https://explorer.avax.network/">Explorer</a> | <a href="https://avalabs.org/avalanche-x">Avalanche-X </a>| <a href="https://t.me/avalancheavax">Telegram</a> | <a href="https://facebook.com/avalancheavax">Facebook</a> | <a href="https://linkedin.com/company/avalancheavax">LinkedIn</a> | <a href="https://reddit.com/r/avax">Reddit</a> | <a href="https://www.youtube.com/c/AVALabsOfficial">YouTube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c97e7968599" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avalancheavax/consolidating-our-identity-avalanche-and-avax-6c97e7968599">Consolidating Our Identity: Ava Labs, Avalanche, and AVAX</a> was originally published in <a href="https://medium.com/avalancheavax">Avalanche</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick look into “What Avalanche paper is not”]]></title>
            <link>https://medium.com/@kevinsekniqi/quick-look-into-what-avalanche-paper-is-not-45c588571c16?source=rss-4fc0ad42ffa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/45c588571c16</guid>
            <dc:creator><![CDATA[Kevin Sekniqi]]></dc:creator>
            <pubDate>Tue, 31 Mar 2020 15:40:25 GMT</pubDate>
            <atom:updated>2020-03-31T15:40:25.882Z</atom:updated>
            <content:encoded><![CDATA[<p>Tl;Dr: The blog post demonstrates a misunderstanding of how to extend basic distributed primitives of voting-based protocols and make them viable for a production ready distributed ledger.</p><p>Let’s take a look at the first critique: <strong>“Snowball as is is not a ready-to-use binary consensus”.</strong></p><p>The claim is that Snowball doesn’t reach consensus by itself as described. Let’s decouple that, and let’s do it using the simpler primitive, which is Snowflake. The primitive says the following: each node samples <strong>k </strong>nodes at random, and flips to whatever some supermajority of them vote for. Notice something important: this is the basic primitive that a classical protocol would use, but instead it would simply choose <strong>k</strong> (the sample size) to be equal to the entire network. If some supermajority (typically 67%) vote the same way, then a node will flip to that color. This means that:</p><blockquote>Snowflake is actually a <strong>universal generalization of all voting-based (or quorum-based) protocols.</strong></blockquote><p>If you were to set <strong>k equal to the network size</strong> in Snowflake, then you just derived the basic <strong>quorum measuring primitive</strong> of all classical consensus protocols. Now, here’s the catch for classical protocols (which every other PoS system currently implements):</p><blockquote>If there is no supermajority (quorum), the convergence time to that simple process is <strong>infinity</strong>.</blockquote><p>Therefore, classical protocols <strong>must </strong>elect a leader or use some other process (maybe some really expensive VDF). Without such a mechanism, nodes could never reach the desired quorum <strong>even if there is zero Byzantine presence</strong>.</p><p>Instead, if you make <strong>k </strong>less than the network size, you suddenly introduce some errors. This is great, because we can use inherent bias in the sample to converge nodes towards some decision value.</p><p>Avalanche uses this basic idea to build the best-in-class protocol for scalability, and does so without using a leader. Naturally, since Avalanche is purposefully designed to not elect a leader (not needed, since it deals with communicative operations), <strong>in the theoretical model</strong>,<strong> </strong>it has a lower threshold of liveness because the adversary could always “undo” the natural bias in the sample. However, here’s the deal. First, this attack is practically unrealistic. It exists in a highly-theoretical model where the adversary has an instant view of the network at all times, and in practice this is very hard to achieve. Second, and much more importantly, if you want to augment Avalanche to the higher end theoretical limits of liveness, then the system designer can simply use any of the liveness mechanisms that classical protocols (including Eth2.0, Cosmos, etc). This is the part that the author of the critiques seems to have entirely missed. Likely not consciously, but due to lack of understanding.</p><p>Employing a leader or a VDF, however, is obviously not needed as the main DAG which is employed in AVA doesn’t need to operate on total ordering. If any transactions are conflicting and can’t make progress, they are issued by Byzantine nodes in the first place. Other subnets in AVA that need total ordering (such as the AVA smart contracts chain), employ the same liveness inducing mechanisms as some of the other latest PoS protocols, so liveness, like scalability in Avalanche, is optimal too.</p><p>The second critique is: <strong>“Some crypto-economic incentive is required to encourage people to post transactions that actually build the DAG.”</strong></p><p>I’ll keep this one very short: every mechanism that any PoS ledger can use to incentivize nodes to validate transactions can be fit for Avalanche as well. The author seems to have little ability to isomorphically map incentives across commutative and linear chain data structures. We’ll leave the author to browse through the AVA codebase for more info.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45c588571c16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crypto Network’s Killer Value Prop]]></title>
            <link>https://medium.com/avalancheavax/crypto-networks-killer-value-prop-1476a72b9c2b?source=rss-4fc0ad42ffa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1476a72b9c2b</guid>
            <category><![CDATA[thoughts]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Kevin Sekniqi]]></dc:creator>
            <pubDate>Tue, 04 Feb 2020 21:30:12 GMT</pubDate>
            <atom:updated>2020-05-19T16:03:43.352Z</atom:updated>
            <content:encoded><![CDATA[<p>What is the biggest value proposition of “crypto networks”? We argue that the answer is the defragmentation of financial markets through the inadvertent creation of two key components:</p><p>1. the creation of the first <strong>common language</strong> of finance, i.e. the ATP, or “Asset Transfer Protocol”, which is the financial equivalent to “HTTP”, or “Hypertext Transfer Protocol”, the common language of the web; and,</p><p>2. the creation of the first <strong>the common infrastructure</strong> of finance, i.e. the first “Amazon Web Services”, which enables the core set of financial apps and primitives to be built upon the common language in a free, but compliant, way.</p><h3>Abstract</h3><p>We attempt to answer a simple question: “<em>What is the killer value prop of crypto networks?</em>” The answer, we believe, is in the functionalization of asset/capital flows.</p><p>In particular, there is a big opportunity in breaking down the division between private and public markets, enabling capital flows to transition through various asset classes effortlessly, thus enabling network effects to be bestowed onto financial markets. This will be done through an interoperable and common network for assets, where assets will be treated as first-class programmable objects, and where they will move around the network freely through simple API calls. Said differently, markets will <strong>**de-fragment**</strong> by moving from bespoke siloed solutions to a common network.</p><h3><strong>What is Functionalization?</strong></h3><p>Functionalization theory (see [[2]] for more details), is an attempt to model market innovation through an abstract functional process. The theory of functionalization is generic enough to itself include market theories such as “Aggregation Theory” [[1]] by Ben Thompson, which we highly recommend to the reader of this article. At a very high level, the statement of the theory is simple (excerpt taken from original article):</p><blockquote>&gt; … functionalization is the process [of] making the consumption of a set of products or services by the end user repeatable, scalable, and predictable, which in turn makes them cheaper and better.</blockquote><blockquote>&gt; [Functionalization is] the composition, transformation, and standardization of a set of platforms (services/products) into a modular and callable function, rendering the platform scalable, repeatable, and predictable.</blockquote><p>It is effectively the process by which we create higher-level “functions” out of existing services through composition.</p><p>Simple example: Amazon.com. On the buyer-side, Amazon.com composes together three key services through one function: searching (i.e. discovery), purchasing, and delivery of consumer products. Before Amazon.com existed, consumers were still able to do the same exact thing you are able to do now. However, until Amazon.com packaged <em>all these three services as one single service</em>, it was just significantly more difficult. Shopify is another great example of functionalization of “payments, marketing, shipping and customer engagement tools to simplify the process of running an online store for small merchants”.</p><p>Those are the basics of functionalization: take multiple products and/or services that exist independently, and compose them together into a single new product and/or service that is repeatable and scalable. This, in turn, makes the selling of the service as a whole cheaper and better than the selling of the sub-components independently.</p><h3><strong>Where Are Capital Markets Today?</strong></h3><p>No more than a hundred years ago, there was no distinction between private and public markets. This distinction was initiated by various governments in an attempt to place a regulatory framework that enables the smoothing out of tail events in markets with open capital flows. In fact, the Federal Reserve’s job is precisely to ensure that financial crises are managed properly if rapid downturns occur.</p><p>Control of monetary policy is a sensible feature of any government desiring stability. However, additional statutory regimes, such as the creation of “securities” and the managing body behind them (U.S. SEC), placed as protective measures after the Great Depression to protect against future economic downturns, created a permanent schism that has arguably debilitated capital markets for generations.</p><p>In particular, this framework created a bifurcation of capital flows into “public” and “private” markets. The unfortunate outcome of this regulation is that it has locked a vast amount of asset classes into illiquid, undiscoverable, inaccessible, and dormant pools. This can be visualized in the following quadrants:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/489/1*rEKp9AdoB5I9XzmhEo06uw.png" /></figure><p>Naturally, this has greatly hindered the potential of financial markets. Imagine, for example, if every-time you wanted to sell an item, the buyer had to go through an extensive process of demonstrating that they were an “accredited” buyer, and if you, as the seller, happened to ever accidentally sell to “non-accredited” buyers due to a subpar vetting process, you would face serious legal penalties. While it’s hard to definitely say, we would argue that if such a restriction was in place for day to day items, Amazon.com would be a tiny fraction of the behemoth that it is today.</p><h3><strong>The Big Opportunity: ProCap (Programmable Capital), i.e. Functionalizing Asset Flows</strong></h3><p>Instead, let’s imagine financial markets without these prohibitive restrictions. Instead, what if we could move any asset class freely (modulo meeting various conditionals) from one owner to another? If we are able to create digital representation of any contract (i.e. asset) and move its ownership set as easily as transferring data over the internet. This is what functionalization of asset flows would entail. If a generic way to encode contracts digitally is enabled, we can now not only move from issuance to discovery of assets much more easily, but it would also be done in a way that still enforces the necessary regulatory conditionals required to comply with local, national, and international regulatory bodies.</p><p><strong>References</strong></p><blockquote>1. Ben Thompson. Aggregation Theory. Accessed 2019. [https://stratechery.com/2015/aggregation-theory/](https://stratechery.com/2015/aggregation-theory/)</blockquote><blockquote>2. Kevin Sekniqi. Functionalization Theory. Accessed 2019. [https://kevin.sekniqi.com/functionalization-theory/](https://kevin.sekniqi.com/functionalization-theory/)</blockquote><h3>About AVA Labs:</h3><p>AVA Labs makes it simple to launch finance applications using blockchain technology–with highly scalable and efficient networks, customizable public and private blockchains, the capability to create any digital asset, and more. We are empowering people to build an open, simple, and democratic internet of finance.</p><p><a href="https://avalabs.org/">Website</a> | <a href="https://avalabs.org/whitepapers">Whitepapers</a> | <a href="https://twitter.com/avalabsofficial">Twitter</a> | <a href="https://discord.com/invite/ccc8vEP">Discord</a> | <a href="https://github.com/ava-labs">GitHub</a> | <a href="https://docs.avalabs.org/">Documentation</a> | <a href="https://www.avalabs.org/ava-x">AVA-X Accelerator</a> | <a href="https://t.me/avacoin_official">Telegram</a> | <a href="http://www.linkedin.com/company/avalabs/">LinkedIn</a> | <a href="https://www.reddit.com/r/ava/">Reddit</a> | <a href="http://facebook.com/avalabsofficial">Facebook</a> | <a href="http://www.youtube.com/c/AVAofficial">YouTube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1476a72b9c2b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avalancheavax/crypto-networks-killer-value-prop-1476a72b9c2b">Crypto Network’s Killer Value Prop</a> was originally published in <a href="https://medium.com/avalancheavax">Avalanche</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Safety and Liveness Trade-offs in Consensus Protocols]]></title>
            <link>https://medium.com/@kevinsekniqi/on-safety-and-liveness-trade-offs-in-consensus-protocols-23b9bbb61e38?source=rss-4fc0ad42ffa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/23b9bbb61e38</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Kevin Sekniqi]]></dc:creator>
            <pubDate>Thu, 23 May 2019 00:51:23 GMT</pubDate>
            <atom:updated>2019-05-24T17:17:29.361Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*3ja_I-Bq27vQzJKAOZLmDA.jpeg" /></figure><p>I wanted to (very) briefly discuss how consensus protocols can trade-off safety and liveness.</p><p>First, a brief primer into the two major classes of consensus, longest-chain and voting-based (quorum-based) protocols. Longest chains protocols work under the premise that the “true” chain (the globally distributed ledger) can be identified via the “heaviest-chain” rule, which is really a function that is defined differently based on the underlying consensus mechanism. Some longest-chain consensus protocols may use hash-power to attribute weight. This is what Nakamoto (Bitcoin) does. Due to some mathematical artifacts of their constructions, longest-chain protocols can only be safe <strong><em>and</em></strong> live if and only if a) we have a strictly synchronous network and b) the Byzantine presence is less than 1/2 of total network. This upper bound turns out to be <em>fundamental</em>, and can’t be broken. So, for example, Bitcoin is entirely unsafe under asynchrony. Voting-based protocols, on the other hand, work under a very different mechanism, which happens to be voting. There’s no weight and no longest chain, instead we simply finalize if we achieve a minimum required quorum. So while voting-based protocols work quite differently from longest-chain protocols, they similarly have fundamental limitations: in synchronous and asynchronous settings, they provide liveness and safety if and only if Byzantine presence is less than 1/2 and 1/3 of network size, respectively.</p><blockquote>This now brings us to the main topic of this post (and which seems to be unfamiliar with the community): <strong><em>these bounds are trade-able.</em></strong></blockquote><p>To demonstrate this briefly, I will focus on voting-based protocols in an asynchronous setting, whose bound is 1/3. Suppose that I have 100 nodes in the network. Then, I can construct a safe <em>and </em>live protocol if Byzantine nodes are at most 33/100, which means that I require a quorum of 67 nodes or more to agree on the same thing. To see why this works: let Byzantine nodes be 33, and correct nodes be 67. The Byzantine nodes can split the correct nodes into two groups of 34 and 33 nodes. Then, they can lie and create two groups of 67 and 66 nodes that agree on the same thing (34 correct + 33 Byz and 33 correct + 33 Byz, respectively). However, since quorum is at 67, only one of these two quorums can ever “win out” (the first one). And in fact, since Byz ≤ 33, and my quorum is at most 67, even if Byzantine nodes always just say random things, we can ignore them and have correct nodes still agree (<em>note</em>: <em>this hides</em> <em>a lot of complexity on how to get them to actually agree</em>).</p><p>But, suppose I want higher tolerance for Byzantine nodes in regards to safety. Then I can request <em>higher </em>quorum intersection, say 80 nodes (instead of 67). What does this mean? It means I can be safe even if Byzantine nodes are higher than 33 (as high as 59), but not be live. To see why this is the case, suppose Byz is 59, and correct is 41. Then, the Byz nodes can again split the correct nodes into two groups of 21 and 20, and create two quorum of 80 and 79 (59 Byz + 21 correct and 59 Byz + 20 correct, respectively). But, since quorum is minimum 80, again *only one of these two can win out*. Conversely, however, since the quorum is 80, I can only tolerate at most 21 Byzantine nodes that just say random things and prevent us from making progress. In summary: I can boost my quorum to 80/100, and get safety for at most 59/100 Byzantine nodes and liveness for at most 21/100 Byzantine nodes.</p><p>Now, this takes me to the final part of this post, which is in regards to the Avalanche consensus protocol. Avalanche consensus takes classical quorum-based voting protocols and <em>makes them probabilistic. </em>At a super high level, the subsampling of the core primitives buys you huge performance gains, but it also means that the bounds above are dampened. So, for example, if you parametrize the system for a quorum of 67%, instead of getting both safety and liveness with an adversary of 33%, you get slightly less (say around 30%, under some choice of sub-sampling and probability of failure). Avalanche chooses a purposefully higher quorum threshold (80%, minimum). The liveness bound, as above, is maximally about 20%, but due to dampening it is slightly lower (about 16%).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23b9bbb61e38" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>