📅 Original date posted:2015-02-05 📝 Original message:Hi Paul, The issue is in ...

Eric Voskuil [ARCHIVE] /

npub1sgs…px3c

2023-06-07 15:29:52

in reply to nevent1q…vmc8

📅 Original date posted:2015-02-05
📝 Original message:Hi Paul,

The issue is in the establishment of trust. Anyone can broadcast the initial information.

e

> On Feb 5, 2015, at 2:01 PM, Paul Puey <paul at airbitz.co> wrote:
>
> The broadcast is ONLY done when the wallet is in Receive mode. Same as when the QR code is visible. The use of the *Name* section is specifically so that a recipient can broadcast their name/handle. Not so the recipient would broadcast the name of the Sender.
>
> On Thu, Feb 5, 2015 at 12:50 PM, Mike Hearn <mike at plan99.net> wrote:
>>> I'm imagining myself walking around broadcasting my photo and MAC
>>> address while hucksters push payment requests to me for approval
>>
>> I hate to break it to you, but you broadcast a photo of your face every time you walk outside ;)
>>
>> Bluetooth MAC addresses are random, they aren't useful identifiers. If someone can see you, a face is a far more uniquely identifying thing than a MAC.
>>
>> "Payment spam" might be a problem. I can imagine a wallet requiring that such requests are signed and then spammers can be blacklisted in the usual fashion so they can't push things to your phone anymore. Anyway, a hurdle that can be jumped if/when it becomes an issue.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150205/d5b26d5f/attachment.html>;

Author Public Key

npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3c

Show more details

Published at

2023-06-07 15:29:52

Kind type

1 Short Text Note

Event JSON

{ "id": "23e18b2b0d0187a60b5e3a26b85878e8812445d1444cb85aa598086ac8124c9a", "pubkey": "82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e", "created_at": 1686151792, "kind": 1, "tags": [ [ "e", "5faa01afc6e1169d2a086249776b02fde5bfa851fa5197990b9cbcbf92c53f4a", "", "root" ], [ "e", "86a895fcfba19b7752c109a2013bbf2c3c1afc5389c9682b0d9673a6a39212cb", "", "reply" ], [ "p", "1cb8643c67340d78eb64edffa0304312be7b70e7c2548b9b328f548a3a0dfee4" ] ], "content": "📅 Original date posted:2015-02-05\n📝 Original message:Hi Paul,\n\nThe issue is in the establishment of trust. Anyone can broadcast the initial information.\n\ne\n\n\u003e On Feb 5, 2015, at 2:01 PM, Paul Puey \u003cpaul at airbitz.co\u003e wrote:\n\u003e \n\u003e The broadcast is ONLY done when the wallet is in Receive mode. Same as when the QR code is visible. The use of the *Name* section is specifically so that a recipient can broadcast their name/handle. Not so the recipient would broadcast the name of the Sender.\n\u003e \n\u003e On Thu, Feb 5, 2015 at 12:50 PM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\u003e\u003e\u003e I'm imagining myself walking around broadcasting my photo and MAC\n\u003e\u003e\u003e address while hucksters push payment requests to me for approval\n\u003e\u003e \n\u003e\u003e I hate to break it to you, but you broadcast a photo of your face every time you walk outside ;)\n\u003e\u003e \n\u003e\u003e Bluetooth MAC addresses are random, they aren't useful identifiers. If someone can see you, a face is a far more uniquely identifying thing than a MAC.\n\u003e\u003e \n\u003e\u003e \"Payment spam\" might be a problem. I can imagine a wallet requiring that such requests are signed and then spammers can be blacklisted in the usual fashion so they can't push things to your phone anymore. Anyway, a hurdle that can be jumped if/when it becomes an issue.\n\u003e \n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150205/d5b26d5f/attachment.html\u003e", "sig": "c54aa4db3290bcd664554680fa63d7dc7ebe51a3071a821509d5748190561e909d254c9efe49a27105dfe172b302ab79309dd8cf7545d06456ac9668fda5f278" }