WO2019114097A1

WO2019114097A1 - Blockchain-based distributed storage method

Info

Publication number: WO2019114097A1
Application number: PCT/CN2018/073677
Authority: WO
Inventors: 尚小朋
Original assignee: 成都链一网络科技有限公司
Priority date: 2017-12-15
Filing date: 2018-01-22
Publication date: 2019-06-20
Also published as: CN108111585A; CN108111585B

Abstract

A blockchain-based distributed storage method, comprising: S1. an uploader in a distributed storage network generating an upload request, and recording the upload request in a smart contract of a blockchain; S2. a file to be stored being segmented into a plurality of file fragments; S3. a storer in the distributed storage network generating a storage request, and recording the storage request in the smart contract of the blockchain; S4. in the blockchain, generating a storage transaction of the uploader and the storer storing the file fragments; S5. the storer storing the file fragments. The method implements the distributed storage of files, and increases the security of file storage.

Description

Blockchain-based distributed storage method

Technical field

The present invention relates to the field of data storage technologies, and in particular, to a distributed storage method based on a blockchain.

Background technique

In the prior art, the data storage has two types of centralized storage solutions and decentralized storage solutions; currently, the internationally famous centralized storage solutions include Dropbox, OneDrive, Google Drive, and SkyDrive, and the more mature centralized storage solutions in China have Baidu network disk, Huawei network disk, Jinshan fast disk, 115 network disk, 360 cloud disk, nut cloud and Tencent micro cloud; decentralized storage solutions are more famous are Storj, Sia and Maidsafe.

Decentralized storage can significantly reduce the risk of data interruption and its loss, increasing the security and confidentiality of data storage. Existing cloud storage relies on third-party large-scale storage to transmit and store data, such as 360 cloud disk, Baidu network disk, etc. These large-scale storage stores have all data backup and all user information, which is limited by the centralized architecture. It is very vulnerable to a variety of security threats; redundant and decentralized distributed storage can effectively improve this situation, effectively resisting tampering and unauthorized access.

technical problem

Existing cloud storage relies on third-party large-scale storage to transmit and store data, such as 360 cloud disk, Baidu network disk, etc. These large-scale storage stores have all data backup and all user information, which is limited by the centralized architecture. Very vulnerable to a variety of security threats.

The object of the present invention is to overcome the deficiencies of the prior art and provide a distributed storage method based on a blockchain, which realizes distributed storage of files and improves file storage security.

Technical solution

The object of the present invention is achieved by the following technical solutions: a blockchain-based distributed storage method, including:

S1. The uploader in the distributed storage network generates an upload request, and records the upload request in a smart contract of the blockchain;

S2. Dividing the file to be stored into multiple file fragments;

S3. The storage in the distributed storage network generates a storage request, and records the storage request in a smart contract of the blockchain;

S4. Generating, in the blockchain, a storage transaction in which the uploader and the store store the file fragments;

S5. The store stores the file fragment.

Preferably, the upload request includes a split number of files, a backup number of files, a file description, an uploader's public key, an uploader's account name, an uploader ID, and a file ID.

Preferably, the storage request includes a storage user's account name, a file ID, and a file shard ID.

Preferably, the file ID is composed of a hash value of the file and a public key of the uploader, and the file fragment ID is composed of a hash value of the file fragment and a public key of the uploader.

Preferably, the S4 includes: an uploader viewing the storage request, and granting the storage permission to store the file fragment.

Preferably, the S5 comprises:

The store initiates a request to the uploader to download the file fragment;

The uploader verifies whether the store has the storage permission of the file fragment, and if so, the uploader allows the store to download the file fragment;

The store downloads and stores the file fragments from the uploader.

Preferably, the S5 further includes:

The storage device updates the storage request, and writes information that the file fragment downloading is completed;

The uploader updates the upload request and writes the information that the file fragment has stored.

Preferably, the information that the file fragment downloading is completed includes a file ID, a file fragment ID, and an account name of the storage, and the information stored in the file fragment includes an account name, a file ID, and a file fragment ID of the uploader. And the store ID.

