Assets APIs

Get familiar with Tokeny's T-REX Engine Assets API - your Tokenisation Engine entrypoint

Overview

The Assets API lets you tokenise your assets and configure the ERC3643 representing them onchain. This guide will explain to you:

  • How to deploy the ERC3643
  • How to interact with it to define the trade rules
  • How to perform agent actions on the token
  • How to manage the data (offchain and onchain) linked to both the ERC3643 and the underlying asset

The trade rules of the ERC3643 include:

  • Token details: logo, instrument type and currency
  • Token ownership: define which wallet owns the ERC3643
  • Identity eligibility: define the eligibility rules that the investor ONCHAINIDs must follow to be authorised to receive the ERC3643
  • Compliance rules: define the authorised countries of residence, supply rules, transfer types or define your own compliance rules

You can define, for each ERC3643 you control, the following type of transfers:

  • Simple transfer: allow an authorised investor to send tokens to another authorised investor.
  • Conditional transfer: approval(s) is(are) required for the transfer to be executed.
  • Transfer whitelisting: only a subset of whitelisted addresses are allowed to perform transfers.

Note: Transfer whitelisting and Conditional transfer are mutually exclusive. You can only activate one or the other on the same ERC3643.

On those type of transfers, you can also define:

  • Transfer limits over a given period of time
  • Transfer fees to be taken on each transfer

Once your asset is deployed, you can then interact with it with an agent account to manage your investors, cap table and data.

As for identities, the data can be both offchain and onchain. This data can be accessed either through the Assets API or through the Catalog API.