📅 Original date posted:2011-10-25
🗒️ Summary of this message: A proposed solution for storing Bitcoin addresses involves using a hash to script mapping, but there are already ways to create secondary keys and private keys.
📝 Original message:On Tue, Oct 25, 2011 at 9:21 AM, Gavin Andresen <gavinandresen at gmail.com> wrote:
> You give the hash to whoever is paying you, and store the hash -->
> script mapping when you do that (assuming you're not using a
> deterministic wallet; if you are, you probably just increment a
> counter in the wallet).
If anyone finds that solution unsatisfying, consider— It's already the
case that I could take one of your disclosed public keys and create an
infinite series of secondary keys out of it for which only you could
decode, and the only way for you to find them in the blockchain would
be to have performed the same procedure and made a note of the
addresses you're watching for.
... or really, more simply I could generate a private key on your
behalf and send funds there. ("What do you mean you didn't get the
funds? I sent them to the private key defined by the cryptographic
hash of the lyrics of your favorite song!")
So it's already the case that if I didn't get your address from you
(or through a negotiation with you), I can't expect you to receive
them.
Gregory Maxwell [ARCHIVE] /
npub1f2…crwet
2023-06-07 02:35:29
in reply to nevent1q…7ndn
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetPublished at
2023-06-07 02:35:29Event JSON
{
"id": "6d021060f18df6a3974b716023dbad1ec38edb1066b19e021435d669b634fb7b",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686105329,
"kind": 1,
"tags": [
[
"e",
"38ab95ef62f6301977f9dec6ff3b1f25746d558345bec15abbd412157a28a77b",
"",
"root"
],
[
"e",
"61e95d6ead33e63166ee1868f7ed2f4cf35c7739dff01dec66a6e74834b30ff6",
"",
"reply"
],
[
"p",
"857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4"
]
],
"content": "📅 Original date posted:2011-10-25\n🗒️ Summary of this message: A proposed solution for storing Bitcoin addresses involves using a hash to script mapping, but there are already ways to create secondary keys and private keys.\n📝 Original message:On Tue, Oct 25, 2011 at 9:21 AM, Gavin Andresen \u003cgavinandresen at gmail.com\u003e wrote:\n\u003e You give the hash to whoever is paying you, and store the hash --\u003e\n\u003e script mapping when you do that (assuming you're not using a\n\u003e deterministic wallet; if you are, you probably just increment a\n\u003e counter in the wallet).\n\nIf anyone finds that solution unsatisfying, consider— It's already the\ncase that I could take one of your disclosed public keys and create an\ninfinite series of secondary keys out of it for which only you could\ndecode, and the only way for you to find them in the blockchain would\nbe to have performed the same procedure and made a note of the\naddresses you're watching for.\n\n... or really, more simply I could generate a private key on your\nbehalf and send funds there. (\"What do you mean you didn't get the\nfunds? I sent them to the private key defined by the cryptographic\nhash of the lyrics of your favorite song!\")\n\nSo it's already the case that if I didn't get your address from you\n(or through a negotiation with you), I can't expect you to receive\nthem.",
"sig": "4e9fa2c0b00b8c6257e1de91730061b10c5b26499c13faf0bae83775532666cc986a9a24a1bbe252e461e429b3aa133b6f9b72fe9ec54ba595ac3e09a4803911"
}