Hello Together

i hope you are doing well :)

i stuck again and would appreciate a bit help...in communication with monero mining pool i very often get this responses and i dont know the reason :( Either i get job not found or wrong hash

i have to submit the job id as little endian and in hex, maybe ?

I don't know what pool it is, but usually job id must be exactly the same string as you got before

its antpool

hmm ok, i m submitting the job id as integer as you can see it

but i get this responses

these*

the other of my problems is the error 'wrong hash' . I think i understood, i have to add my nonce to blob at position 39 in hex format, then decode the packed blob to binary and hash it with randomX, but it does not work-i dont get accepted shares

does someone of you has example job for me and result to be able to validate my hashing process, please ?

nanopool, sorry my mistake - it is nanopool i try to use for monero

Nonce is at positions 39-42 in the binary blob (indexing starts from 0), not hex blob. If you get "Cannot find job 472a5" errors, it means this job is expired. You need to always submit solutions to the last job you received from pool.

And all pools update their jobs frequently, every 15-30 seconds.

hmm ok

the blog i get from mining pool...is this the blob i have to use for pow hashing ?

blob i mean

the job blob is the blob for hashing, isnt it ?

my blob is about 76bytes long

in hex,but as binary it is much over double size

152 bytes or so

in the blob i get from mining pool the i thought that would be the job i would have to use for pow function

but it is in hex

You have to use blob that pools gives you. Convert it to binary and find the nonce.

but i have to convert to binary before inserting nonce or afterward ?

thank you, i will try it

Convert from hex (text) first, then poke the nonce in. Or convert the nonce to hex and plonk that (at twice the offset obviously).

You just need to match binary or text with all your data.

hi moneromoo,ok thanks

selsta: Is there a plan yet when approximately to merge my pr into the release branch? monero-project/monero #8800

with v0.18.3.0, adding such a large change to a tiny point release isn't a good idea

don't have a timeline but will think about it

Thanks!

selsta can we get 8619 tested & reviewed for v0.18.3

it would be a massive improvement, especially for mobile wallets

we need to find someone who will review it, it's a large change

jbermanis there anyone up to the task?

good night guys and thanks

rbrunner: why is that being done against the release branch? typically thats for fixes, this isn't necessarily a fix

I guess selsta already commented on that slightly