Demo Data from EDBT 2026 / reviewers in the wild / expert
Rohan Shrothrium
dblp:407/8745
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2025
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Security and privacy · 1 · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Distributed systems › fault tolerance
byzantine fault tolerance |
0.9 | 1 | 2025 | Sailfish: Towards Improving the Latency of DAG-Based BFT · SP 2025 |
Distributed systems
consensus |
0.9 | 1 | 2025 | Sailfish: Towards Improving the Latency of DAG-Based BFT · SP 2025 |
Distributed systems › fault tolerance › byzantine fault tolerance
DAG-based consensus |
0.9 | 1 | 2025 | Sailfish: Towards Improving the Latency of DAG-Based BFT · SP 2025 |
Distributed systems › consensus
leader-based consensus |
0.9 | 1 | 2025 | Sailfish: Towards Improving the Latency of DAG-Based BFT · SP 2025 |
Methods — techniques the papers use, named apart from their topics
reliable broadcast · 0.9
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Sailfish: Towards Improving the Latency of DAG-Based BFTabstractDirected Acyclic Graph (DAG) based BFT protocols balance consensus efforts across different parties and maintain high throughput even when some designated parties fail. However, existing DAG-based BFT protocols exhibit long latency to commit decisions, primarily because they have a leader every 2 or more “rounds”. Recent works, such as Shoal (FC'23) and Mysticeti, have deemed supporting a leader vertex in each round particularly difficult, if not impossible. Consequently, even under honest leaders, these protocols require high latency (or communication complexity) to commit the proposal submitted by the leader (leader vertex) and additional latency to commit other proposals (non-leader vertices). In this work, we present Sailfish, the first DAG-based BFT that supports a leader vertex in each round. Under honest leaders, Sailfish maintains a commit latency of one reliable broadcast (RBC) round plus round plus$1\delta$to commit to commit the leader vertex (where$\delta$is the actual transmission latency of a message) and only an additional RBC round to commit non-leader vertices. We also extend Sailfish to Multi-leader Sailfish, which facilitates multiple leaders within a single round and commits all leader vertices in a round with a latency of one RBC round plus$1\delta$. Our experimental evaluation demonstrates that our protocols introduce significantly lower latency overhead compared to existing DAG-based protocols, with similar throughput. Nibesh Shrestha, Rohan Shrothrium, Aniket Kate, Kartik Nayak |
SP | 2 |