00:27:42 ????? 03:25:38 I mean, depends on your traffic patterns. If you use the internet from the same residential hookup between accounts and largely use the same websites, it probably doesn't matter privacy-wise if you do an account for 1 year vs 1 month since they can track you all the same 03:29:28 I use home connection 03:56:12 20 years. I'm bullish. 04:48:03 some of us will be dead in 20 years 05:03:15 Reminder to give a way for your wife/children to have access to your crypto if you die, otherwise it's all lost. 11:36:07 On 'monero.fail' and 'xmr.ditatompel.com' someone has entered a lot of .onion nodes that obviously¹ all point to one server or monerod. (¹The port assignment suggests that all hidden services run on one Tor-instance via one IP.) 11:36:41 Over 20: http://234567.*d.onion or http://7777777.*d.onion - I wonder what the point is behind it. 11:36:56 Someone with bad intentions would use random .onion addresses and not make it so obvious with Tor vanity addresses. 12:01:19 Another question: monero-docs and monero.fail/opsec recommend the 'tx-proxy=' option 'disable_noise'. It was previously discouraged because it skips Dandelion++ and has a slight privacy trade off. 12:01:27 'tx-proxy=' Sends local txes through SOCKS5 proxy. 12:01:29 Are txes from users/wallets connecting to my remote nodes RPC port local? 12:01:40 'tx-proxy=' Sends local txes through SOCKS5 proxy. 12:01:41 Are txes from users/wallets connecting to my remote nodes RPC port local? 12:16:26 " Are txes from users/wallets connecting to my remote nodes RPC port local?" Yes 12:18:25 Dandelion isnt needed for tx-proxy. The privacy tradeoff is that the recipient node fluffs immediately, so it doesnt add noise to the recipient node's stems 12:19:17 W/o disable noise, it adds plausible deniability as to which tx are originating at the recipient node vs being received via aninymous-inbound 12:21:16 Imo, for the sender, disable noise is more private and secure than w/o, because it sends to all of your tx-proxy peers, and they all fluff immediately. Its like featherwallets multibroadcast, but private. A malicious peer cant refuse to relay your tx and force you to retry 12:22:15 And thr recipient node wont be sybilled because it will be fluffed to 10s-100s of nodes at once 12:23:21 Thanks, I was unsure about that for years. ;-) Ok, then I will enable 'disable_noise'. 12:25:54 omitting disable_noise is good if you believe your onion peers to not be malicious. If your onion peers are also using tx-proxy (they have to be if they use anon inbound) then their node will only ever broadcast tx that didnt originate from their node 12:26:06 boldsuck planning on reporting the reverse proxied .onion nodes to ditatompel and [@lza_menace:monero.social](https://matrix.to/#/@lza_menace:monero.social) at some point? :D 12:26:47 theyre obvious. Plowsof and a few other ppl know about them as well 12:27:12 They were all offline at the same time, further confirming that they all point to the same underlying node 12:27:48 Lucky number 7 nodes 12:27:50 Boldsuck - the port assignment is likely some 9-5r just doing their job 12:28:17 theres no reason they couldnt have used 18081 for all of them, as the virtual port os per onion 12:28:40 They used different ports a) because they are retarded b) because they are following orders / dont get paid to think 12:29:26 234567 one2345 7777777 6666666, ports 18289 18389 etc 12:31:41 What harm can they cause? High fee.. not relaying tx + perhaps greed mining or forcing user to regenerate the tx on a diff node 12:32:06 AFAIK: You can't have multiple onions with the same port listening on one IP. Not even with multiple Tor instances. 12:32:35 Each onion uses its own virtual port range 👍 12:33:47 You can have 1000 onions on the same instance all using `HiddenServicePort port 18081 127.0.0.1:18081` 12:33:50 bro just thumbs up its own message 12:33:58 bro just thumbs up its own message 👍️ 12:34:07 # 👍️ 12:34:25 You can have 1000 onions on the same instance all using `HiddenServicePort 18081 127.0.0.1:18081` 12:34:50 OK, I'll try this later on a test server. 2 Tor instances listen on one Port 12:35:14 Ya dont believe me? Lol 12:35:26 Each onion has it own port range 12:37:40 ``` 12:37:40 HiddenServiceDir /var/lib/tor/sythbehird 12:37:42 HiddenServicePort 18081 127.0.0.1:18081 12:37:44 HiddenServiceDir /var/lib/tor/ofernxmf 12:37:46 HiddenServicePort 18081 127.0.0.1:18081 12:37:48 HiddenServiceDir /var/lib/tor/monderbull 12:37:50 HiddenServicePort 18081 127.0.0.1:18081 12:37:52 ``` 12:39:10 This is why the 7777777 person is retarded 12:40:28 1. They made vanities for no damn reason 12:40:30 2. They uses different ports for no damn reason 12:40:32 its like a retarded troll or an underpaid employee following instructions from someone who lied on their resume about knowing how 2 use tor 12:41:52 If they did what i just posted, the only way i would have known that they were the same node was by them failing their uptime check 12:41:57 BC: You can have 1000 onions on the same instance. - Theoretically yes. If there are 80-100 hidden services on an instance there are often problems as not all of them come online. 12:42:18 I guess we'll know soon if they read the chat 12:46:05 Also, 1000 was just to say "you can use the sane port as many times as you want (on diff hidden services ofc)". Not that 1000 is realistic 12:47:35 same goes for i2p 12:48:24 Source: i do it all the time. Probably have 5-10 running on port 80 atm 12:51:29 I've never tried this because I haven't needed it yet and I have entire subnets on the servers. 12:52:38 I use port 80 on onion/i2p bcuz it drops requirement of typing port into browser 13:02:47 I think I add a list trusted 'add-priority-node' in monerod.conf. 13:05:52 For onions? The problem with that is using up those trusted peers incoming slots 13:09:23 Also, a lot of ppl seem to think that you can add rpc peers, which just causes your node to constantly try (and fail) to connect 13:10:15 If i add a priority peer, its usually only 1, and usually just to try to make sure that our nodes dont fork off from one another 13:11:46 .. but thats clearnet. I dont think i use priority onion/i2p 13:39:41 I have 3 own onion & clearnet remote nodes in add-priority-node. I add a few clearnet nodes that also have IPv6 as 'add-peer'. 13:43:07 afaik i2p doesn't use ports, all ports point to the same service 13:49:42 I2p uses ports if you have the same key file attached to more than 1 port 13:50:03 The lowest port will respond to anythibf between 0-lowest port 13:50:22 If the key file is only config for 1 tunnel, then any port will work 13:50:37 I2p uses ports if you have the same key file attached to more than 1 tunnel