Linked wallets are overwritten with new files.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Wallet files on Electrum 3.0 are loaded properly when they are linked to the file on let's say remote encrypted fs.
On exit, the wallet file gets re-created in destination folder (wallet). This cause the source file on encrypted fs to be left in old non-updated state and not linked to the wallet anymore.
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
No file or test is named. Start by tracing how Electrum loads linked wallet files and saves them on application exit, then reproduce the behavior with a wallet on a remote encrypted filesystem. Done means the linked source file remains the active, updated wallet rather than being replaced by a new destination file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100