Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Liquid INV rate probably too low

Open
#1,243 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp

Research direction

Start in src/net_processing.cpp at the INVENTORY_BROADCAST_PER_SECOND definition and trace how the limit is applied to inventory broadcasts. Compare it with consensusParams.nPowTargetSpacing and the linked Bitcoin discussion; done means establishing an appropriate rate for Liquid's block interval and covering the resulting behavior with the relevant existing tests.

Written by the indexing model from the issue text.

Description

enhancement

https://github.com/ElementsProject/elements/blob/cfc10a5dd6c18db140dd1d1e94dfa8cad16bfe36/src/net_processing.cpp#LL136C1-L136C1

/** Maximum rate of inventory items to send per second.
 *  Limits the impact of low-fee transaction floods. */
static constexpr unsigned int INVENTORY_BROADCAST_PER_SECOND = 7;

Given liquid's higher block rate, this value should probably be higher (also probably true on Bitcoin itself) -- perhaps it should be coded as (4200 / consensusParams.nPowTargetSpacing) ?

Dominant language
C++
Stars
1.2k
Forks
418
Avg merge
1d 12h
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ElementsProject/elements

All issues in ElementsProject/elements

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.