Skip to content

[draft] MD-118: Implications of L1 assumptions for postconfirmation protocol - #118

Closed
apenzk wants to merge 8 commits into
mainfrom
md/L1-and-postconfirmation
Closed

[draft] MD-118: Implications of L1 assumptions for postconfirmation protocol#118
apenzk wants to merge 8 commits into
mainfrom
md/L1-and-postconfirmation

Conversation

@apenzk

@apenzk apenzk commented Apr 5, 2025

Copy link
Copy Markdown
Contributor

Summary

MD-118

@l-monninger

l-monninger commented Apr 8, 2025

Copy link
Copy Markdown
Contributor

I think this should ask for a list of...

  • Safety assumptions (which components are safe) and to what extent.
  • Liveness assumptions (which components are live) and to what extent.
  • Synchrony assumptions (which components are synchronous) and to what extent.
  • Finality assumptions--when does finality occur and what exactly does it mean.

@l-monninger

Copy link
Copy Markdown
Contributor

Maybe #110 is a useful super framework to improve here?

@l-monninger

Copy link
Copy Markdown
Contributor

What is the weakest set of assumptions under which a given protocol works?

@apenzk

apenzk commented Apr 9, 2025

Copy link
Copy Markdown
Contributor Author

@l-monninger

Finality assumptions--when does finality occur and what exactly does it mean.

individually address this now as D3

Safety assumptions (which components are safe) and to what extent.
Liveness assumptions (which components are live) and to what extent.
Synchrony assumptions (which components are synchronous) and to what extent.

added.

What is the weakest set of assumptions under which a given protocol works?

added.

@apenzk apenzk closed this May 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants