LCX Liechtenstein Protocol: A new standard for security tokens
a LCX Team · · Updated February 6, 2023
The year 2021 is going to be a year of security tokens. Security tokens are basically a tokenized and digital version of traditional securities. The European Securities and Markets Authority (ESMA) defines security tokens as “crypto-assets are a type of private asset that depends primarily on cryptography and DLT”. They categorise security tokens as crypto assets.
LCX’s Liechtenstein Protocol will set a precedent for a new standard for security tokens. The Liechtenstein Protocol stems from the Token and Trusted Technology Service Provider Act (Officially: Token- und VT-Dienstleister-Gesetz; TVTG) also known as the Blockchain Act introduced by Liechtenstein. It is a new regulatory framework that aims at providing a technologically neutral token definition that will form the foundation for a tokenized economy. These new laws have blurred the defining line of the digital and physical world while simultaneously providing a definition of key roles along the value chain of tokenization.
With the technical paper, LCX asserts the need for a new security token standard that will automatically implement compliance and regulatory requirements by implementing them directly on the technology and the token. The paper provides a solution to this by introducing a new token standard presented as an industry-led initiative which derives its core functionality from other standards such as ERC1400, ERC1404, R-Token , or T-REX.
The blockchain agnostic token standard will be implemented on different public chains. It envisions creating a compliant framework for the tokenization of securities in conjunction with enabling the growth and proliferation of asset tokenization as a practice.
The Liechtenstein Protocol standard, and its first iteration, is programmed in a manner that it automatically enforces certain conditions that are necessary from the compliance point of view, on the tokens built on it. This implies that it automates compliance of tokenized assets by necessitating them to adhere to the predefined requirements that are built in the code.