Preferably, the transmission of the file fragment is implemented by the storage between the storage and the uploader.

Beneficial effect

(1) The invention realizes distributed storage of files, and any node does not have a complete backup of the entire file, thereby improving the security of the file;

(2) The important information such as the metadata of the file is stored in the blockchain through the smart contract verification. Since the data stored in the blockchain cannot be tampered with, the important information can be well protected;

(3) Each user can be either a storage demand side or a storage provider, which can effectively improve the utilization of idle storage resources of the network, and also bring corresponding benefits to users who provide storage resources;

(4) The use of eMule for file segmentation transmission has good stability.

DRAWINGS

Figure 1 is a schematic flow chart of the present invention.

Embodiments of the invention

The technical solutions of the present invention will be described clearly and completely in combination with the embodiments. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without any inventive effort are within the scope of the present invention.

Explanation of terms:

Blockchain: A chained data structure that combines data blocks in sequential order in chronological order, and cryptographically guaranteed non-tamperable and unforgeable distributed ledgers.

Smart Contract: A set of commitments defined in digital form, including agreements where contract participants can execute these commitments. From a procedural perspective, a smart contract is a programming language programmed on a blockchain that triggers related operations when certain specified conditions are met.

Referring to FIG. 1, the embodiment provides a distributed storage method based on a blockchain, which specifically includes the following steps:

S1. The uploader in the distributed storage network generates an upload request and records the upload request in the smart contract of the blockchain.

The upload request includes the number of splits of the file, the number of backups of the file, the willingness to pay, the description of the file, the public key of the uploader, the account name of the uploader, the uploader ID, and the file ID. The file ID is composed of a hash value of the file and a public key of the uploader.

The uploader is a user in the distributed storage network as a storage demander, that is, the user has files to be stored. The uploader initiates a request to upload a file to the distributed storage network, performs basic verification on the request, sets relevant parameters, and then calls the transaction of the File_Upload (file upload) contract of the blockchain, and the contract check After there is no problem, create an upload request record for the blockchain.

S2. Divide the file to be stored into multiple file fragments. That is, the file is divided into multiple file fragments according to the number of splits and the number of backups in the upload request; for example, the number of split files is 5, the number of backups is 2, and the file is split into 5 file fragments. There are two copies of each file fragment, and a total of ten file fragments need to be stored.

After the file is divided into multiple file fragments, the file is sliced and stored in the location set by the uploader.

S3. The storage in the distributed storage network generates a storage request and records the storage request in a smart contract of the blockchain.

The storage request includes an account name, a file ID, and a file fragment ID of the storage; the file ID is composed of a hash value of the file and a public key of the uploader, and the file fragment ID is divided by the file The hash value of the slice is composed of the public key of the uploader.

The storage is a user in the distributed storage network as a storage resource provider, that is, the user provides storage resources for the uploader. The storeer calls the blockchain_get__upload_requests interface of the blockchain (checking the existing upload request) to view the uploader's upload request. After seeing the upload request, the store combines the hash value of the file with the uploader's public key to form a file ID. , generate a storage request, declare which file fragments you want to store the file.

S4. Generate, in the blockchain, a storage transaction in which the uploader and the store store the file fragments. That is, the uploader views the storage request and grants the storage owner the storage authority to store the file fragment.

The uploader calls the wallet_list_store_request_for_my_file of the blockchain (the storage request viewing interface is used for the uploader to view the storage request related to the file to be uploaded). The interface views the storage request of the storage, and then the uploader calls the wallet_allow_store_request interface of the blockchain ( The download interface is allowed to grant the storage permission of a file fragment to the store) to allow the store to store the corresponding file fragment (ie, allowing the store to download the corresponding file fragment).

S5. The store stores the file fragment.

The S5 includes: a request by the store to the uploader to download the file slice; the uploader verifies whether the store has the storage permission of the file slice, and if so, the uploader allows the store to download the file slice The store downloads and stores the file fragments from the uploader.

