📅 Original date posted:2017-02-16 📝 Original message:On Tuesday, 14 February ...

Tom Zander [ARCHIVE] /

npub1mju…xnq7

2023-06-07 17:56:24

in reply to nevent1q…m3tc

📅 Original date posted:2017-02-16
📝 Original message:On Tuesday, 14 February 2017 22:01:51 CET Jonas Schnelli via bitcoin-dev
wrote:
> >> - If you use one of the todays available SPV clients, you will reveal
> >> your complete wallet content („~all your addresses") to every network
> >> observer between you and the node you have connected to. This means, if
> >> you pay for a coffee (while being on the owners WIFI), the coffee owner
> >> and all the involved ISPs can correlate your wallet with your other
> >> internet behavior. Same is true for your cellphone provider if you use
> >> cellular.
> >
> > What about allowing trusted users connecting on a different connection.
> > Much like the RPC one.
> > Make that one encrypted. Different usecase, different connection.
>
> - What protocol would you use?

The RPC one. Which I think is JSON.

Your usecase is essentially just calling sendRawTransaction. Don’t
overcomplicate things.

--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel

Author Public Key

npub1mju50kqcm07heu967fkq6h4kq666xgekc4yrldf7q52xx9vr8jnsrdxnq7

Seen on

wss://relay.nostr.band

Show more details

Published at

2023-06-07 17:56:24

Kind type

1 Short Text Note

Event JSON

{ "id": "e326927586d7989ad7a936b0b1775d4916c9a1af46f67c80fb06729663aeaad2", "pubkey": "dcb947d818dbfd7cf0baf26c0d5eb606b5a32336c5483fb53e05146315833ca7", "created_at": 1686160584, "kind": 1, "tags": [ [ "e", "1b51795ee3de0471069901761d0f6325d2b5fe8bd15e565deee4918af435f74c", "", "root" ], [ "e", "aefed6741dd6c23b443dba2477854f8f1de4217cee0d754c9b8a845c79bba497", "", "reply" ], [ "p", "9a463e0fab8963b013698c15a0f2449d19c97f3b88458e5874095b5006df9a0c" ] ], "content": "📅 Original date posted:2017-02-16\n📝 Original message:On Tuesday, 14 February 2017 22:01:51 CET Jonas Schnelli via bitcoin-dev \nwrote:\n\u003e \u003e\u003e - If you use one of the todays available SPV clients, you will reveal\n\u003e \u003e\u003e your complete wallet content („~all your addresses\") to every network\n\u003e \u003e\u003e observer between you and the node you have connected to. This means, if\n\u003e \u003e\u003e you pay for a coffee (while being on the owners WIFI), the coffee owner\n\u003e \u003e\u003e and all the involved ISPs can correlate your wallet with your other\n\u003e \u003e\u003e internet behavior. Same is true for your cellphone provider if you use\n\u003e \u003e\u003e cellular.\n\u003e \u003e \n\u003e \u003e What about allowing trusted users connecting on a different connection.\n\u003e \u003e Much like the RPC one.\n\u003e \u003e Make that one encrypted. Different usecase, different connection.\n\u003e \n\u003e - What protocol would you use?\n\nThe RPC one. Which I think is JSON.\n\nYour usecase is essentially just calling sendRawTransaction. Don’t \novercomplicate things.\n\n-- \nTom Zander\nBlog: https://zander.github.io\nVlog: https://vimeo.com/channels/tomscryptochannel", "sig": "c5e3b44a7727f9c3c4d6797b72e892270dfb695284c484ebdb0f9c0cd8c2cc959625f83fe20dfca3ca293f7df844e87a4919a34f11d845d8c89667a581a20d28" }