Date: Thu, 28 Mar 2024 11:30:33 +0000 (UTC) Message-ID: <1825268099.31.1711625433391@9015160b7955> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30_516526272.1711625433391" ------=_Part_30_516526272.1711625433391 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The definition of the Ledger Layer is NOT part of the specificat= ions of FinP2P - each node and technology vendor may implement it in any wa= y they see fit, as long as the correct behavior of the FinP2P Network Proto= col is maintained. This Ledger Layer chapter of this specification is a ref= erence implementation design only.
The FinP2P Core component is stateless and does not save any securities = or private information. All securities and private information is stored at= the ledger layer, it is separated into two main parts:
Private information relating to users and assets is kept off-chain, and = is only shared with other nodes in the FinP2P that are authorized to see th= at information. This information need to comply with various legal and regu= latory requirements such as GDPR, and therefore will not be stored on a DLT= platform. While the information itself is not held on chain, we still requ= ire the Hash of the data to be kept on the DLT to provide immutability and = a method for validating private information provided to other nodes via the= FinP2P Network Protocol.
Transaction information for all assets have to be stored on the DLT netw= ork chosen by the node, where all information about asset ownership is main= tained across a blockchain of multiple financial institutions.