-
selsta
-
selstalol
-
UkoeHBartificial misinformant at it again
-
hycso much for our AI overlords
-
moneromoooThat's where the three laws of robotics fail. The AI is so insane it will not realize it's going aginst the laws.
-
TheCharlatanI can't verify the gitian sigs, since I'm on holiday.
-
Guest82@+moneromoo thanks for the tip to run with --offline --fixed-difficulty N yesterday. That seems to be working just like I need. :)
-
RaydarI see that when mining with xmrig to the monerod rpc endpoint, Xmrig posts something like the following:
-
RaydarnX-Hash-Difficulty: 10729\r\n\r\n{"id":2,"jsonrpc":"2.0","method":"submitblock","params":["101(shortended)00"]}'
-
RaydarJust the hash and the difficulty. I thought I was going to get a blob and nonce that I can use to verify the work before sending it to the daemon.
-
RaydarAny tips on how I can validate the hash before sending it to the daemon?
-
ofrnxmr[m]i think miner self select config option. #p2pool-mini:libera.chat
-
moneromoooAs an aside, you can check whether X-Hash-Difficulty is at least daemon diff and avoid forwarding in that case. Saves daemon cycles.
-
RaydarI don't think I understand how miner self select config option helps here.
-
RaydarTo check whether X-Hash-Difficulty is at least daemon diff is something, but it's not quite enough for my use case.
-
RaydarI'm pretty sure I do need to validate the hash with randomx and therefore at least need the nonce used for the hash submitted by xmrig.
-
moneromoooThe nonce will be included in the data in params.
-
moneromoooIf you must, you can parse that data as a block hashing blob. But you can just hash it as is.
-
moneromoooI think it *should* be the hashing blob.
-
moneromoooThough you may not have to hash it. Even if the xmrig process is the adversary, something is going to have to hash. Either you or monerod. And monerod will do it anyway.
-
RaydarOh. I must have confused what the params are. I thought that was the completed hash already. Now I need to do some more testing :)