A device may receive, from a user device, a transaction request associated with a first entity and identify a distributed ledger associated with the first entity, the distributed ledger including a set of blocks recording work data associated with the first entity. The set of blocks may include: a first subset of blocks including data specifying work performed by the first entity, and a second subset of blocks including data verifying a portion of the work performed by the first entity and specified by the data included in the first subset of blocks. The device may determine that a transaction, associated with the transaction request, is associated with the first subset of blocks and the second subset of blocks. Based on predetermined instructions that correspond to the transaction and the distributed ledger, the device may perform the transaction.

Aspects of the subject technology relate to systems and methods for sharing encrypted information among multiple devices. A peer-to-peer connection between a first computing device associated with a user account and a second computing device associated with the user account is established. Information associated with at least a portion of a file system of the second computing device may be received by the first computing device, where the portion of the file system comprises encrypted data. The portion of the file system of the second computing device may be mounted on the first computing device based on the received information.

A computer-implemented method (600) and system (1) for verifying ownership of a computer software for installation using a distributed hash table (13) and a peer-to-peer distributed ledger (14). This may be the Bitcoin blockchain or an alternative blockchain implementation. The method includes determining (610) a second user public key associated with a second user (24) from a transaction record stored on the peer-to-peer distributed ledger (14). A second public key associated with the second user may be determined (620) from an entry on the distributed hash table (13). The method further includes comparing (630) the second user public key and the second public key, and verifying (640) the ownership of the computer software based on the comparing of the second user public key and the second public key.

A node device configuring a peer-to-peer network includes: a network interface; and a blockchain management part configured to receive, through the network interface, an information registration request transaction that includes embedded Subscriber Identity Module, SIM, information including SIM identification information, an electronic signature put on the embedded SIM information by using a private key of an information registrant, and a public key paired with the private key, and accumulate the received information registration request transaction into a blockchain based on a consensus building algorithm executed in cooperation with another node device configuring the peer-to-peer network.

A system and method for reducing blockchain transaction delay are disclosed. The system consists of a trusted coin wallet framework that implements a trusted execution environment to initiate currency transactions between two clients. The trusted coin wallet framework includes an API proxy and a trusted shadow wallet. The method used by the trusted coin wallet framework involves interaction between the trusted shadow wallet and a peer trusted wallet owned by the other client, via the API proxy, from within the trusted execution environment. During these operations, the blockchain infrastructure is independently validating the transaction.

A blockchain node receives a service request, where the service request comprises one or more data types and respective service data corresponding to the one or more data types that are stored in a blockchain. At least one of a service type or identification information is determined corresponding to the service request. The service request is parsed to obtain each data type of the service request and service data corresponding to each data type. Based on a mapping relationship between a data type and service data, the service data that is obtained through parsing in a relational database corresponding to the blockchain node is stored.

Methods and systems for providing data manifests as a service (DMAAS) are described herein. a first computing system, may generate a first data manifest comprising a first count parameter and a first hash parameter associated with a first data exchange transaction between the first computing system and a second computing system, store the first data manifest to a blockchain data store and transfer a data payload of the first data exchange transaction. The second computing system may analyze the data payload received via the transport mechanism, generate a second data manifest including a second count parameter and a second hash parameter and store the second data manifest to the blockchain data store. A DMAAS computing system facilitates access to the blockchain data store, identifies transmission errors, and triggers acceptance of data at the second computing system upon a successful data exchange transaction.

When a local server that is connected to a wireless local area network (WLAN) receives a service request from a first electronic device, the server identifies a resource to provide one or more elements of the service. The server assigns the resource to provide the service element(s). The local server also selects one or more mutual distributed ledgers (MDLs) having parameters that correspond to the service request. The local server generates and transmits, to a gateway server, a transaction record having a format that corresponds to the selected MDL. This enables the local server to facilitate the delivery of services such as spectrum sharing, content streaming, and the like using WLAN-connected devices to facilitate delivery of the service. It also enables the gateway server to update each selected MDL with a transaction ledger that follows each selected MDL's format.

An example operation may include one or more of receiving, by a blockchain node or peer, a deploy chaincode blockchain transaction, and in response establishing a cold asset storage repository comprising pointers to each of the assets of a blockchain stored in a shared ledger, each of the assets comprising a key-value pair, establishing a hot asset storage repository of predetermined size and configured to store a subset of the assets of the blockchain, and configuring asset classification rules to organize hot asset storage and cold asset storage.

Nodes determine a first measure of difficulty for a first branch of a split blockchain and a second measure of difficulty for a second branch of the split blockchain. The first measure of difficulty is based on a measure of block generation frequency of each node that mined for the split blockchain during a window that comprises blocks of the first branch. The second measure of difficulty is based on a measure of block generation frequency of each node that mined for the split blockchain during a window that comprises blocks of the second branch. One of the first branch and the second branch is identified as a legitimate branch based on a comparison of the first measure of difficulty and the second measure of difficulty.