CN110750762A - Blockchain-based open source software right confirmation method and system - Google Patents

Abstract

A blockchain-based open-source software right confirmation method and system. On the open-source software blockchain service platform, a blockchain service is initialized, and a smart contract for each node in the blockchain network to transmit contribution information is deployed. . The open source software blockchain service platform completes the creation of the project and generates the corresponding software warehouse according to the request. The developer client of each project performs code cloning, copies the code information in the software warehouse to the developer client of each project, and completes network access. The project developer completes the code submission, and the open source software blockchain service platform completes the distribution of rights and interests according to the amount of code contributed by the project developer, and realizes the confirmation of the rights and interests of the contribution information corresponding to the project developer. The invention can record the code contribution of each project developer in the open source software project development process in the block chain network in a non-tamperable form, so as to realize the conversion of the code contribution to the rights and interests of each project developer, and form an effective protection of.

Description

Blockchain-based open source software right confirmation method and system

technical field

The present application relates to the field of blockchain application technology, in particular to a blockchain-based open source software right confirmation method and system.

Background technique

The operating mechanism of open source software is to open the source code of the program under different types of license systems on the basis of recognizing the traditional copyright, so that the public can develop and use it. There are currently six main types of open source licenses, namely: LGPL, Mozilla, GPL, BSD, MIT, and Apache. These six licenses respectively determine whether the modified code can be closed source, whether the new code adopts the same license, Whether it is necessary to provide documentation for source code modification, whether each modified file needs to place a copyright notice, and whether derivative software advertisements can be limited by the promotion of their own name. But in fact, there are still many flaws in the use of software licenses to restrict the spread of open source software. The main problems are as follows:

1. There are a large number of non-code software products. At present, the software code itself is mainly concerned with the confirmation of software rights, but in fact, in the development process of open source software, there are a large number of process products, such as: issues, comments, etc., among which there are a large number of process products that have a significant impact on software development. Code-like software products that are not covered by open source licenses.

2. Diverse stakeholders. In the process of open source software development, there are various stakeholders, including: core developers in the early stage of software creation, content contributors, investors and communicators in the process of group open participation, and software users after the project is formed. Multiple stakeholders make it difficult for existing methods to confirm the stake of each participant.

3. Code references are frequent and the relationship is complex. In software development, calls to existing APIs are involved, and new APIs may be encapsulated on the basis of existing APIs. For open source licenses, it is difficult to form a network of associations in the huge open source ecosystem, and it is difficult to trace the source of all codes and realize rights confirmation.

4. Coarse-grained indication. For open source licenses, it is mainly a project or file-level indication, but in the actual coding process, there is a lot of method-level reuse. As such, the existing open source licensing approach does not apply to more fine-grained software confirmation.

5. Unknown infringement risk. In the process of using open source projects, because developers do not understand different types of open source licenses, or because they do not carefully check the open source licenses of reused software, it is likely to cause unintentional infringement.

Due to the defects of the open source license, in fact, a large number of infringements in the development of open source software have not been discovered, which to a certain extent leads to the damage to the contribution behavior of contributors and restricts the rapid development of open source software and the open source ecosystem.

At present, there is no fully related work in this field. Although Digital Guardian in the United States and Annie Co., Ltd. in China have already conducted relevant research in the field of digital rights confirmation, they are mainly oriented to data privacy protection. In contrast, open source software also involves the dissemination of code and the use of software, so it is more diverse and complex.

SUMMARY OF THE INVENTION

Aiming at the blank of open source software in terms of right confirmation method, the present invention provides a blockchain-based open source software right confirmation method and system.

For realizing the above-mentioned technical purpose, the technical scheme of the present invention is:

Blockchain-based open source software rights confirmation methods, including:

Step (1), initialize the blockchain.

On the open source software blockchain service platform, initialize a blockchain service and deploy smart contracts for each node in the blockchain network to transmit contribution information; the open source software blockchain service platform will serve as a static access node for regional Other nodes in the chain network access the regional chain network.

Step (2), project creation.

