Blockchain-based change request method and device, request processing method and device, equipment, medium and program product

Abstract

This disclosure provides a blockchain-based change request method, applicable to the fields of blockchain technology, information security technology, big data technology, and fintech technology. The blockchain-based change request method includes: initiating a change request to multiple central nodes when a change to the rights of a first target user node is proposed; and broadcasting a rights verification request to a blockchain consortium network in response to a notification from the central nodes confirming the change consensus. The rights verification request requests a predetermined number of nodes in the blockchain consortium network to verify and confirm the change in rights. These multiple nodes include multiple central nodes, multiple first-type user nodes, and multiple second-type user nodes. This disclosure also provides a blockchain-based change request apparatus, device, storage medium, and program product.

Description

Technical Field

[0001] This disclosure relates to the fields of blockchain technology, information security technology, big data technology, and financial technology, and specifically to a blockchain-based change request method and apparatus, request processing method and apparatus, equipment, medium, and program product. Background Technology

[0002] Online discounts are an important promotional method for merchants and platforms. Existing online discounts come in various forms and have complex rules. Ordinary consumers often cannot obtain comprehensive and accurate discount information in a timely manner when making purchases on merchants or platforms, ultimately failing to enjoy the true benefits. This results in promotional activities not reaching ordinary consumers. Therefore, utilizing blockchain technology for discount information sharing has become a technological trend.

[0003] In realizing the concept disclosed herein, the inventors discovered at least the following problems in the relevant technologies: Currently, most blockchain-based processing methods only involve the sharing of merchant discount information, with a single data interaction processing method, which cannot meet the needs of more complex discount scenarios. Furthermore, because blockchain networks involve a large number of nodes, consensus processing requires significant computing power and network resources, and the processing time is long, failing to meet the demands of online real-time processing. Summary of the Invention

[0004] In view of the above problems, this disclosure provides a blockchain-based change request method and apparatus, request processing method and apparatus, device, medium and program product.

[0005] One aspect of this disclosure provides a blockchain-based change request method, comprising: initiating a change request to multiple central nodes when a change is to be made to the equity of a first target user node, wherein the change request is used to request the multiple central nodes to reach a consensus confirmation on the change in equity, and the first target user node belongs to either a first type of user node or a second type of user node; and broadcasting a change verification request to a blockchain consortium network in response to a notification from the central nodes confirming the change in equity, wherein the change verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the change in equity, and the multiple nodes in the blockchain consortium network include multiple central nodes, multiple first type of user nodes, and multiple second type of user nodes.

[0006] According to embodiments of this disclosure, each user node in the first and second categories corresponds to a user rights record chain, and multiple first blocks in the user rights record chain are used to record the changes in the rights of each user node; each second category user node also corresponds to an activity project record chain, and multiple second blocks in the activity project record chain are used to record the changes in the activity projects of each second category user node; each central node corresponds to a platform rights record chain and a transaction status record chain, and multiple third blocks in the platform rights record chain are used to record the changes in the rights of multiple first and second category user nodes in the blockchain consortium network, and multiple fourth blocks in the transaction status record chain are used to record the order transaction status of multiple first and second category user nodes in the blockchain consortium network.

[0007] According to embodiments of this disclosure, the data stored in the block body of the first block includes at least: the type of equity change, the quantity of equity change, and the address of the first target verification node actively participating in the verification of equity change in the blockchain consortium network; the data stored in the block body of the second block includes at least: the identifier of the changed activity project, the type of equity change triggered by the activity project change, the quantity of equity change triggered by the activity project change, the transaction deduction value corresponding to the activity project, and the address of the second target verification node actively participating in the verification of the activity project change in the blockchain consortium network; the data stored in the block body of the third block includes at least: the type of equity change, the quantity of equity change, the address of the user node where the equity change occurred, and the address of the first central node that performs change consensus confirmation during the change consensus confirmation process; the data stored in the block body of the fourth block includes at least: the identifier of the transaction order, the actual transaction payment value, the address of the user node that initiated the transaction, the quantity of equity consumed by the first type of user node in the transaction, the identifier of the preferred activity project published by the second type of user and used by the first type of user node in the transaction, and the quantity of equity deduction corresponding to the preferred activity project.

[0008] According to an embodiment of this disclosure, in response to a notification from a first target verification node in the blockchain consortium network that has actively participated in verifying changes in rights, a node rights change record is generated; the node rights change record is packaged to generate a first block, and the newly generated first block is uploaded to the user rights record chain corresponding to the first target user node.

[0009] According to embodiments of this disclosure, when the first target user node belongs to a first type of user node, the change in the rights and interests of the first target user node is triggered by the first target user node actively recharging or consuming rights and interests; when the first target user node belongs to a second type of user node, the change in the rights and interests of the first target user node is triggered by the first target user node actively recharging or being recharged with rights and interests, or the change in the rights and interests of the first target user node is triggered by a change in the activity items of the first target user node.

[0010] According to embodiments of this disclosure, when the first target user node belongs to the second type of user node, and the change in the rights and interests of the first target user node is triggered by a change in the activity item of the first target user node, the method further includes: broadcasting a project verification request to the blockchain consortium network, wherein the project verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the change in the activity item of the first target user node; generating an activity item change record in response to a notification from a second target verification node in the blockchain consortium network that has actively participated in the verification of the activity item change; packaging the activity item change record to generate a second block, and uploading the newly generated second block to the activity item record chain corresponding to the first target user node.

[0011] According to embodiments of this disclosure, when the first target user node belongs to a first type of user node and the first target user node intends to initiate a transaction, the method further includes: querying the activity item changes in the target second block located at the tail of the activity item record chain; generating a preferred transaction combination strategy by running a smart contract based on the activity item changes in the target second block, the preferred transaction combination strategy indicating the recommended amount of equity consumption to be executed in the transaction, and information on preferred activity items among multiple activity items published by the second type of user; generating a transaction confirmation request based on the preferred transaction combination strategy; and sending the corresponding transaction confirmation request to multiple central nodes so that the multiple central nodes can perform transaction consensus confirmation on the transaction to be initiated by the first target user node.

[0012] One aspect of this disclosure provides a blockchain-based request processing method, comprising: responding to a rights change request from a first target user node whose rights are to be changed, performing a rights change consensus confirmation on the rights change of the first target user node, wherein the first target user node belongs to a first type of user node or a second type of user node; if the rights change consensus confirmation is passed, sending a notification of successful rights change consensus confirmation to the first target user node, so that the first target user node, in response to the notification of successful rights change consensus confirmation, broadcasts a rights verification request to a blockchain consortium network, wherein the rights verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the rights change, and the multiple nodes in the blockchain consortium network include multiple central nodes, multiple first type of user nodes, and multiple second type of user nodes.

[0013] According to embodiments of this disclosure, the aforementioned blockchain-based request processing further includes: generating a first platform rights change record based on the result of the change consensus confirmation when the change consensus is confirmed; packaging the first platform rights change record to generate a third block; and uploading the newly generated third block to the platform rights record chain corresponding to each central node.

[0014] According to an embodiment of this disclosure, when the first target user node belongs to a first type of user node and the first target user node intends to initiate a transaction, the method further includes: responding to a transaction confirmation request from the first target user node and performing transaction consensus confirmation on the transaction to be initiated by the first target user node.

[0015] According to the embodiments of this disclosure, when the transaction consensus is confirmed, a transaction confirmation record is generated based on the result of the transaction consensus confirmation; the transaction confirmation record is packaged to generate a fourth block, and the newly generated fourth block is uploaded to the transaction status record chain corresponding to each central node.

[0016] According to embodiments of this disclosure, in response to a rights reward request from a first target verification node that actively participates in the verification of rights changes in the blockchain consortium network, a consensus confirmation of the verification status of the first target verification node is performed; if the consensus confirmation of the verification status is passed, a notification of the consensus confirmation of the verification status is sent to the first target verification node, so that the first target verification node performs rights changes based on the notification of the consensus confirmation of the verification status.

[0017] According to embodiments of this disclosure, consensus confirmation of the verification status of the first target verification node includes: obtaining the rights change information of the first target user node from the user rights record chain of the first target user node, wherein the rights change information includes the address information of the first target verification node; and confirming the verification status of the first target verification node based on the rights change information of the first target user node.

[0018] According to the embodiments of this disclosure, if the verification consensus is passed, a second platform rights change record is generated based on the verification consensus result; the second platform rights change record is packaged to generate a third block, and the newly generated third block is uploaded to the platform rights record chain corresponding to each central node.

[0019] Another aspect of this disclosure provides a blockchain-based change request apparatus, comprising: a request module, configured to initiate a change request to multiple central nodes when a change is to be made to the rights of a first target user node, wherein the change request is used to request the multiple central nodes to reach a consensus confirmation on the change in rights, and the first target user node is a first type of user node or a second type of user node; and a first broadcast module, configured to broadcast a change verification request to a blockchain consortium network in response to a notification from the central nodes that the change consensus confirmation has been passed, wherein the change verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the change in rights, and the multiple nodes in the blockchain consortium network include multiple central nodes, multiple first type of user nodes, and multiple second type of user nodes.

[0020] Another aspect of this disclosure provides a blockchain-based request processing apparatus, comprising: a change consensus confirmation module, configured to, in response to a change request from a first target user node whose rights are to be changed, confirm the change consensus of the first target user node, wherein the first target user node belongs to a first type of user node or a second type of user node; and a second sending module, configured to, upon successful change consensus confirmation, send a notification of successful change consensus confirmation to the first target user node, thereby enabling the first target user node to, in response to the notification of successful change consensus confirmation, broadcast a rights verification request to a blockchain consortium network, wherein the rights verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the change in rights, wherein the multiple nodes in the blockchain consortium network include multiple central nodes, multiple first type user nodes, and multiple second type user nodes.

[0021] Another aspect of this disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0022] Another aspect of this disclosure provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0023] Another aspect of this disclosure provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0024] According to the blockchain-based change request method, apparatus, device, medium, and program products provided in this disclosure, by having a central node confirm the change through consensus rather than all nodes, the authenticity of the change request can be confirmed, data security can be enhanced, blockchain consortium network congestion can be reduced, and consensus efficiency can be improved. After the central node's change consensus confirmation is passed, any node in the blockchain consortium network can further verify and confirm the change of interests, which can further confirm the authenticity of the change request and fully mobilize the enthusiasm of other nodes to participate in the consensus. Attached Figure Description

[0025] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0026] Figure 1 The illustration schematically depicts an application scenario of a blockchain-based change request method, apparatus, device, medium, and program product according to embodiments of this disclosure;

[0027] Figure 2 A flowchart illustrating a blockchain-based change request method according to an embodiment of this disclosure is shown schematically.

[0028] Figure 3 A schematic diagram illustrating a system principle of a blockchain-based change request method according to an embodiment of the present disclosure is provided.

[0029] Figure 4 The schematic diagram illustrates the structure of the first block according to an embodiment of the present disclosure;

[0030] Figure 5 A schematic diagram of the block body of the first block according to an embodiment of the present disclosure is shown;

[0031] Figure 6 A schematic diagram illustrating the structure of the second block according to an embodiment of the present disclosure is shown.

[0032] Figure 7 A schematic diagram of the block body of the second block according to an embodiment of the present disclosure is shown;

[0033] Figure 8 A schematic diagram illustrating the structure of the third block according to an embodiment of the present disclosure is shown.

[0034] Figure 9 A schematic diagram of the block body of the third block according to an embodiment of the present disclosure is shown;

[0035] Figure 10 A schematic diagram illustrating the structure of the fourth block according to an embodiment of the present disclosure is shown.

[0036] Figure 11 A schematic diagram of the block body of the fourth block according to an embodiment of the present disclosure is shown;

[0037] Figure 12 A flowchart illustrating a blockchain-based request processing method according to an embodiment of the present disclosure is shown schematically.

[0038] Figure 13 A schematic block diagram of a blockchain-based change request device according to an embodiment of the present disclosure is shown.

[0039] Figure 14 A schematic block diagram of a blockchain-based request processing apparatus according to an embodiment of the present disclosure is shown.

[0040] Figure 15 A block diagram schematically illustrates an electronic device suitable for implementing a blockchain-based change request method and a blockchain-based request processing method according to embodiments of the present disclosure. Detailed Implementation

[0041] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0042] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0043] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0044] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0045] In the technical solution disclosed herein, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding operation entry points are provided for users to choose to authorize or refuse.

[0046] In scenarios involving automated decision-making using personal information, the methods, devices, and systems provided in this disclosure all offer users corresponding entry points for choosing to agree to or reject the automated decision-making results. If the user chooses to reject, the process proceeds to the expert decision-making stage. Here, "automated decision-making" refers to the activity of automatically analyzing and evaluating an individual's behavioral habits, interests, or economic, health, and credit status through computer programs, and then making a decision. Here, "expert decision-making" refers to the activity of making decisions by personnel who specialize in a particular field, possess specialized experience, knowledge, and skills, and have reached a certain level of professional expertise.

[0047] The acquisition, transmission, storage, use, and processing of data in this disclosed technical solution all comply with relevant laws and regulations. It should also be noted that certain software, components, models, and other existing industry solutions may be mentioned in the embodiments of this disclosure. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solution of this disclosure, and do not imply that the applicant has already used or necessarily used the relevant content of that solution.

[0048] It should be noted that the blockchain-based change request method, apparatus, electronic device, and medium of this disclosure can be applied to the fields of blockchain technology, information security technology, big data technology, and financial technology, and can also be used in any field other than blockchain technology, information security technology, big data technology, and financial technology. The embodiments of this disclosure do not limit the application fields of the above-mentioned blockchain-based change request method, apparatus, electronic device, and medium.

[0049] The embodiments of this disclosure provide a blockchain-based change request method, comprising: initiating a change request for equity to multiple central nodes when a change is to be made to the equity of a first target user node, wherein the change request is used to request the multiple central nodes to reach a consensus confirmation on the change in equity, and the first target user node belongs to a first type of user node or a second type of user node; in response to a notification from the central nodes that the change consensus confirmation has been passed, broadcasting a change verification request to a blockchain consortium network, wherein the change verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the change in equity, and the multiple nodes in the blockchain consortium network include multiple central nodes, multiple first type of user nodes, and multiple second type of user nodes.

[0050] Figure 1 The illustration depicts an application scenario of a blockchain-based change request method, apparatus, device, medium, and program product according to embodiments of this disclosure.

[0051] like Figure 1 As shown, application scenario 100 according to this embodiment may include a blockchain consortium network, which includes a first type of user node 101, a second type of user node 102, and a central node 103. The central node 103 is a relatively stable and trustworthy node in the network, for example, it may be a second type of user node elected by voting, or it may be a node other than the first type of user node and the second type of user node.

[0052] In the scenario of this disclosure embodiment, the first type of user node 101 and the second type of user node 102 can participate in one or more activities. Users can pre-purchase benefits on the platform. The benefits of the first type of user node 101 can be used as a discount amount when participating in activities; the benefits of the second type of user node 102 can be used to carry out or change activities. The discount amount supported by the benefits is not a fixed percentage and can be dynamically adjusted according to the actual situation.

[0053] When a promotional activity is launched or changed, the rights and interests of the user nodes of the second type of user node 102 will change accordingly; when the rights and interests of the first type of user node 101 are used as the discount amount when participating in the activity, the rights and interests of the user nodes corresponding to the first type of user node 101 and the second type of user node 102 will both change accordingly.

[0054] The activity could be a promotional event. When both user node 101 (type 1) and user node 102 participate in the promotion, user node 101 can be the consumer's corresponding node in the blockchain consortium network. User node 102 can be the merchant's corresponding node in the blockchain consortium network. For example:

[0055] For merchants: Merchants can create new promotional activities. When a merchant creates a new promotion, they need to set the rules for the current promotion, such as the number of benefits that can be used per order and the corresponding discount amount. Promotional data can be broadcast to the blockchain consortium network for consumers to participate in. The discount rules for promotional activities can be agreed upon through smart contracts.

[0056] Merchants need to have rights to create promotional activities, and the number of rights a merchant has needs to be sufficient to maintain the promotional activities. Therefore, when a merchant creates a new promotional activity, the system needs to freeze the existing rights of the merchant's corresponding second-type user node 102. The frozen rights cannot be changed temporarily to ensure that the number of rights is sufficient to maintain the promotional activities.

[0057] Merchants can also change the number of promotional activities: when a merchant increases promotional activities, the rights and interests of the corresponding second-type user node 102 will be frozen; when a merchant reduces promotional activities, the rights and interests of the corresponding second-type user node 102 will be unfrozen, and the unfrozen rights and interests can be changed. For example, if a merchant reduces promotional activities, the number of rights and interests should also be reduced accordingly. Therefore, it is necessary to unfreeze the rights and interests of the corresponding second-type user node 102 and deduct the number of rights and interests corresponding to the reduced promotional activities.

[0058] For consumers: When a consumer places an order, the corresponding first-type user node 101 can automatically check the latest promotional information from the merchant. After the consumer uses the discount, the discount amount corresponding to the benefits set in the current promotion will be automatically deducted. Accordingly, the number of benefits for the first-type user node 101 will decrease, while the number of benefits for the second-type user node 102 will increase.

[0059] When the rights and interests of the first type of user node 101 and the second type of user node 102 change, the corresponding first type of user node 101 and second type of user node 102 can initiate a rights change request to multiple central nodes 103. After the central node 103 verifies the rights change request, it can send the rights change request to other nodes in the blockchain consortium network for verification.

[0060] It should be understood that Figure 1 The number of the first type of user node 101, the second type of user node 102, and the central node 103 shown in the diagram is merely illustrative. The number of the first type of user node 101, the second type of user node 102, and the central node 103 can be adjusted according to implementation needs.

[0061] The following will be based on Figure 1 The described scene, through Figures 2 to 11The blockchain-based change request method according to embodiments of this disclosure will be described in detail.

[0062] Figure 2 A flowchart illustrating a blockchain-based change request method according to an embodiment of this disclosure is shown schematically.

[0063] like Figure 2 As shown, the blockchain-based change request in this embodiment includes operations S210 to S220, and the blockchain-based change request method can be executed by a first type of user node or a second type of user node.

[0064] In operation S210, when it is proposed to change the rights of the first target user node, a rights change request is initiated to multiple central nodes. The rights change request is used to request multiple central nodes to reach a consensus on the rights change. The first target user node belongs to either the first type of user node or the second type of user node.

[0065] In operation S220, in response to the notification from the central node that the change consensus has been confirmed, a stake verification request is broadcast to the blockchain consortium network. The stake verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the stake change. The multiple nodes in the blockchain consortium network include multiple central nodes, multiple first-type user nodes, and multiple second-type user nodes.

[0066] In embodiments of this disclosure, user consent or authorization must be obtained before obtaining user information. For example, a request to obtain user information must be sent to the user before operation S210. Operation S210 is performed if the user consents or authorizes the acquisition of user information.

[0067] According to embodiments of this disclosure, the rights and interests of user nodes are used to offset a certain amount of consumption during the transaction process, such as coupons, discount coupons, and deductions.

[0068] In operation S210, the first target user node can belong to either a first-type user node or a second-type user node. The first-type user node 101 can be the node corresponding to the consumer in the blockchain consortium network. The second-type user node 102 can be the node corresponding to the merchant in the blockchain consortium network. For example: Because merchant A has launched a new activity, user A's rights need to be changed (the merchant needs to consume certain rights value to launch the activity). User node corresponding to user A can be used as the first target user node to initiate a rights change request to multiple central nodes. For example: Because consumer B needs to purchase items from a merchant and uses some of their rights (such as coupons) during the payment stage, consumer B's rights need to be changed. User node corresponding to consumer B can be used as the first target user node to initiate a rights change request to multiple central nodes.

[0069] Upon receiving a request for a change of rights, multiple central nodes can conduct consensus confirmation of the request to verify its authenticity.

[0070] According to embodiments of this disclosure, in operation S220, if the consensus confirmation of the change at the central node is successful, the first target user node can broadcast the rights verification request to the blockchain consortium network. A small number of nodes in the blockchain consortium network can verify and confirm the rights change to reconfirm the authenticity of the rights change request. If the verification is successful, the rights of the first target user node can be changed. According to embodiments of this disclosure, on the one hand, existing blockchain consensus confirmation methods mostly rely on consensus among all nodes in the blockchain consortium network, which may lead to processing delays and congestion in the blockchain consortium network. In this disclosure, since the central node is a relatively stable and trustworthy node in the network, consensus confirmation through the central node rather than all nodes in the blockchain can effectively confirm the authenticity of the rights change request, enhance data security, reduce network congestion, ensure the stable operation of the blockchain consortium network, and improve consensus efficiency.

[0071] On the other hand, once the central node's consensus on the change of rights is confirmed, a small number of nodes in the blockchain consortium network can further verify and confirm the change of rights, thereby further confirming the authenticity of the request and improving data security and information authenticity. Simultaneously, it can fully mobilize other nodes to participate in the consensus, indirectly achieving consensus across the entire network based on the fundamental principle of blockchain verification consensus. Furthermore, having only a small number of nodes verify and confirm the change of rights further avoids processing delays and blockchain consortium network congestion. Moreover, blockchain technology enables the recording, verification, and sharing of changes in rights between the transacting parties (consumers and merchants), making it adaptable to more complex transaction scenarios.

[0072] According to embodiments of this disclosure, each user node in the first type of user node and the second type of user node corresponds to a user rights record chain, and multiple first blocks in the user rights record chain are used to record the changes in the rights of each user node.

[0073] Each second-type user node also corresponds to an activity project record chain, and multiple second blocks in the activity project record chain are used to record the changes in the activity projects of each second-type user node.

[0074] Each central node corresponds to a platform rights record chain and a transaction record chain. Multiple third blocks in the platform rights record chain are used to record the rights changes of multiple first-class user nodes and multiple second-class user nodes in the blockchain consortium network. Multiple fourth blocks in the transaction record chain are used to record the order transaction information of multiple first-class user nodes and multiple second-class user nodes in the blockchain consortium network.

[0075] Figure 3 A schematic diagram of a system principle for a blockchain-based change request method according to an embodiment of the present disclosure is shown.

[0076] like Figure 3 As shown, each user node corresponds to a user rights record chain 301, the second type of user node also corresponds to an activity project record chain 302, each central node corresponds to a platform rights record chain 303, and a transaction record chain 304.

[0077] According to embodiments of this disclosure, after a first-type user node completes registration and login on the platform, the backend system generates the address and encryption key of the first-type user node. Each first-type user node has its own exclusive user rights record chain.

[0078] After registering and logging in on the platform, the backend system will generate the address and encryption key for each second-type user node. Correspondingly, each second-type user node also has its own exclusive user rights record chain.

[0079] Multiple first blocks in the user rights record chain can record the changes in the rights of each user node.

[0080] For example, when consumer A participates in a promotional activity organized by a merchant, they need to deduct 100 benefits. Therefore, the user node corresponding to consumer A needs to lose 100 benefits. Correspondingly, the deducted 100 benefits will be credited to the user node corresponding to the merchant, thus increasing the user node's benefits by 100. At this time, multiple first blocks in the user benefit record chain corresponding to consumer A can record the decrease of 100 benefits for the user node corresponding to consumer A; multiple first blocks in the user benefit record chain corresponding to the merchant can record the increase of 100 benefits for the user node corresponding to the merchant.

[0081] According to embodiments of this disclosure, users corresponding to the second type of user node can adjust activity items, such as launching new activity items, changing the discount rules of existing activity items, or adding or removing activity items. In this case, multiple second blocks in the activity item record chain corresponding to the second type of user node can record the changes to the activity items.

[0082] According to embodiments of this disclosure, changes in the rights and interests of each user node are recorded not only in the user rights and interests record chain but also in the platform rights and interests record chain.

[0083] Specifically, when a user node initiates a stake change request to multiple central nodes, and the central nodes confirm the change through consensus, the central nodes can generate a stake change record and synchronize it to the platform's stake record chain. Subsequently, when any node in the blockchain consortium network verifies and confirms the stake change, the node used for verification can query the stake change record from the platform's stake record chain, match the record with the stake change request, and thus verify and confirm the stake change request.

[0084] According to embodiments of this disclosure, multiple fourth blocks in the transaction record chain can record order transaction information of multiple first-type user nodes and multiple second-type user nodes in the blockchain consortium network. Order transaction information may include order information and transaction information. Order information may include product name, quantity, etc.; transaction information may include transaction amount, etc.

[0085] For example, when a consumer places an order and makes payment, the corresponding user node automatically queries the latest promotional information from the merchant. After the consumer participates in the promotion, the user node can automatically deduct the corresponding discount amount for the benefits set in the current promotion, generate order information and transaction information, and generate pending accounting data based on the order information and transaction information. The user node can send the pending accounting data to the central node. If the central node confirms that the pending accounting data is valid and the actual payment amount is not zero, the deduction can be completed, and the corresponding benefits of the merchant can be unfrozen. At the same time, the central node will store the pending accounting data in the transaction record chain and notify the user nodes to verify their respective benefits. At this time, the user node can generate a benefit verification request and broadcast the benefit verification request to the blockchain consortium network. After receiving the benefit verification request, any node in the blockchain consortium network can query the relevant pending accounting data from the transaction record chain, verify the benefit verification request based on the pending accounting data, and after confirmation, verify the user's benefits.

[0086] According to embodiments of this disclosure, different functional chains are set up for various nodes in the blockchain network based on their respective functions. Applied to complex transaction scenarios, this enables the categorized storage and management of various transaction-related information. This facilitates both parties in the transaction and the verifying user to obtain the information they need from different functional chains, achieving multi-dimensional sharing and categorized management of transaction information. Based on the user rights record chain, activity project record chain, platform rights record chain, and transaction status record chain, the decentralized, tamper-proof, and traceable characteristics of blockchain can be fully utilized to completely and truthfully record changes in rights, transactions, and activities, facilitating the tracking of information related to each promotional activity.

[0087] Figure 4 The schematic diagram illustrates the structure of the first block according to an embodiment of the present disclosure.

[0088] like Figure 4 As shown, the first block may include a block header and a block body. The block header may be used to store the parent block hash, the current block hash, the sequence number, the timestamp, and the block body hash.

[0089] Figure 5 A schematic diagram of the block body of the first block according to an embodiment of the present disclosure is shown.

[0090] like Figure 5As shown, the data stored in the block body of the first block includes at least: the type of stake change, the number of stake changes, and the address of the first target verification node actively participating in the verification of stake changes in the blockchain consortium network. It may also include the user node's public key, private key, and digital signature. The user node's public and private keys can be assigned by the system. The digital signature is used to verify the authenticity of the data stored in the current block.

[0091] Types of changes in rights and interests can include top-up, write-off, freezing, and unfreezing, and different types of changes in rights and interests can be represented by different numbers.

[0092] The meaning of the data stored in the first block is shown in Table 1.

[0093] Table 1

[0094] Fields illustrate Number of equity changes Number of rights corresponding to the request for change of rights Types of Changes in Equity Recharge: 0; Redemption: 1; Frozen: 2; Unfrozen: 3 The address of the first target verification node Address of nodes that actively participate in the verification of changes in rights and interests Timestamp Timestamp of the most recent change in rights

[0095] Figure 6 A schematic diagram of the structure of the second block according to an embodiment of the present disclosure is shown.

[0096] like Figure 6 As shown, the second block may include a block header and a block body. The block header may be used to store the parent block hash, the current block hash, the sequence number, the timestamp, and the block body hash.

[0097] Figure 7 A schematic diagram of the block body of the second block according to an embodiment of the present disclosure is shown.

[0098] like Figure 7 As shown, the data stored in the block body of the second block includes at least: the identifier of the changed activity project, the type of equity change triggered by the activity project change, the quantity of equity change triggered by the activity project change, the transaction deduction value corresponding to the activity project, and the address of the second target verification node actively participating in the verification of the activity project change in the blockchain consortium network. It may also include the public key, private key, and digital signature of the second user node. The public and private keys of the second user node can be assigned by the system. The digital signature is used to verify the authenticity of the data stored in the current block.

[0099] Changes to the rights and interests triggered by changes in the activity items can include additions, increases, decreases, and no change, and different types of rights and interests changes can be represented by different numbers.

[0100] The meaning of the data stored in the second block is shown in Table 2.

[0101] Table 2

[0102]

[0103] Figure 8A schematic diagram of the structure of the third block according to an embodiment of the present disclosure is shown.

[0104] like Figure 8 As shown, the third block can include a block header and a block body. The block header can be used to store the parent block hash, the current block hash, the sequence number, the timestamp, and the block body hash.

[0105] Figure 9 A schematic diagram of the block body of the third block according to an embodiment of the present disclosure is shown.

[0106] like Figure 9 As shown, the data stored in the block body of the third block includes at least: the type of stake change, the number of stake changes, the address of the user node where the stake change occurred, and the address of the central node that first confirms the stake change consensus during the consensus confirmation process. It may also include the central node's public key, private key, digital signature, etc. The central node's public key and private key can be assigned by the system.

[0107] The meaning of the data stored in the third block is shown in Table 3.

[0108] Table 3

[0109]

[0110] Figure 10 A schematic diagram of the structure of the fourth block according to an embodiment of the present disclosure is shown.

[0111] like Figure 10 As shown, the fourth block can include a block header and a block body. The block header can be used to store the parent block hash, the current block hash, the sequence number, the timestamp, and the block body hash.

[0112] Figure 11 A schematic diagram of the block body of the fourth block according to an embodiment of the present disclosure is shown.

[0113] like Figure 11 As shown, the data stored in the block body of the fourth block includes at least: the identifier of the transaction order, the actual transaction payment value, the address of the user node that initiated the transaction, the amount of rights consumed by the first type of user node in the transaction, the identifier of the preferred activity item published by the second type of user and used by the first type of user node in the transaction, and the amount of rights deducted corresponding to the preferred activity item. It may also include the public key, private key, digital signature, etc. of the central node. The meaning of the data stored in the fourth block is shown in Table 4.

[0114] Table 4

[0115]

[0116] According to embodiments of this disclosure, the method further includes: generating a node equity change record in response to a notification from a first target verification node in the blockchain consortium network that has passed verification; packaging the node equity change record to generate a first block; and uploading the newly generated first block to the user equity record chain corresponding to the first target user node.

[0117] According to embodiments of this disclosure, after the verification node confirms the change in equity, it can generate a notification of verification success and broadcast the notification to the blockchain consortium network. Upon receiving this notification, the first target user node can generate a record of the change in node equity.

[0118] Node equity change records can be used to record changes in the equity of the first target user node. For example, after a first user node deducts 100 equity, a node equity change record can be generated, and the node equity change record can be packaged into the first block. The newly generated first block is then uploaded to the user equity record chain corresponding to the first target user node.

[0119] According to the embodiments of this disclosure, after the consensus confirmation of the central node in the first stage, the final change of rights can only be achieved after verification by the participating nodes in the second stage, thereby improving the authenticity and security of data.

[0120] According to embodiments of this disclosure, when the first target user node belongs to the first type of user node, the change in the rights and interests of the first target user node is triggered by the first target user node actively recharging or consuming rights and interests.

[0121] If the first target user node belongs to the second type of user node, the change in the rights and interests of the first target user node is triggered by the first target user node actively recharging its rights and interests or by being recharged with rights and interests, or the change in the rights and interests of the first target user node is triggered by the change in the activity items of the first target user node.

[0122] For example, the activity is a promotional event. Consumers, corresponding to the first type of user node, can actively recharge on the platform to obtain benefits. When a consumer places an order, the amount of their benefits will also change (the change in benefits is triggered by the consumption benefits).

[0123] When a consumer places an order, the number of benefits for the merchant's corresponding second-type user node also changes (i.e., the change in benefits for the first target user node is triggered by the recharge of benefits). Furthermore, second-type user nodes can actively recharge on the platform to obtain benefits, and can also create or modify activity items; in these cases, the benefits of the merchant's corresponding user node will also change accordingly. Therefore, the change in benefits for the first target user node can be caused by the first target user node actively recharging benefits or being triggered by recharged benefits, or it can be caused by a change in the first target user node's activity items.

[0124] According to embodiments of this disclosure, specifically, when the first target user node belongs to the second type of user node, and the change in the rights and interests of the first target user node is triggered by a change in the activity items of the first target user node, the above method further includes:

[0125] Operation 11: Broadcast the project verification request to the blockchain consortium network. The project verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the changes in the active projects of the first target user node.

[0126] Operation 12: In response to the notification of successful verification from the second target verification node in the blockchain consortium network that actively participated in the verification of the activity project change, generate an activity project change record.

[0127] Operation 13: Package the activity project change records into a second block and upload the newly generated second block to the activity project record chain corresponding to the first target user node.

[0128] According to embodiments of this disclosure, in operation 11, changing an activity item may include creating or changing an activity item, and changing an activity item may include increasing or decreasing the number of activity items.

[0129] After a user creates or changes an activity project, the user node corresponding to that user can generate a project verification request and broadcast the project verification request to the blockchain consortium network.

[0130] According to embodiments of this disclosure, in operation 12, upon receiving a project verification request, any node in the blockchain consortium network can verify the project verification request. After successful verification, the first target user node can generate an activity project change record. The activity project change record can be used to record information about changes to the activity project, such as the number of changes in equity, the changed activity project identifier, etc.

[0131] According to an embodiment of this disclosure, in operation 13, after generating the activity item change record, the activity item change record can be uploaded to the activity item record chain corresponding to the first target user node, so that the activity item change record can be queried in real time and the activity item change status can be obtained based on the activity item change record.

[0132] According to embodiments of this disclosure, when the first target user node belongs to a first type of user node and the first target user node intends to initiate a transaction, the above method further includes:

[0133] Operation 21: Query the changes of the activity items in the target second block located at the end of the activity item record chain.

[0134] Operation 22: Based on the changes in the active items in the target second block, generate a preferred transaction combination strategy by running a smart contract. The preferred transaction combination strategy is used to indicate the amount of equity consumption recommended to be executed in the transaction, as well as the information of the preferred active items among the multiple active items published by the second type of user.

[0135] Operation 23: Generate a transaction confirmation request based on the optimal transaction combination strategy.

[0136] Operation 24: Send transaction confirmation requests to multiple central nodes so that the multiple central nodes can reach a consensus on the transaction to be initiated by the first target user node.

[0137] According to an embodiment of this disclosure, in operation 21, by querying the changes in activity items, the latest activity item corresponding to the transaction that the first target user node intends to initiate can be obtained.

[0138] According to embodiments of this disclosure, in operation 22, merchants or consumer platforms often organize multiple promotional activities, and the rules for each activity may differ. Furthermore, a single transaction may participate in multiple promotional activities simultaneously. The degree of discount enjoyed by a transaction order may vary depending on the combination of these activities.

[0139] Given the complexity of promotional activity rules, allowing consumers to choose their own combinations of activities may not yield the maximum benefits. Therefore, smart contracts can be used to automatically generate optimal trading combination strategies.

[0140] Based on the optimal transaction combination strategy, it is possible to obtain the combination of promotional activities that can maximize the discount for the current transaction order, as well as the amount of benefits to be deducted (i.e., the amount of benefits consumed) for the combination of the above-mentioned activity items. The information on the optimal activity items among multiple activity items published by the second type of user can include the combination of activity items that maximize the discount for the current transaction order, as well as the identifiers of each activity item, etc.

[0141] According to embodiments of this disclosure, in operation 23, after generating the preferred transaction combination strategy, a transaction confirmation request can be generated based on the preferred transaction combination strategy. The transaction confirmation request may include the amount of equity to be deducted in the transaction, the actual amount paid, etc.

[0142] According to embodiments of this disclosure, in operation 24, the first type of user node can send transaction confirmation requests to multiple central nodes. After the central nodes confirm the transaction confirmation request through transaction consensus, the transaction can be completed.

[0143] According to embodiments of this disclosure, when a consumer initiates a transaction, a preferred transaction combination strategy is generated by running a smart contract, making it easier for the consumer to accurately obtain the best offer information and improving the user experience. Since the transaction stage requires transaction consensus, transaction security can be improved.

[0144] Figure 12 A flowchart illustrating a blockchain-based request processing method according to an embodiment of this disclosure is shown.

[0145] like Figure 12 As shown, the blockchain-based request processing in this embodiment includes operations S1210 to S1220, and this blockchain-based request processing method can be executed by a central node.

[0146] In operation S1210, in response to the rights change request from the first target user node whose rights are to be changed, a consensus confirmation is made on the rights change of the first target user node, wherein the first target user node belongs to the first type of user node or the second type of user node.

[0147] In operation S1220, if the change consensus is confirmed, a notification of the change consensus is sent to the first target user node, so that the first target user node responds to the notification of the change consensus and broadcasts the stake verification request to the blockchain consortium network. The stake verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the stake change. The multiple nodes in the blockchain consortium network include multiple central nodes, multiple first-type user nodes, and multiple second-type user nodes.

[0148] For example, when user node A's stake value needs to be changed, it can generate a stake change request and send it to the central node. Upon receiving the stake change request from user node A, the central node can perform a consensus confirmation process to verify the authenticity of the request. After the consensus confirmation is successful, the central node can send a notification of successful consensus confirmation to user node A and broadcast it to other central nodes to synchronize data.

[0149] After receiving the notification that the above-mentioned change consensus has been approved, user node A can broadcast the rights verification request to the blockchain consortium network, requesting any node in the blockchain consortium network to verify the rights verification request.

[0150] According to the embodiments of this disclosure, since the central node is a relatively stable and trustworthy node in the network, consensus confirmation through the central node rather than all nodes in the blockchain can effectively confirm the authenticity of the stake change request, enhance data security, reduce network congestion, ensure the stable operation of the blockchain consortium network, and improve consensus efficiency. After the central node's consensus confirmation of the change is successful, a small number of nodes in the blockchain consortium network can further verify and confirm the stake change request, thereby further confirming its authenticity and fully mobilizing the enthusiasm of other nodes to participate in the consensus. Furthermore, having only a small number of nodes re-verify and confirm the stake change further avoids processing delays and blockchain consortium network congestion.

[0151] Furthermore, blockchain technology enables the recording, verification, and sharing of changes in the rights and interests of both parties in a transaction (consumers and merchants), making it adaptable to more complex transaction scenarios.

[0152] According to the embodiments of this disclosure, when the change consensus is confirmed, a first platform rights change record is generated based on the result of the change consensus confirmation; the first platform rights change record is packaged to generate a third block, and the newly generated third block is uploaded to the platform rights record chain corresponding to each central node.

[0153] According to embodiments of this disclosure, the first platform rights change record can be used to record the rights changes of the first target user node.

[0154] For example, the central node confirms the change of rights request through consensus, and after the consensus confirmation is passed, it can generate the first platform rights change record. The central node can package the first platform rights change record to generate a third block, and upload the newly generated third block to the platform rights record chain corresponding to each central node.

[0155] Upon receiving a rights verification request, any node in the blockchain consortium network can obtain the first platform's rights change record through the platform's rights record chain and verify the rights verification request based on the first platform's rights change record. If the rights verification request matches the first platform's rights change record, the verification confirms that the rights verification request has passed.

[0156] According to an embodiment of this disclosure, when the first target user node belongs to a first type of user node and the first target user node intends to initiate a transaction, the method further includes: responding to a transaction confirmation request from the first target user node and performing transaction consensus confirmation on the transaction to be initiated by the first target user node.

[0157] According to embodiments of this disclosure, a transaction confirmation request may include the amount of equity to be deducted from the transaction to be initiated by the first target user node, the transaction payment value, etc. The first target user node may send transaction confirmation requests to multiple central nodes. After the central nodes confirm the transaction confirmation request through transaction consensus, the first target user node can complete the transaction.

[0158] According to the embodiments of this disclosure, when the transaction consensus is confirmed, a transaction confirmation record is generated based on the result of the transaction consensus confirmation; the transaction confirmation record is packaged to generate a fourth block, and the newly generated fourth block is uploaded to the transaction status record chain corresponding to each central node.

[0159] According to embodiments of this disclosure, after transaction consensus is confirmed, the central node can generate a transaction confirmation record based on the result of the transaction consensus confirmation. The transaction confirmation record may include: the identifier of the transaction order, the actual transaction payment value, the address of the user node that initiated the transaction, the amount of rights consumed by the first type of user node in the transaction, the identifier of the preferred activity item published by the second type of user and used by the first type of user node in the transaction, and the amount of rights deducted corresponding to the preferred activity item, etc.

[0160] According to embodiments of this disclosure, in response to a rights reward request from a first target verification node that actively participates in the verification of rights changes in the blockchain consortium network, a consensus confirmation of the verification status of the first target verification node is performed; if the consensus confirmation of the verification status is passed, a notification of the consensus confirmation of the verification status is sent to the first target verification node, so that the first target verification node performs rights changes based on the notification of the consensus confirmation of the verification status.

[0161] According to embodiments of this disclosure, the first target verification node may be a node that actively participates in the verification of changes in rights and interests.

[0162] To fully motivate all nodes to actively participate in the verification of changes in rights and interests, rewards can be given to nodes other than the central node that actively participate in the verification of changes in rights and interests, such as increasing their rights and interests.

[0163] The first target verification node can proactively submit a reward request to the central node. The central node can conduct consensus confirmation on the verification status of the first target verification node, such as confirming whether the node that issued the reward request is indeed eligible for the reward and whether the requested reward amount is correct. If the verification status is confirmed through consensus, the first target verification node can receive the reward, increasing its reward amount.

[0164] According to embodiments of this disclosure, by rewarding nodes that actively participate in verifying changes in rights and interests, the enthusiasm of blockchain nodes to participate in consensus can be fully mobilized, maintaining the normal operation of the blockchain consensus mechanism. Specifically, according to embodiments of this disclosure, the consensus confirmation of the verification status of the first target verification node includes: obtaining the rights and interests change information of the first target user node from the user rights and interests record chain of the first target user node, wherein the rights and interests change information includes the address information of the first target verification node; and, based on the rights and interests change information of the first target user node, performing consensus confirmation of the verification status of the first target verification node.

[0165] Since the first block of the user rights record chain stores the addresses of verification nodes that actively participate in verifying changes in rights within the blockchain consortium network, the central node can obtain the addresses of these verification nodes from the user rights record chain and match them with the address of the first target verification node that initiated the rights reward request.

[0166] According to the embodiments of this disclosure, if the verification consensus is passed, a second platform rights change record is generated based on the verification consensus result; the second platform rights change record is packaged to generate a third block, and the newly generated third block is uploaded to the platform rights record chain corresponding to each central node.

[0167] According to embodiments of this disclosure, if the address of the verification node actively participating in the verification of changes in rights and interests is consistent with the address of the first target verification node that initiated the rights and interests reward request, the verification consensus is confirmed. At this time, the first target user node can obtain the rights and interests reward. Therefore, it is necessary to record the changes in rights and interests of the first target user node. For example, a second platform rights and interests change record can be generated, and the second platform rights and interests change record can be packaged to generate a third block. The newly generated third block is then uploaded to the platform rights and interests record chain corresponding to each central node.

[0168] Based on the aforementioned blockchain-based change request method, this disclosure also provides a blockchain-based change request apparatus. The following will be combined with... Figure 13 The device is described in detail.

[0169] Figure 13A schematic block diagram of a blockchain-based change request device according to an embodiment of the present disclosure is shown.

[0170] like Figure 13 As shown, the blockchain-based change request device 1300 of this embodiment includes a request module 1310 and a first broadcast module 1320.

[0171] The request module 1310 is used to initiate a rights change request to multiple central nodes when the rights of the first target user node are to be changed. The rights change request is used to request the multiple central nodes to reach a consensus confirmation on the rights change. The first target user node belongs to either a first-type user node or a second-type user node. In one embodiment, the request module 1310 can be used to execute the operation S210 described above, which will not be repeated here.

[0172] The first broadcast module 1320 is used to broadcast a stake verification request to the blockchain consortium network in response to a notification from the central node confirming the success of the change consensus. The stake verification request requests a predetermined number of nodes in the blockchain consortium network to verify and confirm the stake change. These nodes include multiple central nodes, multiple first-type user nodes, and multiple second-type user nodes. In one embodiment, the first broadcast module 1320 can be used to perform the operation S220 described above, which will not be repeated here.

[0173] According to embodiments of this disclosure, each user node in the first and second categories corresponds to a user rights record chain, and multiple first blocks in the user rights record chain are used to record the changes in the rights of each user node; each second category user node also corresponds to an activity project record chain, and multiple second blocks in the activity project record chain are used to record the changes in the activity projects of each second category user node; each central node corresponds to a platform rights record chain and a transaction status record chain, and multiple third blocks in the platform rights record chain are used to record the changes in the rights of multiple first and second category user nodes in the blockchain consortium network, and multiple fourth blocks in the transaction status record chain are used to record the order transaction status of multiple first and second category user nodes in the blockchain consortium network.

[0174] According to embodiments of this disclosure, the data stored in the block body of the first block includes at least: the type of equity change, the quantity of equity change, and the address of the first target verification node actively participating in the verification of equity change in the blockchain consortium network; the data stored in the block body of the second block includes at least: the identifier of the changed activity project, the type of equity change triggered by the activity project change, the quantity of equity change triggered by the activity project change, the transaction deduction value corresponding to the activity project, and the address of the second target verification node actively participating in the verification of the activity project change in the blockchain consortium network; the data stored in the block body of the third block includes at least: the type of equity change, the quantity of equity change, the address of the user node where the equity change occurred, and the address of the first central node that performs change consensus confirmation during the change consensus confirmation process; the data stored in the block body of the fourth block includes at least: the identifier of the transaction order, the actual transaction payment value, the address of the user node that initiated the transaction, the quantity of equity consumed by the first type of user node in the transaction, the identifier of the preferred activity project published by the second type of user and used by the first type of user node in the transaction, and the quantity of equity deduction corresponding to the preferred activity project.

[0175] According to embodiments of this disclosure, the blockchain-based change request device further includes a first confirmation module and a first packaging module.

[0176] The first confirmation module is used to generate a node equity change record in response to the notification that the verification has passed from the first target verification node that actively participates in the verification of equity change in the blockchain consortium network. The first packaging module is used to package the node equity change record to generate a first block and upload the newly generated first block to the user equity record chain corresponding to the first target user node.

[0177] According to embodiments of this disclosure, when the first target user node belongs to a first type of user node, the change in the rights and interests of the first target user node is triggered by the first target user node actively recharging or consuming rights and interests; when the first target user node belongs to a second type of user node, the change in the rights and interests of the first target user node is triggered by the first target user node actively recharging or being recharged with rights and interests, or the change in the rights and interests of the first target user node is triggered by a change in the activity items of the first target user node.

[0178] According to an embodiment of this disclosure, if the first target user node belongs to the second type of user node and the change of rights of the first target user node is triggered by a change in the activity items of the first target user node, the blockchain-based change request device further includes: a second broadcast module, a first generation module, and a second packaging module.

[0179] The second broadcast module is used to broadcast the project verification request to the blockchain consortium network. The project verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the changes in the activity projects of the first target user node. The first generation module is used to generate an activity project change record in response to the notification of verification confirmation from the second target verification node in the blockchain consortium network that actively participated in the verification of the activity project changes. The second packaging module is used to package the activity project change record to generate a second block and upload the newly generated second block to the activity project record chain corresponding to the first target user node.

[0180] According to embodiments of this disclosure, when the first target user node belongs to a first type of user node and the first target user node intends to initiate a transaction, the blockchain-based change request device further includes: a query module, a second generation module, a third generation module, and a first sending module.

