<ravfx:xmr.mx> cheervision.co/ipinfo/asn/54098

<ravfx:xmr.mx> There are missing range in the MRL BAN LIST, please update asap

<ravfx:xmr.mx> 23.29.53.0/24

<ravfx:xmr.mx> 23.92.32.0/20

<ravfx:xmr.mx> 91.198.115.0/24

<ravfx:xmr.mx> 100.42.27.0/24

<ravfx:xmr.mx> 162.218.65.0/24[... more lines follow, see mrelay.p2pool.observer/e/zObj8cAKeGZ5OE80 ]

<ravfx:xmr.mx> 23.92.32.0/20

<ravfx:xmr.mx> 23.92.32.0/20 is lionlink, that's 4096 address lol

<ravfx:xmr.mx> networksdb.io/ip-addresses-of/lionlink-networks

<ravfx:xmr.mx> that one have many other in 23.29.*

<ravfx:xmr.mx> (sorry for the flood, I was just reviewing "what to block" for some friends and noticed new ips)

<ravfx:xmr.mx> that /20 seam to be fresh

<ravfx:xmr.mx> but other for second link to study to confirm

<preland> Nice catch

<preland> Has lionlink made any other comments on the spynode issue past their initial one, or are they just hoping to sweep this all under the rug 😂

<ravfx:xmr.mx> abuseipdb.com/check/AS54098

<ravfx:xmr.mx> here they only list 1280 ip in that 23.92 range (23.92.32.0 - 23.92.36.255)

<ravfx:xmr.mx> I think we have a few 36 in the MRL ban list but it should be good to ban complete range)

<boog900> I only put IPs on the list which actually ran monero nodes > <@ravfx:xmr.mx> 23.29.53.0/24

<boog900> They've had more IPs for a while

<boog900> moneronet.info

<boog900> That's the first time I have seen a node in the big subnets pass the peer checks as well

<boog900> You can see on that site

<boog900> 1 single node in the block of spies

<preland> @boog900: Does that mean that that node isn’t a spy, or that they are learning how to adapt to obfuscate the spying

<ravfx:xmr.mx> Just block the whole thing (imo)

<boog900> @preland: Could be either, there isn't really anything for them to discover on how to fix it though, the method is public.

<boog900> Most likely they just exposed a real node on that IP for whatever reason, if they were going to fix them getting found as spy nodes they would've updated them all.

<preland> @boog900: I guess that’s fair

<preland> Unless they are trying to be smart and are going to slowly switch out the spy nodes with good ones and claim that it was “independent operators” taking over the addresses or smth

<boog900> I don't think that would fool anyone for the LionLink nodes, but yes they could be adding more nodes on other ASNs

<boog900> The amount of nodes in the network hasn't really changed though, that's also tracked on the site

LionLink Network is legit, banning all IPs associated with them it not a good idea

Hi there! I was wondering if it's possible to contribute to the Monero project? I have a Mathematics MSc background, am very interested in decentralized infrastructure, and was wondering if there was any way I could help :)

<namenet:matrix.org> Guest21: #monero-research-lounge:monero.social is typically used for this kind of casual conversation. Your expertise is invaluable, especially when it comes to auditing proofs. You're likely to find others who share similar interests and knowledge in the lounge

<ofrnxmr> @namenet:matrix.org: Lab is the right place

<namenet:matrix.org> I thought labs was for meetings only 😅

<namenet:matrix.org> My mistake then!

<sgp_> > <@kayabanerve:matrix.org> Hello,I reached out to Cypher Stack to request they review the security proofs for GBPs. While Goodell reviewed Aaron's proofs prior, Aaron updated the protocol to a prior draft due to it being a more efficient variation (a few hundred bytes) at my request.Goodall, while reviewing the proofs, no [... too long, see mrelay.p2pool.observer/e/14vEj8EKb0NUdzh4 ]

<sgp_> Prelim approval from me if I don't make the meeting

<sgp_> (not that I get a vote ofc, but it has my support. Let's keep this moving :))