The project creator client sends a project creation request to the open source software blockchain service platform, and the open source software blockchain service platform completes the creation of the project and generates the corresponding software warehouse.

Step (3), project developer code clone and network access.

The developer clients of each project perform code cloning, copy the code information in the software repository to the developer clients of each project, and the developer clients of each project who have completed the code cloning are connected to the open source software blockchain service platform as static access A blockchain network of nodes.

Step (4), project developer code submission and rights confirmation.

After completing the development of the project code, each project developer submits the code to the open-source software blockchain service platform through their corresponding clients, and merges the code into the software warehouse corresponding to the open-source software blockchain service platform; the open-source software blockchain service platform Equity is allocated according to the amount of code contributed by the project developer, and the contribution information corresponding to the project developer is broadcast to other project developer clients in the blockchain network. After receiving the contribution information, other project developer clients access the The open source software blockchain service platform completes the confirmation of the contribution information, thereby completing the confirmation of the rights and interests of the contribution information corresponding to the project developer.

In the present invention, the Trustie server is used as an open source software blockchain service platform, and a blockchain service is initialized through the init command of the blockchain.

In step (2) of the present invention, the project creator client further includes a project creator identity verification step before sending the project creation request. The creator client submits the project creator's authentication request, and the Trustie server performs authentication processing on the received authentication request, and determines whether the identity information carried in the authentication request, such as the user name and password of the project creator, is correct. , the project creator client connects to the blockchain network with the Trustie server as the access node.

In step (2) of the present invention, the project creation request carries the name of the open source software project to be created, and the project creator client sends the project creation request to the Trustie server through the Restful API; the project creation request received by the Trustie server through the Restful API Verification and judgment are carried out on the project creation request, and it is judged whether the project name carried in the project creation request has the same name as other created project names in the Trustie server. If there is no overlapping name, the project can be created. The project is created and the corresponding software warehouse is generated, and the information representing "successful creation" is fed back to the project creator client; if the judgment is not passed, the result information representing "cannot create the project" is fed back to the project creator client. So that the project creator can re-determine the name of the project to be created.

In step (3) of the present invention, each project developer client also includes a project developer identity verification step before accessing the blockchain network. The client of each project developer submits the authentication request of the project developer, and the Trustie server performs authentication processing on the received authentication request, and judges whether the identity information carried in the authentication request, such as the user name and password of the project developer, is correct. If the information is correct, the project developer client is connected to the blockchain network with the Trustie server as the access node.

In step (3) of the present invention, each project developer client obtains the project name of the corresponding project in the Trustie server, and sends a code cloning instruction to the Trustie server by invoking the git service. After receiving the code cloning instruction, the Trustie server responds The code clone request sent by the client of each project developer sends the code information in the software warehouse of the corresponding project to the client of each project developer through the git transmission protocol, so as to complete the cloning of the software warehouse.

In step (4) of the present invention, the method for rights and interests distribution is:

For any project developer a, the open source software blockchain service platform records the number of lines of code submitted by project developer a each time, that is, the amount of contributed code, then the sum of the amount of contributed code submitted by project developer a during the current project development process It represents the intellectual property contribution amount A of the project developer a to the current project; the total amount of code contributed by all project developers to the project during the current project development process is the total intellectual property contribution amount B of the entire project, then the project developer a The stake is A/B.

In step (4) of the present invention, the confirmation method of contribution information is:

The project developer client obtains the text information contained in the received contribution information; the project developer client sends the contribution information query command to the open source software blockchain service platform through the Restful API, and the open source software blockchain service platform receives it. After text information, query the background database to obtain the code change information corresponding to the current code merge and send the code change information to the project developer client. After receiving the code change information, the project developer client compares it with the received text information , complete the confirmation of the contribution information, and finally record the contribution information on the blockchain.

In step (4) of the present invention, the roles corresponding to each project developer are divided into core developers and peripheral contributors, and the background database of the open source software blockchain service platform stores the role information corresponding to each project developer. Whether the code can be directly submitted to the software warehouse in the present invention is the most direct difference between the permissions of peripheral contributors and core developers.

The core developer code submission and rights confirmation methods are as follows:

