00:12:55 * WantClue[m] uploaded an image: (215KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/HkftMEywwRTNGDUKwOpdOoSG/image.png > 00:13:05 thats what is in the log of the rpc 00:13:21 couldn't find anything that is explaining what this unwound call stack is 00:34:00 Os? And what did you do to ufw? 00:34:23 ubuntu 22.04 00:34:56 127.0.0.1 ALLOW 127.0.0.1... (full message at ) 00:35:35 Release binaries? or built from source? 00:35:47 build from source 00:36:12 Try release or do the gitian build if trust issues 00:37:28 https://github.com/monero-project/monero#compiling-monero-from-source I used this so I shall use the release instead ? 00:40:51 just try the 18.2.2 binaries, if those work youll need to do a gitian or a depends build 00:41:10 mh lemme see 00:47:27 probably need to wait one or two hours to see if this now works 00:48:03 `127.0.0.1 ALLOW 127.0.0.1` 00:48:03 Also - i dont think this is necessary.. ? Did you add this because of some other proxy-like service? 00:48:46 yap 00:50:43 just for a local ngnix 06:26:57 hello alltogether 06:29:26 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 06:31:24 i would appreciate any documentation about though, so i could read through if it is some more effort to explain me 06:37:53 You do not submit a hash, but a nonce. 06:38:14 The hash is just a byproduct of hashing the block template with that nonce. 06:44:49 hi moneromooo, does that mean i have only to submit the nonce ? 06:46:41 i try to sent this: {"method":"submit","id":2,"params":{"id":"a35a9bec-2823-49ee-874b-7d7985b9c804","job_id":"142399","nonce":"01b29b0c","result":"9da610102006a2b82bf6b627324c0c2dd27d0ab07dd6d0eace56f2a52c1a4d2b7c985d520091538dcc0000004e2839e8f44ef396e228eabc828f67f24df882f7ffe847ddffbc075947662242e04a9900"}} 06:51:17 I'm not familiar with the pool RPC, but IIRC xmrig has a --verbose flag which hopefully dumps that traggic. 06:51:21 traffic 06:51:49 i m writing on a custom miner 06:52:00 I gathered :) 06:53:05 by stratum protocol the blob is always 80 bytes, isnt it ? 06:56:15 I'm not familiar with the pool RPC, but I doubt the blob is always 80 bytes. 06:56:36 hmm ok 06:57:07 so the hash should be the blob with computed nonce,or not ? 06:57:35 The PoW hash ? It's the hash of the blob with embedded computed nonce. 06:57:50 yes i mean the pow hash 06:58:04 i have to submit the pow hash, right ? 06:58:14 You do not submit a hash, but a nonce. 06:58:19 The hash is just a byproduct of hashing the block template with that nonce. 06:58:40 And indeed, you just posted: {"method":"submit","id":2,"params":{"id":"a35a9bec-2823-49ee-874b-7d7985b9c804","job_id":"142399","nonce":"... 06:58:43 yes, i understood. but the error message says wrong hash 06:59:03 Then maybe you're not calculating that nonce properly. 06:59:33 Apparently a common-ish bug there is mixing up endiannesses on the hash when comparing to the target. 06:59:33 "result":"9da610102006a2b82bf6b627324c0c2dd27d0ab07dd6d0eace56f2a52c1a4d2b7c985d520091538dcc0000004e2839e8f44ef396e228eabc828f67f24df882f7ffe847ddffbc075947662242e04a9900"}} 07:00:06 hmm... 07:00:49 ok, thank you-i suppose i ve to dive more into 07:01:11 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. 07:01:25 Decrease the number of unknowns basically. 07:01:59 ie, a block from the monero chain, where you know this nonce is good for that block hashing block. 07:03:57 ok 07:55:39 which size has target please 07:55:53 target has to be 32 bytes or 4 bytes ? 07:57:02 Depends on the network difficulty. The higher the diff, the more bits will be needed to represent the target. 07:57:17 32 bits is probably not enough. 07:57:55 Take a random recent monero block, count the 0s at the end of the PoW hash, multiply by 4. Gives you a rough idea. 07:59:02 ok 07:59:10 I tried, I count 9 zeroes. 36 bits, give or take. The next digit is a 2, there's at least one more bit. 08:00:18 but the pow hash is always 32 bytes big, how i have to compare it to meet the target, please ? 08:01:32 Look in monerod. 08:01:39 checkhash IIRC 08:01:43 check_hash IIRC 08:02:02 ok, you mean monerod sourc code? 08:02:05 Yes. 08:02:12 ok 08:02:14 ty 11:57:08 fck***, the implemtation of check_hash looks terrible complicate, is there no simpler approach like checking bitcoins ? 11:57:34 i meant like checking pow for bitcoins 12:01:59 It should be the same system. Pick Bitcoin's if you want. Just make sure you get endianness right. 12:03:03 It's just comparing two 256 bit integers really. check_hash is probably optimized with range assumptions. 12:04:27 Yes, I just git grepped, look for "usual slow check", that'll be a very simple, but possibly slow, method. 12:04:30 or maybe bc of asic resistance...the code looks terriblecomplicate 12:04:44 Doesn't factor in. 12:04:51 ah ok 12:05:01 i found something to try, thank you though 12:05:05 In fact, the slowness of monero's PoW hash means you can probaly get away with a slow check_hash anyway. 12:05:27 hmm ok 12:30:36 noob question: how does one efficiently work on a huge code base like monero? 12:31:01 I'm asking because currently I'm building from source and it will probably take ~2h 12:31:07 Same as all code bases. Learn the code. 12:31:21 It does take time, but as yo uget to know it, you get better. 12:31:53 I recommend ccache, and also building just what you need, eg make -C build/wherever game etc. 12:32:23 But yes it is oomphy. 12:33:22 okay thanks, I'll try to get a little more familiar with c++, cmake and how things work in general 12:55:31 hey 12:55:43 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"}} 12:56:15 i get response: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Wrong hash 8d774851987ddc20f1d4ada7617c4546ff2c6fcf910aab8a6b49f18edccf6d5e 009a991599a3e29e7c5368b336ef93ad3c2bfb1e81f1d7eef007a0690195a317"}} 12:57:14 for the hash i actually take the computed pow hash,is that correct ? 12:57:56 difficulty 8947 looks so small to me ... 13:04:39 a common question, is it necessary that i have to compute the merkle root of the new blob before submit the share ? 13:19:09 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 13:19:37 so, if i need coinbase1 and coinbase2 i dont know how to calculate merkle tree root :( 13:19:49 could someone help , please ? 13:45:35 If you're mining to a pool, pools adjust their difficulty to your hash rate. Typically *much* lower than the network difficulty. 13:46:14 You should not have to compute a merkle root with a pool miner. The pool software will do this. 13:46:36 A pool miner just pokes a nonce into the hashing blobl and hashes I think. 13:56:42 hmmmm okey..thank you very much - maybe that info helps me to get a bit further :) 14:03:13 i still get result wrong hash...fck 16:16:14 moneromooo, getblocktemplate command does not work on pool, i m missing something ? 16:17:31 "{\"id\":2,\"jsonrpc\":\"2.0\",\"method\":\"get_block_template\",\"params\":{\"wallet_address\":\"45XMaYZXa61aTu7wCfrwmJ6kPvXt2G12JEkxsocPxfHkgk4SJmvx45e2MFuJwQT1weYJLqtGvLcuCCTCtVVzpwPaFpsvUBX\",\"reserve_size\":60}}\n" 16:19:23 Yes. A pool and monerod are different things. They have different APIs. 16:21:54 oooh okey... 16:22:18 where i could get informations about commands for a pool ? 16:24:18 Well, the world wide web usually has a fair amount of info on various things. There are tools that can search it. 16:25:08 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. 16:25:26 ok :) 16:25:38 (and that, by the way, is a good keyword to search for) 16:25:48 ok 16:26:13 Also, I think I mentined before dumping the RPC traffic from xmrig. 16:27:43 Like this: https://paste.debian.net/hidden/307bfea4/ 16:27:55 Definitely not monerod RPC. 16:28:20 yes 16:28:23 TY 16:28:42 That submit was succesful btw. Guves you an example of correct RPC. 16:34:22 ok 16:36:26 i have to find documentation about how to subscribe to pool 16:36:30 i dont find anything 17:21:11 nick Pascal123 17:22:21 moneromooo, i stepped on a stupid question..have i to hash the blob,or i have to hash the seed_hash ? 17:26:34 You hash the hashing blob IIRC. 17:27:05 If we're on about stupid things... make sure you convert the hex to binary. Happened before. 17:38:35 to bytes im converting, yes i do 17:38:47 hmm 18:27:07 hmm... how much time it would take to resolve difficulty 1300000 with 12 cpu threads ?