Abstract: A technical solution for providing data associated with a predetermined, finite lifetime for access via a distributed ledger is provided. A member computing entity receives a submission provided by a supplying member computing entity associated with a supplying member of a distributed ledger; generates a token and attributing the token to a member account corresponding to the supplying member; attributes a value to the token; and makes the submitted instance of data available for access via the distributed ledger. The submission comprises a submitted instance of data. The submitted instance of data (a) is configured to be provided to a consuming member computing entity via the distributed ledger and (b) is associated with a predetermined lifetime. The value of the token changes with time based on (a) a remaining lifetime of the submitted instance of data, (b) a depreciation policy/protocol corresponding to the distributed ledger, or (c) both.

Abstract: Domain and/or event type-specific consensus processes for distributed ledger are provided. A consensus request is received by a core consensus engine. The consensus request corresponds to an event, the event (i) corresponds to a domain and (ii) has a type, and the consensus request comprises information corresponding to the event. Information corresponding to the event and the type are provided to the processing manager corresponding to the domain. The processing manager identifies a set of processing objects based on the type. The processing manager calls at least one processing object of the set via a corresponding interface and provides information corresponding to the event to the called processing object. The processing object is executed to generate a corresponding object result. The processing manager generates an aggregate result based on the object results. The core consensus engine determines a consensus response based at least in part on the aggregate result.

Abstract: A technical solution for providing data associated with a predetermined, finite lifetime for access via a distributed ledger is provided. A member computing entity receives a submission provided by a supplying member computing entity associated with a supplying member of a distributed ledger; generates a token and attributing the token to a member account corresponding to the supplying member; attributes a value to the token; and makes the submitted instance of data available for access via the distributed ledger. The submission comprises a submitted instance of data. The submitted instance of data (a) is configured to be provided to a consuming member computing entity via the distributed ledger and (b) is associated with a predetermined lifetime. The value of the token changes with time based on (a) a remaining lifetime of the submitted instance of data, (b) a depreciation policy/protocol corresponding to the distributed ledger, or (c) both.

Abstract: Domain and/or event type-specific consensus processes for distributed ledger are provided. A consensus request is received by a core consensus engine. The consensus request corresponds to an event, the event (i) corresponds to a domain and (ii) has a type, and the consensus request comprises information corresponding to the event. Information corresponding to the event and the type are provided to the processing manager corresponding to the domain. The processing manager identifies a set of processing objects based on the type. The processing manager calls at least one processing object of the set via a corresponding interface and provides information corresponding to the event to the called processing object. The processing object is executed to generate a corresponding object result. The processing manager generates an aggregate result based on the object results. The core consensus engine determines a consensus response based at least in part on the aggregate result.