An example operation may include one or more of receiving a blockchain request from a client application, determining a network latency between the client application and the endorsing node based on a network path between the client application and the endorsing node, extracting a timestamp from the blockchain request, determining whether the extracted timestamp is invalid based on the network latency between the client application and the endorsing node, and in response to determining that the timestamp is valid, generating an endorsement for the blockchain request and transmitting the endorsement to the client application.

A blockchain maintenance record system for managing maintenance records of a system, the blockchain maintenance record system including: a part identification tag configured to be located on a part; an application operable through a mobile computing device, the mobile computing device being configured to read the part identification tag, wherein the application is configured to perform operations including; determining a part identity of the part by reading the part identification tag; detecting a location of the system; organizing the part identity of the part and the location of the part into a maintenance data package receipt; and uploading the maintenance data package receipt into a blockchain network.

An interface is instantiated for receiving storage requests for storing data in a software-defined storage network using an append-only storage scheme. The interface receives requests that are agnostic of interfaces and hardware-specific details of the storage devices of the software-defined storage network. A request comprises an identifier of a data object to be stored in the software-defined storage network using the append-only storage scheme. Metadata is generated for the data object indicating that the data object is an append-only object; and the request is translated to instructions for storing the data object in the storage devices using the append-only storage scheme. The data object is stored at one of the plurality of storage devices based on the instructions. The metadata is updated to indicate a mapping between the data object and a stored location of the data object.

An embodiment comprises a method of managing a project. The method comprises storing information, received from a first user via a first user device, regarding a first media project in a first database based on account information provided by the first user. The method also comprises selectively permitting, via a first interface, the second user to identify an action to perform for the first media project, wherein the action includes viewing the first media project or providing one of financial support, creative input, creative services, and property to the first media project and providing a prompt to the first user regarding the action identified by the second user. The method further comprises, when the first user accepts the action identified by the second user, storing data in the first database regarding the identified action to perform relative to the first media project and tracking the first media project within a life cycle including three stages and upon determining that the first media project is in a third stage of the life cycle, distributing records from the first database regarding the first media project for a third user to receive.

A machine for making liquid or semi-liquid food products, including: a first processing container for processing a basic liquid or semi-liquid product and defining a processing chamber; a stirrer positioned inside the first processing container; a thermal system including a heat exchanger, associated with the first processing container; at least one sensor, configured to measure an operating parameter of the machine; a processing and control unit, operatively connected to the at least one sensor and including a module for receiving and transmitting data captured by the sensor, wherein the module for receiving and transmitting data is configured to transmit data captured by the sensor to a “smart contract” program.

A method and an apparatus for managing a service request in a blockchain network are provided. The method includes receiving, by a first device, a service request, identifying an intent from the service request, selecting one or more atomic contracts, each of which is related to the intent, wherein the atomic contracts are associated with a second device on the blockchain network and are verified in the blockchain network, generating a new contract including the atomic contracts, and broadcasting the new contract over the blockchain network.

Hardware and software resources are load balanced when processing multiple blockchains. As more and more entities (whether public or private) are expected to generate their own blockchains for verification, a server or other resource in a blockchain environment may be over utilized. For example, as banks, websites, and retailers issue their own private cryptocoinage, the number of financial transactions may clog or hog networking and/or hardware resources. A blockchain load balancing mechanism thus allocates resources among the multiple blockchains.

Techniques are provided for resynchronizing a synchronous replication relationship. Asynchronous incremental transfers are performed to replicate data of a storage object to a replicated storage object. Incoming write requests, targeting the storage object, are logged into a dirty region log during a last asynchronous incremental transfer. Metadata operations, executed on the storage object, are logged into a metadata log during the last asynchronous incremental transfer. Sequence numbers are assigned to the metadata operations based upon an order of execution. The metadata operations are replicated to the replicated storage object for execution according to the sequence numbers, and the dirty regions are replicated to the replicated storage object in response to the metadata operations having been replicated to the replicated storage object. The storage object and replicated storage object are transitioned to a synchronous replication state where incoming operations are synchronously replicated to the replicated storage object.

Methods, systems, and devices for a cross-linked distributed ledger. The cross-referencing system includes multiple computing devices including a first computing device and a second computing device. A computing device of the multiple computing devices is configured to maintain a first cross-linked distributed ledger. The first cross-linked distributed ledger has a first set of multiple linked records that are associated with a first identifier. The first computing device includes a processor. The processor is configured to link or provide a first record associated with the first identifier to the first cross-linked distributed ledger. The first record has a first reference to a second record. The second record is within a second set of multiple cross-linked records of a second cross-linked distributed ledger.

The present disclosure relates to a method for data replication in a data analysis system (100). A source database system (101) of the data analysis system (100) comprises a transaction log (106) storing log records generated by database transactions. The method comprises in response to determining (303) that a received log record is generated by a database transaction that rolls back a change of another database transaction whose log records are buffered in at least one record buffer, data indicative of a log record generated by the other database transaction buffering (305) in the compensation buffer tag data. The tag data may be used (311) for replicating to a target database system of the data analysis system buffered log records of the record buffer which are not marked as compensation records.