Benjamin Mord [ARCHIVE] on Nostr: 📅 Original date posted:2018-01-11 📝 Original message: Thanks Christian. I'm ...
📅 Original date posted:2018-01-11
📝 Original message:
Thanks Christian. I'm reading the BOLTs and reviewing source code now, so
perhaps my question / request will be more usefully specific once I've
finished that review. Sorry for being vague as to use case for now, let me
just point out that the concept of source routing opens up a lot of
potential use cases that involve collaborations with intermediaries of
various sorts, but for which flexible communication capability would be
desirable or required (unless you do that out-of-band, which would be so
messy as to largely defeat the point.)
I'm impressed so far by how cleanly and explicitly the BOLTs address
extensibility. I find that reassuring, many thanks to whoever applied their
technical creativity to this aspect.
Was there a BOLT #6?
On Thu, Jan 4, 2018 at 12:13 PM, Christian Decker <
decker.christian at gmail.com> wrote:
> Hi Benjamin,
>
> currently the only piece of information that is kept contstant along the
> entire route is the payment hash, and we will be removing that as well
> in order to further decorrelate hops of a payment and make it harder for
> forwarding nodes to collate hops into a route.
>
> As ZmnSCPxj has pointed out we do have the possibility of adding some
> information in the onion packet. You can even give every single hop its
> very specific information in the onion. Say for example you have a node
> that does currency conversion, you may specify the desired exchange rate
> in the onion.
>
> May I ask what use-case you are looking to implement using this feature?
>
> Cheers,
> Christian
>
> Benjamin Mord <ben at mord.io> writes:
> > Are there, or will there be, annotations one can add to a lightning
> > transaction that can be read by all intermediate nodes along a given
> route?
> > Conversely, can one add annotations readable only by certain specific
> known
> > (to sender) intermediate nodes?
> > _______________________________________________
> > Lightning-dev mailing list
> > Lightning-dev at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180111/011a25a2/attachment.html>;
📝 Original message:
Thanks Christian. I'm reading the BOLTs and reviewing source code now, so
perhaps my question / request will be more usefully specific once I've
finished that review. Sorry for being vague as to use case for now, let me
just point out that the concept of source routing opens up a lot of
potential use cases that involve collaborations with intermediaries of
various sorts, but for which flexible communication capability would be
desirable or required (unless you do that out-of-band, which would be so
messy as to largely defeat the point.)
I'm impressed so far by how cleanly and explicitly the BOLTs address
extensibility. I find that reassuring, many thanks to whoever applied their
technical creativity to this aspect.
Was there a BOLT #6?
On Thu, Jan 4, 2018 at 12:13 PM, Christian Decker <
decker.christian at gmail.com> wrote:
> Hi Benjamin,
>
> currently the only piece of information that is kept contstant along the
> entire route is the payment hash, and we will be removing that as well
> in order to further decorrelate hops of a payment and make it harder for
> forwarding nodes to collate hops into a route.
>
> As ZmnSCPxj has pointed out we do have the possibility of adding some
> information in the onion packet. You can even give every single hop its
> very specific information in the onion. Say for example you have a node
> that does currency conversion, you may specify the desired exchange rate
> in the onion.
>
> May I ask what use-case you are looking to implement using this feature?
>
> Cheers,
> Christian
>
> Benjamin Mord <ben at mord.io> writes:
> > Are there, or will there be, annotations one can add to a lightning
> > transaction that can be read by all intermediate nodes along a given
> route?
> > Conversely, can one add annotations readable only by certain specific
> known
> > (to sender) intermediate nodes?
> > _______________________________________________
> > Lightning-dev mailing list
> > Lightning-dev at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180111/011a25a2/attachment.html>;