Neptune-Crypto/neptune-core

Populate mempool on new peer connection

Open

#31 opened on Aug 7, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (45 forks)auto 404
good first issue

Repository metrics

Stars
 (110 stars)
PR merge metrics
 (PR metrics pending)

Description

When a new peer is connected, the n most heavy transactions (highest fee per byte) should be shared. This should be done through a transaction ID where the receiver can then request the transaction if it does not know it.

n doesn't have to be more than 5 to ensure that not too much bandwidth is used.

Contributor guide

Research direction
Explore the existing mempool and peer connection code. Identify where transactions are stored and how peers communicate. Implement a function to select the top N transactions by fee per byte and send their IDs upon new connection. Then handle the request for unknown transactions.
Tech stack
rust
Domain
backendnetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60