thats what is in the log of the rpc

couldn't find anything that is explaining what this unwound call stack is

Os? And what did you do to ufw?

ubuntu 22.04

127.0.0.1 ALLOW 127.0.0.1... (full message at <libera.ems.host/_matrix/media/v3/do…87742d081b7a9ab92116dc9208dfbc31877>)

Release binaries? or built from source?

build from source

Try release or do the gitian build if trust issues

github.com/monero-project/monero#compiling-monero-from-source I used this so I shall use the release instead ?

just try the 18.2.2 binaries, if those work youll need to do a gitian or a depends build

mh lemme see

probably need to wait one or two hours to see if this now works

`127.0.0.1 ALLOW 127.0.0.1`

Also - i dont think this is necessary.. ? Did you add this because of some other proxy-like service?

yap

just for a local ngnix

hello alltogether

i would like to ask for a bit help, i want to submit a share and get as error wrong hash. Which hash i ve to submit, please? i tried the blob with altered nonce and the hash result of pow, nothing works

i would appreciate any documentation about though, so i could read through if it is some more effort to explain me

You do not submit a hash, but a nonce.

The hash is just a byproduct of hashing the block template with that nonce.

hi moneromooo, does that mean i have only to submit the nonce ?

i try to sent this: {"method":"submit","id":2,"params":{"id":"a35a9bec-2823-49ee-874b-7d7985b9c804","job_id":"142399","nonce":"01b29b0c","result":"9da610102006a2b82bf6b627324c0c2dd27d0ab07dd6d0eace56f2a52c1a4d2b7c985d520091538dcc0000004e2839e8f44ef396e228eabc828f67f24df882f7ffe847ddffbc075947662242e04a9900"}}

I'm not familiar with the pool RPC, but IIRC xmrig has a --verbose flag which hopefully dumps that traggic.

traffic

i m writing on a custom miner

I gathered :)

by stratum protocol the blob is always 80 bytes, isnt it ?

I'm not familiar with the pool RPC, but I doubt the blob is always 80 bytes.

hmm ok

so the hash should be the blob with computed nonce,or not ?

The PoW hash ? It's the hash of the blob with embedded computed nonce.

yes i mean the pow hash

i have to submit the pow hash, right ?

You do not submit a hash, but a nonce.

The hash is just a byproduct of hashing the block template with that nonce.

And indeed, you just posted: {"method":"submit","id":2,"params":{"id":"a35a9bec-2823-49ee-874b-7d7985b9c804","job_id":"142399","nonce":"...

yes, i understood. but the error message says wrong hash

Then maybe you're not calculating that nonce properly.

Apparently a common-ish bug there is mixing up endiannesses on the hash when comparing to the target.

"result":"9da610102006a2b82bf6b627324c0c2dd27d0ab07dd6d0eace56f2a52c1a4d2b7c985d520091538dcc0000004e2839e8f44ef396e228eabc828f67f24df882f7ffe847ddffbc075947662242e04a9900"}}

hmm...

ok, thank you-i suppose i ve to dive more into

I'd first rig (ahem) your miner to always work on a known block, and check if accepts the known nonce for that block, etc.

Decrease the number of unknowns basically.

ie, a block from the monero chain, where you know this nonce is good for that block hashing block.

ok

which size has target please

target has to be 32 bytes or 4 bytes ?

Depends on the network difficulty. The higher the diff, the more bits will be needed to represent the target.

32 bits is probably not enough.

Take a random recent monero block, count the 0s at the end of the PoW hash, multiply by 4. Gives you a rough idea.

ok

I tried, I count 9 zeroes. 36 bits, give or take. The next digit is a 2, there's at least one more bit.

but the pow hash is always 32 bytes big, how i have to compare it to meet the target, please ?

Look in monerod.

checkhash IIRC

check_hash IIRC

ok, you mean monerod sourc code?

Yes.

ok

ty

fck***, the implemtation of check_hash looks terrible complicate, is there no simpler approach like checking bitcoins ?

