-
Notifications
You must be signed in to change notification settings - Fork 23
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
Documentation about Praos and the HFC/civic time #1320
base: main
Are you sure you want to change the base?
Conversation
4cfc488
to
097eb92
Compare
097eb92
to
8d81472
Compare
I think this is ready for merge as-is (even despite a couple telling TODOs), unless you dislike how I resolved a couple of your comments. |
- {DespiteChainGrowthViolation}. | ||
All of the above must hold even in the presence of a Chain Growth violation, except switching from a chain that violates Chain Growth to one that does not is allowed to violate the RollbackInsensitiveTranslations subcase of ImmutableTranslations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems even less likely to me that this was a design goal as opposed to "chain growth violation tolerance in all circumstances" which is discussed in #1320 (comment)
What about just dropping this bullet point? The discussion about how the different HFC designs fare in case of chain growth violations is still useful I think, even if chain growth violation tolerance is/was not a design goal.
I've long wanted to write down the Cardano-specific instantiation of the Praos protocol theorem.
This is that document, plus some discussions related to work currently in the IOE innovation pipelines as well as some trade-offs I've been struggling to judge regarding the HFC's behaviors in disaster scenarios. The second document elaborates on the HFC concerns.