See ‘object-id’ in object-type: holding.


See ‘owner-id’ in object-type: holding.
See ‘asset-type’ in object-type: holding.
See ‘asset-id’ in object-type: holding.
See ‘amount’ in object-type: holding.

JSON Examples

Example 1:

    "UpdateType": "CreateHolding",
    "ObjectId": "OBJECT_ID",
    "OwnerId": "OBJECT_ID",
    "AssetType": "Currency",
    "AssetID": "USD",
    "Amount" : 1000000

Example 2:

    "UpdateType": "CreateHolding",
    "ObjectId": "OBJECT_ID",
    "OwnerId": "OBJECT_ID",
    "AssetType": "Bond",
    "AssetID": "OBJECT_ID",
    "Amount" : 100


The following checks are performed:

  • Check that all required attributes have been provided.
  • Check that all provided unique attributes do not exist in the store.
  • Check that OwnerID references a valid organization.
  • Check that AssetType is either “Currency” or “Bond”.
  • If AssetType is “Currency”, check that AssetID is “USD”.
  • If AssetType is “Bond”, check that AssetID references a valid bond.
  • Check that the referenced OwnerID does not already contain a Holding with an identical AssetType, AssetID combination. For example, if the organization already has a Currency holding in USD or a Bond holding for a given Bond object, then the new CreateHolding transaction should be considered invalid.

Anyone is allowed to create holdings, so no checks are done for authorization.

For the purposes of the proof of concept, the check_valid() method should additionally enforce that currency amounts should equal $1B USD and Bond quantities should equal 1000 units on creation.


Create a new object in the store with object-type of ‘holding’.

When a holding is created, increment the owner’s ref count and the asset’s ref count (if the AssetType is “Bond”). Add the holding’s object-id to the owner’s holdings list.