After the core developer completes the development of the project code, the corresponding client sends a code submission request to the open source software blockchain service platform, and the project code is directly merged into the software warehouse of the corresponding project of the open source software blockchain service platform, and the open source software block The chain service platform completes the distribution of rights and interests according to the amount of code contributed by the core developers; the core developers broadcast their contribution information to other project developer clients of the blockchain network through the corresponding clients, and other project developer clients receive the contribution information After that, access the open source software blockchain service platform to complete the confirmation of the contribution information, thereby completing the confirmation of core developer rights;

Among them, the methods of code submission of peripheral developers and confirmation of rights and interests are as follows:

After the peripheral contributors complete the development of the project code, the corresponding client sends a code submission request to the open source software blockchain service platform, and the core developer client accepts the code request through the open source software blockchain service platform and obtains the code contained in the request. The code information, determine whether to pass its code merge request, if it is determined to pass the code merge request, then merge the project code submitted by the external contributor into the software warehouse of the corresponding project of the open source software blockchain service platform, open source software area The blockchain service platform completes the distribution of rights and interests according to the amount of code contributed by the peripheral contributor, and broadcasts its contribution information to other project developer clients of the blockchain network. After receiving the contribution information, other project developer clients access the open source software The blockchain service platform completes the confirmation of the contribution information, thereby completing the confirmation of the rights and interests of peripheral contributors.

The present invention provides a blockchain-based open source software right confirmation system, including:

The building module is used to initialize a blockchain service on the open source software blockchain service platform, and deploy smart contracts for each node in the blockchain network to transmit contribution information; the open source software blockchain service platform will serve as a static The access node is for other nodes in the area chain network to access the area chain network.

The project creation module is used to receive the project creation request sent by the project creator client, complete the creation of the corresponding project and generate the corresponding software warehouse.

The project developer code cloning and network access module is used to receive the code cloning request sent by each project developer client, copy the code information in the software repository to each project developer client, and complete the code cloning of each project. The developer client is connected to the blockchain network with the open source software blockchain service platform as the static access node.

The project developer code submission and rights confirmation module is used to receive and process the submitted code requests from each project developer client, and merge the code submitted by each project developer client into the software repository corresponding to the open source software blockchain service platform; according to the project The developer's contribution code amount completes the equity distribution, and broadcasts the contribution information corresponding to the project developer to other project developer clients in the blockchain network to complete the equity confirmation of the contribution information corresponding to the project developer.

The following technical effects can be achieved by adopting the present invention:

The invention can record the code contribution of each project developer in the open source software project development process in the blockchain network in an untamperable form, thereby realizing the conversion of the code contribution to the rights and interests of each project developer, and forming an effective Therefore, the traditional open source community has changed from the mode of rights and interests owned by a few people to the mode of sharing by all project developers.

Description of drawings

FIG. 1 is a flowchart of an embodiment of the present invention.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present invention clearer, the following will clearly illustrate the spirit of the disclosed contents of the present invention with the accompanying drawings and detailed description. , when changes and modifications can be made by the technology taught by the content of the present invention, it does not depart from the spirit and scope of the content of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

As shown in FIG. 1 , it is a structural flowchart of the blockchain-based open source software right confirmation in one embodiment.

Step (1), initialize the blockchain.

Using the Trustie server as an open source software blockchain service platform, initialize a blockchain service through the init command of the blockchain, and deploy a smart contract for each node in the blockchain network to transmit contribution information. The Trustie server will serve as a static access node for other nodes in the blockchain network to access the blockchain network. The text information contained in the contribution information includes the name of the project developer, the time when the project code was submitted, the project name, the submitted project code, the sha value of the code submission, and the number of lines added or deleted.

Step (2), project creation.

(2.1) Project creator identity verification;

The project creator client submits the project creator's authentication request, and the Trustie server performs authentication processing on the received authentication request, and determines whether the identity information carried in the authentication request, such as the project creator's username and password, is correct, such as identity information If it is correct, the project creator client is connected to the blockchain network with the Trustie server as the access node.

(2.2) Project creation;

