1/ Let's get to the core of the report today; namely the conceptual framework that breaks down a #DLT system into distinct pieces in order to better understand the relationships between its elements.
2/ Speaking of elements: the framework consists of three types: layers, components, and processes.
Each layer is composed of a set of components, and each component comprises a set of processes.
In total, we identify 3 layers, 7 components, and 18 processes.
3/ Let's start with the base layer - the protocol layer.
The protocol layer is the foundation of the entire DLT system: it defines the set of formal rules that governs the system and codifies its architectural design.
1/ Today, I'd like to share some of the highlights in Section 2 of our new report on #DLT systems (available here: papers.ssrn.com/sol3/papers.cf…).
We will provide a formal definition of a DLT system and explain some of the key concepts.
2/ Before diving into the key concepts, it is important to understand that unlike 'traditional' databases, DLT systems are designed to operate in an adversarial environment.
3/ That doesn't necessarily mean that there are adversaries actively trying to attack or sabotage the system; rather, a DLT system should be designed to tolerate the potential presence of malicious actors - to a certain extent.