hey guys

i took again a look into structure of monero data and get to q question...

As i ve seen the blob Data of monero is different than blob Data of bitcoin

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 ...

is that wrong ?

<moneromooo> "Well, the world wide web usually..." <- ^

Im wondering what youre working on?

Wownero 0.3?

lol, its more an experimental project

I think you may be looking for #monero or #monero-community-dev

Have you read mastering monero or zero to monero ii?

i m adapting original some bitcoin code to monero

but actually im confused about the correct nonce byte position

at bitcoin blob it is pos 76 to 79

and i got the feeling at monero it is different

Have you checked if ZtM2 covers it?

i m looking into it right now

I may have missed it, but what code are you trying to adapt? xyproblem.info and all that

What* are you ultimately* trying to do*

getmonero.org/library ztm and others can be found here

its more for my personal educational purposes

in the documentation are mistakes

nonce is not 32 bytes...it are 4 bytes

im reading actually zero to monero doc

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

ah ok position 76 is in hex and not a byte position ?

i need the byte position ...hmm

so it would be... one moment..position 39

correct ?

Two hex characters equal one bytes. I believe the position would be 38 if using zero indexing.

sorry yes 38

maybe that is my mistake why everytime my hash is wrong

so my only rest problem would be comparing job to target... i m using actually c#,...i dont have big integers

i mean really big bigintegers

but the positon of 38 is in byte and not in hex, correct ? bc at bitcoin you insert the nonce at postion 76 (byteposition)

hmm.... now i get another error..cannot find job id

one step further

Monero PoW #monero-pow

Or maybe #p2pool or #p2pool-mini

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.

p2pool.service: Main process exited, code=dumped, status=11/SEGV

p2pool.service: Failed with result 'core-dump'.

er #p2pool:libera.chat

Did you check the stack trace in that core ? If you don't know how: gdb $binaryname $corename

bt

anonimauzanto[m] paste the callstack of the crash at paste.debian.net

It's probably the same as SChernykh/p2pool #262

you need to provide i/o socket for your service, read the comments

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.

that's not a call stack of the crash

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

If it's systemd, try: coredumpctl debug

(from memory)

if you're running the release binary, it will not give any meaningful callstacks. You need to compile your own p2pool binary

I compiled using commands from the p2pool github

cmake ..

make -j$(nproc)

When I run coredumpctl debug it prints to console. Here is the text it prints: paste.debian.net/1279017

yes, so it crashed inside uv_thread_join()

I submitted a possible fix, build the latest source code

you have to build with 8832/8831

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.

2023-05-01 18:30:47.2586 Log started

P2Pool v3.3 (built with GCC/12.1.0 on May 1 2023)

2023-05-01 18:30:47.2603 Log stopped

ofrnxmr[m]: it's #p2pool-log / #p2pool-mini libera:chat, #p2pool afaik it's for the Bitcoin one

except seems like recently was joined by monero folks, it had like 3 people in the past :D

у каго есть ключ

?

#xmr.ru:matrix.org

The [Vulnerability Response Process](github.com/monero-project/meta/blob…r/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 ?