From aj at erisian.com.au Sun Aug 30 00:51:54 2015 From: aj at erisian.com.au (Anthony Towns) Date: Sun, 30 Aug 2015 10:51:54 +1000 Subject: [Lightning-dev] A state machine. In-Reply-To: References: <87si7eiehg.fsf@rustcorp.com.au> <87h9ntifwf.fsf@rustcorp.com.au> <877fopi4un.fsf@rustcorp.com.au> <20150829074239.GA15643@navy> Message-ID: On 29 August 2015 at 22:50, Pierre wrote: > Hi Anthony, > Your svg looks great, thanks for sharing ! > ?Yeah, I like it :) > Regarding the init phase, you seem to be making the assumption that > whoever initiates a channel will be the one funding it. But that's not > necessarily the case if the requester is a merchant who will only receive > payments right ? > Yeah, kind-of. I figure that whoever is providing the anchor will want to make a decision beforehand (rather than just have software do that automatically when a particular packet comes in), and they'll indicate they want to proceed by issuing a "cmd_init_with_my_anchor". Maybe there's some negotiation before that (someone registers on your website, or whatever eg), but I figure that's out-of-band. If you're a merchant, I think it would either be: a) register with paypal, paypal anchors the channel b) merchant anchors the channel with random hub, merchant has all the funds, suggests rebalancing via the blockchain with the hub, rebalancing protocol happens c) merchant anchors the channel, merchant does a HTLC to: - their account on an exchange - their "cold wallet" lightning channel - something else moving all the funds to the other side of their channel and voila, they can receive funds. Of course we can make this initial funding as low as we want, then have the > lightning node fund the channel... > ?You can't increase the capacity of a channel easily -- you need a new anchor transaction for that...? ?Cheers, aj? -- Anthony Towns -------------- next part -------------- An HTML attachment was scrubbed... URL: