Skip to content
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

Consensus Whitepaper #1363

Open
geo2a opened this issue Jan 23, 2025 · 0 comments · May be fixed by #1364
Open

Consensus Whitepaper #1363

geo2a opened this issue Jan 23, 2025 · 0 comments · May be fixed by #1364
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@geo2a
Copy link
Contributor

geo2a commented Jan 23, 2025

As part of creating the Cardano Blueprint, we need to draft a Consensus whitepaper. This document will give an overview of the Consensus component and make it easier to understand and provide guidance for:

  • People implementing alternative Cardano nodes.
  • Users of the Consensus functionality.
  • New contributors to ouroboros-consensus.

In addition, this document will help us elicit additional requirements for the Consensus documentation.

We should aim for an 8-10 pages high-level overview that:

  • describes the components of Consensus,
  • explains the Consensus layer, and how it relates to the Diffusion (aka Network) and Ledger layers,
  • contains diagrams,
  • would make it possible to develop a toy model of the Consensus layer.
@geo2a geo2a added the documentation Improvements or additions to documentation label Jan 23, 2025
@geo2a geo2a added this to the Unknown quarter milestone Jan 23, 2025
@geo2a geo2a self-assigned this Jan 23, 2025
@geo2a geo2a changed the title Draft the Consensus Whitepaper Consensus Whitepaper Jan 23, 2025
@geo2a geo2a linked a pull request Jan 23, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

1 participant