The project creator client sends the project creation request carrying the name of the open source software project to be created to the Trustie server through the Restful API.

The Trustie server receives the project creation request through Restful API and verifies and judges the project creation request, and judges whether the project name carried in the project creation request is the same as the name of other created projects in the Trustie server. If the project is a creatable project, the Trustie server completes the creation of the project and generates the corresponding software repository, and at the same time feeds back information representing "successful creation" to the project creator client; The result information of "Create Project" is sent to the project creator client, so that the project creator can re-determine the name of the project to be created.

Step (3), project developer code clone and network access.

(3.1) Project developer identity verification.

The client of each project developer submits the authentication request of the project developer, and the Trustie server performs authentication processing on the received authentication request, and judges whether the identity information carried in the authentication request, such as the user name and password of the project developer, is correct. If the information is correct, the project developer client is connected to the blockchain network with the Trustie server as the access node.

(3.2) Project developer code clone.

The developer client of each project obtains the project name of the corresponding project in the Trustie server, and sends the code cloning instruction to the Trustie server by calling the git service. After receiving the code cloning instruction, the Trustie server responds to each project developer client. The code clone request sends the code information in the software warehouse of the corresponding project to the client of each project developer through the git transmission protocol to complete the cloning of the software warehouse.

If the cloning fails, and the reasons for the failure include network abnormality, authentication failure, etc., the corresponding project developer client will terminate the operation, and the return value of the git command will be displayed; if the cloning is successful, the command will be automatically sent to connect to the Trustie server. Enter the blockchain network of the node, and form a project development alliance with the clients of other developers in the project. The client will automatically feedback the result of successfully connecting to the blockchain network according to the connection situation.

Step (4), project developer code submission and rights confirmation.

The present invention divides the roles corresponding to each project developer into core developers and peripheral contributors, and the background database of the open source software blockchain service platform stores the role information corresponding to each project developer. Whether the code can be directly submitted to the software warehouse in the present invention is the most direct difference between the permissions of peripheral contributors and core developers.

The core developer code submission and rights confirmation methods are as follows:

After the core developer completes the development of the project code, the corresponding client sends a code submission request to the open source software blockchain service platform, and the project code is directly merged into the software warehouse of the corresponding project of the open source software blockchain service platform, and the open source software block The chain service platform completes the distribution of rights and interests according to the amount of code contributed by the core developers; the core developers broadcast their contribution information to other project developer clients of the blockchain network through the corresponding clients, and other project developer clients receive the contribution information After that, access the open source software blockchain service platform to complete the confirmation of the contribution information, thereby completing the confirmation of core developer rights;

Among them, the methods of code submission of peripheral developers and confirmation of rights and interests are as follows:

After the peripheral contributors complete the development of the project code, the corresponding client sends a code submission request to the open source software blockchain service platform, and the core developer client accepts the code request through the open source software blockchain service platform and obtains the code contained in the request. If the request is submitted through the code, the project code submitted by the external contributor will be merged into the software warehouse of the corresponding project of the open source software blockchain service platform, and the open source software area The blockchain service platform completes the distribution of rights and interests according to the amount of code contributed by the peripheral contributor, and broadcasts its contribution information to other project developer clients of the blockchain network. After receiving the contribution information, other project developer clients access the open source software The blockchain service platform completes the confirmation of the contribution information, thereby completing the confirmation of the rights and interests of peripheral contributors.

Among them, for equity distribution, the method is:

For any project developer a, the open source software blockchain service platform records the number of lines of code submitted by project developer a each time, that is, the amount of contributed code, then the sum of the amount of contributed code submitted by project developer a during the current project development process It represents the intellectual property contribution amount A of the project developer a to the current project; the total amount of code contributed by all project developers to the project during the current project development process is the total intellectual property contribution amount B of the entire project, then the project developer a The stake is A/B.

For the confirmation of contributed information, the methods are:

The project developer client obtains the text information contained in the received contribution information; the project developer client transmits the text information to the open source software blockchain service platform, and after the open source software blockchain service platform receives the text information Query the background database to obtain the code change information corresponding to the current code merge and send the code change information to the project developer client. After the project developer client receives the code change information, it completes the confirmation of the contribution information, and finally records the contribution information onto the blockchain.

The above-mentioned embodiment only expresses a specific embodiment of the present application, and the description thereof is specific and detailed, but it should not be construed as a limitation on the scope of the invention patent. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, several modifications and improvements can be made, which all belong to the protection scope of the present application. Therefore, the scope of protection of the patent of the present application shall be subject to the appended claims.

Claims (10)

1. The open source software right determining method based on the block chain is characterized by comprising the following steps:

step (1), initializing a block chain;

initializing a block chain service on an open source software block chain service platform, and deploying an intelligent contract for each node in a block chain network to transmit contribution information; the open source software block chain service platform is used as a static access node for other nodes in the area chain network to access the area chain network;

step (2), project creation;

the project creator client sends a project creation request to the open source software block chain service platform, and the open source software block chain service platform completes creation of the project and generates a corresponding software warehouse;

step (3), cloning a code of a project developer and accessing a network;

code cloning is carried out on each project developer client, code information in the software warehouse is copied to each project developer client, and each project developer client which completes code cloning is connected to a block chain network which takes an open source software block chain service platform as a static access node;

step (4), submitting codes of the project developers and confirming rights and interests;

after completing the development of project codes, each project developer submits the codes to the open-source software blockchain service platform through the corresponding client and combines the codes into a software warehouse corresponding to the open-source software blockchain service platform; and the open-source software blockchain service platform completes rights and interests distribution according to the contribution code quantity of the project developer, broadcasts the contribution information corresponding to the project developer to other project developer clients in the local area chain network, and the other project developer clients access the open-source software blockchain service platform after receiving the contribution information to complete the confirmation of the contribution information, thereby completing rights and interests confirmation of the contribution information corresponding to the project developer.

2. The method for determining the authority of the open source software based on the block chain as claimed in claim 1, wherein in the step (1), the Trustie server is used as an open source software block chain service platform, and a block chain service is initialized through an init command of the block chain.

3. The open source software authorization method based on the block chain according to claim 2, characterized in that in step (2), before the project creator client sends the project creation request, the project creator client further comprises a project creator authentication step, the project creator client submits the project creator authentication request, the trustee server performs authentication processing on the received authentication request, and determines whether the identity information carried in the authentication request, such as the project creator user name and password, is correct, if the identity information is correct, the project creator client connects to the block chain network using the trustee server as the access node.

4. The open source software authorization method based on block chaining according to claim 3, characterized in that in step (2), the project creation request carries the name of the open source software project to be created, and the project creator client sends the project creation request to the Trustie server through restful API; the Trustie server receives the project creating request through the Restful API and verifies and judges the project creating request, whether the project name carried in the project creating request is duplicated with other created project names in the Trustie server is judged, if no duplication name exists, the project is a creatable project, the Trustie server completes the creation of the project and generates a corresponding software warehouse, and meanwhile, information representing 'successful creation' is fed back to a project creator client; if the judgment is not passed, feeding back result information representing that the project cannot be created to the project creator client so that the project creator can determine the name of the project to be created again.

5. The blockchain-based open source software authentication method according to claim 1, wherein in the step (3), before each project developer client accesses the blockchain network, a project developer identity verification step is further included; and each project developer client submits an identity authentication request of the project developer, the Trustie server performs identity authentication processing on the received identity authentication request, whether identity information carried in the identity authentication request, such as a project developer user name and a password, is correct or not is judged, and if the identity information is correct, the project developer client is connected to a block chain network which takes the Trustie server as an access node.

6. The open source software right determining method based on the block chain as claimed in claim 5, characterized in that in the step (3), each project developer client obtains the project name of the corresponding project in the Trustie server, and sends the code cloning instruction to the Trustie server by calling the git service, after receiving the code cloning instruction, the Trustie server responds to the code cloning request sent by each project developer client, and sends the code information in the corresponding project software warehouse to each project developer client through the git transmission protocol, thereby completing the cloning of the software warehouse.

7. The method for determining the rights of the open source software based on the block chain as claimed in claim 6, wherein in the step (4), the rights and interests are allocated by:

