01:10:25 <gingeropolous> a live nonce distribution visualization would be dope
01:13:47 <gingeropolous> hrm.... i might be able to do that maybe
01:14:43 <xmrpow> Sounds cool ;)
01:16:45 <gingeropolous> oh fuck yeah. it already exists: https://apollo.open-resource.org/flight-control/noncewatch/
01:17:47 <gingeropolous> ah damnit its old
01:17:56 <jwinterm> is that for monello?
01:18:04 <jwinterm> I thought we were over 2M blocks now
01:18:18 <jwinterm> "live"
01:20:13 <gingeropolous> aye. and they're all open this and that but no link to code
01:32:42 <gingeropolous> but yeah. a running monerod. some database thing to store nonce for a given blockheight. and then one of those javascript chart display thingies
01:35:18 <gingeropolous> would also be cool to run a live cluster analysis / PCA to detect when new patterns emerge
06:21:02 <kl_> https://api.hashvault.pro/v3/monero/network/nonce/distribution/png?hashrate=true&nonceColor=%23ff6600
10:49:07 <gingeropolous> kl_, hrmm, that looks like its just recent blocks?
10:55:36 <gingeropolous> hrm, there is a little band there on the bottom right
11:34:53 <hv-bridge> <ＨａｓｈＶａｕｌｔ> Yeah, last 100k blocks.
12:05:57 <sech1> indeed, this is something new: https://i.imgur.com/twOdsl0.png (lower right corner)
12:06:28 <sech1> it almost looks like someone has high byte of the nonce set to 0x01
12:14:55 <Inge-> The red line is Nov30/Dec1 2019?
12:16:18 <sech1> red lines are fork heights
12:18:50 <sech1> it started around block 2144150 (July 17th, noon)
12:21:47 <sech1> there was a 130 MH/s jump at minexmr at that time
12:23:27 <asymptotically> doesn't xmrig-proxy use the higher part of the nonce?
12:23:42 <sech1> it does, but it's a random byte
12:24:13 <sech1> actually jump at minexmr doesn't align with that time, 20 MH/s at f2pool seems more likely for July 17th noon
16:13:32 <moneromooo> Most people use xmrig, right ? Maybe someone who is not me could code a mode where it mines at a random pool in a list, with probability inversely proportional to that pool's share of the network hash rate. Then encourage pool ops to do "reconciliation", where if Alice has sent 1000 hashes to pool0 and 200 hashes to pool1, and Bob sent 500 hashes to pool0 and 500 hashes to pool1, reconciliation
16:13:38 <moneromooo> moves to 1200 for alice/pool0, 300 for bob/pool0, 700 for bob/pool1.
16:14:12 <moneromooo> Pools already run on trust, and this reconciliation would avoid the problem of keeping "dead" pending balances when mining not much on a pool, wich causes miners to not want to do that.
16:15:08 <moneromooo> This should create an easy (and default) way for miners to avoid pools with large hash rate while keeping the same payout frequency.
16:16:24 <moneromooo> It does add a gatekeeper/censor role to whoever maintains the pool list, but that also has positives I guess.
16:19:04 <sech1> I'd rather see sxmr and minexmr switch to self-select only mode :D
16:19:55 <moneromooo> Changing xmrig doesn't rely on pool ops to do something though, which seems like pissing in the wind.
16:20:19 <moneromooo> Ooooh...
16:20:47 <moneromooo> Change xmrig as I said, and add a 0.5 weight multiplier for pools that don't use self select :D
16:57:10 <tevador> several pools could mine to a multisig address (if that's possible)
17:11:09 <gingeropolous> sech1, is there any reason why changing setting the "high byte of the nonce to 0x01" would increase hashrate?
17:11:57 <gingeropolous> is there something unique about the programs that are created if that byte is changed?
17:11:57 <sech1> absolutely no reason, it's probably a bug in the proxy they use
17:12:02 <gingeropolous> ah
17:23:26 <gingeropolous> sech1, you have the code hosted somewhere for pulling that from the chain?
17:23:32 <gingeropolous> githubs etc
17:24:36 <sech1> no
17:25:11 <gingeropolous> bummer. i've half a mind to make a noncewatch webpage thinger
17:27:29 <sech1> it's mostly manual and I have to run a bunch of scripts to get that picture
17:27:44 <sech1> and edit the first one before running to adjust block height
17:28:05 <gingeropolous> yeah, i get it. i just figured I could hack what you have into something else
17:29:42 <gingeropolous> man nanopool's been quiet
17:29:50 <sech1> it calls get_block_headers_range monerod RPC, then extracts nonce values and then calls gnuplot to draw the picture
17:37:29 <gingeropolous> yep, i can imagine the bash script i would write to make that all happen
19:09:30 <hv-bridge> <ＨａｓｈＶａｕｌｔ> Well, if you'd like something more than our api already generate - just let me know.
19:10:22 <hv-bridge> <ＨａｓｈＶａｕｌｔ> Like date range, height range, higher resolution.
19:58:30 <gingeropolous> ah, didn't know that was u
20:00:05 <gingeropolous> this interface was pretty awesome, allows for exploring: https://apollo.open-resource.org/flight-control/noncewatch/