4.3

Role

Last update, October 28

The CAST Framework technical component is based on four pillars:

  • The instrument registry. The instrument registry is a Smart Contract that records all instruments created by the Registrar on a standardized basis.
  • A set of Security Token pre-requisites. The CAST Framework provides functional pre-requisites based on high level operational standards defining operational sequencing.
  • A Settlement Transaction Repository (STR) consists in a technological feature, managed by the Registrar, designed to store key information related to Security Token transactions, notably the identity of Security Token holders or their agents for any specific date and the history of all Security Token holders or their agents since issuance. The STR is a crucial part of the Business Continuity Plan which protects the integrity of the data registered on the DLT from potential technological disruption.
  • Oracles. DLT integration with existing systems is made possible by the Oracles. Based on the CAST Framework, the Oracles feed Security Tokens' Smart Contracts with the required data and allow optimal integration of post-market operational chains with DLT infrastructures. The Oracles based on the CAST Framework are shared on an open-source basis, which reduces the cost of such integration.
CAST Code
Standards
Framework Path Description
bdt
Role
[BDT.attribute.optional]Issuance/Issuance/Role/Role
The Role element describes the activities and services performed by the platform as described in the offering documents. The role type allows for a free text description of one or more roles but also allows the use of a link to a specific role as defined in the partyRole group. Typical roles performed by a DLT platform include registrar, account keeper, custodian and settlement agent.