Abstract: User access to a set of data stored in a distributed ledger, wherein the distributed ledger is stored by a plurality of node computing entities, is provided. A first node computing entity receives a share key request indicating that a first user account has authorized a second user account to have access to a set of data stored in the distributed ledger. A data access key (DAK) for accessing the set of data is encrypted using an encrypting key of the second user account. A block comprising the encrypted DAK is generated, signed using a signing key of the first user account, and posted to the distributed ledger. The block is authenticated using an authentication key of the first user account and accessed via a decrypting key of the second user account such that the second user account may use the DAK to access the set of data.

Abstract: A distributed ledger is stored by a plurality of node computing entities. A node computing entity of the plurality of node computing entities comprises at least one processor, a memory, and a communications interface configured to communicate via at least one network. The node computing entity creates a finite state machine record set. A finite state machine record of the finite state machine record set comprises (a) event data for a corresponding event and (b) a domain object state for a domain object corresponding to the corresponding event. The domain object state indicating the state of the domain object as a result of the corresponding event. The node computing entity generates a block comprising the finite state machine record set and posts the block to the distributed ledger.

Abstract: A snapshot of a distributed ledger is generated, wherein the distributed ledger is stored by a plurality of node computing entities. A first node computing entity reads current states of one or more domain objects from a local cache stored by the node computing entity and corresponding to an application operating on the node computing entity. A snapshot record comprising the current states of the one or more domain objects is generated and written to a segment data file. The snapshot record is posted to the distributed ledger as part of a block.

Abstract: Example embodiments provide for secure storage and accessing of confidential information by a distributed system and for securely executing a function of the distributed system. Responsive to processing a function request identifying a function of the distributed system by a node computing entity, application program code corresponding to the function is accessed within a trusted execution environment. Based on data stored in a secure ledger maintained by the distributed system, the application program code is executed to generate a result within the trusted execution environment. A new entry comprising the result is generated and at least a portion thereof is encrypted using an encryption key within the trusted execution environment. The encrypted new entry is posted to the secure ledger.

Abstract: An immediate failover from a primary order book to a secondary order book is provided. The primary order book represents a current state of one or more orders according to a first node computing entity and the secondary order book represents a current state of all orders according to a second node computing entity. An input stream of order information is processed by the first node computing entity to generate (a) a primary order book and (b) an output stream of order information. A secondary stream of order information is provided to a second node computing entity. The second stream of order information is processed to generate a secondary order book. In the event of the first node computing entity experiencing a fault, the secondary order book can take over as the primary order book immediately and without any signification processing delays.

Abstract: Example embodiments provide for secure storage and accessing of confidential information by a distributed system and for securely executing a function of the distributed system. Responsive to processing a function request identifying a function of the distributed system by a node computing entity, application program code corresponding to the function is accessed within a trusted execution environment. Based on data stored in a secure ledger maintained by the distributed system, the application program code is executed to generate a result within the trusted execution environment. A new entry comprising the result is generated and at least a portion thereof is encrypted using an encryption key within the trusted execution environment. The encrypted new entry is posted to the secure ledger.

Abstract: A snapshot of a distributed ledger is generated, wherein the distributed ledger is stored by a plurality of node computing entities. A first node computing entity reads current states of one or more domain objects from a local cache stored by the node computing entity and corresponding to an application operating on the node computing entity. A snapshot record comprising the current states of the one or more domain objects is generated and written to a segment data file. The snapshot record is posted to the distributed ledger as part of a block.

Abstract: An immediate failover from a primary order book to a secondary order book is provided. The primary order book represents a current state of one or more orders according to a first node computing entity and the secondary order book represents a current state of all orders according to a second node computing entity. An input stream of order information is processed by the first node computing entity to generate (a) a primary order book and (b) an output stream of order information. A secondary stream of order information is provided to a second node computing entity. The second stream of order information is processed to generate a secondary order book. In the event of the first node computing entity experiencing a fault, the secondary order book can take over as the primary order book immediately and without any signification processing delays.

Abstract: User access to a set of data stored in a distributed ledger, wherein the distributed ledger is stored by a plurality of node computing entities, is provided. A first node computing entity receives a share key request indicating that a first user account has authorized a second user account to have access to a set of data stored in the distributed ledger. A data access key (DAK) for accessing the set of data is encrypted using an encrypting key of the second user account. A block comprising the encrypted DAK is generated, signed using a signing key of the first user account, and posted to the distributed ledger. The block is authenticated using an authentication key of the first user account and accessed via a decrypting key of the second user account such that the second user account may use the DAK to access the set of data.

Abstract: A distributed ledger is stored by a plurality of node computing entities. A node computing entity of the plurality of node computing entities comprises at least one processor, a memory, and a communications interface configured to communicate via at least one network. The node computing entity creates a finite state machine record set. A finite state machine record of the finite state machine record set comprises (a) event data for a corresponding event and (b) a domain object state for a domain object corresponding to the corresponding event. The domain object state indicating the state of the domain object as a result of the corresponding event. The node computing entity generates a block comprising the finite state machine record set and posts the block to the distributed ledger.