A method for enabling pruning of a blockchain of a blockchain network includes creating an active blocks commitments Merkle tree from hashes of active blocks and creating an active smart contracts commitments Merkle tree from hashes of active smart contracts. The Merkle trees are created after an amount of blocks created in the blockchain has reached a threshold set by a pruning threshold parameter stored in the blockchain network. Hashes of the roots of the Merkle trees are stored in a header of a new block as a new genesis block. The new genesis block is broadcast to the blockchain network. A set of the active blocks and active smart contracts used respectively to create the active blocks commitments Merkle tree and the active smart contracts commitments Merkle tree are committed to upon the blockchain network reaching consensus on the new genesis block.

In one example, a catalog service may use a peer-to-peer network to distribute a data content item across multiple associated user devices. The catalog service may maintain a device group list describing a device group and a content catalog for the device group listing a data content set stored in the device group. The catalog service may identify a content change to the data content set listed in the content catalog at a seed device of the device group. The catalog service may send an update alert to a leeching device of the device group of the content change to trigger the leeching device to receive the content change over a peer-to-peer network between the seed device and the leaching device.

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.

Provided herein are devices, systems, methods and various means, including those related to providing a community internet drive that may utilize a centrally-managed hub as well as storage devices distributed among various networked machines. In some embodiments, the community internet drive can also include features to enable its users to promote and utilize the user's trusted personal relationships while also enabling an open platform for peer-to-peer and/or other types of sharing schemes.

An example operation may include one or more of receiving a data block for storage on a blockchain from an orderer node, the data block comprising a full-step hash of a storage request and a reduced-step hash of the storage request, performing an approximate hash verification on the data block based on the reduced-step hash of the storage request included in the data block, and in response to a success of the approximate hash verification, committing the data block among a hash-linked chain of data blocks stored within a distributed ledger of a blockchain.

A secure method for exchanging entities via a blockchain is presented. The method comprises receiving, from a user over a communications network, an invitation to perform an exchange of entities; generating a redeem script comprising metadata; hashing the redeem script to generate a redeem script hash; sending the first script and the first script hash on a distributed hash table (DHT); and generating an invitation transaction comprising an output associated with an encrypted digital asset, and a hash of a script comprising an indication of entities to be exchanged, conditions for the exchange, and a public cryptographic key associated with the user.

The invention provides for a cloud-based solution that saves all the data in the cloud storage. The peer devices synchronize data among each other independent of the operating system since the data is synced via web services. Synchronization of data among peer devices is possible even when cloud service is unavailable via a router, Wi-Fi, Bluetooth, NFC or any other mechanism. The peer devices form a hierarchical structure, which designates a master, and the master communicates with the cloud-based service to synchronize data. The master then synchronizes data with the other peer devices in the hierarchy. New devices can be added to the peer devices and can join the hierarchy.

Systems and methods are described herein for facilitating access to a telecommunications network by a third-party device via one or more available subscriber devices. The network-based systems enable devices associated with subscribers of the telecommunications networks to establish connections with other mobile devices (e.g., third-party mobile devices of users that are not subscribers) over peer to peer (P2P) communication protocols. For example, a subscriber device can, over a P2P connection, act as a Hotspot, Wi-Fi tether, or bridge for a third-party or other device requesting access to the networks.

The location of resources for file services are located within the same site, thereby eliminating or reducing performance issues caused by cross-site accesses in a stretched cluster environment. A file server placement algorithm initially places file servers at a site based at least in part on host workload and affinity settings, and can perform failover to move the file servers to a different location (e.g., to a different host on the same site or to another site) in the event of a failure of the host where the file servers were initially placed. File servers may be co-located with clients at a location based on client latencies and site workload. Failover support is also provided in the event that the sites in the stretched cluster have different subnet addresses.

Disclosed embodiments relate to distributed, crowd-sourced Internet of Things (IoT) discovery using Block Chain. In one example, a method includes scanning a network and generating a signature based on IoT device traits discovered, determining whether the signature is already in a verified or an unverified Block Chain, when the signature exists in the verified Block Chain, providing a verified entry including at least the IoT device type, otherwise, when the signature exists in the unverified Block Chain, providing an unverified entry including at least the IoT device type, incrementing a count, and promoting the unverified entry to the verified Block Chain when the count reaches a threshold, and otherwise, when the signature is in neither Block Chain, using the traits to guess the IoT device type, generating a new entry including the IoT device type, a location, and a timestamp, and storing the new entry in the unverified Block Chain.