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

Update tutorial-building-transactions.rst

Browse Source 
Addressed @tudor-malene's comment
This commit is contained in:
Roger Willis 2019-02-20 17:05:36 +00:00 committed by Mike Hearn
parent dce411cfdf
commit 5a4db990e7
1 changed files with 2 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
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
ledger
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
transaction, it has effectively stated that it accepts all the details of the transaction.
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 transaction, it has effectively stated that it accepts all the details of the transaction.
It is best practice for flows to receive back the ``TransactionSignature`` of other parties rather than a full
``SignedTransaction`` objects, because otherwise we have to separately check that this is still the same
@ -295,4 +291,4 @@ overall transaction id is still provable from the
not expose that data to the other node directly. A full example of this
can be found in the ``NodeInterestRates`` Oracle code from the
``irs-demo`` project which interacts with the ``RatesFixFlow`` flow.
Also, refer to the :doc:`tutorial-tear-offs`.
Also, refer to the :doc:`tutorial-tear-offs`.