š
Original date posted:2022-05-02
š Original message:
Good morning John, and Laolu,
> > but instead the requirement to add several feature concepts to LN that
> > would allow tokens to interact with LN nodes and LN routing:
>
> From this list of items, I gather that your vision is actually pretty
> different from ours. Rather than update the core network to understand the
> existence of the various Taro assets, instead we plan on leaving the core
> protocol essentially unchanged, with the addition of new TLV extensions to
> allow the edges to be aware of and interact w/ the Taro assets. As an
> example, we wouldn't need to do anything like advertise exchange rates in
> the core network over the existing gossip protocol (which doesn't seem like
> the best idea in any case given how quickly they can change and the existing
> challenges we have today in ensuring speedy update propagation).
Adding on to this, the American Call Option problem that arises when using H/PTLCs: https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-December/001752.html
The above objection seems to be one reason for proposing multi-asset "on the edge" rather than have it widely deployed in the published Lightning Network.
Regards,
ZmnSCPxj
ZmnSCPxj [ARCHIVE] /
npub1g5ā¦3ms3l
2023-06-09 13:05:58
in reply to nevent1qā¦kwf5
Author Public Key
npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3lPublished at
2023-06-09 13:05:58Event JSON
{
"id": "3b5aea8f195423ff1e09c85c30f3efe09921d342503669c320197956b14ba407",
"pubkey": "4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861",
"created_at": 1686315958,
"kind": 1,
"tags": [
[
"e",
"cf879fa09974fcfb97798ad31f156a820bab60e7331398ab25b54b4e73bb33b9",
"",
"root"
],
[
"e",
"96750ce3e6a686a46cd5a4ac1acfd62c7d8b4e4584dccd75c866cf34a5e9fd57",
"",
"reply"
],
[
"p",
"2df3fc2660459521b852c995d4fc1a93938389a5e085677d0ebb33ef92cc5476"
]
],
"content": "š
Original date posted:2022-05-02\nš Original message:\nGood morning John, and Laolu,\n\n\u003e \u003e but instead the requirement to add several feature concepts to LN that\n\u003e \u003e would allow tokens to interact with LN nodes and LN routing:\n\u003e\n\u003e From this list of items, I gather that your vision is actually pretty\n\u003e different from ours. Rather than update the core network to understand the\n\u003e existence of the various Taro assets, instead we plan on leaving the core\n\u003e protocol essentially unchanged, with the addition of new TLV extensions to\n\u003e allow the edges to be aware of and interact w/ the Taro assets. As an\n\u003e example, we wouldn't need to do anything like advertise exchange rates in\n\u003e the core network over the existing gossip protocol (which doesn't seem like\n\u003e the best idea in any case given how quickly they can change and the existing\n\u003e challenges we have today in ensuring speedy update propagation).\n\nAdding on to this, the American Call Option problem that arises when using H/PTLCs: https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-December/001752.html\n\nThe above objection seems to be one reason for proposing multi-asset \"on the edge\" rather than have it widely deployed in the published Lightning Network.\n\nRegards,\nZmnSCPxj",
"sig": "6ec4e4ce58dcd39f0f0bd0fc754b1a14d0ef600517b3d2781d07b5a170cbd105b3eee0fd3f0708ba39273235b7b2043f052701b5c9e0102303e405a171236121"
}