Erasure encoded fragments are generated by an erasure encoding scheme, represented by an erasure encoding matrix, operating on a data file. A new erasure encoded fragment may be generated from previously-generated erasure encoded fragments without reconstructing the original data file. Available and valid erasure encoded fragments are identified and a set of those fragments is selected. A composite encoding matrix is generated based upon the selected fragments and the fragment specified to be generated. The composite matrix is applied to the selected fragments to produce a plurality of partial sums. The partial sums are then combined to generate the specified fragment. The partial sums may be produced by different devices so as to distribute the computational workload and/or to reduce network traffic. The integrity of a generated fragment may be verified by generating the specified fragment twice, using two different sets of fragments, and then comparing the two results.

A streaming distributed decentralized database task system can perform multiple tasks on clusters of nodes without overloading the clusters' computational resources, such as disk, memory, processors, and network bandwidth. A cluster master can manage a job and add items to node queues. A node manager accepts or rejects queue items based on streaming task limits that are applied at the node level.

Peer-to-peer redundant file server system and methods include clients that determine a target storage provider to contact for a particular storage transaction based on a pathname provided by the filesystem and a predetermined scheme such as a hash function applied to a portion of the pathname. Servers use the same scheme to determine where to store relevant file information so that the clients can locate the file information. The target storage provider may store the file itself and/or may store metadata that identifies one or more other storage providers where the file is stored. A file may be replicated in multiple storage providers, and the metadata may include a list of storage providers from which the clients can select (e.g., randomly) in order to access the file.

A device may receive content data from a content provider, the content data including: data identifying content, and data for verifying that the content has not changed. The device may access a blockchain associated with the content data, the blockchain including validation information specifying instructions for validating the content. In addition, the device may perform, based on the validation information, validation of the content to determine a measure of confidence that the content is accurate and store results of the validation in the blockchain as a transaction. Based on the validation results, the device may perform an action.

A system and method for managing a plurality of network-enabled client devices such as networking equipment and Internet of Things (IoT) devices which employs a distributed ledger, or blockchain, to store network configuration information for each client device. Access to the distributed ledger may be provided through a proxy computing system that is configured to exchange control messages with the client devices. Network configuration information is defined in smart contracts stored in the distributed ledger which are executed on registration of the network-enabled client device in the distributed ledger.

A system includes a plurality of first building components, a private local blockchain, a second building component, and a client device. The private local blockchain includes a device ledger indicating each first building component, a transaction ledger maintaining a plurality of blocks corresponding to a transaction between at least two first building components and including at least one first unique identifier of the corresponding first building component and a timestamp of the transaction, a transaction processor that generates at least one block by executing a predetermined hash function using a previous block, and a local rule engine defining rules to evaluate a transaction. The second building component has at least one second unique identifier. The client device provides the at least one second unique identifier to the private local blockchain. The private local blockchain determines whether to add the second building component to the device ledger.

One or more exercise devices may be connected to a local exercise device network. A user may select an exercise program to be performed that not located on the user's exercise device. Before downloading the exercise program from the cloud, the exercise device receives the requested exercise program from the other exercise devices on the exercise device network.

Methods and systems for creating an implicit profile for use by a recommendation engine or a question router is provided. User behavior on at least one of one or more electronic devices and an electronic communications network is tracked. User-related information relating to the user behavior is analyzed to extract or derive key words therefrom. The key words are stored in a profiles database as the implicit profile and used by the recommendation engine or question router to characterize user interests, expertise, and skills when matching a request from a querying user to a potential user or group of users having the relevant background to respond to the request.

Provided are a device and method for sharing big data using a blockchain. The method of sharing big data using a blockchain includes receiving a search condition from a user terminal, searching a blockchain network for metadata meeting the received search condition and acquiring found metadata, acquiring shared data stored in a distributed storage using the acquired metadata, and transmitting the acquired shared data to the user terminal.

An approach for sharing an asset in a peer-to-peer network is provided. After determining a locally stored first list does not include meta data specifying the asset, a new node is identified. In response to receiving a subscription from the new node, a second list locally stored at the new node is received. The second list includes the meta data and an identification of a source node that has the asset. The first list is updated to include the meta data and the identification of the source node. The updated first list is searched and in response, the meta data and the identification of the source node are detected. Based on the detected meta data and identification, the source node is identified. A request to retrieve the asset is sent to the source node, and in response, the asset is received.