<unnamed>

Public Key

npub1dnqu8va360ltnqewepgg5xqh2xdvs8t32tgvs5eaatz2ne6l2f6sna8mgc

Profile Code

nprofile1qqsxeswrkwca8l4esvhvs5y2rqt4rxkgr4c495xg2v77439fua04yagprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvunrzm8

Publishing to

relay.snort.social

Last Notes

2023-06-09 12:53:36 UTC

- reply

📅 Original date posted:2018-12-27
📝 Original message:
Very good point.
Two possible responses come to mind.
1. Cross-asset brokers charge a standard option premium to perform the brokerage. I can't tell if you think this is totally broken or if it's just sad. I don't understand lightning well enough to figure that out on my own - could you expand more on what effects this would have?
2. Cross-asset brokers require counterparties to issue them a symmetric but slightly more out-of-the-money call, which they can redeem in the event of a large FX swing. This bounds their FX losses.
Will
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, December 27, 2018 1:43 PM, ZmnSCPxj via Lightning-dev <lightning-dev at lists.linuxfoundation.org> wrote:
> HTLCs allow creation of American Call Options.

2023-06-09 12:48:35 UTC

- reply

📅 Original date posted:2018-01-16
📝 Original message:
I agree. Negative shadow prices are incredibly important for optimality of constrained network markets where flows in opposite directions cancel (as is the case with lightning). See for example FTRs. It’s unclear to me how well the analogy holds, but it’s worth considering.
—Will
On Tue, Jan 16, 2018 at 3:32 PM, Benjamin Mord <ben at mord.io> wrote:
> Thanks. It sounds like it was dropped due to difficulty in the routing protocol. Is that difficulty documented somewhere I can review? If so, I might take a crack at a solution to it. But regardless I suggest the protocol should support negative fees, even if an individual routing implementation prefers to treat as 0 for simplicity. That should be up to the implementation I think, and not a protocol constraint.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180116/b22f2a29/attachment-0001.html>