From 46a305602b415be22665e6f2e7670ab60441df0b Mon Sep 17 00:00:00 2001 From: Mike Hearn Date: Thu, 27 Jun 2019 16:25:46 +0200 Subject: [PATCH] Attempt to make a sentence about constraints easier to understand. --- docs/source/whitepaper/corda-technical-whitepaper.tex | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/source/whitepaper/corda-technical-whitepaper.tex b/docs/source/whitepaper/corda-technical-whitepaper.tex index 6410f13aa6..10bfc151b8 100644 --- a/docs/source/whitepaper/corda-technical-whitepaper.tex +++ b/docs/source/whitepaper/corda-technical-whitepaper.tex @@ -655,7 +655,9 @@ attachments along with size limits, to avoid people placing inappropriate files PowerPoints etc). Note that the creator of a transaction gets to choose which files are attached. Therefore, it is typical that -states place constraints on the data they're willing to accept. These mechanisms are discussed +states place constraints on the application JARs they're willing to accept. This enables the software that imposes +logic on the ledger to evolve independently of the stored data, whilst still remaining secure against malicious +evolutions that would, for example, allow an adversary to print money. These mechanisms are discussed in~\cref{sec:contract-constraints}. \paragraph{Signing.}Attachments may be signed using the JAR signing standard. No particular certificate is