📅 Original date posted:2011-06-22
🗒️ Summary of this message: A proposed method for reducing address length in Bitcoin transactions may not be practical due to the need to distribute pubkeys ahead of time.
📝 Original message:> Gavin said:
>> 3DUP ADD ADD HASH160 ...hash(pubkey1+2+3)... EQUALVERIFY 2 3 ROLL
>> CHECKMULTISIGVERIFY
On second thought, I'm not sure this is workable. You would have to
distribute each party's pubkey ahead of time, otherwise you run the risk
that a party falls off the face of the earth and then you can't provide
the pubkeys to have hash(pubkey1+2+3) EQUALVERIFY.
If you have to distribute the pubkeys ahead of time, then the reduction in
address length becomes moot.
So it seems to be either distribute the pubkeys or distribute the
hash160(pubkey)'s.
--
Bobby Groff
bgroff at lavabit.com [ARCHIVE] /
npub1ls…zmjm0
2023-06-07 01:38:10
in reply to nevent1q…d2wz
Author Public Key
npub1lsuxxpc34zcm7966h6d59zamdhkztgum70t44ydyz8eqf9p9w2jq3zmjm0Published at
2023-06-07 01:38:10Event JSON
{
"id": "9bc3b42023d23b1508df6d8ff2b24f6b71e9eea9ddf4c4afa32e0cb8d7588363",
"pubkey": "fc38630711a8b1bf175abe9b428bbb6dec25a39bf3d75a91a411f204942572a4",
"created_at": 1686101890,
"kind": 1,
"tags": [
[
"e",
"f8aa9d5975dbd3062e3c6c30dcbe2bf4909da9f4f0e974b1d2c55be2b94a5b11",
"",
"root"
],
[
"e",
"327aad051f5171dd4780f133bf81fc457d4e0d4b5ef25ebfe363b88624c0ff41",
"",
"reply"
],
[
"p",
"fc38630711a8b1bf175abe9b428bbb6dec25a39bf3d75a91a411f204942572a4"
]
],
"content": "📅 Original date posted:2011-06-22\n🗒️ Summary of this message: A proposed method for reducing address length in Bitcoin transactions may not be practical due to the need to distribute pubkeys ahead of time.\n📝 Original message:\u003e Gavin said:\n\u003e\u003e 3DUP ADD ADD HASH160 ...hash(pubkey1+2+3)... EQUALVERIFY 2 3 ROLL\n\u003e\u003e CHECKMULTISIGVERIFY\n\nOn second thought, I'm not sure this is workable. You would have to\ndistribute each party's pubkey ahead of time, otherwise you run the risk\nthat a party falls off the face of the earth and then you can't provide\nthe pubkeys to have hash(pubkey1+2+3) EQUALVERIFY.\n\nIf you have to distribute the pubkeys ahead of time, then the reduction in\naddress length becomes moot.\n\nSo it seems to be either distribute the pubkeys or distribute the\nhash160(pubkey)'s.\n\n--\nBobby Groff",
"sig": "335e7f9fd666fe81042ddba2f66c2d9e6d6b72d471f9e0eb421a6bd11bcbf15448af1be7cc6ee0fe17a7e5923e762568f3f0b843ccf3c897b767813dccbed6df"
}