ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-06-01 07:00:54 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Removed part about exchanging transaction builder between parties. You can't do this as TransactionBuilder is not serializable.

Browse Source
This commit is contained in:
RogerWillis 2019-02-20 15:39:44 +00:00 committed by Mike Hearn
parent 8306b3f708
commit dce411cfdf
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/source/tutorial-building-transactions.rst
View File

@ -48,11 +48,7 @@ Transactions in Corda contain a number of elements:
period during which the proposed transaction can be committed to the period during which the proposed transaction can be committed to the
ledger ledger
A transaction is built by populating a ``TransactionBuilder``. Typically, A transaction is built by populating a ``TransactionBuilder``.
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.
Once the builder is fully populated, the flow should freeze the ``TransactionBuilder`` by signing it to create a 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 ``SignedTransaction``. This is key to the ledger agreement process - once a flow has attached a node’s signature to a