RE: bitcoin spinoff fork - how to make a clean fork without any replay attack and no blockchain visible changes

You are viewing a single comment's thread from:

bitcoin spinoff fork - how to make a clean fork without any replay attack and no blockchain visible changes

in bitcoin •  8 years ago 

the signature is generated, 70 to 72 bytes (maybe I am off by 1 here), and the sighash byte is just added to the end. It is in the protocol spec, so that is what I did and it works. not familiar with bitcoind code as I wrote iguanacore from scratch

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Maybe it's this line right here, casting nHashType as an unsigned char (1 byte):
https://github.com/bitcoin/bitcoin/blob/d612837814020ae832499d18e6ee5eb919a87907/src/script/sign.cpp#L32