Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Priority

SHOULD

Type of change request

FEATURE

Epic linkhttps://jira.hyperledger.org/browse/IR-578
Status

DRAFT

Target release



Vision

This feature attempts to democratise the asset type creation aspects of the Iroha distributed ledger to enable every user to create any arbitrary tokens of their own choosing. Initially, this was motivated by the idea of recording personal IOUs on the ledger and making such informal ‘debts’ tradable in the system. However, considerations of how to do the implementation led to a more generallzed set of enhancements that can accomplish the same end.

This proposal extends the existing behaviour of Iroha in two ways:

  1. Adding personal domains.
  2. Creating a new class of asset types called derivative assets.

Functional details

Personal domains

Personal domains extend the domain concept to add a domain that is associated with every user account. The user is then given all of the domain and asset administrator permissions normally associated with the domain (except perhaps for adding other users into their personal domain). Ideally, it would be possible for users to create additional personal domains to seperate assets, but at this stage I cannot think of any motivating use cases for this. All personal domain assets are tradable just like normal domain assets.

Derivative Assets

Derivative assets are a type of asset that has a relationship with another pre-existing asset in the ledger. For example, an IOU dollar would be a token that derives from the underlying asset type of dollar, but maintains its separate identity as an IOU. Derivative assets need not be created in the same domain as the underlying linked asset. Most types of derivative assets will need additional properties attached to them.  To continue with the IOU dollar example, it would need fields for specifying an owed by relationship to the user responsible for repayment. 

In a more serious application, a bank might record actual loan information as a debt asset with other metadata such as the loan repayment terms or an options asset might record the maturity date and the strike price.

To obtain maximum flexibility, derivative assets may require an additional change to the asset metadata model to allow any arbitrary additional fields to be added to it at creation time, with restrictions allowed on how/when these metadata fields are updated (if ever).

Environmental objectives

None

Changelog 

#Change descriptionAffected componentChange motivationDependency (optional)
1What is changedWhere it is changed

Why it is done


After #1

Before #1

etc.

Research strategy

#Research activityDetailsAcceptance criteriaResponsible (accepter) 
1



Documentation effort

#Target readerDocumentation description
1

QA activity


#Validation activityIntentionActionsExpected result 
1TestingTest component X and check if …

Given X,

When Y

AND

When Y1

Then Z

OR

Then Z1

Tasks

IR-578 - Getting issue details... STATUS



Template data

Priorities MUST SHOULD COULD WON'T

Change request type FEATURE BUG FIX

Status BACKLOG WORK IN PROGRESS DONE


  • No labels