📅 Original date posted:2022-05-07
📝 Original message:On Sat, May 7, 2022 at 5:52 AM <vjudeu at gazeta.pl> wrote:
> > Re-enabling OP_CAT with the exact same OP would be a hardfork, but
> creating a new OP_CAT2 that does the same would be a softfork.
>
> We have TapScript for that. OP_CAT is defined as OP_SUCCESS, it can be
> re-enabled in a soft-fork way. For now, OP_CAT in TapScript simply means
> "anyone can move those coins", so adding some restrictions is all we need
> to re-enable this opcode. Introducing OP_CAT2 is not needed at all, unless
> it will be totally different, but then it should not be named as OP_CAT2,
> but rather as OP_SOMETHING_ELSE, it depends how different it will be from
> OP_CAT.
>
Oh, well, I didn't know any of that. I guess it could be a modification of
OP_SUCCESS if it makes sense instead of a new opcode.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220507/6b3c1b24/attachment.html>;
Jorge Timón [ARCHIVE] /
npub1fx…cl2d8
2023-06-07 23:09:15
in reply to nevent1q…n29w
Author Public Key
npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8Published at
2023-06-07 23:09:15Event JSON
{
"id": "2a7d4e7927d6372482c56cd8435c9051cbada0c22226bb70571f85c963ff3cd3",
"pubkey": "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84",
"created_at": 1686179355,
"kind": 1,
"tags": [
[
"e",
"cbc59e6bdcc1bf5eb00c43b304431e89f4d455fde09436058aad561d6b24579e",
"",
"root"
],
[
"e",
"401f01736dcb15f6a62661c6718f50e1eb1aca595a6baaa0fd35f57427e42ed6",
"",
"reply"
],
[
"p",
"8d3cf7eba921036409f1fec074cf8cfd8925bc7cb18e35d358b1ccc89752ee32"
]
],
"content": "📅 Original date posted:2022-05-07\n📝 Original message:On Sat, May 7, 2022 at 5:52 AM \u003cvjudeu at gazeta.pl\u003e wrote:\n\n\u003e \u003e Re-enabling OP_CAT with the exact same OP would be a hardfork, but\n\u003e creating a new OP_CAT2 that does the same would be a softfork.\n\u003e\n\u003e We have TapScript for that. OP_CAT is defined as OP_SUCCESS, it can be\n\u003e re-enabled in a soft-fork way. For now, OP_CAT in TapScript simply means\n\u003e \"anyone can move those coins\", so adding some restrictions is all we need\n\u003e to re-enable this opcode. Introducing OP_CAT2 is not needed at all, unless\n\u003e it will be totally different, but then it should not be named as OP_CAT2,\n\u003e but rather as OP_SOMETHING_ELSE, it depends how different it will be from\n\u003e OP_CAT.\n\u003e\n\nOh, well, I didn't know any of that. I guess it could be a modification of\nOP_SUCCESS if it makes sense instead of a new opcode.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220507/6b3c1b24/attachment.html\u003e",
"sig": "1fd6b260c27f456f0df4e27bfa219d7b4aef95475ab9904f2ee0d96b84f16d7926a5b48dd3e40e4ff9f7e132348b0f929bfd23539da25b441e6730b7125c471e"
}