tony777

I hadn't realized that it was the Bitcoin scripting opcodes that explicitly required an invalid signature. Thank you so much for your response

txid: b3e977a2c48145255d84e1c82d4ea07522528991d50ead1cf3a783559d9733e3 So, check it out, the r and s values for the signature are r = 0x52 and s = 0x53. There's no way those could’ve come from a k, which basically means…

What about your envelope, "Master"? :p