Commit-Boost and Preconfirmation #55
Open
Conversation
This file contains hidden or 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
Contributor
There was a problem hiding this comment.
- [ ] This is for commit-boost not preconfs
- Double check commit-boost api
- Check whether commit-boost have a limit of the number of commits
Talk to commit-boost guys about:
- checking our assumptions
- adding endpoint for posting/fetching proofs, and tx hashes
- Can we work with proxy keys? Or how do we know that we can skip the promise step?
- Slashing issues... commit boost protects us from contradicting commitments
Contributor
|
In order to continue to working on the SIP:
For both we need to add a Message Validation section. |
Contributor
|
If we add any arbitrary rate limit, until we have simulation or real life data, we should just have a placeholder for the limit |
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.
No description provided.