paritytech / paritytech/host-rust-core
truapi-host: explain the capability limits of explicit mnemonic mode
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 10
- Forks
- 3
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 148
Description
Part of #517.
Context
An explicit mnemonic performs a read-only username lookup. An account without a registered username can still connect and perform basic signing, but account.getUserId() and ring-backed operations are unavailable.
Continuing in this limited mode is intentional. The current warning looks like an unexpected startup problem instead.
Required behavior
- CLI help states that full account functionality requires an already-registered identity.
- Startup reports whether username-dependent capabilities are available.
- A username-less signer gets a clear message naming the unavailable operations.
- Basic signing remains available.
- The CLI does not register or modify the supplied identity automatically.
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.
Research direction
Start with the explicit mnemonic path in truapi-host and trace its CLI help, startup warning, and username-less signer behavior. Verify registered and unregistered identities, username-dependent operations, basic signing, and the absence of automatic registration; done means the capability limits are clearly reported while signing remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100