07:33:33 <sech1> 63 MH/s
07:33:51 <sech1> this guy stops ramping up on weekends and during the night European time
07:44:04 <gethh> so typical 8/5 day job
07:45:13 <sech1> he probably has to solve a lot of captchas to add "workers" :D
07:46:07 <sech1> These fire hydrants, semaphores, bikes and buses will haunt him forever...
07:48:08 <gethh> lol
08:23:02 <Inge-> new rPi 4 w/8GB ram and 64 bit
08:23:35 <asymptotically> i thought all but the pi 1 were 64 bit, and they just never bothered to ship a 64 bit kernel or userland for it
08:23:49 <Inge-> that might well be true
08:24:11 <Inge-> sech1: I lose a part of my humanity every time I fail a "confirm you are not a robot" captcha
08:38:47 <Inge-> asymptotically: "Not to be left out, today we’ve released an early beta of our own 64-bit operating system image. This contains the same set of applications and the same desktop environment that you’ll find in our regular 32-bit image, but built against the Debian arm64 port."
09:03:51 <hyc> pi3 was the first 64bit, but they have always shipped 32bit OS
09:03:56 <hyc> to retain compat with pi2 and pi1
09:22:14 <Inge-> world moves on
09:24:25 <hyc> it's about time
15:41:19 <xmrpow> 66 Mhs....
15:41:31 <xmrpow> When do you think is this guy going to stop?
15:42:15 <selsta> does the low hashrate per worker speak against ASICs?
15:42:25 <selsta> (not that I think it is an ASIC anyway)
15:42:50 <xmrpow> I think that could be easily faked.
15:54:31 <Inge-> when is that hashrate running?
15:54:39 <Inge-> during workhours, or outside workhours?
15:56:47 <xmrpow> always and it is constantly growing
15:56:56 <xmrpow> Look here: https://xmr.nanopool.org/account/42fVwusSRCpaJvQhLZWCs66Ekf5NUiqfdjhqFR5w4KdgTJkymxrRV4CRb2KkDdwofLVvWMJ6trXSFShN7CA9q7gYU2aChVM/t1wkk37k100
15:57:37 <xmrpow> even the workers shown as offline are just some weak machines which can not submit shares that often
15:58:18 <Inge-> not sure what I'm seeing. 1700H/s?
15:58:48 <xmrpow> ?
15:59:00 <xmrpow> sry wrong link
15:59:05 <xmrpow> that was just one worker
15:59:14 <xmrpow> https://xmr.nanopool.org/account/42fVwusSRCpaJvQhLZWCs66Ekf5NUiqfdjhqFR5w4KdgTJkymxrRV4CRb2KkDdwofLVvWMJ6trXSFShN7CA9q7gYU2aChVM
15:59:44 <Inge-> 60K workers
15:59:51 <xmrpow> yep
16:00:54 <Inge-> all hashrates seem to be multiples of 840 h/s
16:01:57 <xmrpow> hmm you are right...
16:02:00 <xmrpow> good point
16:02:27 <xmrpow> Maybe this guy faked the workers?
16:02:37 <Inge-> There is a clue there, just not sure what it is.
16:07:24 <xmrpow> Why does this guy even bother pointing out each single miner. That does not make much sense.
16:16:10 <sech1> multiples of 840 h/s is just how nanopool counts shares
16:16:25 <sech1> just select individual worker and see hashrate graphs
16:17:57 <selsta> I have to add https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_cs_disable-executable-page-protection to get randomx working with hardened runtime on macOS, does anyone know why?
16:18:38 <xmrpow> sech1: ok
16:20:07 <hyc> selsta: because randomx needs to create code in writable RAM and execute it
16:20:52 <hyc> although we also have a mode to make the pages read-only again before trying to execute, that's not the default
16:21:08 <hyc> and resetting page protections is a perf hit
16:21:44 <selsta> hyc: there is also https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_cs_allow-unsigned-executable-memory but that was not enough
16:22:01 <selsta> but thanks, we can use `com.apple.security.cs.disable-executable-page-protection` without problems
16:28:09 <hyc> in monerod you could set env MONERO_RANDOMX_UMASK 16
16:28:17 <hyc> 16 = RANDOMX_FLAG_SECURE
16:28:29 <hyc> which will toggle the pages to readonly before executing
16:29:17 <selsta> with a perf hit?
16:29:21 <hyc> yes
16:39:57 <selsta> can’t get it to work with the env var, but yea it’s not a problem anyway
16:41:26 <hyc> ok
16:44:01 <hyc> I'm surprised allow_unsigned_executable_memory wasn't enough
16:44:17 <selsta> allow_unsigned_executable_memory is required so that monerod starts without crashing
16:44:29 <selsta> but then when mining it says `Error: Mining did not start -- BUSY`
16:45:45 <hyc> strange
16:46:22 <selsta> do you think there is value in this runtime hardening?
16:47:00 <hyc> for the especially paranoid, yes
16:47:16 <hyc> I think the allow_unsigned... flag only works if we use MAP_JIT on our mmap call
16:47:37 <hyc> which we currently don't
16:47:52 <selsta> there is also https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_cs_allow-jit
16:47:59 <hyc> so if you can play with patching that in randomx/src/virtual_memory.cpp
16:48:02 <selsta> but that did not help, most likely because we don’t use MAP_JIT
16:48:04 <hyc> might be worth testing again
16:48:33 <hyc> here's a relevant patch https://github.com/herumi/xbyak/pull/84/files
16:49:09 <selsta> will try
16:53:13 <hyc> only the mmap in allocMemoryPages() needs this flag
16:53:31 <hyc> allocLargePagesMemory can be left unchanged
17:06:39 <selsta> hmm it’s a bit difficult to test
17:07:10 <selsta> looks like it only likes code signing only likes static gitian binaries
17:07:41 <selsta> don’t have static bin setup here... will test later with gitian
19:39:03 <geonic> hyc did you set the threshold to 64gb after we spoke? I solo mined another block.
19:39:19 <geonic> http://convos.yantra.pw:3000/file/2/G9X5zyDlyFbJAGD0
19:39:23 <geonic> lol
19:42:15 <tevador> geonic: what hashrate?
19:42:35 <geonic> 4000 H/s
19:43:02 <tevador> cool, you won the lottery - twice
19:43:45 <geonic> this is how addictions start
19:46:20 <tevador> post on /r/MoneroMining, it may motivate more solo miners to join
19:46:38 <geonic> I just spammed the main sub
19:47:46 <geonic> will post there as well
19:49:59 <niocbrrrrrr> geonic: couldn't happen to a nicer guy
19:50:19 <geonic> thanks nioc
20:06:44 <hyc> I will take my 10% commission now ;)
20:14:47 <xmrpow> 69 Mhs
20:20:16 <geonic> haha
20:42:53 <gethh> thats around 0.6MW using the most efficient cpu available
20:49:08 <jwinterm> $750 per day at 5 cents per kWh
20:49:25 <jwinterm> 720 even
21:20:29 <xmrpow> It would be like 5307 ryzen9. That would be round about 2,6 million for equipment. With current diff it would take this guy 884 days. I dont think that is worth the risk for an investor.
21:20:55 <xmrpow> * would take him 884 days for roi
21:22:29 <selsta> hyc: did not get it working with MAP_JIT
21:24:24 <selsta> https://github.com/selsta/RandomX/commit/747a76fdbafbe639d669f136a01be8b2ac4f5aa6
21:25:50 <selsta> hmm runtime hardening randomx benchmark might be easier to test...
21:31:46 <selsta> lol I’m dumb :)))
21:32:48 <selsta> com.apple.security.cs.allow-unsigned-executable-memory is enough, even without MAP_JIT
21:32:57 <selsta> my daemon was not synced......
21:41:34 <selsta> hyc: so it appears adding MAP_JIT means it is possible to use com.apple.security.cs.allow-jit instead of com.apple.security.cs.allow-unsigned-executable-memory
21:41:53 <selsta> which looks like an improvement