cryptoadvance / cryptoadvance/specter-desktop
Swan Integration - Addresses reserved vs Addr. used, seem +1 off
Open
extension
question
- Dominant language
- Python
- Stars
- 847
- Forks
- 259
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 2
Description
[Feedback](https://swanbitcoin.slack.com/archives/C0443TZ8PPY/p1667327707457269) from Swan customer via Brandon Quittem:
"Small bug within Specter integration.
The addresses reserved for Swan are not the ones being used used by Swan.
So far it seems like they are indexed +1 from the denoted reserved addresses."
Contributor guide
Research direction
No file, test, or entry point is named. Start by tracing the Swan integration's reserved-address and used-address handling, using the linked customer feedback and the reported +1 indexing discrepancy; done means the addresses reserved for Swan match those used by Swan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100