00:47:49 ok, seems like a worthwhile change. I can PR it or do you want to? 00:47:58 I did already 00:48:11 ok cool 00:48:13 https://github.com/tevador/RandomX/pull/183 00:52:35 I commented. I don't like duplicating the mmap call multiple times. 00:52:43 would prefer just tweaking the flags instead 00:57:05 yep ok 00:57:59 updated 00:59:24 looks good, approved 00:59:48 iOS should have the same concern, and it runs arm64 native 01:00:32 does MAP_JIT exist on linux? 01:00:38 nope 01:00:58 it's definitely Apple-specific 07:25:46 70.5 MH/s, seems to have stopped growing 07:26:30 the fucker earns $3272/day 11:02:17 commandeering data centers for fun and profit 11:03:17 such a methodical increase in hashrate. maybe it's not stealing unused cycles. maybe it's an actual mining farm 11:03:37 but built from old/reclaimed servers 11:16:19 and now he's dropping, 69.6 MH/s... not a mining farm! 11:18:56 consider how many kW he must be burning thru, e probably saw his electric bill :P 19:05:54 mega miner just lost 50 Mh/s https://xmr.nanopool.org/account/42fVwusSRCpaJvQhLZWCs66Ekf5NUiqfdjhqFR5w4KdgTJkymxrRV4CRb2KkDdwofLVvWMJ6trXSFShN7CA9q7gYU2aChVM 19:06:01 40 I guess 19:06:24 this guy looks more like a botnet with daily oscillations https://xmr.nanopool.org/account/47NG3EVgM374qBkK2Cn4PpD5PwajyqDj41URpkrc9nj1CVRqUCFcwjCFv2j5KZehUVeo34GvBq7e1hFTohnjK9VG9cU3f1G 19:13:27 Friday. someone must've shut off a bunch of machines for the weekend ;) 19:14:47 a botnet that stopped growing? how? usually a malware infection just keeps continuing to spread. 19:15:12 maybe more like a sysadmin net 19:16:17 that could be, yeah, ramping up for otherwise idle time. but it spends more time up than down 19:17:13 maybe it's a dedicated mining farm, but in a place with poor ventilation, so it only operates during cooler hours of the day 19:17:38 or in a place with differential electrical rates, so it only ramps up during low fee hours 19:18:01 that seems more likely, but if that was the case why run half the machines when it's not profitable? 19:19:43 yeah, no idea 19:22:22 or someone exploiting cloud providers in some way and one provider found out about it 21:23:11 Down to 27.5 MH/s, just as I thought. Some big cloud provider was first to kick him! 21:24:40 yea sounds most likely 21:29:19 someone on TG was talking about having had 60MH on AWS until recently 21:31:56 i heard MS as well but it was just an article title, i didnt read it. 22:21:42 I'm surprised that they could get past a service provider's billing system. they should be tracking every CPU second being burned.