config: cleanup
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
The issue names no files, tests, or entry points. Start by locating the hardcoded network, amounts, key pairs, and RPC configuration, then trace how callers construct and use the library; done means callers can provide each of these values without changing library code.
Written by the indexing model from the issue text.
Description
Some variables that should be configurable but are currently hardcoded:
- network
- amounts
- key pairs
- rpc config
These should be configurable by callers of the library.
- Dominant language
- Go
- Stars
- 58
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from evstack/bitcoin-da
-
Tests failing in CI Open
evstack/bitcoin-da#27 · 1 assignee ·
-
evstack/bitcoin-da#25 · 1 assignee ·
-
feat: namespaces Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
evstack/bitcoin-da#20 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
evstack/bitcoin-da#12 ·
-
docs: spec Open
Difficulty 3/5 1-2 days Newbie friendliness 30/100
evstack/bitcoin-da#8 ·
All issues in evstack/bitcoin-da
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100