The storage device sends a request for downloading the corresponding file fragment to the uploader's eMule. After receiving the request, the uploader's eMule calls the download_validation of the blockchain (authentication interface for performing download permission authentication) to verify whether the storage is allowed. Download. If allowed, the store's eMule downloads the corresponding file fragment from the uploader's eMule.

The S5 further includes: the storage device updating the storage request, and writing the information that the file fragment downloading is completed; the uploader updating the upload request, and writing the information that has been stored in the file fragment.

The file fragment downloading completed information includes a file ID, a file fragment ID, and a storage user's account name. The file fragment stored information includes an uploader's account name, a file ID, a file fragment ID, and a storage. ID.

After the storage of the storage device is completed, the storeer calls the declare_piece_saved of the blockchain (the storage completion declaration interface is used for the store to initiate the declaration that the file storage has been completed), and the file is written on the blockchain. The status of the slice download is completed, the uploader calls the blockchain_list_file_save_declare of the blockchain (the storage completion statement view interface is used to list the storage completion declarations related to the specified file appearing in the blockchain network). The interface queries the file to be uploaded by itself. After storing the status information, the uploader sees that a file fragment of the file has been stored, and calls the confirm_piece_saved of the blockchain (confirming the storage declaration interface, for the uploader to initiate the storage of the confirmed file to complete the file fragmentation. The statement) writes the status of "The file fragment has been stored" on the blockchain. When all the file fragments of the file are downloaded by the storage, the storage of the file is completed.

The above is only a preferred embodiment of the present invention, and it should be understood that the present invention is not limited to the forms disclosed herein, and is not to be construed as being limited to the other embodiments, but may be used in various other combinations, modifications and environments. Modifications can be made by the techniques or knowledge of the above teachings or related art within the scope of the teachings herein. All changes and modifications made by those skilled in the art are intended to be within the scope of the appended claims.

Claims

A blockchain-based distributed storage method, comprising:

S1. The uploader in the distributed storage network generates an upload request, and records the upload request in a smart contract of the blockchain;

S2. Dividing the file to be stored into multiple file fragments;

S3. The storage in the distributed storage network generates a storage request, and records the storage request in a smart contract of the blockchain;

S4. Generating, in the blockchain, a storage transaction in which the uploader and the store store the file fragments;

S5. The store stores the file fragment.
The blockchain-based distributed storage method according to claim 1, wherein the upload request includes a split number of files, a backup number of files, a file description, an uploader's public key, and an uploader's account. Name, uploader ID, and file ID.
The blockchain-based distributed storage method according to claim 1, wherein the storage request includes a storage person's account name, a file ID, and a file fragment ID.
The blockchain-based distributed storage method according to claim 3, wherein the file ID is composed of a hash value of the file and a public key of an uploader, and the file fragment ID is The hash of the file fragment and the public key of the uploader.
The blockchain-based distributed storage method according to claim 1, wherein the S4 comprises: an uploader viewing the storage request, and granting the storage permission to store the file fragment for the storage .
The blockchain-based distributed storage method according to claim 1, wherein the S5 comprises:

The store initiates a request to the uploader to download the file fragment;

The uploader verifies whether the store has the storage permission of the file fragment, and if so, the uploader allows the store to download the file fragment;

The store downloads the file fragment from the uploader.
The blockchain-based distributed storage method according to claim 6, wherein the S5 further comprises:

The storage device updates the storage request, and writes information that the file fragment downloading is completed;

The uploader updates the upload request and writes the information that the file fragment has stored.
The blockchain-based distributed storage method according to claim 7, wherein the file fragment downloading completed information includes a file ID, a file fragment ID, and a storage user's account name, and the file fragmentation The stored information includes the uploader's account name, file ID, file shard ID, and store ID.
The blockchain-based distributed storage method according to claim 6, wherein the storage of the file fragments is implemented by the storage device and the uploader.