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

Handle Active Leaves update in collator protocol #3829

Conversation

kishansagathiya
Copy link
Contributor

Handling active leaves updates are quite important in collator protocol since

  • It tells us which relay parents to remove or add
  • which candidates to add or remove
  • Most importantly it leads us to letting us know as a validator which parachain we are assigned to.

This commit add logic to react to active leaves update by

  • updating view
  • updating active leaves
  • updating our parachain assignments

Changes

Tests

go test -tags integration github.com/ChainSafe/gossamer

Issues

linked to issue #3515

Primary Reviewer

@axaysagathiya

This commit introduces collator side of the collator protocol. This is just a skeleton that
- implements the SubSystem interface for the new subsystem
- registers it
- add common methods like processMessage

linked to issue #3824
Subsystems needs to know about the peers in collation and validation protocol.
This commit
- adds logic to network package for emitting network events when a new peer joins or a peer disconnects.
- introduces a method to get a channel that will give us network events.
- make collator protocol validator side listen to these events and react to it by editing its peer data

Linked to issue #3515
Handling active leaves updates are quite important in collator protocol since
- It tells us which relay parents to remove or add
- which candidates to add or remove
- Most importantly it leads us to letting us know as a validator which parachain we are assigned to.

This commit add logic to react to active leaves update by
- updating view
- updating active leaves
- updating our parachain assignments

linked to issue #3515
dot/parachain/collator-protocol/validator_side.go Outdated Show resolved Hide resolved
dot/parachain/collator-protocol/validator_side.go Outdated Show resolved Hide resolved
dot/parachain/collator-protocol/validator_side.go Outdated Show resolved Hide resolved
dot/parachain/collator-protocol/validator_side.go Outdated Show resolved Hide resolved
dot/parachain/collator-protocol/validator_side.go Outdated Show resolved Hide resolved
dot/parachain/collator-protocol/validator_side.go Outdated Show resolved Hide resolved
dot/parachain/collator-protocol/validator_side.go Outdated Show resolved Hide resolved
kishansagathiya and others added 5 commits April 4, 2024 16:57
Co-authored-by: Eclésio Junior <eclesiomelo.1@gmail.com>
Co-authored-by: Eclésio Junior <eclesiomelo.1@gmail.com>
…github.com:ChainSafe/gossamer into kishan/feat/active-leaves-update-collator-protocol
Copy link
Member

@EclesioMeloJunior EclesioMeloJunior left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Base automatically changed from kishan/feat/network-events-collator-protocol to feat/parachain April 22, 2024 08:46
@kishansagathiya kishansagathiya merged commit 2866c9c into feat/parachain Apr 24, 2024
20 of 21 checks passed
@kishansagathiya kishansagathiya deleted the kishan/feat/active-leaves-update-collator-protocol branch April 24, 2024 06:29
timwu20 pushed a commit that referenced this pull request Jun 17, 2024
)

Handling active leaves updates are quite important in collator protocol since
- It tells us which relay parents to remove or add
- which candidates to add or remove
- most importantly it leads us to letting us know as a validator which parachain we are assigned to.

This commit add logic to react to active leaves update by
- updating view
- updating active leaves
- updating our parachain assignments

Issue #3515
timwu20 pushed a commit that referenced this pull request Jun 17, 2024
)

Handling active leaves updates are quite important in collator protocol since
- It tells us which relay parents to remove or add
- which candidates to add or remove
- most importantly it leads us to letting us know as a validator which parachain we are assigned to.

This commit add logic to react to active leaves update by
- updating view
- updating active leaves
- updating our parachain assignments

Issue #3515
timwu20 pushed a commit that referenced this pull request Jun 20, 2024
)

Handling active leaves updates are quite important in collator protocol since
- It tells us which relay parents to remove or add
- which candidates to add or remove
- most importantly it leads us to letting us know as a validator which parachain we are assigned to.

This commit add logic to react to active leaves update by
- updating view
- updating active leaves
- updating our parachain assignments

Issue #3515
kishansagathiya added a commit that referenced this pull request Jul 15, 2024
)

Handling active leaves updates are quite important in collator protocol since
- It tells us which relay parents to remove or add
- which candidates to add or remove
- most importantly it leads us to letting us know as a validator which parachain we are assigned to.

This commit add logic to react to active leaves update by
- updating view
- updating active leaves
- updating our parachain assignments

Issue #3515
kishansagathiya added a commit that referenced this pull request Jul 15, 2024
)

Handling active leaves updates are quite important in collator protocol since
- It tells us which relay parents to remove or add
- which candidates to add or remove
- most importantly it leads us to letting us know as a validator which parachain we are assigned to.

This commit add logic to react to active leaves update by
- updating view
- updating active leaves
- updating our parachain assignments

Issue #3515
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.

4 participants