A system includes a ledger on which a task giver may register a task. The task may include executable code. A task solver may accept the task and execute the code to produce a solver output that is recorded on the ledger. Verifiers may provide competing verifier outputs which may also be recorded on the ledger. The solver and verifiers may compare their outputs to determine if there is agreement. Agreement may signify consistent and accurate execution of the code. Disagreement may indicate the presence of errors. In some cases, the solver and verifiers may compete in a contention-based protocol where a solver may assert control of tokens where the solver identifies an error in verifier execution. Additionally or alternatively, a verifier may assert control of tokens where the verifier identifies an error in solver execution.

A system for security key rotation in a cloud computing environment is disclosed. The system performs steps to at least initiate, at a predetermined interval, a call to determine whether to initiate generation of a public-private key pair for a client application. The system determines whether to initiate generation of the public-private key pair for the client application and based on determining to initiate generation of the public-private key pair for the client application, transmits a control signal requesting generation of the public-private key pair The system generates the public-private key pair and transmits a private key associated with the public-private key pair to a secure storage location for later retrieval by the client application and transmits a public key associated with the public-private key pair to a public key service for later retrieval by a client associated with the client application.

A federated-data-room server manages information about a collection of electronic documents residing elsewhere (under different organizational/customer control). The server can anchor documents to a blockchain, record usage history of each document, and provide access to the documents for authorized users. As a result, the federated-data-room server operates on customers' data, while leaving the data in control of the customers. At the same time, the federated-data-room server provides data access and enables traceability via blockchain recordation of document identifiers and document hash values.

Methods and systems are provided for crowdsourced funding via a blockchain system. A token contract, associated with a token issuer, is generated on a blockchain system. Tokens are issued to a plurality of token holders. Each of the plurality of token holders is allowed access to a feedback mechanism associated with the token issuer. A performance of the token issuer in an associated field is monitored to provide at least one performance metric. A dividend is paid to each token holder proportional to a number of tokens held by the token holder after a predetermined amount of time based on the at least one performance metric.

Systems and methods are disclosed with respect to using a blockchain for managing the subrogation claim process related to a vehicle accident, in particular, determining fault as part of the subrogation process. An exemplary embodiment may include receiving an electronic notification of a vehicle collision; receiving sensor data (such as telematics, image, audio, vehicle operational, or other sensor data) related to the vehicle collision; determining a percentage of fault of the vehicle collision for one or more vehicles, vehicle systems, and/or drivers based upon, at least in part, analysis of the sensor data collected; and creating a blockchain for the vehicle collision with one or more links to the sensor image data and an indication of the percentage of fault(s) determined to facilitate blockchain-based claim handling.

A global resource locator (GRL) device can be used to track a physical asset. The GRL device can a semiconductor chip with a processor and a timing device. The semiconductor chip can generate a timing signal. The GRL device can include a blockchain, a communication device, and a memory in logical communication with the processor. The memory can store an identifier, a public key, a private key, and a hash. The communication device can communicate wirelessly with an authenticated radio source, the micro sized timing device, and the blockchain. Each authenticated radio source can be located at a respective reference location. The communication device can receive wireless timing signals from at least three authenticated radio sources. The GRL device can be affixed to a product.

Systems and methods to timestamp and authenticate digital documents using a secure ledger are described. Some implementations can include computer-implemented method to timestamp and authenticate electronic documents. The method can include receiving, by a timestamp and authentication server and from a user device, a unique hash value that is generated at the user device based on a source document and a device identifier of the user device, and verifying, by the timestamp and authentication server, the device identifier. The method can also include, upon verifying the device identifier, inserting, by the timestamp and authentication server, the hash value and the device identifier into a secure ledger, and upon successful insertion into the secure ledger, transmitting, from the timestamp and authentication server to the user device, a success status message including a location in the secure ledger where the hash value was inserted.

Systems and methods of providing immutable records, and immutable ordering of records, in a computing system are disclosed. The computing system can be a member of a blockchain network of a plurality of blockchains. Each block can include a cryptographic digest (or hash) conforming to a minimum degree of difficulty, a nonce by which the cryptographic digest was generated in conformation with the degree of difficulty, and a list of cryptographic digests of most recent blocks of participating neighbor blockchains. Blocks may be passed between blockchains of the plurality of blockchains, which enables each member of the blockchain network to verify an immutable record of data transactions free of the mutual trust requirement of a typical blockchain environment. In conjunction with the generation of each block, an event record may be entered into an event log of the computing system wherein the block was generated. The event record, which may contain actionable instructions, requests, etc., may be transmitted to computing systems of participating neighbor blockchains, where actionable items may be acted upon. Further, the event logs of each computing system may be exchanged, compared, and adjusted to reflect the earliest appearance of each block of each participating neighbor blockchain.

A verification platform may include a data connection to receive a stream of industrial asset data, including a subset of the industrial asset data, from industrial asset sensors. The verification platform may store the subset of industrial asset data into a data store, the subset of industrial asset data being marked as invalid, and record a hash value associated with a compressed representation of the subset of industrial asset data combined with metadata in a secure, distributed ledger (e.g., associated with blockchain technology). The verification platform may then receive a transaction identifier from the secure, distributed ledger and mark the subset of industrial asset data in the data store as being valid after using the transaction identifier to verify that the recorded hash value matches a hash value of an independently created version of the compressed representation of the subset of industrial asset data combined with metadata.

Disclosed herein are methods, systems, and apparatus for processing blockchain-based guarantee information. One of the methods includes receiving a first cyphertext of a first digital document specifying a guarantee from a first computing device associated with at least a first guarantor and one or more zero-knowledge proofs (ZKPs) related to one or more values associated with the guarantee, and the first digital document specifies one or more predetermined conditions of executing the guarantee; verifying that the one or more ZKPs are correct; storing the first cyphertext to a blockchain based on performing a consensus algorithm; receiving a first message from a second computing device associated with a beneficiary or a representative of the beneficiary.