a state can not only name a class that implements the Contract interface but also place constraints on the zip/jar file that provides it. That constraint can in turn be used to ensure that the contract checks the authenticity of the data – either by checking the hash of the data directly, or by requiring the data to be signed by some trusted third party
If you want to change selection, open document below and click on "Move attachment"
- (no access) - corda-technical-whitepaper.pdf, p19
|status||not read|| ||reprioritisations|
|last reprioritisation on|| ||suggested re-reading day|
|started reading on|| ||finished reading on|