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

Peer synchronization during consensus #5144

Open
mversic opened this issue Oct 10, 2024 · 0 comments
Open

Peer synchronization during consensus #5144

mversic opened this issue Oct 10, 2024 · 0 comments
Assignees
Labels
Consensus This issue is related to the Sumeragi consensus

Comments

@mversic
Copy link
Contributor

mversic commented Oct 10, 2024

We've always suffered from a risk that nodes can silently diverge but this has become especially evident after #4967.

The current algorithm works like this:

  1. Leader creates a block, signs and broadcasts it to all peers without validating transactions
  2. All peers (including Leader) validate block transactions independently of each other
  3. After validating transactions, Validating peers send their signatures to ProxyTail
  4. After ProxyTail has collected enough signatures it broadcasts confirmation to all peers

We need to modify this approach so that transaction errors are agreed and synchronized between the nodes. This must be done during the consensus round. We can't include transaction error into the block hash but we can protect them with block signatures.

@mversic mversic added the Consensus This issue is related to the Sumeragi consensus label Oct 10, 2024
@mversic mversic self-assigned this Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Consensus This issue is related to the Sumeragi consensus
Projects
None yet
Development

No branches or pull requests

1 participant