03:21:37 <Pascal123> hey guys
03:22:29 <Pascal123> i took again a look into structure of monero data and get to q question...
03:23:47 <Pascal123> As i ve seen the blob Data of monero is different than blob Data of bitcoin
03:25:31 <Pascal123> the blob by monero is Block Header + Merkle Tree + xxxxx . so could it be possible that i m changing the nonce at the wrong position ? Actually i m changing the nonce at position 76 to 80, like Bitcoins blob ...
03:25:38 <Pascal123> is that wrong ?
03:51:05 <ofrnxmr[m]> <moneromooo> "Well, the world wide web usually..." <- ^
03:51:06 <ofrnxmr[m]> Im wondering what youre working on? 
03:51:46 <ofrnxmr[m]> Wownero 0.3?
04:01:37 <Pascal123> lol, its more an experimental project
04:04:16 <ofrnxmr[m]> I think you may be looking for #monero or #monero-community-dev
04:04:16 <ofrnxmr[m]> Have you read mastering monero or zero to monero ii?
04:05:35 <Pascal123> i m adapting original some bitcoin code to monero
04:07:35 <Pascal123> but actually im confused about the correct nonce byte position
04:07:57 <Pascal123> at bitcoin blob it is pos 76 to 79
04:08:09 <Pascal123> and i got the feeling at monero it is different
04:09:23 <ofrnxmr[m]> Have you checked if ZtM2 covers it?
04:09:41 <Pascal123> i m looking into it right now
04:11:11 <ofrnxmr[m]> I may have missed it, but what code are you trying to adapt? xyproblem.info and all that
04:11:36 <ofrnxmr[m]> What* are you ultimately* trying to do*
04:12:35 <ofrnxmr[m]> https://www.getmonero.org/library/ ztm and others can be found here
04:18:00 <Pascal123> its more for my personal educational purposes
04:18:10 <Pascal123> in the documentation are mistakes
04:18:25 <Pascal123> nonce is not 32 bytes...it are 4 bytes
04:18:40 <Pascal123> im reading actually zero to monero doc
04:18:50 <anonimauzanto[m]> From what I recall in the block hex there is [major_version, minor_version, timestamp, prev_block_id, nonce, ...]. The first three are varint but I would guess [1 byte, 1 byte, 4 bytes, 32 bytes, 4 bytes (nonce) ...] which would put the nonce at position 76 in hex
04:19:56 <Pascal123> ah ok position 76 is in hex and not a byte position ?
04:20:42 <Pascal123> i need the byte position ...hmm
04:21:05 <Pascal123> so it would be... one moment..position 39
04:21:13 <Pascal123> correct ?
04:21:51 <anonimauzanto[m]> Two hex characters equal one bytes. I believe the position would be 38 if using zero indexing.
04:22:04 <Pascal123> sorry yes 38
04:22:33 <Pascal123> maybe that is my mistake why everytime my hash is wrong
04:23:13 <Pascal123> so my only rest problem would be comparing job to target... i m using actually c#,...i dont have big integers
04:23:29 <Pascal123> i mean really big bigintegers
04:25:28 <Pascal123> but the positon of 38 is in byte and not in hex, correct ? bc at bitcoin you insert the nonce at postion 76 (byteposition)
05:08:02 <Pascal123> hmm.... now i get another error..cannot find job id
05:08:17 <Pascal123> one step further
06:19:10 <ofrnxmr[m]> Monero PoW #monero-pow
06:22:12 <ofrnxmr[m]> Or maybe #p2pool or #p2pool-mini
17:32:42 <anonimauzanto[m]> I built the latest p2pool v3.3 on arm64 arch linux using the same build process as has been used for v3.2 and prior releases. The latest release completes the build process but crashes when attempting to run exactly at the prior versions have run. To confirm I rebuilt v3.2 and it is functioning correctly.
17:32:51 <anonimauzanto[m]> p2pool.service: Main process exited, code=dumped, status=11/SEGV
17:32:51 <anonimauzanto[m]> p2pool.service: Failed with result 'core-dump'.
17:37:51 <ofrnxmr[m]> er #p2pool:libera.chat 
17:37:53 <moneromooo> Did you check the stack trace in that core ? If you don't know how: gdb $binaryname $corename
17:37:58 <moneromooo> bt
17:38:50 <sech1> anonimauzanto[m] paste the callstack of the crash at https://paste.debian.net/
17:39:09 <sech1> It's probably the same as https://github.com/SChernykh/p2pool/issues/262
17:39:21 <sech1> you need to provide i/o socket for your service, read the comments
17:42:44 <anonimauzanto[m]> https://paste.debian.net/1279012/
17:43:28 <anonimauzanto[m]> I will read the comments and attempt modifications. I am not very advanced so it will take me a while to understand what to do.
17:46:34 <sech1> that's not a call stack of the crash
18:11:02 <anonimauzanto[m]> When I start the service it creates zst files in `/var/lib/systemd/coredump`. Running `gdb p2pool <one of those file names>` does not work but that was just a guess because I do not know how to run the command correctly. I do not want to waste anyone's time because of my lack of understanding. If I can do something that helps provide information I will
18:11:49 <moneromooo> If it's systemd, try: coredumpctl debug
18:11:58 <moneromooo> (from memory)
18:14:50 <sech1> if you're running the release binary, it will not give any meaningful callstacks. You need to compile your own p2pool binary
18:15:44 <anonimauzanto[m]> I compiled using commands from the p2pool github 
18:15:45 <anonimauzanto[m]> cmake ..
18:15:45 <anonimauzanto[m]> make -j$(nproc)
18:18:13 <anonimauzanto[m]> When I run coredumpctl debug it prints to console. Here is the text it prints: https://paste.debian.net/1279017/
18:19:09 <sech1> yes, so it crashed inside uv_thread_join()
18:19:23 <sech1> I submitted a possible fix, build the latest source code
18:26:50 <selsta> you have to build with 8832/8831
18:32:32 <anonimauzanto[m]> It is working. I pulled from github, rebuilt, replaced the binary, and confirmed the service started correctly. I also confirmed with the new `p2pool --version` command and received the following after the service started. 
18:32:32 <anonimauzanto[m]> 2023-05-01 18:30:47.2586 Log started
18:32:32 <anonimauzanto[m]> P2Pool v3.3 (built with GCC/12.1.0 on May  1 2023)
18:32:32 <anonimauzanto[m]> 2023-05-01 18:30:47.2603 Log stopped
20:27:04 <DataHoarder> ofrnxmr[m]: it's #p2pool-log / #p2pool-mini libera:chat, #p2pool afaik it's for the Bitcoin one
20:27:28 <DataHoarder> except seems like recently was joined by monero folks, it had like 3 people in the past :D
22:26:51 <RafoAgaev[m]> у каго есть ключ
22:27:16 <RafoAgaev[m]>  ?
22:30:13 <plowsof11> #xmr.ru:matrix.org 
22:40:43 <someoneelse49549> The [Vulnerability Response Process](https://github.com/monero-project/meta/blob/master/VULNERABILITY_RESPONSE_PROCESS.md) seems outdated. The forum is obviously dead and seeing the amount displayed in it don't correlate with the reward being distributed to older (disclosed) report. Is it linked to the Monero General Fund now ?