for any project developer a, the open source software blockchain service platform records the code line number submitted by the project developer a each time, namely the contribution code quantity, and the sum of the contribution code quantity submitted by the project developer a in the current project development process represents the intellectual property contribution quantity A of the project developer a to the current project; in the current project development process, the sum of the contribution code amounts of all the project developers to the project is the total contribution amount B of the intellectual property of the whole project, and the rights and interests of the project developers a are A/B.

8. The method for determining the authority of the open source software based on the block chain according to claim 6, wherein in the step (4), the roles corresponding to the project developers are divided into a core developer and a peripheral contributor, and role information corresponding to the project developers is stored in a background database of the open source software block chain service platform;

the method for submitting the core developer code and confirming the rights and interests comprises the following steps:

after completing the development of project codes, a core developer sends a code submission request to an open-source software block chain service platform through a corresponding client, the project codes are directly merged to a software warehouse of a project corresponding to the open-source software block chain service platform, and the open-source software block chain service platform completes rights and interests distribution according to the contribution code quantity of the core developer; the core developer broadcasts the contribution information to other project developer clients of the regional chain network through the corresponding client, and after receiving the contribution information, the other project developer clients access the open-source software blockchain service platform to complete the confirmation of the contribution information, so that the rights and interests of the core developer are confirmed;

the method for submitting the codes of the peripheral developers and confirming the rights and interests comprises the following steps:

after completing the development of project codes, a peripheral contributor sends a code submission request to an open-source software blockchain service platform through a corresponding client, a core developer client receives the code request through the open-source software blockchain service platform and acquires code information carried in the request, determines whether the code combination request passes through the code combination request, if the code combination request passes through the code combination request, combines the project codes submitted by the peripheral contributor into a software warehouse of a project corresponding to the open-source software blockchain service platform, the open-source software blockchain service platform completes rights and interests distribution according to the contribution code quantity of the peripheral contributor and broadcasts contribution information to other project developer clients of an area chain network, and after receiving the contribution information, other project developer clients access the open-source software blockchain service platform to complete the confirmation of the contribution information, thereby completing the peripheral contributor equity validation.

9. The method for determining the authority of the open source software based on the block chain according to claim 8, wherein in the step (4), the method for confirming the contribution information is as follows:

the project developer client acquires the text information contained in the received contribution information; the project developer client sends a contribution information query command to the open source software blockchain service platform through the restful API, the open source software blockchain service platform queries the background database after receiving the text information to obtain code change information corresponding to current code combination and sends the code change information to the project developer client, the project developer client compares the code change information with the received text information after receiving the code change information to complete confirmation of the contribution information, and finally the contribution information is recorded to a blockchain.

10. Open source software right confirming system based on block chains is characterized by comprising:

the system comprises a building module, a block chain service module and a block chain management module, wherein the building module is used for initializing a block chain service on an open source software block chain service platform and deploying an intelligent contract used for transmitting contribution information by each node in a block chain network; the open source software block chain service platform is used as a static access node for other nodes in the area chain network to access the area chain network;

the project creation module is used for receiving a project creation request sent by a project creator client, completing the creation of a corresponding project and generating a corresponding software warehouse;

the system comprises a project developer code cloning and network access module, a block chain network and a software database, wherein the project developer code cloning and network access module is used for receiving a code cloning request sent by each project developer client, copying code information in a software warehouse to each project developer client, and connecting each project developer client which completes code cloning into the block chain network with an open-source software block chain service platform as a static access node;

a project developer code submission and rights and interests confirmation module; the system comprises a code submitting module, a code receiving module, a code submitting module, a code merging module and a software warehouse, wherein the code submitting module is used for receiving and processing a code submitting request of each project developer client and merging codes submitted by each project developer client to the software warehouse corresponding to the open source software block chain service platform; and completing rights and interests distribution according to the contribution code quantity of the project developer, broadcasting the contribution information corresponding to the project developer to other project developer clients in the area chain network, and completing rights and interests confirmation of the contribution information corresponding to the project developer.

Images