mirror of
https://github.com/corda/corda.git
synced 2025-02-07 03:29:19 +00:00
Clear up wording around how the FungibleAsset superclass is used
Clear up wording around how the FungibleAsset superclass is used, and in particular that it contains contract code, but provides an interface that should be extended by subclass state objects.
This commit is contained in:
parent
8d1ac66787
commit
4b39ab0357
@ -38,9 +38,10 @@ 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, which also provides a standard
|
||||||
example. This is intended to be readily extensible to cover other assets, for example commodities could be modelled by
|
interface for its subclasses' state objects to implement. The clear use-case is ``Cash``, however ``FungibleAsset`` is
|
||||||
using a state object that included further details such as location of the commodity.
|
intended to be readily extensible to cover other assets, for example commodities could be modelled by using a subclass
|
||||||
|
whose state objects include further details (location of the commodity, origin, grade, etc.) as needed.
|
||||||
|
|
||||||
Transaction Types
|
Transaction Types
|
||||||
-----------------
|
-----------------
|
||||||
|
Loading…
x
Reference in New Issue
Block a user