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

Update move.md #740

Merged
merged 1 commit into from
Mar 10, 2022
Merged

Update move.md #740

merged 1 commit into from
Mar 10, 2022

Conversation

Clay-Mysten
Copy link
Contributor

Fix "Let use" typo

Fix "Let use" typo
@Clay-Mysten Clay-Mysten merged commit e6244ce into main Mar 10, 2022
@Clay-Mysten Clay-Mysten deleted the Clay-Mysten-patch-6 branch March 10, 2022 23:27
mwtian added a commit to mwtian/sui that referenced this pull request Sep 29, 2022
…tarting round (MystenLabs#848)

Part 1/n of MystenLabs#740

This PR adds logic to `BlockSynchronizer` to broadcast a request to fetch certificate digests with a starting round, and collect valid certificate digests from the received responses.

High level overview of the algorithm (as discussed with @huitseeker):
1. When a primary needs to sync a range of certificates, it first finds the last round of certificate it has. Then it broadcasts a requests to synchronize certificate from higher rounds (last round + 1).
2. Other primaries / authorities will reply with certificate digests at or above the requested round (to be implemented later).
3. The requesting primary will collect the responses until heard from all, or timeout. Then, certificate digests having collected stakes above the committee validity threshold (f + 1 stake) are considered valid. Valid digests are returned.

Notably, this PR does not contain the logic to handle the range sync request on primary, or the logic to drive fetching certificates based on the valid digests.

A unit test is added for the happy path.
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.

None yet

2 participants