Skip to content

Move discv4 tasks into spawned process #3389

Closed

Description

@ElFantasma

We should use spawned GenServers to migrate discv4 tasks in the same fashion we are doing that for p2p RLPxConnection. That way all communication between RLPxConnections and discv4 processes would be done through spawned messages and concurrency problems will be handled on spawned side. Ideally, all tokio references should disappear from ethrex codebase

Activity

  1. added this to the [L1] 5 - Syncing milestone on Sep 1, 2025
  2. ElFantasma commented on Sep 1, 2025

    @ElFantasma
    ContributorAuthor

    There is already a version of Discv4 on spawned Genservers but it needs some improvements.

    Refactor is in progress in refactor_discv4 branch (it branches from snap_sync_final).

  3. self-assigned this
    on Sep 1, 2025
  4. moved this to In Review in ethrex_l1on Sep 9, 2025
  5. added a commit that references this issue on Sep 10, 2025
    15d5844
  6. moved this from In Review to Done in ethrex_l1on Sep 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

L1Ethereum clientp2pIssues related to p2p networksyncingSnap sync, Full sync

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions