Abstract: Systems and methods for efficiently storing a distributed ledger of records. In an exemplary aspect, a method may include generating a record comprising a payload and a header, wherein the payload stores a state of a data object associated with a distributed ledger and the header stores a reference to state information in the payload. The method may further comprise including the record in a trunk filament comprising a first plurality of records indicative of historic states of the data object, wherein the trunk filament is part of a first lifeline. The method may include identifying a jet of the distributed ledger, wherein the jet is a logical structure storing a second lifeline with a second plurality of records. In response to determining that the first plurality of records is related to the second plurality of records, the method may include storing the first lifeline in the jet.

Abstract: Disclosed herein are systems and methods for governing domain-based smart contract execution in a DLT network. In one exemplary aspect, a method may comprise receiving a request to register a first domain in a cloud that comprises nodes of the DLT network and generating the first domain responsive to the request, wherein the first domain comprises a set of smart contracts and policies, e.g. specifically for personal data management, for a first subset of the nodes and wherein a pre-existing second domain in the cloud comprises a different set of smart contracts and policies for a second subset of the nodes. In response to determining to execute the smart contract from the first domain, the method comprises executing a domain policy associated with the first domain, wherein the domain policy determines data privacy settings for the smart contract. The method may comprise executing the smart contract and storing computation results.

Abstract: Systems and methods for efficiently storing a distributed ledger of records. In an exemplary aspect, a method may include generating a record comprising a payload and a header, wherein the payload stores a state of a data object associated with a distributed ledger and the header stores a reference to state information in the payload. The method may further comprise including the record in a trunk filament comprising a first plurality of records indicative of historic states of the data object, wherein the trunk filament is part of a first lifeline. The method may include identifying a jet of the distributed ledger, wherein the jet is a logical structure storing a second lifeline with a second plurality of records. In response to determining that the first plurality of records is related to the second plurality of records, the method may include storing the first lifeline in the jet.

Abstract: Disclosed herein are systems and method for extendable cryptography in a distributed ledger. In an exemplary aspect, a method receives a request to process an object by generating a new record data of the object and adding, to a distributed ledger, a new record comprising the new record data associated with the object. The method obtains hash information for a preceding record in the distributed ledger. The method generates a new platform hash and a new custom hash for the new record, and creates a main portion of the new record, the main portion comprising the new record data, the platform hash of the previous record, and the new platform hash. The method generates and appends an extendable portion to the new record, the extendable portion comprising the custom hash of the previous record and the new custom hash. The method then adds the new record to the distributed ledger.

Abstract: Systems and methods for storing records and data in a distributed ledger or blockchain are provided. In an extended form of a ledger or blockchain, referred to as an assured ledger, one or more records may have a reference to a previous record and a reference to a reason record that represents an operation that caused creation of the record itself. The assured ledger technology tracks causation as a chain of reasons why the ledger was updated and a change was made to a certain object that is represented on the distributed ledger, such as a smart contract.