Releases: AIBlockOfficial/Chain
v1.1.3
v1.1.2
Changelog
tx_is_validandtx_outs_are_validhave changed from aboolreturn type to a(bool, String)return type, where theStringcontains reasoning or additional information about the nature of the validation.
Some Notes: In most cases, a correct validation will return no additional information at the chain level. For incorrect validations, the reasoning should in most cases provide more comprehensive context but may need to be updated when newer error types become possible
v1.1.1
Changelog
- Removes the correct validation of signature messages under old structures
TODO: Old transactions will have signature information that contains old structures, and old spends on-chain will no longer validate correctly. This should be noted in future, as external validations will need to be correctly proved.
v1.1.0 (tw_chain)
Changelog
- Removes the old P2PKH transaction validation structure. Note that this is a non-backwards compatible change, motivating a minor version bump
v1.0.6
v1.0.5
v1.0.4
Changelog
- Adds validation for input signature for payments to a combination of the previous output's transaction hash and all available outputs' addresses.
Validation Change
It's now possible to use the following structure for data to be signed for P2PKH transactions:
let signable_data = ""df8f140e031c380a379d6eff80f767f58c13f314bfd7a34875fca7368bde0d52""56181905ff39daad6d02b87e5c6a1630b54a3374b74f2ec7cf836a1487d34bde"000000"Where the first 2 values, in quotes, are the addresses of the outputs, and the last value (000000) is the transaction hash of the particular input's previous outpoint