07:19:31 Bye bye Qubic, we won't miss you: https://github.com/qubic/core/releases/tag/v1.288.0 07:19:34 "remove XMR mining" 07:27:31 Pubic gone 🦀🦀🦀 07:28:41 nice 07:30:09 DataHoarder has a nice page to see hashrate distribution https://blocks.p2pool.observer/pools 07:31:46 (i notice a Monero General fund pool, someone mined a full block there?) 07:33:49 someone on p2pool 07:34:22 plowsof: https://mini.p2pool.observer/share/5313b6628b27c6d48420393a86b941b4416f0cfa8b83af47b53edf46d6a11ed0 07:35:12 💗 09:03:54 sech1: Please check DM 09:05:06 I'm on IRC, you're on Matrix. DMs don't go through 09:07:11 sech1: How should I contact you directly regarding xmrig? 09:07:35 https://github.com/xmrig/xmrig/issues/ 09:07:49 Or #monero-pools on Rizon 09:08:00 Or join the IRC :) 09:09:10 sech1: My github account got blocked because of Tor 09:09:31 sech1: I need to send files 09:09:45 I wouldn't open those files anyway 09:10:26 sech1: No 0-day inside. I promise 09:16:49 Is there a mirrored repo somewhere esle? > https://github.com/xmrig/xmrig/issues/ 11:32:52 the cubists are gone? 11:33:04 where are all the headlines? 11:34:27 nioc: Time for dadaism to kick in... 12:28:40 @user2570:unredacted.org: Just post it on your own repo and share the link 13:47:42 The 200kUSD of XMR planned by THORChain would not be sufficient should another similar hack occur...https://cointelegraph.com/news/kelp-dao-hacker-launders-nearly-all-75700-eth-through-thorchain 13:56:51 @ofrnxmr:xmr.mx: You are god damn right! 14:25:25 You forgot the comma before "damn" /s 16:45:04 then how does it connect to peers with onion addresses > <@ofrnxmr:xmr.mx> you can run the node behind tor, but you cant accept incoming connections over tor 16:49:57 There is no blockchain sync over onion 16:50:48 Those incoming onion connections (anonymous-inbound) are just an endpoint for peers that are using tx-proxy 16:51:20 What is the context of this again? Do normal wallets have this limitation? 16:55:00 User asked if running a node and enabling port forwarding to allow incoming connections would have any privacy implications 16:56:23 I responded that running a node has privacy implications, period. and that you can put the traffjc behind tor, but that incoming connections (over tor) isnt possible in that configuration (the original q about incoming connections) 17:02:49 Ah! So a client can sync their wallet over Tor just fine, it's just that the node cannot sync its own info? 17:08:40 lol @ qubic 17:15:10 BlueyHealer: Yes 17:16:42 cannot sync the blockchain at all over onion*. And cannot have incoming blockchain sync over tor socks proxy (exit nodes) 17:17:17 ah