Skip to content

DAG-based consensus #5375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
s8sato opened this issue Mar 18, 2025 · 0 comments
Open

DAG-based consensus #5375

s8sato opened this issue Mar 18, 2025 · 0 comments
Labels
Consensus This issue is related to the Sumeragi consensus Optimization Something isn't working as well as it should Performance non-functional research

Comments

@s8sato
Copy link
Contributor

s8sato commented Mar 18, 2025

Expected benefits:

  • 50% less memory usage by eliminating the need for backup mechanisms to handle soft forks.
  • 3× faster settlement finality by reducing required network messages from 5*2 to 3.
  • Reduced network traffic by eliminating transaction gossiping.
  • TPS scalability potentially proportional to the number of validators.

Core idea:

  • Instead of gossiping transactions, nodes create and broadcast their own blocks.
  • Commits are determined by supporting blocks backward in the graph rather than voting on blocks.

For more details, see Mysticeti, which inspired this approach.
Further research and likely some formal verification are required to ensure the algorithm's reliability before implementation.

References:

@s8sato s8sato added Consensus This issue is related to the Sumeragi consensus Optimization Something isn't working as well as it should Performance non-functional research labels Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Consensus This issue is related to the Sumeragi consensus Optimization Something isn't working as well as it should Performance non-functional research
Projects
None yet
Development

No branches or pull requests

1 participant