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

Should -d flag just be a -i string input

Open
#10 2 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
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli, cryptography

Research direction

Start by tracing the CLI argument parsing and the existing handling of -d and -i. Compare the documented manual behavior with the implementation and current tests, then confirm whether -d should become the -i seedphrase input described in the issue. Done means the interface is consistent and its behavior is covered by tests or documentation.

Written by the indexing model from the issue text.

Description

As is becoming clear when I'm writing out the manual, -d is really just a different way to randomly seed a seed, like -i dice, -i cards, etc. Consistency would suggest it should be -i seedphrase.

Dominant language
Rust
Stars
11
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

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 BlockchainCommons/seedtool-cli-rust

All issues in BlockchainCommons/seedtool-cli-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.