Skip to content
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

broadcast new transactions only over tor directly to peers #1598

Open
AndySchroder opened this issue Jan 20, 2025 · 0 comments
Open

broadcast new transactions only over tor directly to peers #1598

AndySchroder opened this issue Jan 20, 2025 · 0 comments

Comments

@AndySchroder
Copy link

In sparrow wallet I'd like the ability to broadcast new transactions only over tor directly to peers and skip the normally configured blockchain server. Peers should be discovered using DNS seeds and/or manually configured. TOR stream isolation should be used for connection to each peer. We should also be able to choose if we don't want to use TOR but still broadcast to a specific node (see below for motivation on this).

Motivation for this is as follows:

I've created an enhanced a standalone tool that serves these needs (https://github.com/AndySchroder/bitcoin-submittx), but it would be really nice to have this feature built into sparrow wallet so that it can be used from a GUI and within Sparrow, you'd only have a single application that you would need and you don't need to deal with installing a bunch of dependencies since my tool uses python (which is uncompiled).

I'd like to be able to this feature with

  • Private electrum node
  • Public electrum node
  • Private bitcoin core node
    • If this option is selected, we should recommend setting walletbroadcast=0.
  • No bitcoin node

therefor, I don't think romanz/electrs#750 is the best way to solve this.

Also, since we we can open signed raw transactions without even having a wallet configured, we should be able to do so with this feature as well.

In addition to privacy, we may want to be able to broadcast to a different (potentially pruned and/or local) node that we own that has different fee limits and mempool size in order to workaround #1264 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant