A blockchain-based user cooperation method, equipment, and medium

Abstract

Embodiments of the present application provide a user cooperation method and device based on a blockchain, and a medium, which comprises: receiving first cooperation agreement data sent by a first user; performing consensus processing on the first cooperation agreement data in a blockchain network in which a blockchain node device is located, and if the consensus is passed, uploading the first cooperation agreement data to the blockchain network and returning a consensus passing result to the first user; receiving second cooperation agreement data input by a second user in response to the first cooperation agreement data; performing consensus processing on the second cooperation agreement data in the blockchain network, and if the consensus is passed, determining that the first user and the second user have successfully signed a cooperation agreement and uploading the second cooperation agreement data to the blockchain network; and sending a cooperation agreement signing success result to the first user and the second user. The user cooperation method based on the blockchain provided by the embodiments of the present application can transparentize channel sales cooperation, and is helpful to improve the service quality of a channel sales cooperation platform.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a user collaboration method, device and medium based on blockchain. Background Technology

[0002] Currently, various channel sales cooperation platforms store data in a centralized manner. The participants in channel sales cooperation include enterprises and distributors. Enterprises publish channel sales cooperation information through the channel sales cooperation platform, and distributors apply for channel sales cooperation through the same platform. After the cooperation application is successful, the enterprise and the distributor sign a cooperation agreement, and can further sign an order contract and a delivery contract after the cooperation agreement is signed. If the enterprise and the distributor sign paper agreements and contracts, there is a possibility that the data in the agreements and contracts may be lost or tampered with. The agreements and contracts stored on the channel sales cooperation platform are also subject to the possibility of data loss or tampering. Therefore, making the data of the channel sales cooperation platform open and transparent is an urgent problem to be solved. Summary of the Invention

[0003] This application proposes a blockchain-based user collaboration method, device, and medium that makes channel sales collaboration transparent and helps improve the service quality of the channel sales collaboration platform.

[0004] On one hand, embodiments of this application provide a blockchain-based user collaboration method, which is applied to a blockchain node device and includes:

[0005] Receive first cooperation agreement data sent by a first user, the first cooperation agreement data including first agreement information and first signature information;

[0006] The first cooperation agreement data is processed for consensus in the blockchain network where the blockchain node device is located. If the consensus is successful, the first cooperation agreement data is uploaded to the blockchain network and the consensus result is returned to the first user.

[0007] Receive second cooperation agreement data input by the second user in response to the first cooperation agreement data, the second cooperation agreement data including second agreement information and second signature information;

[0008] The second cooperation agreement data is processed for consensus in the blockchain network. If the consensus is successful, it is determined that the first user and the second user have successfully signed the cooperation agreement, and the second cooperation agreement data is uploaded to the blockchain network.

[0009] Send a successful signing result of the cooperation agreement to the first user and the second user.

[0010] On the other hand, embodiments of this application provide a blockchain node device that has the function of implementing the above-described blockchain-based user collaboration method. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes:

[0011] The first receiving unit is configured to receive first cooperation agreement data sent by the first user, wherein the first cooperation agreement data includes first agreement information and first signature information.

[0012] The processing unit is used to perform blockchain consensus on the first cooperation agreement data. If the consensus is successful, it returns the consensus success result to the first user and publishes the first cooperation agreement data.

[0013] The second receiving unit is configured to receive second cooperation agreement data input by the second user in response to the first cooperation agreement data. The second cooperation agreement data includes second agreement information and second signature information.

[0014] The processing unit is also used to perform blockchain consensus on the second cooperation agreement data. If the consensus is successful, the agreement is confirmed to be signed successfully, and the signing result of the agreement is sent to the first user and the second user.

[0015] On the other hand, embodiments of this application provide a blockchain node device, which includes a memory and a processor. The memory stores a set of program code, and the processor calls the program code stored in the memory to execute the operations involved in the aforementioned blockchain-based user collaboration method.

[0016] On the other hand, embodiments of this application provide a computer-readable storage medium for storing computer program instructions for use by a blockchain node device, which includes programs for executing the aforementioned blockchain-based user collaboration method.

[0017] In this embodiment, the blockchain node device first receives first cooperation agreement data sent by a first user. This first cooperation agreement data includes first agreement information and first signature information. Then, consensus processing is performed on the first cooperation agreement data within the blockchain network where the blockchain node device resides. If consensus is successful, the first cooperation agreement data is uploaded to the blockchain network, and a consensus success result is returned to the first user. Next, the device receives second cooperation agreement data input by a second user in response to the first cooperation agreement data. This second cooperation agreement data includes second agreement information and second signature information. Consensus processing is then performed on the second cooperation agreement data within the blockchain network. If consensus is successful, it is determined that the first user and the second user have successfully signed the cooperation agreement, and the second cooperation agreement data is uploaded to the blockchain network. Finally, a successful signing result is sent to both the first user and the second user to ensure that the terms of the agreement are automatically fulfilled. By storing the channel sales cooperation agreements of the first user and the second user on the blockchain, the channel sales cooperation platform can ensure the reliability and validity of the agreement data and prevent data loss. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1a This is a schematic diagram of a blockchain structure provided in an embodiment of this application;

[0020] Figure 1b This is a schematic diagram of a blockchain-based user collaboration system architecture provided in an embodiment of this application;

[0021] Figure 1c This is a schematic diagram of user collaboration interaction based on blockchain provided in the embodiments of this application;

[0022] Figure 2 This is a flowchart illustrating a blockchain-based user collaboration method provided in an embodiment of this application;

[0023] Figure 3 This is a flowchart illustrating another blockchain-based user collaboration method provided in an embodiment of this application;

[0024] Figure 4 This is a flowchart illustrating another blockchain-based user collaboration method provided in an embodiment of this application;

[0025] Figure 5 This is a schematic diagram of the structure of a blockchain node device provided in an embodiment of this application;

[0026] Figure 6 This is a schematic diagram of another blockchain node device provided in an embodiment of this application. Detailed Implementation

[0027] The embodiments of this application are described below with reference to the accompanying drawings.

[0028] Channel sales cooperation refers to the combination and reliance of the same sales strategy among different enterprises. The purpose of cooperation is to seek mutual benefit. In this application, the participants in channel sales cooperation include first users and second users. In specific implementation scenarios, the first user can refer to the enterprise, and the second user can refer to the distributor. The channel sales cooperation platform is referred to as the platform. Enterprises and distributors work together and cooperate to win customer trust, increase market share, and increase sales. Cooperation at different levels within the same sales channel is beneficial to both parties. Currently, various channel sales cooperation platforms suffer from information asymmetry due to centralized data storage and inconsistent platform quality. Furthermore, if the business data provided by the platform is non-standard or falsified, it can also cause damage to the interests of enterprises and distributors. The blockchain-based user cooperation method in this application, based on smart contracts and oracle technology, can provide a trustworthy channel sales cooperation platform. Blockchain is a distributed ledger that maintains a reliable database in a decentralized and trustless manner. A smart contract is a set of agreements defined, propagated, verified, or executed in digital form, including protocols that the contract participants can execute. Smart contracts allow for trusted transactions without third parties, and the executed transactions are traceable and irreversible. Oracles, serving as platforms for providing external information, are themselves a type of smart contract, providing an interactive link between the blockchain and the real world. In this application, the channel sales cooperation platform can upload the identities of enterprises and distributors to the blockchain for storage. Smart contracts enable a closed loop for signing channel sales cooperation agreements, ensuring the execution of the contractual terms, making channel sales transparent, and helping to improve the service quality of the channel sales cooperation platform.

[0029] This application provides a blockchain-based user collaboration method that aims to solve the market sales traps caused by centralized data storage in traditional channel sales cooperation platforms, such as counterfeit brands and hoarding that disrupt market prices. It can also address economic crimes and help the industry develop better. After enterprises complete real-name authentication through the channel sales cooperation platform, their identities are stored on the blockchain. This involves submitting the enterprise's public and private keys, along with relevant enterprise information, to a notary public for authentication, and issuing certificates for the public and private keys to facilitate the later storage of contract signing and delivery data on the blockchain. Similarly, after distributors complete real-name authentication through the channel sales cooperation platform, their identities are stored on the blockchain. This involves submitting the distributor's public and private keys, along with relevant distributor qualification information, to a notary public for authentication, and issuing certificates for the public and private keys to facilitate the later storage of contract signing and order data on the blockchain. Enterprises publish channel sales cooperation bidding information through the channel sales cooperation platform and store it on the blockchain. Distributors participate in bidding for channel sales cooperation through the channel sales cooperation platform and store their bids on the blockchain. Enterprises and distributors sign channel sales cooperation agreements through the channel sales cooperation platform and store the signed agreement on the blockchain in a closed loop. After signing, the smart contract executes tasks according to the terms of the agreement. Distributors store their order data on the blockchain through the channel sales cooperation platform, and enterprises store their delivery data on the blockchain through the channel sales cooperation platform.

[0030] Blockchain is a chain-like data structure that links data blocks sequentially in chronological order, using cryptography to ensure the data's immutability and tamper-proof nature. Multiple independent distributed nodes (i.e., the first blockchain node devices) store the same records. Blockchain technology achieves decentralization, becoming the cornerstone for trusted digital asset storage, transfer, and transactions.

[0031] by Figure 1a Taking the illustrated blockchain structure diagram as an example, whenever new data needs to be written to the blockchain, this data is aggregated into a block and added to the end of the existing blockchain. A consensus algorithm ensures that each node's newly added block is identical. Each block records platform protocol data and / or activity announcement data, and also includes the hash value of the previous block. All blocks are linked sequentially, storing the hash values ​​of the previous blocks, to form the blockchain. The header of the next block in the blockchain stores the hash value of the previous block. When the fingerprint data in the previous block changes, the hash value of this block also changes. Therefore, fingerprint data uploaded to the blockchain network is difficult to tamper with. Transactions between clients and business platforms on the blockchain achieve transparency in the transaction process, improving the reliability of fingerprint data.

[0032] Please see Figure 1b ,like Figure 1bAs shown, the blockchain-based user collaboration system architecture includes a first user device, a second user device, a blockchain node device, and a blockchain network. The first user device can be a device corresponding to an enterprise, the second user device can be a device corresponding to a distributor, and the blockchain node device can be a device corresponding to a channel sales cooperation platform. The first user device, the second user device, and the blockchain node device can be clients or servers, and this embodiment does not limit them. The client can be any of the following: a terminal, a standalone application, an API (Application Programming Interface), or a SDK (Software Development Kit). The terminal can include, but is not limited to, smartphones (such as Android phones, iOS phones, etc.), tablet computers, portable personal computers, mobile internet devices (MIDs), etc., and this embodiment does not limit them.

[0033] This application introduces blockchain technology into the data storage of a channel sales cooperation platform, proposing a blockchain-based user cooperation method applied to blockchain node devices. Please refer to... Figure 1c ,like Figure 1c As shown, the blockchain-based user cooperation method specifically comprises: 101. A blockchain node device receives first cooperation agreement data sent by a first user device. The first cooperation agreement data includes first agreement information and first signature information; 102. The blockchain node device performs consensus processing on the first cooperation agreement data within its blockchain network; 103. If consensus is successful, the first cooperation agreement data is uploaded to the blockchain network; 104. The blockchain node device returns a consensus success result to the first user terminal; 105. The blockchain node device receives second cooperation agreement data input by a second user in response to the first cooperation agreement data. The second cooperation agreement data includes second agreement information and second signature information; 106. The blockchain node device performs consensus processing on the second cooperation agreement data within the blockchain network; 107. If consensus is successful, it is determined that the first user and the second user have successfully signed the cooperation agreement, and the second cooperation agreement data is uploaded to the blockchain network; 108. A successful signing result for the cooperation agreement is sent to the first user device; 109. A successful signing result for the cooperation agreement is sent to the second user device.

[0034] The process for putting channel sales cooperation platform qualifications on the blockchain is as follows:

[0035] The channel sales cooperation platform uploads its qualifications to the blockchain via blockchain node devices. Specifically, the platform generates asymmetric public and private keys locally, signs its identity and service qualification information issued by an authoritative institution using the private key, and then applies for a certificate from a notary public using the public key, platform information, and signature. After the notary public verifies the received certificate, it issues a platform certificate. The platform uploads the certificate to the blockchain through a transaction, and the blockchain verifies the legality of the transaction. Once consensus is reached, the transaction is executed. During transaction execution, a smart contract is invoked to calculate the digest hash of the platform certificate. The digest hash is then used to check if the certificate already exists. If not, the digest hash is used as the key to write the platform certificate into the smart contract. After blockchain consensus is achieved, the results are written to the blockchain ledger, and the upload result and the digest hash of the platform certificate are sent to the notary public. The notary public then returns the platform certificate and its digest hash to the platform, which stores the certificate and digest hash.

[0036] The process for storing enterprise identity on the blockchain is as follows:

[0037] After a company completes real-name authentication through the channel sales cooperation platform, the platform generates an asymmetric private key for the company. The company's identity is then signed using the private key. The public key, company identity information, and company signature are then sent to a notary public to apply for a certificate. Upon receiving the application for real-name authentication, the notary public issues a certificate to the company and uploads the certificate to the blockchain through a transaction. The blockchain verifies the legality of this transaction and, after consensus is reached, calls a smart contract to store the company certificate. First, a digest hash is calculated on the company certificate. Then, the digest hash is used to check if the company certificate already exists. If it does not exist, the digest hash is used as the key to write the company certificate into the smart contract. After blockchain consensus is completed, the certificate is written into the blockchain ledger, and the on-chain result and the company certificate are sent to the notary public. The notary public then returns the company certificate and digest hash to the channel sales cooperation platform. The channel sales cooperation platform stores the company certificate and digest hash and informs the company. The company can choose whether to store the certificate and certificate digest hash locally.

[0038] The process for storing dealer identities on the blockchain is as follows:

[0039] After a distributor completes real-name authentication through the channel sales cooperation platform, the platform generates an asymmetric private key for the distributor. The distributor's identity is then signed using the private key, and the public key, distributor identity information, and distributor signature are sent to a notary public to apply for a certificate. Upon receiving the application for real-name authentication, the notary public issues a distributor certificate and uploads the certificate to the blockchain through a transaction. The blockchain verifies the legality of this transaction and, after consensus is reached, calls a smart contract to store the distributor certificate. First, a digest hash is calculated on the distributor certificate. Then, the digest hash is used to check if the distributor certificate already exists. If not, the digest hash is used as the key to write the distributor certificate into the smart contract. After blockchain consensus is achieved, the certificate is written into the blockchain ledger, and the on-chain result and the distributor certificate are sent to the notary public. The notary public then returns the distributor certificate and digest hash to the channel sales cooperation platform. The channel sales cooperation platform stores the distributor certificate and digest hash and informs the distributor. The distributor can choose whether to store the certificate and certificate digest hash locally.

[0040] The channel sales cooperation platform deploys smart contracts for channel sales cooperation agreements. The specific process is as follows:

[0041] The channel sales cooperation platform deploys a smart contract for channel sales cooperation agreements. Specifically, the platform deploys the smart contract to the blockchain via a transaction. The transaction data includes the smart contract, the platform certificate digest hash, and the public key. After receiving the transaction data, the blockchain verifies the legality of the transaction. If consensus is reached, the transaction data undergoes blockchain consensus and is written into the blockchain ledger. The blockchain then returns the transaction result and the smart contract address to the channel sales cooperation platform, which stores the transaction data, the transaction result, and the smart contract address.

[0042] Enterprises publish channel sales cooperation information through the platform and upload this information to the blockchain. The specific process is as follows:

[0043] Enterprises need to publish channel sales cooperation information through a channel sales cooperation platform and upload this information to the blockchain. Specifically, enterprises use the platform to digitally sign the channel sales cooperation information with their private keys in the form of a transaction and send it to the blockchain. The transaction data includes cooperation information data, enterprise identifier, smart contract address, enterprise certificate digest hash, and public key. The blockchain verifies the legality of the digital signature using the public key and executes the transaction after consensus is reached. It checks whether the smart contract used for signing has been deployed by querying the smart contract address. If so, it calls the smart contract to publish the channel sales cooperation information and generates a digest hash for the channel sales cooperation information data. It checks whether the channel sales cooperation information has already been published by querying the digest hash. If so, it queries the enterprise certificate by querying the enterprise certificate digest hash. If the enterprise certificate is found, it compares the public key in the enterprise certificate with the public key in the transaction data. If they match, it uses the digest hash as the key and writes the channel sales cooperation data and enterprise identifier into the smart contract. The blockchain sends the publication result, digest hash, and transaction hash to the channel sales cooperation platform. The channel sales cooperation platform stores the channel sales cooperation data and the data returned by the blockchain and informs the enterprise.

[0044] Distributors apply for channel sales cooperation through the platform and upload the application information to the blockchain. The specific process is as follows:

[0045] Distributors need to apply for channel sales cooperation through the platform and upload the application information to the blockchain. Specifically, the distributor applies for channel sales cooperation by digitally signing the cooperation application data with their private key in the form of a transaction, and then sending it to the blockchain. The transaction data includes the cooperation application data, channel sales cooperation data digest hash, distributor identifier, smart contract address, distributor certificate digest hash, and public key. The blockchain verifies the legality of the digital signature using the public key and executes the transaction after consensus is reached. It checks whether the smart contract used for signing is deployed through the smart contract address. If so, it calls the smart contract to perform the insurance operation. It checks the distributor certificate through the distributor digest hash. If the distributor certificate is found... The system compares the public key in the queried dealer certificate with the public key in the transaction data. If they match, it generates a digest hash for the cooperation application data and uses this hash as the key to write the channel sales cooperation application data, dealer identifier, and transaction hash into the smart contract. It then uses the channel sales cooperation data digest hash as the key to write the channel sales cooperation application data hash into the corresponding application form. The system performs blockchain consensus on the transaction results and, after consensus is reached, writes the transaction into the blockchain ledger. The blockchain returns the release result of the channel sales cooperation platform application information and the transaction hash. The channel sales cooperation platform stores the channel sales cooperation application data and the data returned by the blockchain, and informs the enterprise and dealer.

[0046] Please see Figure 2 , Figure 2This is a flowchart illustrating a blockchain-based user collaboration method provided in an embodiment of this application. The method is applied to blockchain node devices associated with a channel sales collaboration platform, and includes, but is not limited to, the following steps S201~S205:

[0047] S201. Receive first cooperation agreement data sent by the first user, the first cooperation agreement data including first agreement information and first signature information.

[0048] In this context, "first user" refers to the enterprise, "second user" refers to the distributor, and "channel sales cooperation platform" is referred to as the "platform." After the platform's qualifications, the identities of both users are recorded on the blockchain, the platform deploys a smart contract for signing. The first user can publish channel sales cooperation information through the platform and record this information on the blockchain. The second user can apply for channel sales cooperation through the platform and record their application information on the blockchain. Then, the first and second users can sign a channel sales cooperation agreement through the platform. The first user sends the first cooperation agreement data to the blockchain in the form of a transaction through the platform. After receiving the first cooperation agreement, the blockchain node devices need to perform blockchain consensus on the data. The first cooperation agreement data includes first agreement information and first signature information. The first agreement information may include, for example, the first user identifier, the second user identifier, the smart contract address, the first cooperation agreement, and the agreement number. The first signature information may include, for example, the channel sales cooperation digest hash, the channel sales cooperation application digest hash, the first certificate digest hash, and the public key.

[0049] In specific implementation, the consensus processing of the first cooperation agreement data in the blockchain network where the blockchain node device is located includes: querying whether a smart contract is deployed in the blockchain based on the smart contract address; if so, querying the first certificate based on the first certificate digest hash and checking whether the public key included in the queried first certificate matches the first public key; if so, querying the first cooperation agreement based on the channel sales cooperation digest hash; checking whether the user identifier in the first cooperation agreement matches the first user identifier; if so, querying the channel sales cooperation application data based on the channel sales cooperation application digest hash; when it is determined that the first user is in a signed state based on the channel sales cooperation application data, the consensus of the first cooperation agreement data is determined to be passed, and the first cooperation agreement data and the first user's signed transaction hash are written into the smart contract using the agreement number as the key. The consensus result is written into the blockchain ledger, and the consensus result is returned to the platform, which then returns it to the first user.

[0050] S202. The first cooperation agreement data is processed for consensus in the blockchain network where the blockchain node device is located. If the consensus is successful, the first cooperation agreement data is uploaded to the blockchain network and the consensus result is returned to the first user.

[0051] Once the first cooperation agreement passes consensus on the blockchain network where the blockchain node device is located, the first cooperation agreement data is uploaded to the blockchain network, and the consensus result is returned to the first user. At this time, it indicates that the first user has successfully signed the first cooperation agreement.

[0052] S203. Receive second cooperation agreement data input by the second user in response to the first cooperation agreement data. The second cooperation agreement data includes second agreement information and second signature information.

[0053] The second user inputs second protocol data based on the first cooperation protocol data and sends the second protocol data to the blockchain node device through the platform. After receiving the second cooperation protocol data, the blockchain node device can perform blockchain consensus on the second protocol data, that is, perform consensus processing on the second cooperation protocol data in the blockchain network. The second protocol data includes second protocol information and second signature information. The second protocol information may include, for example, the first user identifier, the second user identifier, the smart contract address, the second cooperation protocol, and the protocol number. The second signature information may include, for example, the channel sales cooperation digest hash, the channel sales cooperation application digest hash, the second certificate digest hash, and the second public key, as well as the first user's contract transaction hash.

[0054] S204. Consensus processing is performed on the second cooperation agreement data in the blockchain network. If the consensus is successful, it is determined that the first user and the second user have successfully signed the cooperation agreement, and the second cooperation agreement data is uploaded to the blockchain network.

[0055] In this process, blockchain node devices reach a consensus on the second cooperation agreement data within the blockchain network. If both consensuses are reached simultaneously, it can be determined that the first and second users have successfully signed the cooperation agreement. The second user can query the content of the cooperation agreement uploaded by the first user on the blockchain using the agreement number to check if it matches the content of the cooperation agreement published on the channel sales cooperation platform. If they match, the distributor digitally signs the channel sales cooperation agreement and sends the second cooperation agreement data to the channel sales cooperation platform in the form of a transaction. The channel sales cooperation platform then uploads the second cooperation agreement to the blockchain.

[0056] In specific implementation, the consensus processing of the second cooperation agreement data in the blockchain network includes: querying whether a smart contract is deployed in the blockchain based on the smart contract address; if so, querying the second certificate based on the second certificate digest hash, and checking whether the public key included in the queried second certificate matches the second public key; if so, searching for the first cooperation agreement stored in the smart contract based on the protocol number; determining whether the first user in the first cooperation agreement has signed up; if so, checking whether the user identifier in the first cooperation agreement and the second user identifier are consistent; if so, checking whether the first cooperation agreement and the second cooperation agreement are consistent; if so, determining that the consensus of the second cooperation agreement data has passed, and updating the content of the first cooperation agreement so that both the first user and the second user in the content of the first cooperation agreement are in a signed state, and simultaneously writing the second user's signed transaction hash into the smart contract. Specifically, the first cooperation agreement data stored in the blockchain can be found through the agreement number. The hash of the first user's signing transaction and the hash of the second user's signing transaction in the first cooperation agreement data are compared. If they are consistent, and the hash of the channel sales cooperation summary and the hash of the channel sales cooperation application summary in the first agreement data are consistent with the hash of the channel sales cooperation summary and the hash of the channel sales cooperation application summary in the second agreement data, the second agreement input is written into the blockchain ledger, and the second user's signing result is sent to the channel sales cooperation platform, which then informs the first user and the second user.

[0057] S205. Send the successful signing result of the cooperation agreement to the first user and the second user.

[0058] In one implementation, the first user needs to publish channel sales cooperation information to the outside world through the platform and upload the channel sales cooperation information to the blockchain. Therefore, the method further includes: receiving first cooperation information data sent by the first user, the first cooperation information data including cooperation information signature and first public key information; performing blockchain consensus on the first cooperation information data according to the first public key information, and publishing the channel sales cooperation information of the first user after the blockchain consensus is passed. The process involves the first user sending first cooperation information data to the blockchain node device through the platform. This data includes a first cooperation information signature and a first public key. The first user signs the first cooperation information with their private key and sends it to the blockchain. The first cooperation information includes channel sales cooperation information data, the first user's identifier, the smart contract address, and the first certificate digest hash. The blockchain node device verifies the first cooperation information signature using its public key. After successful verification, it checks whether a smart contract has been deployed based on the smart contract address. If so, it calls the smart contract to publish the channel sales cooperation information and generates a digest hash based on the channel sales cooperation information data. The digest hash is used to check whether the channel sales cooperation information has already been published. If not, it queries the certificate based on the first certificate digest hash and compares the public key in the queried certificate with the first public key. If they match, the first cooperation information is written into the smart contract using the first certificate digest hash as the key value. When the blockchain consensus notification for the first cooperation information is received, the information is written into the blockchain consensus ledger. The blockchain returns the publication result of the first cooperation information, along with the digest hash and transaction hash, to the platform. The platform stores the data returned by the blockchain and informs the first user.

[0059] In one implementation, the second user needs to apply for cooperation through the platform and upload the application information to the blockchain. Therefore, the method further includes: the second user applies for channel sales cooperation through the platform and signs the cooperation application data with a private key polarity in the form of a transaction. Then, the cooperation application signature and the second public key are sent to the blockchain. The cooperation application data includes a channel sales cooperation data digest hash, a second user identifier, a smart contract address, and a second certificate digest hash. After receiving the second cooperation information data, the cooperation application signature is verified by public key verification. After the verification is passed, it is checked whether the signed smart contract has been deployed according to the smart contract address. If so, the smart contract is invoked. The bidding process is initiated, and the certificate is queried using the second certificate digest hash. The queried certificate is compared with the second certificate in the second cooperation information. If they are the same, the cooperation information is queried using the channel sales cooperation digest hash. If found, a digest hash is generated based on the cooperation application data, and the cooperation application data is written into the cooperation application form using the cooperation application digest hash as the key. The cooperation result is then subject to blockchain consensus, and after consensus is passed, the cooperation result is written into the blockchain ledger. The blockchain returns the release result of the channel sales cooperation application information and the transaction hash to the platform. The platform stores the channel sales cooperation application data and the data returned by the blockchain, and informs the first user and the second user.

[0060] This application proposes a blockchain-based user collaboration method. This method is applied to blockchain node devices associated with a channel sales collaboration platform. The blockchain node device first receives first collaboration agreement data sent by a first user. This first collaboration agreement data includes first agreement information and first signature information. Then, consensus processing is performed on the first collaboration agreement data within the blockchain network where the blockchain node device resides. If consensus is successful, the first collaboration agreement data is uploaded to the blockchain network, and a consensus success result is returned to the first user. Next, the method receives second collaboration agreement data input by a second user in response to the first collaboration agreement data. This second collaboration agreement data includes second agreement information and second signature information. Consensus processing is then performed on the second collaboration agreement data within the blockchain network. If consensus is successful, it is determined that the first user and the second user have successfully signed the collaboration agreement, and the second collaboration agreement data is uploaded to the blockchain network. Finally, a successful signing result is sent to both the first user and the second user to ensure that the terms of the agreement can be automatically fulfilled. Adding blockchain technology makes the entire channel sales process transparent, and channel sales collaboration information can be queried through the blockchain, solving potential data security issues in the channel sales industry and contributing to the better development of the industry.

[0061] Please see Figure 3 , Figure 3This is a flowchart illustrating another blockchain-based user collaboration method provided in this application embodiment. The method is applied to a blockchain node device and includes, but is not limited to, the following steps S301~S309:

[0062] S301. Receive first cooperation agreement data sent by the first user, wherein the first cooperation agreement data includes first agreement information and first signature information.

[0063] S302. The first cooperation agreement data is processed for consensus in the blockchain network where the blockchain node device is located. If the consensus is successful, the first cooperation agreement data is uploaded to the blockchain network and the consensus result is returned to the first user.

[0064] S303. Receive second cooperation agreement data input by the second user in response to the first cooperation agreement data. The second cooperation agreement data includes second agreement information and second signature information.

[0065] S304. Consensus processing is performed on the second cooperation agreement data in the blockchain network. If the consensus is successful, it is determined that the first user and the second user have successfully signed the cooperation agreement, and the second cooperation agreement data is uploaded to the blockchain network.

[0066] S305. Send the successful signing result of the cooperation agreement to the first user and the second user.

[0067] Specifically, steps S301-S305 can be found in [reference needed]. Figure 2 Steps S201-S205 in the process.

[0068] S306. Receive the first transaction data sent by the first user, wherein the first transaction data includes a first user identifier, a second user identifier, order contract data, and third signature information.

[0069] In this process, the first user sends the first transaction data to the blockchain in the form of a transaction. The first transaction data includes the first user identifier, the second user identifier, the order contract data, and the third signature. The third signature includes the smart contract address, the protocol number, the first certificate digest hash, and the public key.

[0070] S307. Perform blockchain consensus on the first transaction data, and publish the first transaction data after the consensus is passed.

[0071] Upon receiving the first transaction data, a blockchain consensus is established. This includes querying the blockchain to see if a smart contract has been deployed using the smart contract address. If so, the certificate is queried using the first certificate digest hash, and the public key in the queried certificate is compared with the public key in the first transaction data. If so, the channel sales cooperation data is found using the protocol number, and the first user identifier in the channel sales cooperation data is checked against the first user identifier in the first transaction data. If they match, the second user identifier in the channel sales cooperation data is further checked against the second user identifier in the first transaction data. If they match, the order contract data and the first user's signed transaction hash are added to the order list using the protocol number as the key, and then written into the smart contract.

[0072] S308. Receive second transaction data sent by the second user, the second transaction data including a first user identifier, a second user identifier and fourth signature information.

[0073] The second user signs the order contract and sends the second transaction data in the form of a transaction. The blockchain node device receives the second transaction data sent by the second user. The second transaction data includes the first user identifier, the second user identifier, and the fourth signature information. The fourth signature information includes the smart contract address, protocol number, the hash of the first user's signed transaction, and the second certificate and public key information.

[0074] S309. Perform blockchain consensus on the second transaction data. If the consensus is successful, update the order contract data and send the updated order contract data to the first user and the second user.

[0075] During the blockchain consensus process, it is necessary to verify whether the order contract data sent by the first user is consistent with the order contract data published by the platform. If they are consistent, the second user can sign the order contract, and the contract becomes effective after the second user signs the order contract.

[0076] This application proposes a blockchain-based user collaboration method. This method is applied to blockchain node devices associated with a channel sales collaboration platform. The blockchain node device first receives first collaboration agreement data sent by a first user. This first collaboration agreement data includes first agreement information and first signature information. Then, consensus processing is performed on the first collaboration agreement data within the blockchain network where the blockchain node device resides. If consensus is successful, the first collaboration agreement data is uploaded to the blockchain network, and a consensus success result is returned to the first user. Next, the method receives second collaboration agreement data input by a second user in response to the first collaboration agreement data. This second collaboration agreement data includes second agreement information and second signature information. Consensus processing is then performed on the second collaboration agreement data within the blockchain network. If consensus is successful, it is determined that the first user and the second user have successfully signed the collaboration agreement, and the second collaboration agreement data is uploaded to the blockchain network. Finally, a successful signing result is sent to both the first user and the second user to ensure that the terms of the agreement can be automatically fulfilled. Adding blockchain technology makes the entire channel sales process transparent, and channel sales collaboration information can be queried through the blockchain, solving potential data security issues in the channel sales industry and contributing to the better development of the industry.

[0077] Please see Figure 4 , Figure 4 This is a flowchart illustrating another blockchain-based user collaboration method provided in this application embodiment. The method is applied to a blockchain node device and includes, but is not limited to, the following steps S401~S409:

[0078] S401. Receive first cooperation agreement data sent by the first user, wherein the first cooperation agreement data includes first agreement information and first signature information.

[0079] S402. The first cooperation agreement data is processed for consensus in the blockchain network where the blockchain node device is located. If the consensus is successful, the first cooperation agreement data is uploaded to the blockchain network and the consensus result is returned to the first user.

[0080] S403. Receive second cooperation agreement data input by the second user in response to the first cooperation agreement data. The second cooperation agreement data includes second agreement information and second signature information.

[0081] S404. Consensus processing is performed on the second cooperation agreement data in the blockchain network. If the consensus is successful, it is determined that the first user and the second user have successfully signed the cooperation agreement, and the second cooperation agreement data is uploaded to the blockchain network.

[0082] S405. Send the successful signing result of the cooperation agreement to the first user and the second user.

[0083] Specifically, steps S401-S405 can be found in [reference needed]. Figure 2 Steps S201-S205 in the process.

[0084] S406. Receive the third transaction data sent by the first user, wherein the third transaction data includes the first user identifier, the second user identifier, the delivery contract data, and the fifth signature information.

[0085] The first user sends the third transaction data to the blockchain in the form of a transaction through the platform. The third transaction data includes the first user's identifier, the second user's identifier, the delivery contract data, and the fifth signature information, which includes the smart contract address, the protocol number, the first certificate digest hash, and the public key.

[0086] S407. Perform blockchain consensus on the third transaction data, and publish the third transaction data after the consensus is passed.

[0087] Upon receiving the third transaction data, a blockchain consensus is reached on the third transaction data, and the data is written into the blockchain ledger after the consensus is passed. Specifically, the process is as follows: The system queries the blockchain to see if a smart contract has been deployed based on the smart contract address. If so, it queries the certificate based on the first certificate digest hash and checks if the public key included in the queried certificate matches the public key in the third transaction data. If so, it queries the channel sales cooperation data using the protocol number and checks if the first user identifier in the channel sales cooperation data matches the first user identifier in the third transaction data. If so, it checks if the second user identifier in the channel sales cooperation data matches the second user identifier in the third transaction data. If so, the system writes the third transaction data into the blockchain ledger using the protocol number as the key and returns the transaction result to the platform, which then informs both the first and second users. The second user can find the delivery contract using the protocol number and can further compare the content of the delivery contract published by the first user on the platform with the content of the delivery contract in the blockchain. If they match, the second user can choose whether to sign the delivery contract and thus execute the terms of the delivery contract.

[0088] S408. Receive the fourth transaction data sent by the second user, the fourth transaction data including the first user identifier, the second user identifier and the sixth signature information.

[0089] When the second user confirms the signing of the delivery contract, the fourth transaction data can be sent to the blockchain through the platform in the form of a transaction. The fourth transaction data includes the first user identifier, the second user identifier, and the sixth signature information. The sixth signature information includes the smart contract address, protocol number, second certificate digest hash, and public key.

[0090] S409. Perform blockchain consensus on the fourth transaction data. If the consensus is successful, update the delivery contract data and send the updated delivery contract data to the first user and the second user.

[0091] This application proposes a blockchain-based user collaboration method. This method is applied to blockchain node devices associated with a channel sales collaboration platform. The blockchain node device first receives first collaboration agreement data sent by a first user. This first collaboration agreement data includes first agreement information and first signature information. Then, consensus processing is performed on the first collaboration agreement data within the blockchain network where the blockchain node device resides. If consensus is successful, the first collaboration agreement data is uploaded to the blockchain network, and a consensus success result is returned to the first user. Next, the method receives second collaboration agreement data input by a second user in response to the first collaboration agreement data. This second collaboration agreement data includes second agreement information and second signature information. Consensus processing is then performed on the second collaboration agreement data within the blockchain network. If consensus is successful, it is determined that the first user and the second user have successfully signed the collaboration agreement, and the second collaboration agreement data is uploaded to the blockchain network. Finally, a successful signing result is sent to both the first user and the second user to ensure that the terms of the agreement can be automatically fulfilled. Adding blockchain technology makes the entire channel sales process transparent, and channel sales collaboration information can be queried through the blockchain, solving potential data security issues in the channel sales industry and contributing to the better development of the industry.

[0092] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of a blockchain node device provided in an embodiment of this application. The blockchain node device is used to execute... Figures 2-4 The steps performed by the first blockchain node device in the corresponding method embodiment include: one or more processors 501; one or more input devices 502; one or more output devices 503; and a memory 504. The processors 501, input devices 502, output devices 503, and memory 504 are connected via a bus 505. The memory 502 stores a computer program, which includes program instructions. The processors 501, input devices 502, and output devices 503 execute the program instructions stored in the memory 504 to perform the following operations:

[0093] Input device 502 receives first cooperation agreement data sent by a first user, the first cooperation agreement data including first agreement information and first signature information;

[0094] The processor 501 performs consensus processing on the first cooperation agreement data in the blockchain network where the blockchain node device is located. If the consensus is successful, the first cooperation agreement data is uploaded to the blockchain network and the consensus result is returned to the first user.

[0095] Input device 502 receives second cooperation agreement data input by a second user in response to the first cooperation agreement data. The second cooperation agreement data includes second agreement information and second signature information.

[0096] The processor 501 performs consensus processing on the second cooperation agreement data in the blockchain network. If the consensus is passed, it determines that the first user and the second user have successfully signed the cooperation agreement, and uploads the second cooperation agreement data to the blockchain network.

[0097] Output device 503 sends a successful signing result of the cooperation agreement to the first user and the second user.

[0098] In one implementation, the processor 501 performs consensus processing on the first cooperation agreement data within the blockchain network where the blockchain node device resides, including:

[0099] Query whether a smart contract is deployed in the blockchain based on the smart contract address;

[0100] If so, query the first certificate based on the first certificate digest hash, and check whether the public key included in the queried first certificate matches the first public key;

[0101] If so, query the first cooperation agreement based on the hash of the channel sales cooperation summary;

[0102] Detect whether the user identifier in the first cooperation agreement is consistent with the first user identifier;

[0103] If so, query the channel sales cooperation application data based on the hash of the channel sales cooperation application summary;

[0104] When the first user is determined to be in a contracted state based on the channel sales cooperation application data, the consensus of the first cooperation agreement data is determined to be passed, and the first cooperation agreement data and the first user's contracted transaction hash are written into the smart contract using the agreement number as the key.

[0105] In one implementation, the processor 501 performs consensus processing on the second cooperation agreement data in the blockchain network, including:

[0106] Query whether a smart contract is deployed in the blockchain based on the smart contract address;

[0107] If so, query the second certificate based on the second certificate digest hash, and check whether the public key included in the queried second certificate matches the second public key;

[0108] If so, locate the first cooperation agreement stored in the smart contract based on the protocol number;

[0109] Determine whether the first user in the first cooperation agreement has signed the contract;

[0110] If so, check whether the user identifier in the first cooperation agreement and the second user identifier are consistent;

[0111] If so, check whether the first cooperation agreement and the second cooperation agreement are consistent;

[0112] If so, the consensus on the second cooperation agreement is confirmed, and the content of the first cooperation agreement is updated so that both the first user and the second user in the first cooperation agreement are in a signed state. At the same time, the hash of the second user's signed transaction is written into the smart contract.

[0113] In one implementation, the processor 501 further includes: receiving first transaction data sent by the first user, wherein the first transaction data includes a first user identifier, a second user identifier, order contract data, and third signature information;

[0114] A blockchain consensus is reached on the first transaction data, and the first transaction data is published after the consensus is passed.

[0115] Receive second transaction data sent by the second user, the second transaction data including a first user identifier, a second user identifier, and fourth signature information;

[0116] A blockchain consensus is reached on the second transaction data. If the consensus is successful, the order contract data is updated, and the updated order contract data is sent to the first user and the second user.

[0117] In one implementation, the processor 501 further includes: receiving third transaction data sent by the first user, wherein the third transaction data includes a first user identifier, a second user identifier, delivery contract data, and fifth signature information;

[0118] A blockchain consensus is reached on the third transaction data, and the third transaction data is published after the consensus is passed.

[0119] Receive fourth transaction data sent by the second user, the fourth transaction data including a first user identifier, a second user identifier, and a sixth signature information;

[0120] A blockchain consensus is reached on the fourth transaction data. If the consensus is successful, the delivery contract data is updated, and the updated delivery contract data is sent to the first user and the second user.

[0121] In one implementation, the processor 501 further includes: receiving first cooperation information data sent by the first user, wherein the first cooperation information data includes a cooperation information signature and first public key information;

[0122] Based on the first public key information, a blockchain consensus is reached on the first cooperation information data, and the channel sales cooperation information of the first user is released after the blockchain consensus is passed.

[0123] In one implementation, processor 501 further includes:

[0124] Receive second cooperation information data sent by the second user in response to the first cooperation information data, wherein the second cooperation information data includes a cooperation application signature and second public key information;

[0125] Based on the second public key information, a blockchain consensus is reached on the second cooperation information data, and after the blockchain consensus is passed, the hash of the second user's channel sales cooperation application data is written into the smart contract;

[0126] The channel sales cooperation application result of the second user is published, and the channel sales cooperation application result is sent to the first user and the second user.

[0127] Please see Figure 6 , Figure 6 This is a schematic diagram of the structure of a blockchain node device provided in an embodiment of this application. The blockchain node device is used to execute... Figures 2-4 The steps performed by the first blockchain node device in the corresponding method embodiment may include:

[0128] The first receiving unit 601 is configured to receive first cooperation agreement data sent by the first user, wherein the first cooperation agreement data includes first agreement information and first signature information.

[0129] The processing unit 602 is used to perform blockchain consensus on the first cooperation agreement data. If the consensus is successful, it returns the consensus success result to the first user and publishes the first cooperation agreement data.

[0130] The second receiving unit 603 is used to receive second cooperation agreement data input by the second user in response to the first cooperation agreement data. The second cooperation agreement data includes second agreement information and second signature information.

[0131] The processing unit 602 is also used to perform blockchain consensus on the second cooperation agreement data. If the consensus is successful, the agreement is confirmed to be signed successfully, and the signing result of the agreement is sent to the first user and the second user.

[0132] In one implementation, when the first cooperation agreement data is processed in the blockchain network where the blockchain node device is located, the processing unit 602 further includes:

[0133] Query whether a smart contract is deployed in the blockchain based on the smart contract address;

[0134] If so, query the first certificate based on the first certificate digest hash, and check whether the public key included in the queried first certificate matches the first public key;

[0135] If so, query the first cooperation agreement based on the hash of the channel sales cooperation summary;

[0136] Detect whether the user identifier in the first cooperation agreement is consistent with the first user identifier;

[0137] If so, query the channel sales cooperation application data based on the hash of the channel sales cooperation application summary;

[0138] When the first user is determined to be in a contracted state based on the channel sales cooperation application data, the consensus of the first cooperation agreement data is determined to be passed, and the first cooperation agreement data and the first user's contracted transaction hash are written into the smart contract using the agreement number as the key.

[0139] In one implementation, when the second cooperation agreement data is processed for consensus in the blockchain network, the processing unit 602 further includes:

[0140] Query whether a smart contract is deployed in the blockchain based on the smart contract address;

[0141] If so, query the second certificate based on the second certificate digest hash, and check whether the public key included in the queried second certificate matches the second public key;

[0142] If so, locate the first cooperation agreement stored in the smart contract based on the protocol number;

[0143] Determine whether the first user in the first cooperation agreement has signed the contract;

[0144] If so, check whether the user identifier in the first cooperation agreement and the second user identifier are consistent;

[0145] If so, check whether the first cooperation agreement and the second cooperation agreement are consistent;

[0146] If so, the consensus on the second cooperation agreement is confirmed, and the content of the first cooperation agreement is updated so that both the first user and the second user in the first cooperation agreement are in a signed state. At the same time, the hash of the second user's signed transaction is written into the smart contract.

[0147] In one implementation, the processing unit 602 further includes:

[0148] Receive first transaction data sent by the first user, the first transaction data including a first user identifier, a second user identifier, order contract data and third signature information;

[0149] A blockchain consensus is reached on the first transaction data, and the first transaction data is published after the consensus is passed.

[0150] Receive second transaction data sent by the second user, the second transaction data including a first user identifier, a second user identifier, and fourth signature information;

[0151] A blockchain consensus is reached on the second transaction data. If the consensus is successful, the order contract data is updated, and the updated order contract data is sent to the first user and the second user.

[0152] In one implementation, the processing unit 602 further includes:

[0153] Receive third transaction data sent by the first user, the third transaction data including the first user identifier, the second user identifier, the delivery contract data and the fifth signature information;

[0154] A blockchain consensus is reached on the third transaction data, and the third transaction data is published after the consensus is passed.

[0155] Receive fourth transaction data sent by the second user, the fourth transaction data including a first user identifier, a second user identifier, and a sixth signature information;

[0156] A blockchain consensus is reached on the fourth transaction data. If the consensus is successful, the delivery contract data is updated, and the updated delivery contract data is sent to the first user and the second user.

[0157] In one implementation, the processing unit 602 further includes:

[0158] Receive the first cooperation information data sent by the first user, wherein the first cooperation information data includes a cooperation information signature and a first public key information;

[0159] Based on the first public key information, a blockchain consensus is reached on the first cooperation information data, and the channel sales cooperation information of the first user is released after the blockchain consensus is passed.

[0160] In one implementation, the processing unit 602 further includes:

[0161] Receive second cooperation information data sent by the second user in response to the first cooperation information data, wherein the second cooperation information data includes a cooperation application signature and second public key information;

[0162] Based on the second public key information, a blockchain consensus is reached on the second cooperation information data, and after the blockchain consensus is passed, the hash of the second user's channel sales cooperation application data is written into the smart contract;

[0163] The channel sales cooperation application result of the second user is published, and the channel sales cooperation application result is sent to the first user and the second user.

[0164] This application also provides a computer-readable storage medium storing a computer program, the computer program including program instructions, which, when executed by a processor, can perform the steps described in the above embodiments.

[0165] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0166] The above-disclosed embodiments are merely some of the embodiments of this application, and should not be construed as limiting the scope of this application. Those skilled in the art can understand that implementing all or part of the above embodiments and making equivalent changes in accordance with the claims of this application still fall within the scope of the invention.

Claims

1. A blockchain-based user collaboration method, characterized in that, The method includes: Receive first cooperation agreement data sent by the first user. The first cooperation agreement data includes first agreement information and first signature information. The first agreement information includes: smart contract address, first user identifier, second user identifier, first cooperation agreement and agreement number. Consensus processing is performed on the first cooperation agreement data in the blockchain network where the blockchain node device is located, including: verifying whether the corresponding smart contract has been deployed on the blockchain based on the smart contract address, verifying the identity information and signing authority of the first user based on the first signature information, verifying the validity of the first cooperation agreement, and confirming that the first user is qualified to sign. If the consensus is passed, the first cooperation agreement data is uploaded to the blockchain network, and the consensus result is returned to the first user; Receive second cooperation agreement data input by the second user in response to the first cooperation agreement data. The second cooperation agreement data includes second agreement information and second signature information. The second agreement information includes smart contract address, first user identifier, second user identifier, second cooperation agreement, and agreement number. Consensus processing is performed on the second cooperation agreement data in the blockchain network, including: verifying whether the corresponding smart contract has been deployed on the blockchain according to the smart contract address, verifying the identity information and signing permission of the second user according to the second signature information, searching for the first cooperation agreement in the smart contract according to the protocol number, confirming the signing status of the first user, and verifying the consistency between the first cooperation agreement and the second cooperation agreement. If the consensus is reached, it is determined that the first user and the second user have successfully signed the cooperation agreement, the status of the cooperation agreement is updated to "signed by both parties", and the data of the second cooperation agreement is uploaded to the blockchain network; Send a successful signing result of the cooperation agreement to the first user and the second user.

2. The method according to claim 1, characterized in that, The first cooperation agreement data includes a smart contract address, a first user identifier, a second user identifier, a first cooperation agreement, an agreement number, a channel sales cooperation digest hash, a channel sales cooperation application digest hash, a first certificate digest hash, and a first public key; The consensus processing of the first cooperation agreement data in the blockchain network where the blockchain node device is located includes: Query whether a smart contract is deployed in the blockchain based on the smart contract address; If so, query the first certificate based on the first certificate digest hash, and check whether the public key included in the queried first certificate matches the first public key; If so, query the first cooperation agreement based on the hash of the channel sales cooperation summary; Detect whether the user identifier in the first cooperation agreement is consistent with the first user identifier; If so, query the channel sales cooperation application data based on the hash of the channel sales cooperation application summary; When the first user is determined to be in a contracted state based on the channel sales cooperation application data, the consensus of the first cooperation agreement data is determined to be passed, and the first cooperation agreement data and the first user's contracted transaction hash are written into the smart contract using the agreement number as the key.

3. The method according to claim 1 or 2, characterized in that, The second cooperation agreement data includes a smart contract address, a first user identifier, a second user identifier, a second cooperation agreement, an agreement number, a channel sales cooperation digest hash, a channel sales cooperation application digest hash, a second certificate digest hash, and a second public key; The consensus processing of the second cooperation agreement data in the blockchain network includes: Query whether a smart contract is deployed in the blockchain based on the smart contract address; If so, query the second certificate based on the second certificate digest hash, and check whether the public key included in the queried second certificate matches the second public key; If so, locate the first cooperation agreement stored in the smart contract based on the protocol number; Determine whether the first user in the first cooperation agreement has signed the contract; If so, check whether the user identifier in the first cooperation agreement and the second user identifier are consistent; If so, check whether the first cooperation agreement and the second cooperation agreement are consistent; If so, the consensus on the second cooperation agreement is confirmed, and the content of the first cooperation agreement is updated so that both the first user and the second user in the first cooperation agreement are in a signed state. At the same time, the hash of the second user's signed transaction is written into the smart contract.

4. The method according to claim 1 or 2, characterized in that, The method further includes: Receive first transaction data sent by the first user, the first transaction data including a first user identifier, a second user identifier, order contract data and third signature information; A blockchain consensus is reached on the first transaction data, and the first transaction data is published after the consensus is passed. Receive second transaction data sent by the second user, the second transaction data including a first user identifier, a second user identifier, and fourth signature information; A blockchain consensus is reached on the second transaction data. If the consensus is successful, the order contract data is updated, and the updated order contract data is sent to the first user and the second user.

5. The method according to claim 4, characterized in that, The method further includes: Receive third transaction data sent by the first user, the third transaction data including the first user identifier, the second user identifier, the delivery contract data and the fifth signature information; A blockchain consensus is reached on the third transaction data, and the third transaction data is published after the consensus is passed. Receive fourth transaction data sent by the second user, the fourth transaction data including a first user identifier, a second user identifier, and a sixth signature information; A blockchain consensus is reached on the fourth transaction data. If the consensus is successful, the delivery contract data is updated, and the updated delivery contract data is sent to the first user and the second user.

6. The method according to claim 1, characterized in that, The method further includes: Receive the first cooperation information data sent by the first user, wherein the first cooperation information data includes a cooperation information signature and a first public key information; Based on the first public key information, a blockchain consensus is reached on the first cooperation information data, and the channel sales cooperation information of the first user is released after the blockchain consensus is passed.

7. The method according to claim 6, characterized in that, The method further includes: Receive second cooperation information data sent by the second user in response to the first cooperation information data, wherein the second cooperation information data includes a cooperation application signature and second public key information; Based on the second public key information, a blockchain consensus is reached on the second cooperation information data, and after the blockchain consensus is passed, the hash of the second user's channel sales cooperation application data is written into the smart contract; The channel sales cooperation application result of the second user is published, and the channel sales cooperation application result is sent to the first user and the second user.

8. A blockchain-based user collaboration device, characterized in that, include: The first receiving unit is configured to receive first cooperation agreement data sent by the first user. The first cooperation agreement data includes first agreement information and first signature information. The first agreement information includes: smart contract address, first user identifier, second user identifier, first cooperation agreement, and agreement number. The processing unit is used to perform blockchain consensus on the first cooperation agreement data. If the consensus is successful, it returns the consensus success result to the first user and publishes the first cooperation agreement data. Regarding the blockchain consensus on the first cooperation agreement data, the processing unit is specifically used to verify whether the corresponding smart contract has been deployed on the blockchain based on the smart contract address, to verify the identity information and signing authority of the first user based on the first signature information, to verify the validity of the first cooperation agreement, and to confirm that the first user is qualified to sign. The second receiving unit is used to receive second cooperation agreement data input by the second user in response to the first cooperation agreement data. The second cooperation agreement data includes second agreement information and second signature information. The second agreement information includes a smart contract address, a first user identifier, a second user identifier, a second cooperation agreement, and an agreement number. The processing unit is also used to perform blockchain consensus on the second cooperation agreement data. If the consensus is successful, the agreement is confirmed to be signed successfully, the cooperation agreement status is updated to be signed by both parties, and the signing result of the agreement is sent to the first user and the second user. Regarding the blockchain consensus on the second cooperation agreement data, the processing unit is specifically used to verify whether the corresponding smart contract has been deployed on the blockchain based on the smart contract address, verify the identity information and signing authority of the second user based on the second signature information, search for the first cooperation agreement in the smart contract based on the agreement number, confirm the signing status of the first user, and verify the consistency between the first cooperation agreement and the second cooperation agreement.

9. A blockchain node device, characterized in that, The system includes a processor, an input device, an output device, and a memory, which are interconnected. The memory stores a computer program, which includes program instructions. The processor is configured to invoke the program instructions to execute the blockchain-based user collaboration method as described in any one of claims 1-7.

10. A computer storage medium, characterized in that, The computer storage medium stores computer program instructions adapted for loading and execution by a processor of the blockchain-based user collaboration method as described in any one of claims 1-7.

Images