Skip to content

More private sync using Electrum #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
afilini opened this issue Nov 18, 2020 · 0 comments
Open

More private sync using Electrum #176

afilini opened this issue Nov 18, 2020 · 0 comments
Labels
module-blockchain new feature New feature or request

Comments

@afilini
Copy link
Member

afilini commented Nov 18, 2020

The current syncing algorithm for Electrum (and Esplora) tries to minimize the number of requests made, with the disadvantage that the addresses are checked with the server sequentially, and the server could use that information to reduce the privacy of the user.

One mitigation could be to not ask for addresses sequentially and mix together both the external and internal addresses. This however makes it harder to find a sufficiently large gap without any utxo, which allows the sync to stop earlier, so it would probably translate to many more requests than what's necessary with the sequential process.

We could implement this with a flag that the user can switch to choose which "process" to use, the "fast" (but less private) one or the more private and slower one.

@afilini afilini added new feature New feature or request module-blockchain labels Nov 18, 2020
@afilini afilini mentioned this issue Nov 18, 2020
nickfarrow pushed a commit to nickfarrow/bdk that referenced this issue Feb 21, 2022
@notmandatory notmandatory moved this to Discussion in BDK Chain Mar 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module-blockchain new feature New feature or request
Projects
Status: Discussion
Development

No branches or pull requests

1 participant