Simple constraints such as “any contract of this name signed by these keys” allow for some upgrade flexibility, at the cost of increased exposure to rogue contract developers. Requiring combinations of signatures helps reduce the risk of a rogue or hacked developer publishing a bad contract version, at the cost of increased difficulty in releasing new versions.
If you want to change selection, open document below and click on "Move attachment"
pdf
owner:
ionutt93 - (no access) - corda-technical-whitepaper.pdf, p24
Summary
status | not read | | reprioritisations | |
---|
last reprioritisation on | | | suggested re-reading day | |
---|
started reading on | | | finished reading on | |
---|
Details