📅 Original date posted:2016-12-23
📝 Original message:The first issue is that doing two OP_SWAP's in a row will just return
you to the original state. The second issue is that all of them end up
hashing the same key, so anyone on the network can spend this output.
(See https://en.bitcoin.it/wiki/Script for a good resource on opcodes
and what each of them do. There are also a few simulators floating
around, but I can't recommend any in particular.)
Third, if you're concerned about exposing public keys, why not use a
P2SH script? That won't expose your public keys until you spend from
it.
On Thu, Dec 22, 2016 at 11:29 AM, Andrew via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> Hi
>
> Is there a worked out scriptPubKey for doing multisig with just hashes
> of the participants? I think it is doable and it is more secure to a
> compromised ECDSA. I'm thinking something like this for the
> scriptPubKey:
> 2 OP_SWAP OP_SWAP OP_SWAP OP_DUP OP_HASH160 <pubKeyHash1>
> OP_EQUALVERIFY OP_DUP OP_HASH160 <pubKeyHash2> OP_EQUALVERIFY OP_DUP
> OP_HASH160 <pubKeyHash3> OP_EQUALVERIFY 3 OP_CHECKMULTISIG
>
> and <sigs><pubkeys> for the scriptSig
>
> Can anyone confirm or send me a link to the worked out script?
>
> Thanks
>
> --
> PGP: B6AC 822C 451D 6304 6A28 49E9 7DB7 011C D53B 5647
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
Nick ODell [ARCHIVE] /
npub192…qwur0
2023-06-07 17:55:02
in reply to nevent1q…ftll
Author Public Key
npub192dh6dprqsvsrdeche436s9xunwnlyzpu7jl5j3d83nz62tgznrsnqwur0Published at
2023-06-07 17:55:02Event JSON
{
"id": "bad5278e11b9a335dbb1b273953470d0ac2056a66253a8d2f7c85696e87ed81b",
"pubkey": "2a9b7d3423041901b738be6b1d40a6e4dd3f9041e7a5fa4a2d3c662d296814c7",
"created_at": 1686160502,
"kind": 1,
"tags": [
[
"e",
"f9f1981bc1fd27c1193c617c13c87679227d52718c27bf55a35ec8757f453b54",
"",
"root"
],
[
"e",
"b3e1f0d84dd3e1d3064222b8f8cb6d90666797ae464b22caf2eff53fbc70067b",
"",
"reply"
],
[
"p",
"f9ca566c8a15d0510cba9326659e9d235ad5681c8eb6f5594af50b92b640fb66"
]
],
"content": "📅 Original date posted:2016-12-23\n📝 Original message:The first issue is that doing two OP_SWAP's in a row will just return\nyou to the original state. The second issue is that all of them end up\nhashing the same key, so anyone on the network can spend this output.\n(See https://en.bitcoin.it/wiki/Script for a good resource on opcodes\nand what each of them do. There are also a few simulators floating\naround, but I can't recommend any in particular.)\n\nThird, if you're concerned about exposing public keys, why not use a\nP2SH script? That won't expose your public keys until you spend from\nit.\n\nOn Thu, Dec 22, 2016 at 11:29 AM, Andrew via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e Hi\n\u003e\n\u003e Is there a worked out scriptPubKey for doing multisig with just hashes\n\u003e of the participants? I think it is doable and it is more secure to a\n\u003e compromised ECDSA. I'm thinking something like this for the\n\u003e scriptPubKey:\n\u003e 2 OP_SWAP OP_SWAP OP_SWAP OP_DUP OP_HASH160 \u003cpubKeyHash1\u003e\n\u003e OP_EQUALVERIFY OP_DUP OP_HASH160 \u003cpubKeyHash2\u003e OP_EQUALVERIFY OP_DUP\n\u003e OP_HASH160 \u003cpubKeyHash3\u003e OP_EQUALVERIFY 3 OP_CHECKMULTISIG\n\u003e\n\u003e and \u003csigs\u003e\u003cpubkeys\u003e for the scriptSig\n\u003e\n\u003e Can anyone confirm or send me a link to the worked out script?\n\u003e\n\u003e Thanks\n\u003e\n\u003e --\n\u003e PGP: B6AC 822C 451D 6304 6A28 49E9 7DB7 011C D53B 5647\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev",
"sig": "7e441b7094bfbab6e9b00a33fbdd00c3cbbb4f0e86c5af82c999cc1af05386ad8d74ff2f92fdec8c46c68f34fca0847d6bd6fe54808f9b57f98718672c7140d0"
}