This is probably a server-side issue, but looking up online gave zero clues, wondered if you could hint me at what might be wrong.
Running a Bitcoin Core-based altcoin on localhost:8332 and trying to set up cpuminer to mine for it. cpuminer successfully fetches work, yet when it submits calculated blocks, the server rejects them with this:
{"result":null,"error":{"code":-22,"message":"Block does not start with a coinbase"},"id":1}
EDIT 2: I may be wrong, but it looks like the nonce field is 8 bytes instead of 4 in this altcoin, causing the whole block structure to shift compared to the original Bitcoin. Wonder if the miner can be adapted to a different nonce field size?
Hello!
This is probably a server-side issue, but looking up online gave zero clues, wondered if you could hint me at what might be wrong.
Running a Bitcoin Core-based altcoin on localhost:8332 and trying to set up cpuminer to mine for it. cpuminer successfully fetches work, yet when it submits calculated blocks, the server rejects them with this:
Running the miner with the following arguments:
./minerd -q -a sha256d -R 5 -o http://localhost:8332/ -O mylogin:mypass --coinbase-addr="<34-char address>"
Uploaded the packet capture with the HTTP exchange, if it helps: traffic.pcap.gz.
Any help is greatly appreciated, thank you in advance!
EDIT: retrieved data for the previous block to the one being mined, in case it helps.
EDIT 2: I may be wrong, but it looks like the nonce field is 8 bytes instead of 4 in this altcoin, causing the whole block structure to shift compared to the original Bitcoin. Wonder if the miner can be adapted to a different nonce field size?