03:10:06 <viperperidot[m]> Is there any way to know if you are connected to an asshole node so you can ban them?
03:10:10 <viperperidot[m]> My initial sync seems to be taking a long time
03:23:19 <selsta> You can increase out_peers and limit_down
03:23:45 <selsta> initial sync time is most likely not affected by bad nodes, SSD helps
03:25:05 <viperperidot[m]> I am using a raspberry pi 4b with 4gb of ram, 500gb external ssd, I also have 2gb of swap enabled. So the those are the 2 best options to decrease sync time?
03:27:33 <viperperidot[m]> I will increase those thanks
08:18:05 <Inge-> Isthmus: Did there come out any practical guidelines for people to mitigate any of the potential quantum weaknesses? e.g. using more separate wallets to avoid a compromised public address to unravel more than absolutely necessary or similar?
08:25:21 <Inge-> Block time variance is up a bit since last fork: https://bitinfocharts.com/comparison/confirmationtime-xmr.html#2y
08:26:54 <Inge-> Possibly due to "hanoiboi" and hashrate variance?
08:59:01 <selsta> viperperidot[m]: it will decrease sync time if hardware is not the bottleneck
08:59:59 <selsta> raspberry pi is not the strongest machine so I would not be surprised about long sync times
15:26:47 <viperperidot[m]> Ok thank you, I have noticed an increase since changing those settings.
15:26:58 <viperperidot[m]> Increase in sync speed that is
17:12:46 <binaryFate> Anybody knows if any of these authors did any follow-up work or are involved whatsoever with Monero? This was from mid-2018 but I just only found it http://courses.csail.mit.edu/6.857/2018/project/Hu-Macias-Jachymiak-Siabi-Monero.pdf
19:00:43 <midipoet> https://usercontent.irccloud-cdn.com/file/8B1KoGcH/43.pdf
19:00:57 <midipoet> Found this related as well
19:04:35 <midipoet> Which was published at Financial Cryptography
22:04:14 <yanmaani> ping aaaa
22:04:21 <yanmaani> (oops, wrong window, carry on)
22:08:48 <yanmaani> It seems like a good defense against eclipse attacks would be to have a large list of nodes to which you probabilistically send information.
22:09:49 <yanmaani> So, I contact 1000 nodes and tell them, "whenever there's a new block, send the header to me if rand(0,1000) == 999". And they either say they'll honor it or they won't.
22:11:30 <yanmaani> I then have a 1-1/e chance of receiving each block, regardless of network topology
22:12:24 <yanmaani> You could trivially extend this against network attacks too. "I'll ACK it with key X, if I don't then try to connect to xxxxxxxxxxx.onion instead".