-
m-relay
<0xfffc:monero.social> selsta I am able to reproduce exact same linker error with boost 1.88.
paste.debian.net/1395365 Why we did hit this issue right after we updated to 1.89. I am not sure yet.
-
m-relay
<0xfffc:monero.social> In addition to that I don't see any commit here that is related to our CI failure:
github.com/msys2/MINGW-packages/com…69ad240bbd96c62c25965a92492f5867+35
-
m-relay
<0xfffc:monero.social> Other than this:
msys2/MINGW-packages 64cfb02 which is quite suspicious.
-
m-relay
<0xfffc:monero.social> Sorry for spamming, let me try reversing this patch.
-
m-relay
<someguyxmr:matrix.org> P2Pool is precompiled to support dev by merge-mining Tari - Does it increase CPU/MEM usage on mining machines?
-
m-relay
<syntheticbird:monero.social> NO
-
m-relay
<syntheticbird:monero.social> no
-
selsta
0xfffc: ty for checking
-
m-relay
<someguyxmr:matrix.org> 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.
-
m-relay
<anotherone:xmr.se> same, randomx dataset (2gb) updates every 2 days, doesn't matter what pool or diff you set
-
m-relay
<someguyxmr:matrix.org> "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...
-
m-relay
<someguyxmr:matrix.org> 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
-
m-relay
<anotherone:xmr.se> yeah, if you set lower diff you will see more requests to pool
-
m-relay
<anotherone:xmr.se> I mean, those request doesn't consume a lot of bandwidth, randomx dataset does
-
m-relay
<anotherone:xmr.se> but if you don't want to see a lot of network activity at all
-
m-relay
<anotherone:xmr.se> set higher diff
-
m-relay
<anotherone:xmr.se> also, p2pool adjusts diff automatically
-
m-relay
<anotherone:xmr.se> and also, tuning diff won't cause you to loose profit (be in a pplns window)
-
m-relay
<someguyxmr:matrix.org> how high it is typically, let's say for average pc with ~20 KH/s
-
m-relay
<someguyxmr:matrix.org> oh yea forgot it's on PPLNS
-
m-relay
<anotherone:xmr.se> idk to be honest, but it seems pretty high, I adjust diff manually for each miner and use p2pool through xmrig-proxy
-
m-relay
<anotherone:xmr.se> trying to adjust it so miners do shares approx every 30 secs
-
m-relay
<anotherone:xmr.se> don't know if I'm doing it right actually
-
m-relay
<anotherone:xmr.se> I was learning about this stuff too lately
-
m-relay
<ofrnxmr:xmr.mx> off topic
-
m-relay
<someguyxmr:matrix.org> sorry, will clean it up
-
m-relay
<ofrnxmr:xmr.mx> Dont delete
-
m-relay
<ofrnxmr:xmr.mx> Doesnt actuallt delete anyrhin, just move discussion to Monero Mining or Monero
-
m-relay
<everoddandeven:monero.social> Hi guys, but when I run a --regtest node, how high do I have to mine to activate v16 of the protocol?
-
m-relay
<jeffro256:monero.social> 0 blocks , with regtest it starts out as the latest fork already
-
m-relay
<gingeropolous:monero.social> what else is regtest mode supposed to be capable of doing?
-
moneromooo
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.
-
DataHoarder
@anotherone: dataset doesn't consume bandwidth. It's generated locally. The seed to generate these is always sent and it's 32 bytes
-
m-relay
<anotherone:xmr.se> thanks for clarifying DataHoarder
-
m-relay
<everoddandeven:monero.social> Oh good, thank you
-
m-relay
<everoddandeven:monero.social> So wallet must be a testnet one?
-
m-relay
<ofrnxmr:monero.social> No
-
m-relay
<masayuki:wired.rehab> Is there a mailing list thread or something on developer discussion for addressing the weaknesses demonstrated by Qubic?
-
m-relay
<masayuki:wired.rehab> All I've been able to find on the topic so far is speculation and opinions, not much in terms of technical discussion.
-
moneromooo
-
moneromooo
And/or hang out in #monero-research-lab, they have regular meetings
-
m-relay
<masayuki:wired.rehab> A lot of duplicates, scattered discussions, but this is better
-
m-relay
<masayuki:wired.rehab> Thanks for the links
-
m-relay
<ofrnxmr:xmr.mx> There's a lot of noise on the topic in general
-
m-relay
<ofrnxmr:xmr.mx> The mrl meeting logs are at monero-project/meta/issues
-
DataHoarder