Re: [Lightning-dev] Proposal to include some form of best effort routing, fragmentation and local AMP

2018-11-16 Thread ZmnSCPxj via Lightning-dev
Good morning Rene, Packet switching could theoretically be done if switching ephkeys were possible, which would be needed for rendezvous nodes anyway. An intermediate node is handed an opaque onion and the node to give that onion to, which, when you squint, is what the payer is given in the

Re: [Lightning-dev] Base AMP

2018-11-16 Thread Anthony Towns
On Thu, Nov 15, 2018 at 11:54:22PM +, ZmnSCPxj via Lightning-dev wrote: > The improvement is in a reduction in `fee_base_msat` in the C->D path. I think reliability (and simplicity!) are the biggest things to improve in lightning atm. Having the flag just be incuded in invoices and not need

Re: [Lightning-dev] Packet switching via intermediary rendezvous node

2018-11-16 Thread Anthony Towns
On Thu, Nov 15, 2018 at 07:24:29PM -0800, Olaoluwa Osuntokun wrote: > > If I'm not mistaken it'll not be possible for us to have spontaneous > > ephemeral key switches while forwarding a payment > If this _was_ possible, then it seems that it would allow nodes to create > unbounded path lengths

Re: [Lightning-dev] type,len,value standard

2018-11-16 Thread Christian Decker
Conner Fromknecht writes: >> For a sequence of `type,len,value`, the `type`s must be in ascending order >> -- not explicitly accepted or rejected. It would be easier to check >> uniqueness > (the previous rule we accepted) here for a naive parser (keep >> track of some "minimum allowed type"

Re: [Lightning-dev] Splicing Proposal: Now with RBF

2018-11-16 Thread ZmnSCPxj via Lightning-dev
Good morning Rusty, > I tried to simplify RBF as much as possible; it adds a lot of > complexity :( In particular, below we have one side pay the fees (and > thus responsible for RBF), in violation of the summit agreement, > and simplified the fee amount as much as reasonable. This

Re: [Lightning-dev] Strawman BOLT11 static "offer" format using probes.

2018-11-16 Thread René Pickhardt via Lightning-dev
Dear Rusty, I am not getting this proposal (maybe I am lacking some technical basic understandings) however I decided to ask more questions in order to complete my onboarding process faster and hope this is fine. My problem starts with the fact that I can't find the term "lightning probe

[Lightning-dev] Proposal to include some form of best effort routing, fragmentation and local AMP

2018-11-16 Thread René Pickhardt via Lightning-dev
Good morning list, in Adelaide I had a long conversation with another participant who complained that slow payments and failing payments are still a major UX issue for people that try to use the lightning network. While I believe this is a very valid point and we might want to think heavily about

Re: [Lightning-dev] Strawman BOLT11 static "offer" format using probes.

2018-11-16 Thread ZmnSCPxj via Lightning-dev
Good morning Rene, Not Rusty, but I shall spam the list as for my normal habit anyway. >My problem starts with the fact that I can't find the term "lightning probe >message" in the current BOLTs (actually the term probe only occures two >times and these seem unrelated to what you are talking

Re: [Lightning-dev] Approximate assignment of option names: please fix!

2018-11-16 Thread ZmnSCPxj via Lightning-dev
Good morning, I believe this is simply an argument about meanings of words; to me spontaneous means that the payee does not generate a new secret to be sold as a valuable good in exchange for money, using the mechanisms for routing on Lightning. In any case, it would still be possible to

Re: [Lightning-dev] Approximate assignment of option names: please fix!

2018-11-16 Thread Olaoluwa Osuntokun
> OG AMP is inherently spontaneous in nature, therefore invoice might not exist > to put the feature on. That is incorrect. One can use an invoice along with AMP as is, in order to tag a payment. As an example, I want to deposit to an exhcange, so I get an invoice from them. I note that the