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

[FEAT] - use Bitcoin Core's chain params for archival node size

Open
#1,501 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
shell

Research direction

Start by locating the archival-node size calculation in the repository, then compare its values with assumed_blockchain_size and assumed_chain_state_size in Bitcoin Core's src/kernel/chainparams.cpp. Verify that the requested parameters are sourced from Bitcoin Core and that the resulting archival node size is reported correctly.

Written by the indexing model from the issue text.

Description

feature
Describe the Problem

Using empirical data from my own archival node

Describe the Solution

Use the hard-coded parameters in Bitcoin Core's source code:

curl -fsSL https://github.com/bitcoin/bitcoin/raw/master/src/kernel/chainparams.cpp | grep -A 100 CMainParams > /tmp/testfile
BITCOIN_CORE_BLOCKCHAIN_SIZE_IN_GIB="$(grep assumed_blockchain_size /tmp/testfile | cut -d= -f2 | tr -d ' ;')"
BITCOIN_CORE_CHAINSTATE_SIZE_IN_GIB="$(grep assumed_chain_state_size /tmp/testfile | cut -d= -f2 | tr -d ' ;')"
Optional Additional Details

No response

Dominant language
Shell
Stars
7
Forks
0
Avg merge
2h 38m
Merged PRs (30d)
30

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 bitcoin-tools/nodebuilder

All issues in bitcoin-tools/nodebuilder

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.