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

DOCS - use signInitialTransaction instead of toSignedTransaction in tutorial docs (#5280)

Browse Source
This commit is contained in:
Joseph Tharakan
2019-07-08 19:24:43 +05:30
committed by Shams Asari
parent 933330bc4c
commit 8a6fc2964c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/source/tutorial-contract.rst
View File

@ -513,7 +513,7 @@ from the ledger). Finally, we add a Redeem command that should be signed by the
A ``TransactionBuilder`` is not by itself ready to be used anywhere, so first, we must convert it to something that A ``TransactionBuilder`` is not by itself ready to be used anywhere, so first, we must convert it to something that
is recognised by the network. The most important next step is for the participating entities to sign it. Typically, is recognised by the network. The most important next step is for the participating entities to sign it. Typically,
an initiating flow will create an initial partially signed ``SignedTransaction`` by calling the ``serviceHub.toSignedTransaction`` method. an initiating flow will create an initial partially signed ``SignedTransaction`` by calling the ``ServiceHub.signInitialTransaction`` method.
Then the frozen ``SignedTransaction`` can be passed to other nodes by the flow, these can sign using ``serviceHub.createSignature`` and distribute. Then the frozen ``SignedTransaction`` can be passed to other nodes by the flow, these can sign using ``serviceHub.createSignature`` and distribute.
The ``CollectSignaturesFlow`` provides a generic implementation of this process that can be used as a ``subFlow`` . The ``CollectSignaturesFlow`` provides a generic implementation of this process that can be used as a ``subFlow`` .