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.

Sign up for GitHub

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

Jump to bottom

0-conf channel opening #4136

Closed
nicolasburtey opened this issue Apr 1, 2020 · 4 comments
Closed

0-conf channel opening #4136

nicolasburtey opened this issue Apr 1, 2020 · 4 comments
Labels
enhancement Improvements to existing features / behaviour feature request Requests for new features funding Related to the opening of new channels with funding transactions on the blockchain

Comments

@nicolasburtey
Copy link

Background

Be able to operate a channel before it's funding transaction gets mined.

Your environment

  • version of btcd, bitcoind, or other backend

I would assume this would only work with btcd or bitcoind, as lnd don't received data from mempool AFAIK. and 0-conf channel required mempool data

Expected behavior

Currently, the min-channel size is 1. I'd like to understand how to have 0 instead.

I know it's not for every use cases, but for some use case this makes sense (ie: Phoenix wallet does this, and it shifts the trust assumption from "trustless" to trust-minimized)

This would assume both nodes want to operate with this particular flag/mode, and as I guess this would not be compliant to bolt.
@Roasbeef Roasbeef added enhancement Improvements to existing features / behaviour feature request Requests for new features funding Related to the opening of new channels with funding transactions on the blockchain labels Apr 1, 2020
@nicolasburtey
Copy link
Author

I started looking at the code and I guess the action lies in fundingmanager.go.

One of my first interrogations is regarding pendingChanID. I guess we need to abstract this?

I’ll continue digging in in the upcoming days, but I’d love to have some feedback around this.

@halseth
Copy link
Contributor

halseth commented Jul 20, 2020

Related: #4424

@tvolk131
Copy link
Contributor

Related: #5955

@morehouse
Copy link
Collaborator

Another zeroconf issue I think we can close.

@guggero guggero closed this as completed Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Improvements to existing features / behaviour feature request Requests for new features funding Related to the opening of new channels with funding transactions on the blockchain
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Roasbeef @guggero @halseth @nicolasburtey @tvolk131 @morehouse