09:01:45 There is no third network, other private blockchains are personal projects of individual developers that nobody cares about, with at most 40 reachable nodes. Linking transactions to their sender origin in those networks can be done by anyone with a monthly budget of $100. It's literally just Monero that has a network, regardless of whether the majority of it consists of spy nodes and botnets... 09:01:45 The Zaldo RichList will be released to the public when summer is over for me, in about two weeks. 09:10:54 @jhendrix:imagisphe.re: what about FIRO ? A developers private project ?! 09:19:22 Well firo has trusted masternodes trading decentralisation for 51% attack def and fast finality 09:24:15 @antilt:we2.ee: Yes, it's the same problem as with Zcash. I analyzed their network while working on Maldo Map, and most blocks are either empty or contain transparent transactions. 09:24:31 It's better to move to the off-topic room. 12:11:08 @jhendrix:imagisphe.re: thats what my analysis showed, too. 12:16:20 I love how this new bot have the side effect of logging forever across several matrix instances the exact timestamp at which IRC people connected and the IP with which they connected... 12:16:42 all the other IRC loggers do the same :) 12:17:38 the IPs are no longer shown by default if you have a libera account, but I think I mentioned it elsewhere and probably will remove these unless they are a user or project mask 12:17:43 cloak* 12:19:42 ack 12:20:05 says user/meow/DataHoarder :) 12:27:52 @tevador Did not make it Wed, but PoP is a most promising proposal. Compared it to the well tested chain fork rule in Ethereum - which is also calculating fork weights (LMD GHOST). There is btw an incentive to keep your local time synced, same as in Eth, which worked so far for Eth. 13:24:24 hi 20:49:57 @antilt:we2.ee: I think time is fragile NTP is insecure 20:56:23 @kedihacker-5f270858d73408ce4feb2b57:gitter.im: NTP is an insecure protocol, but you don't particularly needs to rely on it for syncing time. Kicksecure (whonix) relies on fetching the timestamp in the header of an onion site for syncing time. 20:57:24 they then subtract the request/response latency and they get more than enough precision 21:15:29 #144 doesn't need synced clocks.