Share Registry

Introduction

Along with tokenization, micobo Tokenization Engine(MET) also has a share register that keeps track of all the tokens minted, transferred, and burned. Once we have clarified all the key terms around the share register, it will become clear how it works and how to interpret the responses.

Tranches

A tranche represents an entry in the share registry which contains information pertaining to a certain set of token(s). A tranche contains the following information:

[1] Tranche Start & End

"Tranche start" and "Tranche end" represent the token number where this tranche starts and ends respectively. For e.g. - when a certain number of tokens (say n) are issued for a newly deployed token, the tranche end and start will be 1 and n respectively.

[2] Tranche Owners

"Previous owner" and "Owner" are exactly what they say, the previous owner of the tranche and the current owner. In case of minting, there is no previous owner and in case of burning, there is no current owner. For transfers, the previous owner and owner field correspond to the sender and recipient of a token transfer.

[3] Origin

It specifies what caused the tranche to be created. It can take the following values: issued, bought and burned. These value represents token mint, transfer and burn respectively.

[4] State

Origin alone is not sufficient to fully understand the nature of an entry in the share register, to complement origin we have another parameter called state. State represents the state of the tranche, a tranche can be in the following states:

  • current
  • outdated
  • withdrawn
  • remained

current means that the tranche is active implying all the tokens belong to the said current owner, outdated means that the tranche is no longer active, withdrawn means that all the tokens in this tranche were burned and lastly, remained refers to the condition where a part of this tranche still resides with the owner but remaining was reallocated to someone else.

Also, it is imperative that a share register be read from top to bottom, reading a single entry may convey information that does not make sense. It a complete history of operation on the token that must be read fully to understand the course of operations that were done of the said security token.

Was this page helpful?