š
Original date posted:2022-10-19
š Original message:> Currently Lightning is somewhere around 15% of our total bitcoin
payments. This is very much not nothing, and all of us here want Lightning
to grow, but I think it warrants a serious discussion on whether we want
Lightning adoption to go to 100% by means of disabling on-chain commerce.
Is this about disabling "on-chain instant commerce"?
- Waiting for confirmation on-chain before shipping a product won't
change, normally it's 15 minutes or so. This doesn't change that.
- An easy way to cancel/rbf a transaction doesn't exist - like you said,
there's no UX for this now, and I don't anticipate one being broadly used
except by inter-exchange transfers, etc.
So what does this change?
- In the rare event that an RBF transaction is received where the fee
level means confirmation times will be slow a merchant will have to wait
very long for at least 1 confirmation, the merchant should alert the user
that the transaction may take longer than the BTC FX rate guarantee window,
and may require additional funds if FX rates change.
- Users with wallets that support RBF can now be encouraged to accelerate
the tx, with help and advice depending on their wallet, in order to lock in
the FX rates
- 0 conf is still viable strategy for releasing an order, as long as fees
are very high, and it's very likely to be included in the next block.
More fee analysis is needed to validate 0 conf and mitigate risks, but now
it is, at least, more "honest" to the true risks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20221019/2a1058ab/attachment-0001.html>;
Erik Aronesty [ARCHIVE] /
npub1y2ā¦5taj0
2023-06-07 23:14:37
in reply to nevent1qā¦n530
Author Public Key
npub1y22yec0znyzw8qndy5qn5c2wgejkj0k9zsqra7kvrd6cd6896z4qm5taj0Published at
2023-06-07 23:14:37Event JSON
{
"id": "643033c8d750b215b87a5b85431bcae81265116b749a33952effc9ea3d744dc3",
"pubkey": "22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa",
"created_at": 1686179677,
"kind": 1,
"tags": [
[
"e",
"946b9a8231803f73c278c08ca74b58bc34d6ba681eae8ff2a82e75b78f2e09ab",
"",
"root"
],
[
"e",
"67de08ecaca754968984119b92cca0485fbb250cb03616d5a078f4ea7240c1b0",
"",
"reply"
],
[
"p",
"6c4821c93cad469f3b37d8304ecd7384018a56f69f660bc5a92913288098623c"
]
],
"content": "š
Original date posted:2022-10-19\nš Original message:\u003e Currently Lightning is somewhere around 15% of our total bitcoin\npayments. This is very much not nothing, and all of us here want Lightning\nto grow, but I think it warrants a serious discussion on whether we want\nLightning adoption to go to 100% by means of disabling on-chain commerce.\n\nIs this about disabling \"on-chain instant commerce\"?\n\n - Waiting for confirmation on-chain before shipping a product won't\nchange, normally it's 15 minutes or so. This doesn't change that.\n\n - An easy way to cancel/rbf a transaction doesn't exist - like you said,\nthere's no UX for this now, and I don't anticipate one being broadly used\nexcept by inter-exchange transfers, etc.\n\nSo what does this change?\n\n - In the rare event that an RBF transaction is received where the fee\nlevel means confirmation times will be slow a merchant will have to wait\nvery long for at least 1 confirmation, the merchant should alert the user\nthat the transaction may take longer than the BTC FX rate guarantee window,\nand may require additional funds if FX rates change.\n\n - Users with wallets that support RBF can now be encouraged to accelerate\nthe tx, with help and advice depending on their wallet, in order to lock in\nthe FX rates\n\n - 0 conf is still viable strategy for releasing an order, as long as fees\nare very high, and it's very likely to be included in the next block.\n More fee analysis is needed to validate 0 conf and mitigate risks, but now\nit is, at least, more \"honest\" to the true risks.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20221019/2a1058ab/attachment-0001.html\u003e",
"sig": "763a09ad89aae815868d773dd99c3481cb3314405d7e2d4a1f3723b81c93eac1b4d41cf936ee07d75c647d2367fa084322877486cbd21d29d8f91fecb214316a"
}