00:31:54 <nioc> vtnerd opened pull request #8996: Add SSL support to P2P
00:31:54 <nioc> > https://github.com/monero-project/monero/pull/8996
03:15:23 <m-relay> <1​23bob123:matrix.org> I assume this wouldnt be full verify as there is no CA?
09:39:58 <copypaste> sech1: same question but hopefully less noise in here :)
09:54:02 <sech1> It's better to use https://github.com/hinto-janai/monero-vanity - it's faster on CPU than my code on GPU thanks to better algorithm
11:03:25 <copypaste> sech1: that's just evidence to me that via sycl more performance could be achieved >:)
11:05:20 <sech1> No - sycl, opencl, cuda are just compilers. Performance is all about better algorithm.
11:08:16 <copypaste> sech1: meaning, u could implement the better algorithm on sycl :')
11:08:33 <copypaste> not that using existing algorithm on cuda/sycl would be better
14:02:03 <Lyza> noticing that my node is connecting to its own I2P address, possibly related to 8918 because I didn't specify a port in my config but the "self" I'm connecting to has :18080 appended at the end
14:39:14 <m-relay> <v​tnerd:monero.social> Dan r/dark (Is not the man & Braxman Tomsparks Advocate ): there is verification via CLI - you can specify an IP and fingerprint. There is also limited verification after first use, of the remote peer opts into persistent certificates
14:39:28 <m-relay> <v​tnerd:monero.social> *if the peer
15:50:34 <m-relay> <o​frnxmr:monero.social> Lyza https://github.com/monero-project/monero/issues/8918
15:51:29 <Lyza> yep that's the one I mentioned. the last comment is mine
15:51:50 <m-relay> <o​frnxmr:monero.social> Yeah, its the same bug
15:52:21 <Lyza> 👍
15:53:04 <m-relay> <o​frnxmr:monero.social> If you changr your port in your config, youll rebroadcast a new port and add yet another valid entry to the peerlist
15:53:42 <m-relay> <o​frnxmr:monero.social> Then this `Im not sure what conditions must be met, but in certain circumstances it will broadcast 18080 as the port. ` is your issue
15:53:49 <m-relay> <o​frnxmr:monero.social> All stem from broadcasting ports
15:55:15 <Lyza> yeah I'm not sure what causes 18080 to be appended either since there are entries with no port in my peer list
15:55:52 <Lyza> I believe some changes were made to the logic with this PR https://github.com/monero-project/monero/pull/7017
16:00:16 <Lyza> it says self connect can be caused by a "misconfiguration" due to this PR but doesn't really elaborate on what proper configuration looks like. I guess we are "supposed" to specify a port? but it doesn't seem ideal to just let the "misconfiguration" silently persist
16:09:14 <m-relay> <o​frnxmr:monero.social> If we supply a port, changing it doesnt invalidate the old entry, so its still broken
16:09:38 <m-relay> <o​frnxmr:monero.social> I2p doesnt seem to care about ports. Bitcoin fix was to simply force port 0
16:10:48 <m-relay> <o​frnxmr:monero.social> https://github.com/bitcoin/bitcoin/issues/21389
16:11:31 <m-relay> <o​frnxmr:monero.social> https://github.com/bitcoin/bitcoin/pull/22112
16:12:49 <Lyza> wouldn't we want to avoid connecting to the same address at different ports anyway? I mean even for i2p or tor where ports are supported
16:13:01 <Lyza> ideally outgoing connections should each be to *independent* nodes
16:13:14 <Lyza> even for ip4*
16:14:20 <Lyza> "changing it doesnt invalidate the old entry," <--- so you're saying there was probably also an entry for my i2p address that has null port, and I still might self connect to that one if I change my config to 18080
16:15:07 <Lyza> anyway I agree forcing i2p address to null port or port 0 makes the most sense
16:15:21 <m-relay> <o​frnxmr:monero.social> And if you change it to 18085, youll have 3 valid peers
16:16:18 <Lyza> right I get that, I thought maybe 18080 was always getting appended to the null port address wouldn't be in peer lists
16:16:31 <m-relay> <o​frnxmr:monero.social> Example: http://node.i2p.b32:18085/get_info 
16:16:31 <m-relay> <o​frnxmr:monero.social> vs http://node.i2p.b32/get_info
16:16:32 <m-relay> <o​frnxmr:monero.social> vs http://node.i2p.b32:18080/get_info 
16:16:32 <m-relay> <o​frnxmr:monero.social> will all return the same result.
16:16:51 <m-relay> <o​frnxmr:monero.social> i think 18080 might be getting appended automatically if no port is broadcast
16:17:54 <m-relay> <o​frnxmr:monero.social> Which causes 2 entries to be broadcast. The one with no port, and the one with 18080. Im not sure, as i didnt take the time to reproduce it. All i know is i _never_ manually configured mine for 18080, yet it is there on peerlist as a valid peer (and ive connected to myself)
16:19:08 <Lyza> well for now I have configured mine to 18080 and am waiting to see if I self connect to the 'no port' entry at some point
16:22:06 <m-relay> <o​frnxmr:monero.social> The other problem with broadcasting 18080.. cosmetic - is its technically incorrect. a "dummy port" but the wrong dummy port. 18080 is for full p2p, and i2p anon inbound cant bind to 18080 if p2p already is
16:22:52 <m-relay> <o​frnxmr:monero.social> So i still believe this to be ideal
16:25:03 <Lyza> so I'm checking my peer list with `print pl` and I see entries like ".b32.i2p:0" ".b32.i2p:18080:0"
16:25:20 <m-relay> <o​frnxmr:monero.social> also because sync_info and peerlists are ugly, with some nodes having :0, some having no port, some with 18080 and then a plethora of custom ports
16:25:45 <Lyza> it seems like a :0 is getting appended without removing the port given in the config
16:26:15 <m-relay> <o​frnxmr:monero.social> Grep it for sel or s3l
16:29:57 <Lyza> ok? looks similar to other entries
16:30:49 <m-relay> <o​frnxmr:monero.social> When i last checked, i found multiple "duplicates"
16:31:22 <Lyza> yes, most entries have duplicates
16:31:54 <Lyza> jesus I'
16:32:10 <Lyza> I've got i2p entries in my peer list back from when i2p still used peer_IDs
16:32:38 <m-relay> <o​frnxmr:monero.social> 😅
16:32:51 <Lyza> gray peers should like, eventually be purged I feel like
16:34:06 <m-relay> <o​frnxmr:monero.social> Are there old onions too?
16:34:24 <Lyza> node was never configured for tor
16:34:35 <m-relay> <o​frnxmr:monero.social> Ok
16:49:03 <m-relay> <m​urksombra:matrix.org> the research meeting happens on this channel, correct?
16:49:22 <m-relay> <m​urksombra:matrix.org> oh, wrong channel. My bad
18:25:57 <listener> i want to use monero as the main currency for my online business attempts, and i would like to automate as much as possible. Do i have to use the GUI merchant mode or can i use the CLI wallet to automate creation of reception addresses (and an external tool for QR codes) ?
18:28:55 <listener> sorry, wrong channel