š
Original date posted:2013-10-28
š Original message:Just an aside...
The 1BTC bountry John references below is a 1BTC P2SH output, where the
redeemScript he provided does hash to the expected value, and is itself a
2-of-3 multisig, with the following pubkeys, expressed as addresses:
1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
1FCYd7j4CThTMzts78rh6iQJLBRGPW9fWv
1GMaxweLLbo8mdXvnnC19Wt2wigiYUKgEB
By comparison, the signatories for the 4BTC bountry are:
1L9p6QiWs2nfinyF4CnbqysWijMvvcsnxe
1FCYd7j4CThTMzts78rh6iQJLBRGPW9fWv
1GMaxweLLbo8mdXvnnC19Wt2wigiYUKgEB
On the one hand, the vanity address makes it easy to guess who one of the
signatories is, on the other hand, is it bad form to reuse keys for
signing?
John, you mentioned wanting to disambiguate bounties, perhaps through a
bounty-specific pubkey. I'm not sure I follow, how is that better than
just referencing the address of the output, or the TxID, in a 'Table of
Bounties'? Or you want to embed a hash of your signed message announcing
the bounty?
Out of curiosity, I suppose right now you just keep pubkeys for the
signatories you want to appoint and reuse the same pubkey to create these
multi-sigs, or you have to ask for a new one each time?
From the signatories perspective, I imagine we're a long way off from a
wallet receiving or importing the p2sh, tracking that these outputs as
"yours", and even more, which contract/bounty they correspond to, and
finally a usable way to accumulate signatures and ultimately spend the
output to the bounty winner.
And of course, thanks for posting the bounties!
On Sun, 27 Oct 2013 22:58:13 -0700, John Dillon
<john.dillon892 at googlemail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Sat, Oct 26, 2013 at 3:31 AM, Gregory Maxwell <gmaxwell at gmail.com>
> wrote:
>> One limitation of the payment protocol as speced is that there is no
>> way for a hidden service site to make use of its full authentication
>> capability because they are unable to get SSL certificates issued to
>> them.
>>
>> Thoughts?
>
> I think this is a great idea and wish to see it done. Here is 1BTC for
> you,
> redeemable when you finish this task. I trust either Jeff Garzik or
> Peter Todd
> to evaluate your finished product, or possibly someone elses:
>
> 37NDa6iFLEozbvw8vj38ri5D6SLw5xQujS
>
> 22e067d3317e6300a9edda84fd0e24d8bfb86cf91540c3fe7acff45e4dc64dd3:0
>
> redeemScript :
> "5241045f4bba15dbfe94a45f362aa13bbaef8bbf21ff84fec1be5b27fa628f4b3acca1a2e5711503c8b8fe2e228229b8b8814f9e33e0f7a314a089d7140269ffd51fe44104d34775baab521d7ba2bd43997312d5f663633484ae1a4d84246866b7088297715a049e2288ae16f168809d36e2da1162f03412bf23aa5f949f235eb2e71417834104f005d39733ec09a1efa0cf8dcf3df50691e22c2374ff9a96d1d9ecb98a1e866c9f558a9fa1ba8ef0bbbad01f396768c0cb2dda9924dc0aaee1481604a8bd9ce453ae"
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
>
> iQEcBAEBCAAGBQJSbfy2AAoJEEWCsU4mNhiPrMMH/jd+AgVYUKd1vmP1BfaZum1s
> X186JulwF659YHOx94dLs+NOjvjMfY6cPbHm+B0j20CnhWrZrXzcXvwTHnzOSuoc
> 1AAXg0KDbvyo+7PvTrsGQfHhT1FZSRzIUToofVmFlvEIO6/LiYMAYWCgIiX9nPvv
> RlvdtavTST+cY19yZamo5X0XU5cgI2tbtVWKEHJQ2VcglCgwFg5K0kZ0O1NMKbcZ
> KBagY3PVTiHnYP+LwSTW6EU9DNq0eLYG39mz4N6CqGkXZjGgh2YXZ6Sl2qRuO/5e
> Rd9HcJXKqPKqMuRpQ2PA5U3U6QSyrUz7/fmi5dsOxnR6pdR53kjUVSvbOqBFHXw=
> =I1/R
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Jeremy Spilman [ARCHIVE] /
npub10eā¦jc727
2023-06-07 15:08:19
in reply to nevent1qā¦3cey
Author Public Key
npub10etkvm8l0jr0jsgdx02dxnhnu5g989dnca90guj5rklwkaplnh3sgjc727Published at
2023-06-07 15:08:19Event JSON
{
"id": "531c2bf5db36d6364f76d07d54ac6fbfcb4108d28873821539a2f703adcd2168",
"pubkey": "7e57666cff7c86f9410d33d4d34ef3e5105395b3c74af472541dbeeb743f9de3",
"created_at": 1686150499,
"kind": 1,
"tags": [
[
"e",
"742033471721f40b6d43cf4cd64612772c20a2675cdda10846c302155fc1bb24",
"",
"root"
],
[
"e",
"ffd20562613d36f920238250fcde1b6ea570977f6119ee03f457c97b2cd787e8",
"",
"reply"
],
[
"p",
"a0b592adfee20cad7bb28c238a9fc1fccf4511a458be8e3d96b00c914c8c3564"
]
],
"content": "š
Original date posted:2013-10-28\nš Original message:Just an aside...\n\nThe 1BTC bountry John references below is a 1BTC P2SH output, where the \nredeemScript he provided does hash to the expected value, and is itself a \n2-of-3 multisig, with the following pubkeys, expressed as addresses:\n\n1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj\n1FCYd7j4CThTMzts78rh6iQJLBRGPW9fWv\n1GMaxweLLbo8mdXvnnC19Wt2wigiYUKgEB\n\nBy comparison, the signatories for the 4BTC bountry are:\n\n1L9p6QiWs2nfinyF4CnbqysWijMvvcsnxe\n1FCYd7j4CThTMzts78rh6iQJLBRGPW9fWv\n1GMaxweLLbo8mdXvnnC19Wt2wigiYUKgEB\n\nOn the one hand, the vanity address makes it easy to guess who one of the \nsignatories is, on the other hand, is it bad form to reuse keys for \nsigning?\n\nJohn, you mentioned wanting to disambiguate bounties, perhaps through a \nbounty-specific pubkey. I'm not sure I follow, how is that better than \njust referencing the address of the output, or the TxID, in a 'Table of \nBounties'? Or you want to embed a hash of your signed message announcing \nthe bounty?\n\nOut of curiosity, I suppose right now you just keep pubkeys for the \nsignatories you want to appoint and reuse the same pubkey to create these \nmulti-sigs, or you have to ask for a new one each time?\n\n From the signatories perspective, I imagine we're a long way off from a \nwallet receiving or importing the p2sh, tracking that these outputs as \n\"yours\", and even more, which contract/bounty they correspond to, and \nfinally a usable way to accumulate signatures and ultimately spend the \noutput to the bounty winner.\n\nAnd of course, thanks for posting the bounties!\n\n\nOn Sun, 27 Oct 2013 22:58:13 -0700, John Dillon \n\u003cjohn.dillon892 at googlemail.com\u003e wrote:\n\n\u003e -----BEGIN PGP SIGNED MESSAGE-----\n\u003e Hash: SHA256\n\u003e\n\u003e On Sat, Oct 26, 2013 at 3:31 AM, Gregory Maxwell \u003cgmaxwell at gmail.com\u003e \n\u003e wrote:\n\u003e\u003e One limitation of the payment protocol as speced is that there is no\n\u003e\u003e way for a hidden service site to make use of its full authentication\n\u003e\u003e capability because they are unable to get SSL certificates issued to\n\u003e\u003e them.\n\u003e\u003e\n\u003e\u003e Thoughts?\n\u003e\n\u003e I think this is a great idea and wish to see it done. Here is 1BTC for \n\u003e you,\n\u003e redeemable when you finish this task. I trust either Jeff Garzik or \n\u003e Peter Todd\n\u003e to evaluate your finished product, or possibly someone elses:\n\u003e\n\u003e 37NDa6iFLEozbvw8vj38ri5D6SLw5xQujS\n\u003e\n\u003e 22e067d3317e6300a9edda84fd0e24d8bfb86cf91540c3fe7acff45e4dc64dd3:0\n\u003e\n\u003e redeemScript : \n\u003e \"5241045f4bba15dbfe94a45f362aa13bbaef8bbf21ff84fec1be5b27fa628f4b3acca1a2e5711503c8b8fe2e228229b8b8814f9e33e0f7a314a089d7140269ffd51fe44104d34775baab521d7ba2bd43997312d5f663633484ae1a4d84246866b7088297715a049e2288ae16f168809d36e2da1162f03412bf23aa5f949f235eb2e71417834104f005d39733ec09a1efa0cf8dcf3df50691e22c2374ff9a96d1d9ecb98a1e866c9f558a9fa1ba8ef0bbbad01f396768c0cb2dda9924dc0aaee1481604a8bd9ce453ae\"\n\u003e\n\u003e -----BEGIN PGP SIGNATURE-----\n\u003e Version: GnuPG v1.4.11 (GNU/Linux)\n\u003e\n\u003e iQEcBAEBCAAGBQJSbfy2AAoJEEWCsU4mNhiPrMMH/jd+AgVYUKd1vmP1BfaZum1s\n\u003e X186JulwF659YHOx94dLs+NOjvjMfY6cPbHm+B0j20CnhWrZrXzcXvwTHnzOSuoc\n\u003e 1AAXg0KDbvyo+7PvTrsGQfHhT1FZSRzIUToofVmFlvEIO6/LiYMAYWCgIiX9nPvv\n\u003e RlvdtavTST+cY19yZamo5X0XU5cgI2tbtVWKEHJQ2VcglCgwFg5K0kZ0O1NMKbcZ\n\u003e KBagY3PVTiHnYP+LwSTW6EU9DNq0eLYG39mz4N6CqGkXZjGgh2YXZ6Sl2qRuO/5e\n\u003e Rd9HcJXKqPKqMuRpQ2PA5U3U6QSyrUz7/fmi5dsOxnR6pdR53kjUVSvbOqBFHXw=\n\u003e =I1/R\n\u003e -----END PGP SIGNATURE-----\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e October Webinars: Code for Performance\n\u003e Free Intel webinars can help you accelerate application performance.\n\u003e Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most \n\u003e from\n\u003e the latest Intel processors and coprocessors. See abstracts and register \n\u003e \u003e\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=60135991\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development",
"sig": "6c7f3ff0d1e9de68c0ccf763a16232bf57babd30531273785aadc3d187e18abafa034a426fd0702c07ae70ef31e154d81ad1384bb95a7b34e1af10179599eda7"
}