📅 Original date posted:2014-01-13
📝 Original message:How is this different from the proposal I have made?
You distribute the root public key (but not chaincode!) of a BIP32
branch. You can put your root key on a business card if you want. Then
when someone wants to pay you, you simply give them the multiplier and
root key (they already have the root key, but should verify). The
multiplier does not reveal the chaincode, thus keeping it private, but
it does allow them to confirm that the final address they are paying is
derived from that root key they know belongs to you ("Please pay address
X; oh btw, X=rootKey*mult").
You can /choose/ to reveal that a given payment address is linked to
your root key without any compromise of privacy. Or you can choose to
ignore it and just give them a bare address the old way and still
maintain privacy. What advantages does "stealth addresses" have over
this scheme? You could extend it using some kind of deterministic
sub-branching and/or ECDH to create multiple payment addresses without
querying the payee.
I had planned to implement this system and push for people to accept it
because I don't see any downsides to it. It can easily be integrated
into a WoT (with signed root keys), or CA system piggybacking on SSL.
-Alan
On 01/13/2014 02:44 PM, Drak wrote:
> On 13 January 2014 19:40, Roy Badami <roy at gnomon.org.uk
> <mailto:roy at gnomon.org.uk>> wrote:
>
> At the moment, I can give them a business card with a Bitcoin address.
> Being able to give out a business card with a stealth address would be
> a major advance.
>
>
> My thoughts exactly.
>
> Drak
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140113/85d58fe9/attachment.html>;
Alan Reiner [ARCHIVE] /
npub1sm…mnq7h
2023-06-07 15:11:52
in reply to nevent1q…cdzf
Author Public Key
npub1sm6zhjmk5scuz294jmpkw99wwwjzetjgwp4fu4gn6utqgdz87hkqamnq7hPublished at
2023-06-07 15:11:52Event JSON
{
"id": "a6221ad05fde05d1728c28c3cf1158bfc7a1cfc6fd91f08fceca187db264b829",
"pubkey": "86f42bcb76a431c128b596c36714ae73a42cae48706a9e5513d716043447f5ec",
"created_at": 1686150712,
"kind": 1,
"tags": [
[
"e",
"6b79d8c7bec3dc6952db91cc68d0510d9897c37dcf58a24d8e2f4288fe42525c",
"",
"root"
],
[
"e",
"c1e77f290f735ff38efc3a8c393b1a7e0b7ddf9488eff2a6a7d07a6ff112974c",
"",
"reply"
],
[
"p",
"50ece7cbb2dc316af1cd5da0d62e0e1fec40f20919242c8fbedd53702fba95db"
]
],
"content": "📅 Original date posted:2014-01-13\n📝 Original message:How is this different from the proposal I have made?\n\nYou distribute the root public key (but not chaincode!) of a BIP32\nbranch. You can put your root key on a business card if you want. Then\nwhen someone wants to pay you, you simply give them the multiplier and\nroot key (they already have the root key, but should verify). The\nmultiplier does not reveal the chaincode, thus keeping it private, but\nit does allow them to confirm that the final address they are paying is\nderived from that root key they know belongs to you (\"Please pay address\nX; oh btw, X=rootKey*mult\").\n\nYou can /choose/ to reveal that a given payment address is linked to\nyour root key without any compromise of privacy. Or you can choose to\nignore it and just give them a bare address the old way and still\nmaintain privacy. What advantages does \"stealth addresses\" have over\nthis scheme? You could extend it using some kind of deterministic\nsub-branching and/or ECDH to create multiple payment addresses without\nquerying the payee. \n\nI had planned to implement this system and push for people to accept it\nbecause I don't see any downsides to it. It can easily be integrated\ninto a WoT (with signed root keys), or CA system piggybacking on SSL.\n\n-Alan\n\n\nOn 01/13/2014 02:44 PM, Drak wrote:\n\u003e On 13 January 2014 19:40, Roy Badami \u003croy at gnomon.org.uk\n\u003e \u003cmailto:roy at gnomon.org.uk\u003e\u003e wrote:\n\u003e\n\u003e At the moment, I can give them a business card with a Bitcoin address.\n\u003e Being able to give out a business card with a stealth address would be\n\u003e a major advance.\n\u003e\n\u003e\n\u003e My thoughts exactly.\n\u003e\n\u003e Drak \n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e CenturyLink Cloud: The Leader in Enterprise Cloud Services.\n\u003e Learn Why More Businesses Are Choosing CenturyLink Cloud For\n\u003e Critical Workloads, Development Environments \u0026 Everything In Between.\n\u003e Get a Quote or Start a Free Trial Today. \n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=119420431\u0026iu=/4140/ostg.clktrk\n\u003e\n\u003e\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\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140113/85d58fe9/attachment.html\u003e",
"sig": "81a49f00ff8ca884dffddfc30bc4246cecb28a17a98389de5705e2c989578939971814afdda4763715749f22bf16b21c8ffbf67bf891319259631d2281498e50"
}