Bye bye Qubic, we won't miss you: github.com/qubic/core/releases/tag/v1.288.0

"remove XMR mining"

<pyratevevo:matrix.org> Pubic gone 🦀🦀🦀

nice

DataHoarder has a nice page to see hashrate distribution blocks.p2pool.observer/pools

(i notice a Monero General fund pool, someone mined a full block there?)

someone on p2pool

plowsof: mini.p2pool.observer/share/5313b662…1b4416f0cfa8b83af47b53edf46d6a11ed0

💗

<user2570:unredacted.org> sech1: Please check DM

I'm on IRC, you're on Matrix. DMs don't go through

<user2570:unredacted.org> sech1: How should I contact you directly regarding xmrig?

Or #monero-pools on Rizon

Or join the IRC :)

<user2570:unredacted.org> sech1: My github account got blocked because of Tor

<user2570:unredacted.org> sech1: I need to send files

I wouldn't open those files anyway

<user2570:unredacted.org> sech1: No 0-day inside. I promise

<user2570:unredacted.org> Is there a mirrored repo somewhere esle? > <sech1> github.com/xmrig/xmrig/issues

the cubists are gone?

where are all the headlines?

<hbs:matrix.org> nioc: Time for dadaism to kick in...

<ofrnxmr:xmr.mx> @user2570:unredacted.org: Just post it on your own repo and share the link

<hbs:matrix.org> The 200kUSD of XMR planned by THORChain would not be sufficient should another similar hack occur...cointelegraph.com/news/kelp-dao-hac…rly-all-75700-eth-through-thorchain

<user2570:unredacted.org> @ofrnxmr:xmr.mx: You are god damn right!

<ofrnxmr> You forgot the comma before "damn" /s

<kiersten5821:matrix.org> 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

<ofrnxmr:xmr.mx> There is no blockchain sync over onion

<ofrnxmr:xmr.mx> Those incoming onion connections (anonymous-inbound) are just an endpoint for peers that are using tx-proxy

What is the context of this again? Do normal wallets have this limitation?

<ofrnxmr:xmr.mx> User asked if running a node and enabling port forwarding to allow incoming connections would have any privacy implications

<ofrnxmr:xmr.mx> 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)

Ah! So a client can sync their wallet over Tor just fine, it's just that the node cannot sync its own info?

lol @ qubic

<ofrnxmr:xmr.mx> BlueyHealer: Yes

<ofrnxmr:xmr.mx> cannot sync the blockchain at all over onion*. And cannot have incoming blockchain sync over tor socks proxy (exit nodes)

ah