seddd: around ?

ew. Wrong chen, nvm.

hyc: ok. people seem to have trouble writing randomx in golang or any other vm because of this one instruction.

how sad for them

:D

a lot of GPUs struggle with it too

but the point of using cfround is to make life miserable for ASIC builders

and it achieves that

yeah makes sense

hyc: it also hurts attempts to implement say a full node in wasm

yes

we already discovered this...

ok

the solution, if you want to do things from a web client, is to call out to a randomx service

tevador has already written this too

I don't really understand the point of reimplementing librandomx in Golang, particularly since Go isn't a low-level enough language to do it.

Maybe to be able to claim you created it ? :)

lol

to get decent performance from a randomX VM you need asm support. the purpose of Go is to isolate inexperienced programmers from the hardware. completely conflicting goals.

<[discord] Arctic#5824>: randomX... in *java*

<[discord] Arctic#5824>: nono, ***PYTHON***

if you enjoy implementing floating point math in interpreted languages, knock yourself out...

hyc: if Intel/AMD/ARM fix their floating point implementations in a processor 100 years from now, won't all old randomx calls become unverifiable?

what do you mean fix?

what makes you think they're broken?

if i were the "deep state" "cigarette smoking man" much like how NIST tried to implement kleptographic backdoor in Dual_EC_DRBG, i would influence IEEE to upgrade IEEE 754 ever so subtley just to hurt monero

How could that hurt Monero? Just use softfloat or something similar in that unlikely case?

lol

nobody is going to incompatibly upgrade IEEE-754. Scientists all around the world would revolt.

all the supercomputing centers around the country, wher ethe gov't runs their nuclear bomb simulations, would break.

once people start trading nukes using monero, those neutron transport equations in those computers will be worth breaking

the RandomX PR looks now merged

is the code safe enough to include in the upcoming release or would it be better master only for a while?

I don't think it's urgent for release, master would be fine

ok

yes, keep it in master for now unless we need to patch the rounding modes

wat is in the PR?

but I don't think Monero is affected

niocbrrrrrr RandomX used to modify the rounding mode of the calling thread

which apparently caused some issues on some other blockchain

thx

tevador: apparently the Loki issue was not because of RandomX

is there a write-up somewhere?

see monero-project/monero #6534

it has also been an issue with monero for a while

there's no floating point math in the monero source

aside from printing values like hashrate and such

btw coming up on 6 months since the fork

hashrate still looks normal

how's nonce distribution looking?

I haven't seen a recent analysis, but I'm sure there are no ASICs for RandomX (apart from those made by AMD)

Nonce distribution looks all the same since the fork

I tried many different visualization approaches and didn't find any irregularities