ChainSafe / ChainSafe/gossamer

update `overseer::Seconded`

Open
#4,255 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
454
Forks
144
PR merge metrics
No merged PRs in 30d

Description

## Issue summary

Needed updates from the current code:
- Notify collation seconded (https://github.com/ChainSafe/gossamer/issues/4675)
- See if we've unblocked other collations for seconding.
- Dequeue next collation and fetch if prospective-candidate exists.

## Links

- https://github.com/paritytech/polkadot-sdk/blob/3ff1b1db36260cbc47297ab753e2dcec1f5999fd/polkadot/node/network/collator-protocol/src/validator_side/mod.rs#L1490

Contributor guide

Open the contributing guide

Research direction

Start by locating the overseer::Seconded implementation in gossamer and compare its behavior with the linked polkadot-sdk validator_side/mod.rs reference. Trace the collation-seconding flow and verify that collation-seconded notification, newly unblocked collations, and prospective-candidate dequeue and fetch behavior are covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.