i meant like checking pow for bitcoins

It should be the same system. Pick Bitcoin's if you want. Just make sure you get endianness right.

It's just comparing two 256 bit integers really. check_hash is probably optimized with range assumptions.

Yes, I just git grepped, look for "usual slow check", that'll be a very simple, but possibly slow, method.

or maybe bc of asic resistance...the code looks terriblecomplicate

Doesn't factor in.

ah ok

i found something to try, thank you though

In fact, the slowness of monero's PoW hash means you can probaly get away with a slow check_hash anyway.

hmm ok

noob question: how does one efficiently work on a huge code base like monero?

I'm asking because currently I'm building from source and it will probably take ~2h

Same as all code bases. Learn the code.

It does take time, but as yo uget to know it, you get better.

I recommend ccache, and also building just what you need, eg make -C build/wherever game etc.

But yes it is oomphy.

okay thanks, I'll try to get a little more familiar with c++, cmake and how things work in general

hey

could that be possible ?? Submit (Difficulty 8947) : {"method":"submit","id":2,"params":{"id":"4ef16f07-be52-4f90-ac9a-812d05cc5cbd","job_id":"143807","nonce":"000fc468","result":"009a991599a3e29e7c5368b336ef93ad3c2bfb1e81f1d7eef007a0690195a317"}}

i get response: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Wrong hash 8d774851987ddc20f1d4ada7617c4546ff2c6fcf910aab8a6b49f18edccf6d5e 009a991599a3e29e7c5368b336ef93ad3c2bfb1e81f1d7eef007a0690195a317"}}

for the hash i actually take the computed pow hash,is that correct ?

difficulty 8947 looks so small to me ...

a common question, is it necessary that i have to compute the merkle root of the new blob before submit the share ?

i m a bit confused..if i connect to a monero pool - the server immediatly send me a response with job and not the block template

so, if i need coinbase1 and coinbase2 i dont know how to calculate merkle tree root :(

could someone help , please ?

If you're mining to a pool, pools adjust their difficulty to your hash rate. Typically *much* lower than the network difficulty.

You should not have to compute a merkle root with a pool miner. The pool software will do this.

A pool miner just pokes a nonce into the hashing blobl and hashes I think.

hmmmm okey..thank you very much - maybe that info helps me to get a bit further :)

i still get result wrong hash...fck

moneromooo, getblocktemplate command does not work on pool, i m missing something ?

"{\"id\":2,\"jsonrpc\":\"2.0\",\"method\":\"get_block_template\",\"params\":{\"wallet_address\":\"45XMaYZXa61aTu7wCfrwmJ6kPvXt2G12JEkxsocPxfHkgk4SJmvx45e2MFuJwQT1weYJLqtGvLcuCCTCtVVzpwPaFpsvUBX\",\"reserve_size\":60}}\n"

Yes. A pool and monerod are different things. They have different APIs.

oooh okey...

where i could get informations about commands for a pool ?

Well, the world wide web usually has a fair amount of info on various things. There are tools that can search it.

Though IIRC what monero pools call "stratum" is inspired by, but not equivalent to, the Bitcoin "stratum". So make sure you look at the monero version only.

ok :)

(and that, by the way, is a good keyword to search for)

ok

Also, I think I mentined before dumping the RPC traffic from xmrig.

Like this: paste.debian.net/hidden/307bfea4

Definitely not monerod RPC.

yes

TY

That submit was succesful btw. Guves you an example of correct RPC.

ok

i have to find documentation about how to subscribe to pool

i dont find anything

nick Pascal123

moneromooo, i stepped on a stupid question..have i to hash the blob,or i have to hash the seed_hash ?

You hash the hashing blob IIRC.

If we're on about stupid things... make sure you convert the hex to binary. Happened before.

to bytes im converting, yes i do

hmm

hmm... how much time it would take to resolve difficulty 1300000 with 12 cpu threads ?