ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-05-31 14:40:52 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Move fungible definition up the document

Browse Source
This commit is contained in:
Ross Nicoll 2016-06-10 11:25:41 +01:00
parent fc3bc163aa
commit 874892df93
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/source/transaction-data-types.rst
View File

@ -11,8 +11,9 @@ a type used to define the underlying asset, for example a ``TokenDefinition``, o
such as an obligation contract issuance definition (which in turn contains a token definition for whatever the obligation such as an obligation contract issuance definition (which in turn contains a token definition for whatever the obligation
is to be settled in). is to be settled in).
.. note:: Fungible means that instances of an asset is interchangeable for any other identical instance, for example a .. note:: Fungible is used here to mean that instances of an asset is interchangeable for any other identical instance,
£5 note can reasonably be exchanged for any other £5 note. and that they can be split/merged. For example a £5 note can reasonably be exchanged for any other £5 note, and a
£10 note can be exchanged for two £5 notes, or vice-versa.
Contract State Contract State
-------------- --------------
@ -35,7 +36,7 @@ Things (such as attachments) which are identified by their hash should implement
which standardises how the ID is extracted. which standardises how the ID is extracted.
FungibleAssets and Cash FungibleAssets and Cash
~~~~~~~~~~~~~~~~~~~~~~~ -----------------------
There is a common ``FungibleAsset`` superclass for contracts which model fungible assets, with ``Cash`` being the obvious There is a common ``FungibleAsset`` superclass for contracts which model fungible assets, with ``Cash`` being the obvious
example. This is intended to be readily extensible to cover other assets, for example commodities could be modelled by example. This is intended to be readily extensible to cover other assets, for example commodities could be modelled by
@ -51,7 +52,7 @@ signatures or attachments is represented using the ``WireTransaction`` class, wh
with valid signatures are encapsulated in the ``AuthenticatedObject`` type. with valid signatures are encapsulated in the ``AuthenticatedObject`` type.
Party and PublicKey Party and PublicKey
~~~~~~~~~~~~~~~~~~~ -------------------
Identities of parties involved in signing a transaction can be represented simply by their ``PublicKey``, or by further Identities of parties involved in signing a transaction can be represented simply by their ``PublicKey``, or by further
information (such as name) using the ``Party`` class. An ``AuthenticatedObject`` contains a list of the public keys information (such as name) using the ``Party`` class. An ``AuthenticatedObject`` contains a list of the public keys