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

Add manual coin selection for channel opening #234

Open
MaxHillebrand opened this issue Jan 9, 2020 · 2 comments
Open

Add manual coin selection for channel opening #234

MaxHillebrand opened this issue Jan 9, 2020 · 2 comments

Comments

@MaxHillebrand
Copy link

MaxHillebrand commented Jan 9, 2020

Feature Request

Manual coin selection is very useful to open a channel with only carefully selected utxos, which is good for privacy. I would like to have the option to select exactly which coins to use in the input of the channel opening transaction. Especially together with the Use All Funds option, this can create 1 input || 1 output channel openings.

@pm47
Copy link
Member

pm47 commented Jan 10, 2020

Have you considered using several distinct wallets ? You could do pretty much that. Granted, on a single phone that would require enabling gdrive backups which may be a no-go for you.

Side note: on Phoenix, since channels are always funded by our node, you don't leak any UTXOs when creating channels. You can also choose to empty your wallet over LN, which means that your UTXO set remains completely untouched during the whole lifecycle of the app. Caveat: in its current version Phoenix is less private than Eclair Mobile wrt LN payments.

@MaxHillebrand
Copy link
Author

Several wallets won't help much, because I will want to send and receive payments from any one of these channels. If I have 5 channels in 5 wallets, then I would have to provide 5 invoices to get the same routing success.

My usecase is rather simple:

  1. Send bitcoin from external wallet to eclair onchain
  2. Use exactly that coin that just got received to open a channel, 1 input || 1 output transaction

This is a generic user flow, and it would increase privacy tremendously.

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

No branches or pull requests

2 participants