š
Original date posted:2013-09-06
š Original message:Hi all,
We're thinking about ways of automatically exchanging contact details between wallets, in order to encourage the proliferation of identifiable names and photos rather than long and hard-to-verify addresses.
The simplest version goes like this:
2 BTC Bitcoin is sent to someone, and a data lookup hash is inserted into the transaction. When it arrives on the other end, it is indeed looked up, and instead of being presented with a dialogue that says "you received 2 BTC from 13Y94z43Nbbb6wevRyk82CeDoYQ5S28zmA", it's "You received 2 BTC from Frank Jones" including a nice photo.
Now. We can simply delete this data in reference to the transaction ID after it happens (or delete it after a time), but is there any more decentralized way to do it? I would prefer us to run no dedicated servers that would ever put us in a position of being coerced into giving data, or otherwise altering our system to store it.
Any thoughts about this?
-wendell
grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130906/6be1e4b2/attachment.sig>;
Wendell [ARCHIVE] /
npub1c5ā¦34kvp
2023-06-07 15:06:36
in reply to nevent1qā¦09rr
Author Public Key
npub1c56tk56u5846gc9tj6kcd886y9sztx6yrj24zhegrsv87qfs7nes834kvpSeen on
wss://relay.noswhere.comPublished at
2023-06-07 15:06:36Event JSON
{
"id": "774481533b50dc50216c2e2b477d71ad1679b2b2eb32d4db719fbf8bc1adcda5",
"pubkey": "c534bb535ca1eba460ab96ad869cfa2160259b441c95515f281c187f0130f4f3",
"created_at": 1686150396,
"kind": 1,
"tags": [
[
"e",
"81353ffadfcedef76e290d10f50e6602d23d96b23fcfba53fc07623cddfe7e57",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "š
Original date posted:2013-09-06\nš Original message:Hi all,\n\nWe're thinking about ways of automatically exchanging contact details between wallets, in order to encourage the proliferation of identifiable names and photos rather than long and hard-to-verify addresses.\n\nThe simplest version goes like this:\n\n2 BTC Bitcoin is sent to someone, and a data lookup hash is inserted into the transaction. When it arrives on the other end, it is indeed looked up, and instead of being presented with a dialogue that says \"you received 2 BTC from 13Y94z43Nbbb6wevRyk82CeDoYQ5S28zmA\", it's \"You received 2 BTC from Frank Jones\" including a nice photo.\n\nNow. We can simply delete this data in reference to the transaction ID after it happens (or delete it after a time), but is there any more decentralized way to do it? I would prefer us to run no dedicated servers that would ever put us in a position of being coerced into giving data, or otherwise altering our system to store it.\n\nAny thoughts about this?\n\n-wendell\n\ngrabhive.com | twitter.com/grabhive | gpg: 6C0C9411\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 841 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130906/6be1e4b2/attachment.sig\u003e",
"sig": "3936b9a39de233982d6cb919f8d7e5afcf3f284a1d53741a8323e9b1a015eb5edb4ac35df09531cfaa45ef149d2bb89808c9ce6a8e8daa7b82ceb27dfa3362a3"
}