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

move quorum driver from its own crate to sui-core #4611

Merged
merged 1 commit into from
Sep 14, 2022

Conversation

longbowlu
Copy link
Contributor

This PR simply moves quorum drive from its own crate to sui-core. The main reason for this change is we'd like to make integrate quorum drive with other components in sui-core (e.g. node sync) to proactively execute finalized txns locally.

Today quorum-driver depends on sui-core, the integration will make sui-core depend on quorum-driver forming a circular dependency.

@mystenmark
Copy link
Contributor

I have no problem with moving this code, but can you explain what you mean by integrating with node sync? I don't think any integration with that component per se will be required. Instead, QD should only interface with AuthorityState - just call handle_node_sync_certificate once you have the effects cert.

@mystenmark
Copy link
Contributor

just call handle_node_sync_certificate once you have the effects cert.

On second thought, you do probably want to use node sync, in case there are missing dependencies.

@longbowlu longbowlu merged commit 21d1853 into main Sep 14, 2022
@longbowlu longbowlu deleted the move-quorum-driver-to-sui-core branch September 14, 2022 23:56
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