07:51:59 <0xfffc:monero.social> selsta I am able to reproduce exact same linker error with boost 1.88. https://paste.debian.net/1395365/ Why we did hit this issue right after we updated to 1.89. I am not sure yet. 08:06:44 <0xfffc:monero.social> In addition to that I don't see any commit here that is related to our CI failure: https://github.com/msys2/MINGW-packages/commits/master/?since=2025-08-05&until=2025-08-21&before=7395b7c769ad240bbd96c62c25965a92492f5867+35 08:21:22 <0xfffc:monero.social> Other than this: https://github.com/msys2/MINGW-packages/commit/64cfb020b767b315332dc3632dd034ec8515ed64 which is quite suspicious. 08:21:39 <0xfffc:monero.social> Sorry for spamming, let me try reversing this patch. 10:04:20 P2Pool is precompiled to support dev by merge-mining Tari - Does it increase CPU/MEM usage on mining machines? 10:05:48 NO 10:05:52 no 12:42:08 0xfffc: ty for checking 13:08:07 How much more network traffic there is by using P2Pool vs Centralized Pool? I'm using xmrig-proxy and currently it's auto-adjusted to ~480k diff, how this compares to P2Pool? asking before testing on my own, because I don't want to overload my mining network with too many packets. 13:11:21 same, randomx dataset (2gb) updates every 2 days, doesn't matter what pool or diff you set 13:13:04 "doesn't matter what pool or diff you set" - I don't think that's true, set diff to 1 and see how many packets will be sent... 13:13:43 on P2Pool I don't want to manually set the diff, because it can be too high for the given time window but afraid that auto will be too low 13:13:57 yeah, if you set lower diff you will see more requests to pool 13:14:32 I mean, those request doesn't consume a lot of bandwidth, randomx dataset does 13:14:42 but if you don't want to see a lot of network activity at all 13:14:46 set higher diff 13:15:11 also, p2pool adjusts diff automatically 13:15:46 and also, tuning diff won't cause you to loose profit (be in a pplns window) 13:15:47 how high it is typically, let's say for average pc with ~20 KH/s 13:16:09 oh yea forgot it's on PPLNS 13:17:06 idk to be honest, but it seems pretty high, I adjust diff manually for each miner and use p2pool through xmrig-proxy 13:17:33 trying to adjust it so miners do shares approx every 30 secs 13:17:58 don't know if I'm doing it right actually 13:18:15 I was learning about this stuff too lately 13:18:57 off topic 13:19:15 sorry, will clean it up 13:19:31 Dont delete 13:19:47 Doesnt actuallt delete anyrhin, just move discussion to Monero Mining or Monero 13:20:27 Hi guys, but when I run a --regtest node, how high do I have to mine to activate v16 of the protocol? 14:03:47 0 blocks , with regtest it starts out as the latest fork already 14:08:27 what else is regtest mode supposed to be capable of doing? 14:24:05 It nukes your chain at startup (unless you tell it not to), it has a generateblocks call (not sure why it's regtest only, I canned that), it mimics testnet while using a different db location by default. 14:43:42 @anotherone: dataset doesn't consume bandwidth. It's generated locally. The seed to generate these is always sent and it's 32 bytes 15:15:25 thanks for clarifying DataHoarder 18:06:39 Oh good, thank you 18:06:58 So wallet must be a testnet one? 18:56:00 No 19:58:12 Is there a mailing list thread or something on developer discussion for addressing the weaknesses demonstrated by Qubic? 19:58:43 All I've been able to find on the topic so far is speculation and opinions, not much in terms of technical discussion. 20:03:46 Look around https://github.com/monero-project/research-lab/issues 20:04:15 And/or hang out in #monero-research-lab, they have regular meetings 20:05:55 A lot of duplicates, scattered discussions, but this is better 20:06:07 Thanks for the links 20:06:34 There's a lot of noise on the topic in general 20:07:17 The mrl meeting logs are at monero-project/meta/issues 20:23:14 ^ https://libera.monerologs.net/monero-research-lounge and https://libera.monerologs.net/monero-research-lab logs