From dce411cfdf32ec572a59e0fd9afba1f5b1c503b5 Mon Sep 17 00:00:00 2001 From: RogerWillis Date: Wed, 20 Feb 2019 15:39:44 +0000 Subject: [PATCH] Removed part about exchanging transaction builder between parties. You can't do this as TransactionBuilder is not serializable. --- docs/source/tutorial-building-transactions.rst | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/source/tutorial-building-transactions.rst b/docs/source/tutorial-building-transactions.rst index 32be2f37587..61bc5beb902 100644 --- a/docs/source/tutorial-building-transactions.rst +++ b/docs/source/tutorial-building-transactions.rst @@ -48,11 +48,7 @@ Transactions in Corda contain a number of elements: period during which the proposed transaction can be committed to the ledger -A transaction is built by populating a ``TransactionBuilder``. Typically, -the ``TransactionBuilder`` will need to be exchanged back and forth between -parties before it is fully populated. This is an immediate consequence of -the Corda privacy model, in which the input states are likely to be unknown -to the other node. +A transaction is built by populating a ``TransactionBuilder``. Once the builder is fully populated, the flow should freeze the ``TransactionBuilder`` by signing it to create a ``SignedTransaction``. This is key to the ledger agreement process - once a flow has attached a node’s signature to a