[0181] The query module is used to query the changes of activity projects in the target second block located at the tail of the activity project record chain; the second generation module is used to generate a preferred transaction combination strategy by running a smart contract based on the changes of activity projects in the target second block. The preferred transaction combination strategy is used to indicate the amount of equity consumption recommended to be executed in the transaction, as well as the information of the preferred activity projects among the multiple activity projects published by the second type of user; the third generation module is used to generate a transaction confirmation request based on the preferred transaction combination strategy; the first sending module is used to send the corresponding transaction confirmation request to multiple central nodes, so that the multiple central nodes can conduct transaction consensus confirmation on the transaction to be initiated by the first target user node.

[0182] According to embodiments of this disclosure, any plurality of modules in the request module 1310 and the first broadcast module 1320 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules may be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the request module 1310 and the first broadcast module 1320 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. Alternatively, at least one of the request module 1310 and the first broadcast module 1320 may be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0183] Figure 14 A schematic block diagram of a blockchain-based request processing apparatus according to an embodiment of the present disclosure is shown.

[0184] like Figure 14 As shown, the blockchain-based request processing device 1400 of this embodiment includes a change consensus confirmation module 1410 and a second sending module 1420.

[0185] The change consensus confirmation module 1410 is used to respond to a rights change request from a first target user node whose rights are to be changed, and to confirm the rights change status of the first target user node, wherein the first target user node belongs to either a first type of user node or a second type of user node. In one embodiment, the change consensus confirmation module 1410 can be used to perform the operation S1210 described above, which will not be repeated here.

[0186] The second sending module 1420 is used to send a notification of successful change consensus confirmation to the first target user node when the change consensus confirmation is successful. This causes the first target user node to respond to the notification by broadcasting a stake verification request to the blockchain consortium network. The stake verification request requests a predetermined number of nodes in the blockchain consortium network to verify and confirm the change in stake. These nodes include multiple central nodes, multiple first-type user nodes, and multiple second-type user nodes. In one embodiment, the second sending module 1420 can be used to execute the operation S1220 described above, which will not be repeated here.

[0187] According to embodiments of this disclosure, the blockchain-based request processing apparatus further includes a fourth generation module and a third packaging module.

[0188] The fourth generation module is used to generate the first platform rights change record based on the result of the change consensus confirmation when the change consensus is confirmed; the third packaging module is used to package the first platform rights change record to generate the third block and upload the newly generated third block to the platform rights record chain corresponding to each central node.

[0189] According to embodiments of this disclosure, when the first target user node belongs to a first type of user node and the first target user node intends to initiate a transaction, the blockchain-based request processing device further includes a second confirmation module.

[0190] The second confirmation module is used to respond to the transaction confirmation request from the first target user node and to perform transaction consensus confirmation on the transaction to be initiated by the first target user node.

[0191] According to embodiments of this disclosure, the blockchain-based request processing apparatus further includes a fifth generation module and a fourth packaging module.

[0192] The fifth generation module is used to generate a transaction confirmation record based on the transaction consensus confirmation result when the transaction consensus is confirmed. The fourth packaging module is used to package the transaction confirmation record to generate a fourth block and upload the newly generated fourth block to the transaction status record chain corresponding to each central node.

[0193] According to embodiments of this disclosure, the blockchain-based request processing apparatus further includes a consensus confirmation module and a third sending module.

[0194] The consensus confirmation module is used to respond to the rights reward request from the first target verification node in the blockchain consortium network that actively participates in the verification of rights changes, and to confirm the verification status of the first target verification node. The third sending module is used to send a notification that the verification status has been confirmed to be ...

[0195] According to embodiments of this disclosure, the consensus confirmation module includes an acquisition submodule and a consensus confirmation submodule.

[0196] The acquisition submodule is used to obtain the rights change information of the first target user node from the user rights record chain of the first target user node, wherein the rights change information includes the address information of the first target verification node; the consensus confirmation submodule is used to perform consensus confirmation on the verification status of the first target verification node based on the rights change information of the first target user node.

[0197] According to embodiments of this disclosure, the blockchain-based request processing apparatus further includes a sixth generation module and a fifth packaging module.

[0198] The sixth generation module is used to generate a second platform rights change record based on the result of the verification consensus confirmation if the verification status is confirmed. The fifth packaging module is used to package the second platform rights change record to generate a third block and upload the newly generated third block to the platform rights record chain corresponding to each central node.

[0199] According to embodiments of this disclosure, any plurality of modules in the change consensus confirmation module 1410 and the second sending module 1420 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules may be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the change consensus confirmation module 1410 and the second sending module 1420 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging the circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. Alternatively, at least one of the change consensus confirmation module 1410 and the second sending module 1420 may be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0200] Figure 15 A block diagram schematically illustrates an electronic device suitable for implementing a blockchain-based change request method and a blockchain-based request processing method according to embodiments of the present disclosure.

[0201] like Figure 15 As shown, an electronic device 1500 according to an embodiment of the present disclosure includes a processor 1501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1502 or a program loaded from a storage portion 1508 into a random access memory (RAM) 1503. The processor 1501 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1501 may also include onboard memory for caching purposes. The processor 1501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0202] RAM 1503 stores various programs and data required for the operation of electronic device 1500. Processor 1501, ROM 1502, and RAM 1503 are interconnected via bus 1504. Processor 1501 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 1502 and / or RAM 1503. It should be noted that programs may also be stored in one or more memories other than ROM 1502 and RAM 1503. Processor 1501 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in one or more memories.

[0203] According to embodiments of this disclosure, the electronic device 1500 may further include an input / output (I / O) interface 1505, which is also connected to a bus 1504. The electronic device 1500 may also include one or more of the following components connected to the input / output (I / O) interface 1505: an input section 1506 including a keyboard, mouse, etc.; an output section 1507 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1508 including a hard disk, etc.; and a communication section 1509 including a network interface card such as a LAN card, modem, etc. The communication section 1509 performs communication processing via a network such as the Internet. A drive 1510 is also connected to the input / output (I / O) interface 1505 as needed. A removable medium 1511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 1510 as needed so that computer programs read from it can be installed into the storage section 1508 as needed.

[0204] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0205] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 1502 and / or RAM 1503 and / or one or more memories other than ROM 1502 and RAM 1503 described above.

[0206] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code enables the computer system to implement the blockchain-based change request method and the blockchain-based request processing method provided in embodiments of this disclosure.

[0207] When the computer program is executed by the processor 1501, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0208] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 1509, and / or installed from the removable medium 1511. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0209] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1509, and / or installed from the removable medium 1511. When the computer program is executed by the processor 1501, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0210] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0211] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0212] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0213] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A blockchain-based change request method, comprising: In the event of a proposed change to the rights and interests of the first target user node, a rights and interests change request is initiated to multiple central nodes. The rights and interests change request is used to request the multiple central nodes to reach a consensus on the rights and interests change. The first target user node belongs to either the first type of user node or the second type of user node. In response to a notification from the central node confirming the change consensus, a stake verification request is broadcast to the blockchain consortium network. The stake verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the stake change. The multiple nodes in the blockchain consortium network include the multiple central nodes, multiple first-type user nodes, and multiple second-type user nodes. Each user node in the first type of user node and the second type of user node corresponds to a user rights record chain, and multiple first blocks in the user rights record chain are used to record the changes in the rights of each user node. Each of the second type of user nodes also corresponds to an activity item record chain, and multiple second blocks in the activity item record chain are used to record the changes in the activity items of each of the second type of user nodes; Each central node corresponds to a platform rights record chain and a transaction record chain. Multiple third blocks in the platform rights record chain are used to record the rights changes of multiple first-type user nodes and multiple second-type user nodes in the blockchain consortium network. Multiple fourth blocks in the transaction record chain are used to record the order transaction information of multiple first-type user nodes and multiple second-type user nodes in the blockchain consortium network.

2. The method according to claim 1, wherein: The data stored in the block body of the first block includes at least: the type of equity change, the number of equity changes, and the address of the first target verification node in the blockchain consortium network that actively participates in the verification of equity changes; The data stored in the block body of the second block includes at least: the changed activity project identifier, the type of equity change triggered by the change of the activity project, the number of equity changes triggered by the change of the activity project, the transaction deduction value corresponding to the activity project, and the address of the second target verification node in the blockchain consortium network that actively participates in the verification of the change of the activity project; The data stored in the block body of the third block includes at least: the type of equity change, the number of equity changes, the address of the user node where the equity change occurred, and the address of the first central node to confirm the change consensus during the change consensus confirmation process; The data stored in the block body of the fourth block includes at least: the identifier of the transaction order, the actual transaction payment value, the address of the user node that initiated the transaction, the amount of rights consumed by the first type of user node in the transaction, the identifier of the preferred activity item published by the second type of user and used by the first type of user node in the transaction, and the amount of rights deducted corresponding to the preferred activity item.

