Keybase generates invalid XLM addresses
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
My Keybase is generating invalid XLM address QR codes, on both Android app and MacOS app. I am advanced user. I don't know what else to write here to help you solve this bug. But if you want spesific info, please ask me questions.
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
Start by reproducing the generated XLM address QR codes in the Android and macOS apps, then check whether the decoded values are valid XLM addresses. Done means both apps generate QR codes that decode to valid XLM addresses; the issue names no files or tests, so locating the responsible entry points will require repository research.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, macos
- Domain
- blockchain, desktop-dev, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100