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

Leader fault detection and rotation within primary execution committee #340

Open
ryscheng opened this issue Jun 1, 2018 · 1 comment
Open
Labels
c:runtime/compute Category: runtime compute worker p:1 Priority: core feature

Comments

@ryscheng
Copy link
Contributor

ryscheng commented Jun 1, 2018

Any worker can act maliciously in an execution committee. The most problematic is the leader, who drives 1. transaction ordering/batching, 2. forwarding to other workers 3. coordinating commit-reveal, 4. storing states to storage.

Any of these steps can be mishandled. We need ways to

  • Detect faulty leaders
  • Prove the consensus layer of its faults
  • Rotate leaders to satisfy liveness
@ryscheng ryscheng changed the title Leader rotation within primary execution committee Leader fault detection and rotation within primary execution committee Jun 1, 2018
@ryscheng ryscheng added p:1 Priority: core feature c:runtime/compute Category: runtime compute worker labels Jun 1, 2018
@ryscheng ryscheng modified the milestones: Version A: MVP features + Testnet, Version A: Internal Testing Jun 1, 2018
@ryscheng-mobile ryscheng-mobile removed this from the Version A: Internal Testing milestone Jun 22, 2018
@kostko
Copy link
Member

kostko commented Jul 18, 2018

Leader rotation depends on #366.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:runtime/compute Category: runtime compute worker p:1 Priority: core feature
Projects
None yet
Development

No branches or pull requests

3 participants