3. The method according to claim 1, further comprising: In response to the notification of successful verification from the first target verification node that actively participates in the verification of changes in equity in the blockchain consortium network, a node equity change record is generated; The node rights change records are packaged to generate a first block, and the newly generated first block is uploaded to the user rights record chain corresponding to the first target user node.

4. The method according to claim 1, wherein: When the first target user node belongs to the first type of user node, the change in the rights and interests of the first target user node is caused by the first target user node actively recharging or consuming rights and interests. If the first target user node belongs to the second type of user node, the change in the rights and interests of the first target user node is caused by the first target user node actively recharging its rights and interests or being recharged with its rights and interests, or the change in the rights and interests of the first target user node is caused by the change in the activity items of the first target user node.

5. The method according to any one of claims 1-4, wherein when the first target user node belongs to the second type of user node, and the change in the rights and interests of the first target user node is triggered by a change in the activity items of the first target user node, the method further includes: The project verification request is broadcast to the blockchain consortium network, wherein the project verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the changes in the active projects of the first target user node. In response to the notification of successful verification from the second target verification node that actively participates in the verification of activity item changes in the blockchain consortium network, an activity item change record is generated; The activity item change records are packaged into a second block, and the newly generated second block is uploaded to the activity item record chain corresponding to the first target user node.

6. The method according to any one of claims 1-4, wherein when the first target user node belongs to the first type of user node and the first target user node intends to initiate a transaction, the method further comprises: Query the changes to the activity items in the target second block located at the end of the activity item record chain; Based on the changes in the active items in the target second block, a preferred transaction combination strategy is generated by running a smart contract. The preferred transaction combination strategy is used to indicate the recommended amount of equity consumption to be executed in the transaction, as well as the information of the preferred active items among multiple active items published by the second type of user. A transaction confirmation request is generated based on the preferred transaction combination strategy; Send transaction confirmation requests to multiple central nodes so that the multiple central nodes can conduct transaction consensus confirmation for the transaction to be initiated by the first target user node.

7. A blockchain-based request processing method, comprising: In response to a rights change request from a first target user node whose rights are to be changed, a consensus confirmation is made on the rights change of the first target user node, wherein the first target user node belongs to a first type of user node or a second type of user node; If the change consensus is confirmed, a notification of the change consensus is sent to the first target user node, so that the first target user node responds to the notification of the change consensus and broadcasts the rights verification request to the blockchain consortium network. The rights verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the rights change. The multiple nodes in the blockchain consortium network include multiple central nodes, multiple first-type user nodes, and multiple second-type user nodes. Each user node in the first type of user node and the second type of user node corresponds to a user rights record chain, and multiple first blocks in the user rights record chain are used to record the changes in the rights of each user node. Each of the second type of user nodes also corresponds to an activity item record chain, and multiple second blocks in the activity item record chain are used to record the changes in the activity items of each of the second type of user nodes; Each central node corresponds to a platform rights record chain and a transaction record chain. Multiple third blocks in the platform rights record chain are used to record the rights changes of multiple first-type user nodes and multiple second-type user nodes in the blockchain consortium network. Multiple fourth blocks in the transaction record chain are used to record the order transaction information of multiple first-type user nodes and multiple second-type user nodes in the blockchain consortium network.

8. The method according to claim 7, further comprising: If the consensus on the change is approved, a record of the change of rights and interests of the first platform will be generated based on the result of the consensus confirmation. The first platform rights change record is packaged into a third block, and the newly generated third block is uploaded to the platform rights record chain corresponding to each central node.

9. The method according to claim 7, wherein when the first target user node belongs to the first type of user node and the first target user node intends to initiate a transaction, the method further includes: In response to a transaction confirmation request from the first target user node, a transaction consensus confirmation is performed on the transaction to be initiated by the first target user node.

10. The method of claim 9, further comprising: If the transaction consensus is passed, a transaction confirmation record is generated based on the result of the transaction consensus confirmation; The transaction confirmation records are packaged to generate a fourth block, and the newly generated fourth block is uploaded to the transaction record chain corresponding to each central node.

11. The method of claim 7, further comprising: In response to the rights reward request from the first target verification node in the blockchain consortium network that actively participates in the verification of rights changes, a consensus confirmation of the verification status of the first target verification node is made. If the consensus on the verification status is confirmed, a notification confirming the consensus on the verification status is sent to the first target verification node, so that the first target verification node can make changes to its rights based on the notification confirming the consensus.

12. The method according to claim 11, wherein the consensus confirmation of the verification status of the first target verification node includes: Obtain the change information of the rights and interests of the first target user node from the user rights and interests record chain of the first target user node, wherein the change information of the rights and interests includes the address information of the first target verification node; Based on the changes in the rights and interests of the first target user node, a consensus confirmation is made on the verification status of the first target verification node.

13. The method of claim 11, further comprising: If the verification results are confirmed by consensus, a second platform rights change record will be generated based on the verification results. The second platform rights change record is packaged into a third block, and the newly generated third block is uploaded to the platform rights record chain corresponding to each central node.

14. A blockchain-based change request device, characterized in that, The device includes: The request module is used to initiate a rights change request to multiple central nodes when the rights of a first target user node are to be changed. The rights change request is used to request the multiple central nodes to reach a consensus confirmation on the rights change, wherein the first target user node belongs to either a first type of user node or a second type of user node. The first broadcast module is used to broadcast a rights verification request to the blockchain consortium network in response to a notification from the central node confirming the change consensus. The rights verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the rights change. The multiple nodes in the blockchain consortium network include the multiple central nodes, multiple first-type user nodes, and multiple second-type user nodes. Each user node in the first type of user node and the second type of user node corresponds to a user rights record chain, and multiple first blocks in the user rights record chain are used to record the changes in the rights of each user node. Each of the second type of user nodes also corresponds to an activity item record chain, and multiple second blocks in the activity item record chain are used to record the changes in the activity items of each of the second type of user nodes; Each central node corresponds to a platform rights record chain and a transaction record chain. Multiple third blocks in the platform rights record chain are used to record the rights changes of multiple first-type user nodes and multiple second-type user nodes in the blockchain consortium network. Multiple fourth blocks in the transaction record chain are used to record the order transaction information of multiple first-type user nodes and multiple second-type user nodes in the blockchain consortium network.

15. A blockchain-based request processing device, characterized in that, The device includes: The consensus confirmation module is used to respond to a rights change request from a first target user node whose rights are to be changed, and to confirm the rights change of the first target user node, wherein the first target user node belongs to a first type of user node or a second type of user node. The second sending module is used to send a notification of successful change consensus confirmation to the first target user node when the change consensus confirmation is successful, so that the first target user node responds to the notification of successful change consensus confirmation and broadcasts a rights verification request to the blockchain consortium network. The rights verification request is used to request a predetermined number of nodes in the blockchain consortium network to verify and confirm the rights change. The multiple nodes in the blockchain consortium network include multiple central nodes, multiple first-type user nodes, and multiple second-type user nodes. Each user node in the first type of user node and the second type of user node corresponds to a user rights record chain, and multiple first blocks in the user rights record chain are used to record the changes in the rights of each user node. Each of the second type of user nodes also corresponds to an activity item record chain, and multiple second blocks in the activity item record chain are used to record the changes in the activity items of each of the second type of user nodes; Each central node corresponds to a platform rights record chain and a transaction record chain. Multiple third blocks in the platform rights record chain are used to record the rights changes of multiple first-type user nodes and multiple second-type user nodes in the blockchain consortium network. Multiple fourth blocks in the transaction record chain are used to record the order transaction information of multiple first-type user nodes and multiple second-type user nodes in the blockchain consortium network.

16. An electronic device comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 13.

17. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 13.

18. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 13.

Images