{"type":"rich","version":"1.0","author_name":"npub1y22yec0znyzw8qndy5qn5c2wgejkj0k9zsqra7kvrd6cd6896z4qm5taj0","author_url":"https://nostr.ae/npub1y22yec0znyzw8qndy5qn5c2wgejkj0k9zsqra7kvrd6cd6896z4qm5taj0","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 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"}
