LankyDan 9bf26c20e0 CORDA-2920 Hash to Signature Constraint automatic propagation ... Allow Hash Constraints to propagate to Signature Constraints. When propagating, the new jar is added to the transaction instead of the original contract attachment (jar). The following requirements must be met to do so: - System property "net.corda.node.disableHashConstraints" must be set to `true` - The min platform version must be 4 or greater - There must be an input state with a hash constraint - There must be no output states with a hash constraint - The new jar must be signed If these requirements are not met, the original Hash Constraint will be kept and the contract attachment related to it is also used. This transition is done at the start of `handleContract` as it is not the normal path a transition would follow. It is considered a backdoor and should be treated separately from the rest of the attachment and constraint logic. Furthermore, it will only work in private network since all nodes must set the special `disableHashConstraints` flag.		2019-07-29 12:58:58 +02:00
..
src	CORDA-2920 Hash to Signature Constraint automatic propagation	2019-07-29 12:58:58 +02:00
build.gradle	ETO-39 Move core tests (#5255)	2019-07-09 10:09:21 +01:00