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 | Espresso: a shared sequencer with a hotshot-style consensus |
|---|---|
| What the text proposes | Espresso publishes a shared sequencer: many rollups can take their order of transactions from one consensus, instead of each running a private mempool. |
| Who may write | Espresso Systems |
| What is settled | The sequencer consensus finalises an order. Each rollup derives its own state from the slice of that order it claims. |
| Load-bearing assumption | No latency number is stated here. |
| What this library says afterwards | A reading of the project's public design document. Not a copy, not a benchmark, and not an offer. |
| Rights | Official external source only |