I've setup node-open-mining-portal for development purposes. I start mining, but coin daemon keep rejecting newly mined blocks. After some edits I managed to get raw block before submitting and here is how its looks:

00000020a5f3f24c9ea0fd233f5f6f3263bc2dd8ae2af747ea5c68bf7e53aa4c06000000126c8e37e2290df88154e50e21daff960ee1ad89672d989c4ac71c87baefa3ceb4fd4b5bffff0f1da02048fa0101000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4c03cc020804b4fd4b5b08fabe6d6d00000000ffffffff000000010000000100000000000000000000000001f15c28010000000000000010000000000000000d2f6e6f64655374726174756d2f00000000050000000000000000266a24aa21a9ede2f61c3f71d1defd3fa999dfa36953755c690689799962b48bebd836974e8cf944776007000000001976a914935c5d62b5b34757d4b2d134e3376ee9020b28db88ac544b0600000000001976a9147fd7e409fc303e407a933b3392aa197c66348da688ac544b0600000000001976a914d293b99e28340330e2bf148da97244a6ce442be588ac544b0600000000001976a914dd36ae345ae796cfc7405c9ed42a58f7bc50defb88ac00000000

When I tried submit it to daemon bad-txnmrklroot error appear:

bad-txnmrklroot error

After some digging in internet I find this nice forum post which in details describe structure of Bitcoin/Dash transaction (I assume they pretty much the same). So, after that I tried check my block on my own and here what I get (sorry if I made some stupid mistakes here c: )

// Specific block data (error may be here)
00000020a5f3f24c9ea0fd233f5f6f3263bc2dd8ae2af747ea5c68bf7e53aa4c060000004e4ba3da3c966972850a053159de2279bec07559a04ba980db576ad94220d72c5dc1485bffff0f1d4027326301

// Version
01000000

// Count of inputs (newly created coins)
01

// Prevout
0000000000000000000000000000000000000000000000000000000000000000

ffffffff

// scriptSig
2003cc0208045dc1485b0828000000000000000d2f6e6f64655374726174756d

// ??
2f

// nSequence
00000000

// Count of outputs
05

// Value ???
0000000000000000

// ?????
266a24

aa21a9ede2f61c3f71d1defd3fa999dfa36953755c690689799962b48bebd836974e8cf944776007

00000000

// Transactions 
1976a914935c5d62b5b34757d4b2d134e3376ee9020b28db88ac544b0600000000001976a9147fd7e409fc303e407a933b3392aa197c66348da688ac544b0600000000001976a914d293b99e28340330e2bf148da97244a6ce442be588ac544b0600000000001976a914dd36ae345ae796cfc7405c9ed42a58f7bc50defb88ac00000000

After that I decided to verify transaction using slightly modified version of coinbin (you can check it here if you want) and thats what I get:

strange output

I assume, that this strange output somehow related to this question, but I'm not managed to find any more info about that :(

I'm struggling around with this issue for almost week now, so any help would be appreciated.

P.s. I use slightly modified version of Bitcoin 0.15 whit changed header hashing algo (groestl) and changed adrress prefixes. P.s.s This peoples 1 2 3 also experienced this issue, so I'm not the only one :D

up vote -1 down vote accepted

Issue was in wrong hash function, nevermind :)

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.