📅 Original date posted:2019-12-17
📝 Original message:
Thanks a lot David for the suggestion and pointers, that's a really
interesting solution.
I will dive into that in-depth, it could be very useful for many layer-2
constructions.
Thanks ZmnSCPxj as well for the quick feedback and the `OP_CAT`
construction,
a lot of cool tricks coming up once (if?) we have such tools in the future
;)
Le mar. 17 déc. 2019 à 16:14, ZmnSCPxj <ZmnSCPxj at protonmail.com> a écrit :
> Good morning David, t-bast, and all,
>
>
> > I'm not aware of any way to currently force single-show signatures in
> > Bitcoin, so this is pretty theoretical. Also, single-show signatures
> > add a lot of fragility to any setup and make useful features like RBF
> > fee bumping unavailable.
>
> With `OP_CAT`, we can enforce that a particular `R` is used, which allows
> to implement single-show signatures.
>
> # Assuming signatures are the concatenation of (R,s)
> <R> OP_SWAP OP_CAT <ACINQ> OP_CHECKSIG
>
> The above would then feed `s` only on the witness stack.
>
> Regards,
> ZmnSCPxj
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20191217/b717706a/attachment.html>;
Bastien TEINTURIER [ARCHIVE] /
npub17f…ntr0s
2023-06-09 12:57:48
in reply to nevent1q…pygk
Author Public Key
npub17fjkngg0s0mfx4uhhz6n4puhflwvrhn2h5c78vdr5xda4mvqx89swntr0sPublished at
2023-06-09 12:57:48Event JSON
{
"id": "13b8992ebb29706e5ac0a5f10dae7dfd4129b318359754647a5c489cb69c7e6b",
"pubkey": "f26569a10f83f6935797b8b53a87974fdcc1de6abd31e3b1a3a19bdaed8031cb",
"created_at": 1686315468,
"kind": 1,
"tags": [
[
"e",
"e45c5a8385868cf007616f6909d9e9621b3b808a38fc0e859d163cf4d778a1c0",
"",
"root"
],
[
"e",
"082fd02b4ca316876183fa687225a97ceaf662e2330a31870e36e30b3bc23240",
"",
"reply"
],
[
"p",
"4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861"
]
],
"content": "📅 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",
"sig": "524d30ee2c87e7d3654b8f0d5020da27aec0abffbb377dd6768f1fb1a63ed727ff1b335e0fdc461e61451e8d7e204e01132f7e6383cbe3a04e49d7adb37ab2dc"
}