This page depicts the domain model of the NUTS platform. It presents all key data elements as well as the interactions demonstrated in the interaction diagrams in the following pages.
A generic key-value store. Both key and value are strings.
A standard ERC20 token(not shown the in the graph above).
An extension of the standard escrow which implements withdrawal pattern and supports hosting of both Ether and any ERC20 tokens. The Token Escrow exposes two sets of API, one for Ether and one for other tokens.
The deposit()/depositToken()/withdraw()/withdrawToken() functions are used by sellers and buyers to send Ether/token to/from the escrow, while transfer()/transferToken() are used by NUTS platform to manipulate the token in the escrow; in most case, sending Ether/token to/from issuance.
A registry that holds information about FSPs and financial instruments. Before creating new issuance of any financial instrument, NUTS platform will validate the status of the financial instrument using the validate() function.
A template to create new issuances. The financial instrument is singleton and stateless in nature as issuance id and state passed in in all function calls.
In order to achieve flexibility and extensibility, the financial instrument is event-driven and processEvent() is the main entry to interact with this component. It provides the following hooks for FSP to implement custom logic in handling specific events:
The central portal for all NUTS operations.