Section 11: beta to beta_dagga #248
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It is, but I'm not sure why we would use a later state item over an earlier one, since it suggests a dependency which does not exist. |
|
But if we adopt only one option that can reduce complexity and the chance of misunderstandings |
|
In the rest of the sections, there will be a clear sequence of state transition, except for this one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When working on extrinsics guarantee-related programs, I found that the beta state has two reference targets. However, the beta dagga should actually be applicable to all Section 11 extrinsics guarantee-related verification.
ref beta dagga here
https://graypaper.fluffylabs.dev/#/5f542d7/153201153301
but ref beta here
https://graypaper.fluffylabs.dev/#/5f542d7/15b10115ee01