Compare
Four documents, the same five questions.
No throughput league table and no yield. The cells are what this library is willing to say about the text.
| Question | Bullshark: DAG BFT Protocols Made Practical |
|---|---|
| What the text proposes | DAG-Rider is built for asynchrony and pays for it on the common path. Bullshark keeps a DAG and a local commit rule, but adds a fast path for when the network is timely. The paper also writes down a simpler partially synchronous version. |
| Who may write | Alexander Spiegelman, Neil Giridharan, Alberto Sonnino and Lefteris Kokoris-Kogias |
| What is settled | Vertices still form a round DAG by quoting a quorum of the previous round. |
| Load-bearing assumption | A reported transactions-per-second number in a paper is not a service level. |
| What this library says afterwards | The committee is known. Later chains that cite Bullshark still have to say how validators are chosen. |
| Rights | Official external source only |