📅 Original date posted:2021-02-08
📝 Original message:
Hey ZmnSCPxj,
Am I correct in understanding that this is a proposal to change the spec
(maybe add a new BOLT) so that all lightning implementations can try to
support this feature.
If the above is true, then I'm wondering: could a Lightning-based escrow
system be implemented that doesn't require to modify the existing
implementations? Maybe if we simplify the requirements a bit? Like,
removing the "Escrow only learns of dispute cases, never learns non-dispute
case" aspect? That is, the third-party S always knows about an escrow
between A and B taking place.
I understand that the above requirement is a good to have, but if removing
it allows a simpler version of escrow be implemented, then at least there
could be an interim solution for non-custodial exchanges to start adopting
this (otherwise they have to resort to custodial-based escrows, which is
worse than lacking the escrow privacy brought by the requirement above).
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20210208/7070bbe6/attachment.html>;
Andrés G. Aragoneses [ARCHIVE] /
npub13e…tkq6u
2023-06-09 13:01:57
in reply to nevent1q…6pet
Author Public Key
npub13e0usm0e4q8qmxvgyq85xapy84hrsks3yp376dqx0ma5ahedsq4s2tkq6uPublished at
2023-06-09 13:01:57Event JSON
{
"id": "54e792eb11dd989b7423df868f7b625033a675fbd460ad3fe472402d9391f635",
"pubkey": "8e5fc86df9a80e0d9988200f4374243d6e385a112063ed34067efb4edf2d802b",
"created_at": 1686315717,
"kind": 1,
"tags": [
[
"e",
"314d09df8983f36a6cfef295360e46d7142fc01ed765a13fbdab5e1db6b5c415",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2021-02-08\n📝 Original message:\nHey ZmnSCPxj,\n\nAm I correct in understanding that this is a proposal to change the spec\n(maybe add a new BOLT) so that all lightning implementations can try to\nsupport this feature.\n\nIf the above is true, then I'm wondering: could a Lightning-based escrow\nsystem be implemented that doesn't require to modify the existing\nimplementations? Maybe if we simplify the requirements a bit? Like,\nremoving the \"Escrow only learns of dispute cases, never learns non-dispute\ncase\" aspect? That is, the third-party S always knows about an escrow\nbetween A and B taking place.\n\nI understand that the above requirement is a good to have, but if removing\nit allows a simpler version of escrow be implemented, then at least there\ncould be an interim solution for non-custodial exchanges to start adopting\nthis (otherwise they have to resort to custodial-based escrows, which is\nworse than lacking the escrow privacy brought by the requirement above).\n\nThanks\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20210208/7070bbe6/attachment.html\u003e",
"sig": "671a0ff370a260eaa218d3ba085186fedf7c39cb330affcaf63325783823810b10d706fe701fa5fa8f5092c0c83e6f9afcf2dd3c71ff836dbbeb09a3836d42ac"
}