--- Log opened Fri May 31 00:00:12 2024
06:40 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #silentpayments
06:54 < josie_> setavenger: regarding pushtx, I haven't taken a close look but the general approach sounds good. there's also a BIP324 proxy library being worked on by a few people so the light client could also connect to peers using transportv2 (p2p encryption), which further helps with privacy. using p2pv2, the client would only be losing privacy against active attackers, e.g. bitcoin nodes ran with the
06:54 < josie_> intent of collecting data (spy nodes)
06:55 < josie_> here is the post on bip324 proxy: https://delvingbitcoin.org/t/bip324-proxy-easy-integration-of-v2-transport-protocol-for-light-clients-poc/678
07:16 < _andrewtoth_> josie_: pushtx and bip324 are complementary to each other. pushtx finds the peers through dns, and then could also use bip324 to establish an encrypted connection
07:16 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
07:17 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #silentpayments
07:18 < _andrewtoth_> but I think pushtx is better than along lived connection over bip324 due to privacy. The peer you have an encrypted connection with can link every tx you send to the same wallet, vs with pushtx each broadcast is an ephemeral connection so even spy nodes can't link your txs
07:18 < _andrewtoth_> *a long
07:19 < josie_> _andrewtoth_: yeah, i typed that poorly. what i was envisioning was find peers via pushtx and then connect via p2pv2
07:20 < josie_> altho you make a good point about long lived connections. the way i was imagining it is your p2pv2 would be a short lived connection (e.g. just for pushing a single tx). but maybe there is too much overhead in doing the p2pv2 handshake for a short lived connection?
07:25 < _andrewtoth_> If you use tor with pushtx, then I don't see a benefit to p2pv2? But without access to a tor proxy, any eavesdropper will not be able to see which tx you just broadcasted, only the recipient node will?
07:25 < _andrewtoth_> I mean for the latter case if you did use p2pv2
07:58 < josie_> _andrewtoth_: yep, no need for p2pv2 if using tor. however, even with tor + pushtx, recipient node still sees the tx, right?
07:58 < josie_> the benefit i see of p2pv2 + pushtx is this is likely much easier to implement for a mobile wallet than tor 
07:58 < josie_> and i think you get the same privacy benefit, except the recipient node could learn your IP
07:59 < _andrewtoth_> josie_: recipient node would have to see the tx for it to broadcast, not sure I understand? Agree with your other two points
08:00 < _andrewtoth_> actually, not learning your IP is a pretty big benefit, so not sure it can be discounted as the same if you just encrypt the connection but not go through tor
08:01 < josie_> _andrewtoth_: more responding to your last comment, "only the recipient node will," it seemed you were implying that with tor + pushtx you hide the tx from eavesdroppers and the recipient node. was more just clarifying in every case the recipient node sees the tx 
08:02 < _andrewtoth_> i.e. if there are *lots* of spy nodes, and making ephemeral connections from the same IP to different ones they can link your txs to the same wallet, with tor they cannot
08:06 < josie_> _andrewtoth_: agree re: tor vs p2pv2. idk enough about mobile dev to know if this is possible, but the ideal setup in my mind would be download tweak data on clearnet and broadcast over tor
08:21 -!- pyth__ [~pyth@116.110.41.135] has joined #silentpayments
10:35 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 260 seconds]
10:39 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #silentpayments
13:26 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 260 seconds]
22:56 -!- pyth [~pyth@116.110.41.135] has joined #silentpayments
22:56 -!- pyth__ [~pyth@116.110.41.135] has quit [Read error: Connection reset by peer]
--- Log closed Sat Jun 01 00:00:13 2024