oasisprotocol / oasisprotocol/oasis-sdk
signer-ledger doesn't follow ADR-0008
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 90
- Forks
- 35
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
we had built this before ADR-0008 https://github.com/oasisprotocol/oasis-core/blob/master/docs/adr/0008-standard-account-key-generation.md was decided, and it currently uses a different path (5 components) from what ADR-0008 prescribes (3 components)
and there are products out that use signer-ledger
so now what
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Read ADR-0008 and inspect signer-ledger's current five-component path. The issue does not identify files or tests; first establish the compatibility impact for existing products, then document an agreed migration or compatibility plan and its acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100