00:21:30 e​longated:matrix.org: Why you want to brick something? It’s cpu mining
00:21:57 e​longated:matrix.org: Unless you want only intel and and mining
00:22:06 e​longated:matrix.org: Unless you want only intel and amd mining
00:22:39 s​yntheticbird:monero.social: Formality vs Objectivity
00:23:08 s​yntheticbird:monero.social: Formality: RandomX is an algorithm made to be inefficient on ASIC. X9 is a very efficient CPU, there is no problem
00:23:39 e​longated:matrix.org: Botnet-dominant-algo ?
00:23:43 s​yntheticbird:monero.social: Objectivity: RandomX is an algorithm made to fight ASIC centralization. X9 is 77% more efficient than the competition, drawing people around it. There is a problem.
00:24:22 s​yntheticbird:monero.social: and I can even argue that RandomX is made so that "everyone" can access mining, so in that sense intel and amd wining is not an issue
00:24:39 s​yntheticbird:monero.social: you just have to adapt it when ARM will conquer the HPC world
00:24:56 e​longated:matrix.org: Botnet operators rejoice
00:27:28 e​longated:matrix.org: Someone made an efficient cpu ? Fork it
00:30:03 e​longated:matrix.org: What was qubic using to mine ?
00:30:04 e​longated:matrix.org: Not bitmain but same cpus you want to have better hashrate
00:32:44 s​yntheticbird:monero.social: actually iirc, they forced their nodes to have threadrippers
00:32:48 s​yntheticbird:monero.social: and you want EPYC cpus
00:33:22 s​yntheticbird:monero.social: but anyway, Qubit sponsoring is still \* ahem \* a mystery \* AHEM AHEM \*
00:33:24 e​longated:matrix.org: “Mining”
00:34:03 s​yntheticbird:monero.social: so I would argue that doesn't count because they really could have just bought the X9 and attack monero too
00:34:54 e​longated:matrix.org: ztrash ecosystem, right before their pump
00:34:56 e​longated:matrix.org: Reorg made sure we have slow money flow due to increased conf by exchanges
00:36:03 e​longated:matrix.org: Nobody in right Mind is going to buy x9 to kill a coin they are mining
00:36:03 e​longated:matrix.org: But you could do that by renting servers
00:36:38 e​longated:matrix.org: Same thing randomxv2 wants efficiency for
00:37:30 e​longated:matrix.org: Anyways you guys killed xmr in 2018 , feel free to do it again
00:42:31 s​yntheticbird:monero.social: what happened in 2018?
00:42:34 s​yntheticbird:monero.social: I wasn't born yet
05:39:29 g​ingeropolous:monero.social: yeah, just upping the dataset seems not right. though, at some point, we may get 2gb cache .. granted, that could be a while.....
07:15:44 sech1: I didn't say that I want to brick X9. Because even if it's bricked by some specific change, next version will return with the same efficiency gap. It's more sustainable to close the efficiency gap by making it more fit for regular CPUs, so this is the main plan.
08:55:03 eureka: what's the word on the x9
08:55:16 eureka: haven't done any nonce analysis lately but i'd wager it's no different from the x5 pattern
08:55:21 eureka: anybody done the heavy lifting yet?
08:55:41 eureka: also jumping straight to x9 seems to infer there was an x7 that didn't hit the market, curious
08:57:43 eureka: been keeping eyes on sophon and no real sign of new cores on that front, possible that bitmain put together a rx-specific core for the x9 instead of reusing their existing core
08:58:37 eureka: did we ever figure out if sg2042r was particularly different from stock sg2042?
09:04:57 sech1: No, sg2042r never had public datasheets, so no idea
09:06:51 sech1: nonce patterns seem to be the same
09:11:14 eureka: hm, figures probably roughly the same host firmware, job distribution, program generation etc
09:11:20 eureka: just a more efficient core
09:11:54 eureka: i never had luck getting a decently priced x5, best offer i got was $1500 lol L
09:14:20 eureka: i did have some potential leads on loading custom code on x5, it really looks like they run the sg2042r more or less bare metal, small bootstrap program to bring up the other cores and load jobs/send responses
09:14:42 eureka: found some snippets of rv64 code inside the arm-compiled xmrig binary on the host firmware
10:27:08 DataHoarder: eureka: I posted some nonce analysis from before focusing on their stripes as well, if anything they have stayed stable or gone down over time
14:54:47 gingeropolous: amazing bitmain chose this path again.
15:11:52 sech1: The zoomed-in nonce suggests 32 mining threads per CPU (there are more than 32 stripes, but they fade out quickly after 32nd).
15:25:55 DataHoarder: There are 11 stripes (0-10) and I have stacked them all together via modulo. 0th is removed due to the amount of other stuff there. I haven't calculated difficulty / hashrate for these bands yet, I estimate I'll be done sometime next year
15:27:36 DataHoarder: On the zoom-in stack they appear slightly offset from why would be powers of two, so I'll check that a bit closer as well
15:28:26 DataHoarder: Do we have insight into the binary code what was making these splits?
16:00:44 hyc: the SG2042 is really a pretty weak chip compared to AMD Epyc https://arxiv.org/html/2406.12394v1
16:03:17 hyc: but they would have released the SG2044 last year https://github.com/RISCVtestbed/riscvtestbed.github.io/blob/main/assets/files/hpcasia24/hpc_asia_wang.pdf
16:04:19 hyc: SG2042 had 4 channels DDR4-3200. SG2044 has 8 channels LPDDR5-9000
16:07:24 hyc: SG2044 would be the most likely chip in the X9 https://arxiv.org/abs/2508.13840
16:07:45 hyc: same cores as SG2042, but upgraded to vector extension 1.0, and upgraded memroy controllers
16:12:00 hyc: 2x24GB is 1687euro https://www.ldlc.com/en/product/PB00668682.html