0
I'm writing a stand alone process that needs to verify that a known UTXO is part of a new transaction with a valid signature.
Inputs [ UTXO, raw transaction, input_number ]
How do to I verify the signature for this specific input?
As I understand, depending on the SIGHASH, I would need to parse the entire transaction and replace/remove some data. However, the length bytes seem to make the entire process extremely complex.
Does a segwit transaction make everything easier? Or are there still bytes that need to be removed depending on SIGHASH?
On a side note. in general, will APIs that return "raw transactions" no longer have the signature data for segwit transactions? or are they all appended to the end?
Yes, I agree this base case is simple. And I too only use non-segwit sighash_all transactions coded in QT! however, my issue is trying to prove that a known UTXO was already "spent". I want to do this offline, without any access the Bitcoin network. A signed byte string that contains my UTXO in the digest is considered "spent". This is the final piece of my custom atomic swap code in a new blockchain. – jaybny – 2019-03-06T15:58:00.910