Testing current master with lethekit
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- blockchain, cli
Research direction
Start by reproducing test vector 2 with keytool's address-index, full-address-derivation-path, and address-pkh entry points, then trace how those commands select derivation paths and address formats. Compare the output with the reported 44h expectation and segwit observation; done means the behavior is clarified or corrected and covered by repeatable test vectors.
Written by the indexing model from the issue text.
Description
Abstract
Testing 7604c8089008896bf86c7c18c800aeb86fe5f83e
Test vector 1
seed_lethekit=$(seedtool --in ur ur:crypto-seed/oyadgdvlpfssfwmkztcebbnyzowkspnljlrhdkztykahhf)
keytool \
--seed $seed_lethekit \
--address-index '*' \
output-descriptor
result OK, matches with lethekit:
wpkh([b238a845/84h/0h/0h]xpub6D1GQL3S3qryEx5gQccdVB5Fy1ePkeDGU8bMmW1GKfDQvtBsbJ6FaaudsBphw2WwtjYyJ4ARR6Mh9ZRTTKqro6eZww2m6SVxG7WuY2DALVp/0/*)
Test vector 2
# address wpkh not supported only pkh and sh?
for (( i=0; i <= 9; ++i ))
do
keytool \
--seed 1eb5338edac6fae54cbb172091ae6c1a \
--address-index $i \
address-index \
full-address-derivation-path \
address-pkh
done
Result:
0
c1859926/84h/0h/0h/0/0
17u4HStkGWxJ5PtNqzCMEKRzaPJ8h35eBc
1
c1859926/84h/0h/0h/0/1
1JyxrbHYS7ZGhq68JewhJAMWka38Bv8tFw
2
Here I noticed no support for segwit addresses? Also, the output shows segwit derivation path (84h) when address-pkh specified (44h) -> Not OK.
You can generate more test vectors for a particular seed (e.g. lethekit_seed/mnemonic: together mail awful cradle scrub apart hip leader silk slice unusual embark) in https://iancoleman.io/bip39/
- Dominant language
- C++
- Stars
- 6
- Forks
- 5
- 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 BlockchainCommons/keytool-cli
-
Install on Sonoma Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
BlockchainCommons/keytool-cli#27 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
BlockchainCommons/keytool-cli#23 · 1 comment ·
-
--cosigner option? Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
BlockchainCommons/keytool-cli#13 · 1 comment ·
All issues in BlockchainCommons/keytool-cli
Similar issues
-
ai_reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ydb-platform/ydb#53869 · 3 comments ·
-
bug cert blocker needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
project-chip/connectedhomeip#74373 ·
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31035 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
vllm-project/vllm-ascend#17329 ·