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

Should herald support --chain argument, or should the chain (aka env.coin) be inferred from DBState?

Open
#90 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start with the herald CLI shown in the issue and inspect how --db_dir, --chain, and DBState are handled, then compare that with the scribe --chain setting. Determine whether the chain can be reliably inferred from the database or whether the explicit argument must remain; done means the project has a decided behavior and corresponding documented or tested CLI expectations.

Written by the indexing model from the issue text.

Description

area: herald area: scribe type: improvement

In most cases the DB (--db_dir=X) will have been populated by scribe, and so it's the scribe --chain=Y argument that's determinative.

(venv) swdev1@Jonathans-Mac-mini hub % herald --help
usage: herald [-h] --db_dir DB_DIR [--reorg_limit REORG_LIMIT] [--chain {mainnet,regtest,testnet}] [--max_query_workers MAX_QUERY_WORKERS] [--cache_all_tx_hashes] [--cache_all_claim_txos]
..snip...
optional arguments:
  -h, --help            show this help message and exit
  --db_dir DB_DIR       Path of the directory containing lbry-rocksdb.
  --reorg_limit REORG_LIMIT
                        Max reorg depth
  --chain {mainnet,regtest,testnet}
                        Which chain to use, default is mainnet, others are used for testing
...snip...
Dominant language
Python
Stars
15
Forks
16
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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 lbryio/hub

All issues in lbryio/hub

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.