{"type":"rich","version":"1.0","author_name":"npub17fjkngg0s0mfx4uhhz6n4puhflwvrhn2h5c78vdr5xda4mvqx89swntr0s","author_url":"https://nostr.ae/npub17fjkngg0s0mfx4uhhz6n4puhflwvrhn2h5c78vdr5xda4mvqx89swntr0s","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2019-12-17\n📝 Original message:\nThanks a lot David for the suggestion and pointers, that's a really\ninteresting solution.\nI will dive into that in-depth, it could be very useful for many layer-2\nconstructions.\n\nThanks ZmnSCPxj as well for the quick feedback and the `OP_CAT`\nconstruction,\na lot of cool tricks coming up once (if?) we have such tools in the future\n;)\n\nLe mar. 17 déc. 2019 à 16:14, ZmnSCPxj \u003cZmnSCPxj at protonmail.com\u003e a écrit :\n\n\u003e Good morning David, t-bast, and all,\n\u003e\n\u003e\n\u003e \u003e I'm not aware of any way to currently force single-show signatures in\n\u003e \u003e Bitcoin, so this is pretty theoretical. Also, single-show signatures\n\u003e \u003e add a lot of fragility to any setup and make useful features like RBF\n\u003e \u003e fee bumping unavailable.\n\u003e\n\u003e With `OP_CAT`, we can enforce that a particular `R` is used, which allows\n\u003e to implement single-show signatures.\n\u003e\n\u003e     # Assuming signatures are the concatenation of (R,s)\n\u003e     \u003cR\u003e OP_SWAP OP_CAT \u003cACINQ\u003e OP_CHECKSIG\n\u003e\n\u003e The above would then feed `s` only on the witness stack.\n\u003e\n\u003e Regards,\n\u003e ZmnSCPxj\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20191217/b717706a/attachment.html\u003e"}