Option to server fallback to next bookmarked server.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Everytime the server we use goes down for just 1h it causes a disproportionate amount of confusion for the users.
This is a situation where the end user is not the same as the person who's chosen the server,
This invariably lead to them switching to Automatic selection and compromise any privacy gain that was being achieved by using trusted servers.
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
The issue does not name files, tests, or entry points. Start by locating Electrum's server-selection and bookmarked-server logic, then determine how fallback should behave when a chosen server is unavailable. Done means a user can opt into trying the next bookmarked server without being switched to automatic selection, with tests covering the fallback behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100