﻿<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Simplex Consensus</title>
    <link>https://simplex.blog/</link>
    <description>Recent content on Simplex Consensus</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://simplex.blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Protocol in a Nutshell</title>
      <link>https://simplex.blog/protocol/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://simplex.blog/protocol/</guid>
      <description>Protocol in a Nutshell # What is Consensus? # Consensus. (Also known as State Machine Replication, or the Permissioned Blockchain problem.1) We want a protocol that works as follows:
Setup. There are \(n\) players, \(f\) of whom are faulty. Here, we assume that \(f &amp;lt; n/3\), and that each of these faulty players are malicious (syn: Byzantine), and can deviate arbitrarily from the protocol. (Of course, one may not need to be so pessimistic about faulty behavior &amp;mdash; see Simplex for Crash Faults.</description>
    </item>
    
    <item>
      <title>Simplex for Crash Faults</title>
      <link>https://simplex.blog/crashfaults/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://simplex.blog/crashfaults/</guid>
      <description>Simplex for Crash Faults # It is easy to adapt Simplex to a setting with crash faults instead of byzantine faults. We interpret it as a natural extension of the original protocol. In the crash fault version of Simplex, we can eliminate an entire round of communication. The resulting protocol looks a lot like Log Paxos. Crash Faults vs Byzantine Faults # In weaker deployment settings (i.e. in datacenters), we may be more optimistic about the nature of faults.</description>
    </item>
    
  </channel>
</rs