A blockchain delegation governance method, system, electronic device and readable medium

Abstract

The embodiment of the present disclosure discloses a blockchain delegation governance method, system, electronic device and readable medium, and relates to the technical field of blockchain. The method comprises the following steps: a blockchain governance delegation terminal generates a blockchain governance delegation request and uploads the blockchain, wherein the delegation request comprises a delegation governance strategy, and the delegation governance strategy indicates a delegation rule of delegating one or more to-be-delegated governance decision voting rights to one or more blockchain governance trustee terminals; the trustee terminal synchronizes the delegation governance strategy from the blockchain, generates a blockchain governance trustee request and uploads the blockchain, wherein the trustee request comprises a to-be-trusted governance decision, and the to-be-trusted governance decision is a to-be-delegated governance decision that the trustee terminal agrees to receive the voting right; the blockchain executes an intelligent contract, verifies the trustee request based on the delegation governance strategy, and generates a trustee result. The present disclosure achieves the purpose of blockchain delegation governance by setting an intelligent contract on the blockchain.

Description

Technical Field

[0001] This disclosure relates to the field of blockchain technology, and more particularly to a delegated governance method, system, electronic device, and readable medium for blockchain. Background Technology

[0002] Blockchain governance refers to the establishment and implementation of a series of rules, protocols, and mechanisms within a blockchain network to ensure its secure, stable, and efficient operation. Taking consortium blockchains as an example, governance can be implemented in two ways: off-chain governance, which involves special off-chain configurations, such as a consensus node list maintained by a unified off-chain configuration file; and on-chain governance, which leverages the inherent characteristics of the blockchain itself to perform governance on the blockchain. Off-chain governance requires additional assurance of consistency of configuration information across nodes (currently achieved through transaction sending), and the governance results can impact the original consensus mechanism or permissions, making the overall design complex and prone to problems. On-chain governance, through automatic execution via smart contracts, helps reduce the costs of off-chain governance and improves governance efficiency.

[0003] Currently, in on-chain governance, all governance authorities are required to personally fulfill their governance responsibilities, and governance is typically carried out by a single authority. This approach is relatively simplistic and cannot meet the diverse governance needs of the real world. In specific blockchain systems, particularly consortium blockchains, some governance authorities may not wish to perform all governance tasks personally and could delegate them to trusted delegators. Therefore, a flexible method for delegating governance authority is needed. Summary of the Invention

[0004] This disclosure provides a method, system, electronic device, and readable medium for delegated governance of blockchain, which enables delegated governance of blockchain.

[0005] To achieve the above technical objectives, the embodiments of this disclosure adopt the following technical solutions:

[0006] In a first aspect, embodiments of this disclosure provide a delegated governance method for blockchain, wherein an on-chain governance smart contract is deployed on the blockchain, and the method includes:

[0007] The blockchain governance delegation terminal generates a blockchain governance delegation request and uploads it to the blockchain. The delegation request includes a delegation governance strategy, which indicates the delegation rules for delegating one or more voting rights for governance decisions to one or more blockchain governance delegation terminals.

[0008] The entrusted terminal synchronizes the entrusted governance strategy from the blockchain, generates a blockchain governance entrusted request and uploads it to the blockchain. The entrusted request includes the proposed entrusted governance decision, which is the entrusted governance decision in which the entrusted terminal agrees to receive voting rights.

[0009] Blockchain executes smart contracts, verifies entrusted requests based on delegated governance strategies, and generates entrusted results.

[0010] In some possible implementations, the delegated governance strategy is a hierarchical governance strategy, which indicates the delegation rules that delegate one or more hierarchical voting rights for governance decisions to one or more hierarchical blockchain governance delegated terminals.

[0011] In some possible implementations, the hierarchical governance strategy further includes the correspondence between the hierarchical structure of entrusted terminals and the hierarchical structure of governance decisions to be entrusted.

[0012] In some possible implementations, the blockchain executes smart contracts, verifies delegated requests based on a delegated governance strategy, and further includes:

[0013] Based on the correspondence, the level of blockchain governance decision that can be delegated is determined according to the level of the delegated terminal that generates the delegation request;

[0014] Determine whether the level of the proposed entrusted governance decision fully or partially meets the level of blockchain governance decision that can be delegated.

[0015] In some possible implementations, if the level of the proposed entrusted governance decision fully or partially meets the level of a delegated blockchain governance decision, it is further determined whether the voting rights of the governance decision that meets the level have not been fully delegated to other entrusted terminals.

[0016] In some possible implementations, the voting rights for one or more blockchain governance decisions held by a delegated terminal are delegated to other delegated terminals.

[0017] In some possible implementations, the blockchain executes smart contracts, verifies delegated requests based on a delegated governance strategy, and generates delegated results, further including:

[0018] If the smart contract passes verification, the generated trusteeship result includes trusteeship confirmation information, which indicates the current delegated governance decision.

[0019] or,

[0020] If the smart contract fails to verify, the generated trusteeship result will include trusteeship failure information.

[0021] In some possible implementations, the entrusted terminal receives entrusted confirmation information;

[0022] The entrusted terminal receives on-chain governance requests, which include decisions to be governed; it determines whether the decision to be governed belongs to the current delegated governance decision; if the decision to be governed belongs to the current delegated governance decision, it votes on the decision to be governed.

[0023] In some possible implementations, the delegation request further includes the delegation of governance time;

[0024] The entrusted governance period includes the length of the entrusted period or the deadline of the entrusted period. When the length of the entrusted period is reached or the deadline of the entrusted period is reached, the entrusted terminal no longer holds the voting rights for the current entrusted governance decision.

[0025] In some possible implementations, the delegated governance time may include one or more, each set for one or more governance decisions to be delegated.

[0026] In some possible implementations, the delegating terminal generates a delegation termination request and uploads it to the blockchain, wherein the delegation termination request includes the governance decision or governance decision level to be terminated;

[0027] The blockchain executes smart contracts, verifies delegate termination requests, and generates termination results.

[0028] And / or,

[0029] The delegated terminal generates a delegation change request and uploads it to the blockchain. The delegation change request includes the governance decision or governance decision level to be changed.

[0030] The blockchain executes smart contracts, verifies delegation change requests, and generates change results.

[0031] In some possible implementations, the hierarchical governance strategy is set separately by the delegated terminal;

[0032] or,

[0033] Blockchain includes one or more hierarchical governance strategies, and the delegated terminal selects one hierarchical governance strategy as needed.

[0034] In some possible implementations, one or more of the blockchain governance delegation request, delegation termination request, and delegation change request include a signature of the delegation terminal's private key;

[0035] And / or,

[0036] A blockchain governance delegation request includes the signature of the delegated terminal's private key.

[0037] In some possible implementations, the current governance state is synchronized from the blockchain, including the governance terminals currently holding voting rights, and one or more blockchain governance decisions they hold.

[0038] Secondly, embodiments of this disclosure provide a blockchain-based delegated governance system, wherein on-chain governance smart contracts are deployed on the blockchain, and the governance system further includes a blockchain governance delegation terminal and one or more blockchain governance delegation terminals, wherein:

[0039] The delegated terminal is configured to generate a blockchain governance delegation request and upload it to the blockchain. The delegation request includes a delegation governance strategy, which indicates the delegation rules for delegating one or more voting rights for governance decisions to one or more blockchain governance delegated terminals.

[0040] The entrusted terminal is configured to synchronize the entrusted governance strategy from the blockchain, generate a blockchain governance entrusted request and upload it to the blockchain. The entrusted request includes a proposed entrusted governance decision, which is a governance decision to be entrusted that the entrusted terminal agrees to receive voting rights.

[0041] The blockchain is configured to execute smart contracts, verify entrusted requests based on a delegated governance strategy, and generate entrusted results.

[0042] Thirdly, embodiments of this application provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the blockchain governance method as described in the first aspect.

[0043] Fourthly, embodiments of this application provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the blockchain governance method as described in the first aspect.

[0044] The technical solution of the first aspect provided by the embodiments of this application brings at least the following beneficial effects: An on-chain governance smart contract is deployed on the blockchain; a blockchain governance delegation terminal generates a blockchain governance delegation request and uploads it to the blockchain; the delegation request includes a delegation governance strategy, which indicates the delegation rules for delegating one or more voting rights for governance decisions to one or more blockchain governance delegation terminals; the delegation terminal synchronizes the delegation governance strategy from the blockchain, generates a blockchain governance delegation request, and uploads it to the blockchain; the delegation request includes a proposed delegation governance decision, which is a governance decision for which the delegation terminal agrees to receive voting rights; the blockchain executes the smart contract, verifies the delegation request based on the delegation governance strategy, and generates a delegation result. By setting up a smart contract on the blockchain, the delegation request can be verified based on the delegation governance strategy, thereby realizing delegated governance of the blockchain.

[0045] It should be noted that the technical effects of any of the implementation methods in the second to fourth aspects can be found in the technical effects of the corresponding implementation methods in the first aspect, and will not be repeated here.

[0046] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0047] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments of this disclosure will be briefly described below. Clearly, the drawings described below only relate to some embodiments of this disclosure and are not intended to limit the scope of this disclosure.

[0048] Figure 1 A block diagram of a blockchain governance system according to at least one embodiment of the present disclosure is shown;

[0049] Figure 2 A flowchart illustrating the operational sequence of an exemplary blockchain governance method according to at least one embodiment of the present disclosure is shown;

[0050] Figure 3 A flowchart illustrating the operational sequence of another exemplary blockchain governance method according to at least one embodiment of the present disclosure is shown;

[0051] Figure 4 A schematic diagram of a hierarchical governance strategy according to at least one embodiment of the present disclosure is shown;

[0052] Figures 5A to 5B A schematic diagram illustrating another hierarchical governance strategy change according to at least one embodiment of the present disclosure is shown;

[0053] Figure 6 A schematic diagram of the delegation process for a hierarchical governance strategy according to at least one embodiment of the present disclosure is shown;

[0054] Figure 7 A flowchart of a blockchain governance method according to at least one embodiment of the present disclosure is shown;

[0055] Figure 8 A flowchart illustrating the operational sequence of a blockchain governance voting method according to at least one embodiment of the present disclosure is shown;

[0056] Figure 9 A schematic diagram of an electronic device according to at least one embodiment of the present disclosure is shown;

[0057] Figure 10 A schematic diagram of a readable storage medium according to at least one embodiment of the present disclosure is shown. Detailed Implementation

[0058] Reference will now be made in detail to specific embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. Although the present disclosure will be described in conjunction with specific embodiments, it will be understood that it is not intended to limit the present disclosure to the described embodiments. Rather, it is intended to cover variations, modifications, and equivalents included within the spirit and scope of the present disclosure as defined by the appended claims. It should be noted that the method operations described herein can be implemented by any functional block or functional arrangement, and any functional block or functional arrangement can be implemented as a physical entity or a logical entity, or a combination of both.

[0059] To enable those skilled in the art to better understand this disclosure, the disclosure will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0060] Note that the examples described below are merely specific examples and are not intended to limit the embodiments of this disclosure to the specific shapes, hardware, connections, operations, values, conditions, data, sequences, etc., shown and described. Those skilled in the art can utilize the concepts of this disclosure to construct further embodiments not mentioned herein by reading this specification.

[0061] The terminology used in this disclosure is that which is currently widely used in the art in consideration of the functionality of this disclosure; however, these terms may vary depending on the intent, precedent, or new technology of those skilled in the art. Furthermore, specific terms may be chosen by the applicant, and in such cases, their detailed meanings will be described in the detailed description of this disclosure. Therefore, the terminology used in this specification should not be construed as simple names, but rather based on the meaning of the terms and the overall description of this disclosure.

[0062] To better understand the embodiments of this disclosure, the relevant terms involved in this disclosure will first be defined and explained.

[0063] Blockchain governance refers to the process of establishing and implementing a series of rules, protocols, and mechanisms within a blockchain network to ensure its secure, stable, and efficient operation. On-chain governance is a governance model that takes place within the protocol and updates the protocol through smart contracts.

[0064] Delegated governance in blockchain refers to the delegation of voting rights by a governance authority holding decision-making power on the blockchain (i.e., a governance authority with voting rights for a specific governance decision). Delegation can be conducted off-chain or on-chain. This disclosure adopts on-chain delegation of voting rights through smart contracts.

[0065] This publicly disclosed blockchain provides smart contract functionality for on-chain governance. A smart contract on a blockchain is a contract that can be triggered and executed by transactions on the blockchain system. Smart contracts can be defined in the form of code, typically containing a set of predefined rules. According to these rules, the parties to the smart contract agree to interact with each other, allowing value transfers and condition judgments on the blockchain network based on these rules. This enables automated contract execution without third-party intervention, offering advantages such as decentralization, automated execution, immutability, and reduced transaction costs.

[0066] It should be noted that the technical solutions in this disclosure, including the collection, updating, analysis, processing, use, transmission, and storage of user personal information, all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0067] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0068] Figure 1 A block diagram of a blockchain governance system according to at least one embodiment of the present disclosure is shown. Figure 1 Consensus decision-making in a blockchain system provides the foundational capabilities of the blockchain. The consensus decision-making process involves multiple distinct roles, each with different responsibilities: ordinary nodes participate in data synchronization and transaction forwarding, are responsible for backing up node data and selecting consensus nodes; consensus nodes participate in voting during the consensus process, maintaining the security of the blockchain network; and proposal nodes participate in proposing during the consensus process, maintaining the activity of the blockchain network. In addition to these node types, the blockchain also includes ordinary users (not shown in the diagram), consisting of a user's public key address and private key. These users represent the actual service users on the blockchain. In public blockchains, a user only needs a wallet identity to send transactions on the chain. In some application scenarios of consortium blockchains, users can only send transactions after obtaining authorization.

[0069] Meanwhile, the secure, stable, and efficient operation of a blockchain network requires the formulation and implementation of a series of rules, protocols, and mechanisms. This process is blockchain governance, and the entities participating in blockchain governance constitute the set of governance providers for the blockchain system. Currently, there are two ways to implement governance: one is off-chain governance, which involves special off-chain configurations, such as maintaining the consensus node list using a unified off-chain configuration file; the other is on-chain governance, which utilizes the inherent characteristics of the blockchain to perform corresponding governance on the blockchain itself, i.e., locating, executing, or running relevant governance processes within the blockchain. For example, the consensus node list can be maintained by a unified transaction or smart contract, and the scope of governance power can be controlled by restricting the permissions that can send transactions or invoke smart contracts.

[0070] from Figure 1 As can be seen, a governor is not a specific type of node, but rather a governance identity with governance authority. Governors can be proposal nodes, consensus nodes, ordinary nodes, or ordinary users; this disclosure does not impose any restrictions. Generally, the identity of a governor is determined off-chain, not on-chain. After obtaining governance identity off-chain, some governors may have a need to avoid personally handling on-chain governance. In such cases, they can delegate their voting rights for governance decisions through on-chain governance smart contracts.

[0071] Blockchain governance involves various decisions within a blockchain system, typically including basic metadata, protocol version, consensus-related decisions, block-related decisions, and user and permission management. Understandably, different governance decisions have varying impacts on the blockchain system's operation. Table 1 exemplarily lists relevant governance decisions and their levels within a blockchain system. It's understandable that core governance functions, such as adding a new blockchain member or changing consensus nodes or algorithms, can be assigned a higher decision level (e.g., exemplarily set to level A) and performed directly by the governance leader. Relatively basic governance functions, such as modifying user permission management, can be assigned a lower decision level (e.g., exemplarily set to level C) and delegated to a trustee. Decision levels can be set globally on the blockchain. For example, multiple different level lists can be set based on varying degrees of detail. When a governance leader wishes to delegate governance decisions, they directly select and invoke the relevant level list; thus, the governance decision level list is global. Optionally, the governance decision level list can also be created by the governance leader currently planning to delegate governance, reflecting their level of importance for different decisions. In this scenario, different decision levels can correspond to settings indicating whether or not delegation is permissible. For example, level A cannot be delegated, while levels below A, such as levels B, C, and D, can be delegated. Similarly, which levels can and cannot be delegated can be globally configured on the blockchain or set by the delegator. The delegator can determine the decision to be delegated, i.e., the "delegated governance decision," from the governance decisions corresponding to the levels that can be delegated.

[0072] Alternatively, the delegate may choose not to classify governance decisions, but instead directly select a portion of governance decisions to delegate; the selected governance decisions are referred to as "governance decisions to be delegated".

[0073] Table 1. Diagram of Governance Decisions and Decision Levels Related to Blockchain Systems

[0074]

[0075]

[0076] Figure 2 A flowchart illustrating the operational sequence of an exemplary blockchain governance method according to at least one embodiment of the present disclosure is shown.

[0077] In step S201, the delegating administrator with blockchain governance decision-making authority can determine, based on their own needs, which governance decisions can be delegated to a delegated administrator who will then exercise voting rights on behalf of the delegating administrator. Specifically, the delegating administrator generates a governance delegation request, which includes a delegation governance strategy. The delegation governance strategy specifies the rules by which one or more delegated administrators delegate voting rights for one or more "government decisions to be delegated." That is, the delegated administrator who ultimately obtains voting rights for certain governance decisions according to these delegation rules can vote on behalf of the delegating administrator for the aforementioned governance decisions to complete blockchain governance.

[0078] Specifically, the delegation rules indicated by the delegation governance strategy may involve one or more delegated governance entities and one or more "delegated governance decisions". When multiple delegated governance entities and multiple "delegated governance decisions" are involved, different delegated governance entities can be set to entrust all "delegated governance decisions", or different delegated governance entities can be set to correspond to different "delegated governance decisions", and one or more delegated governance entities can be entrusted with one or more "delegated governance decisions".

[0079] Optionally, the delegation request may further include a delegation period, which represents the timeframe within which the delegate can vote on behalf of the delegator. It is understood that the delegation period can be either the length of the delegation or the deadline for the delegation. When the length of the delegation period or the deadline for the delegation is reached, the delegate will no longer hold the voting rights for the current delegated governance decision. Optionally, there can be multiple delegation periods, each set separately for different governance decisions to be delegated. For example, if the current delegator has governance decisions J1 and J2, when the delegator delegates governance decisions J1 and J2, different delegation periods can be set for different governance decisions. For instance, the delegation period for J1 can be set to one month, and the delegation period for J2 can be set to the end of the current month.

[0080] Optionally, the voting rights of a delegated administrator can be obtained based on their governance status or through a delegated governance process with other administrators. It is understood that if their voting rights are derived from a delegated request from another administrator, the delegated governance decisions they set should meet the delegated governance decision requirements related to obtaining those voting rights. For example, if the current delegated administrator has governance decisions J1 and J2, where governance decision J2 was delegated by a previous delegated administrator, and that the previous delegated administrator requires that governance decision J2 cannot be delegated again, then the current delegated administrator can only delegate governance decision J1 again.

[0081] In step S202, the delegated administrator sends the generated governance delegation request to the blockchain.

[0082] In step S203, blockchain users and nodes listen to the governance delegation request sent by the delegated governance entity on the blockchain.

[0083] In step S204, the entrusted governance entity determines whether it falls within the scope of entrusted governance based on the entrusted governance strategy in the governance entrustment request, and the corresponding "entrusted governance decision".

[0084] For example, a delegating governance entity W plans to delegate "delegated governance decisions" J1, J2, J3, and J4 to delegated governance entities S1, S2, and S3. Specifically, delegated governance entities S1 can delegate governance decisions J1 and J2, S2 can delegate governance decisions J1, J2, and J3, and S3 can delegate governance decisions J4. When on-chain governance entity S4 receives the delegation request, it determines that it is not within the scope of delegation and therefore does not initiate further operations. When on-chain governance entity S2 receives the delegation request, it determines that it is within the scope of delegation and can act as a delegated governance entity, further determining the governance decisions it can delegate, namely J1-J3.

[0085] The entrusted governance entity can further determine whether to entrust governance-related decisions based on its own wishes. In the example above, entrusted governance entity S2 may be willing to assume voting rights for governance decisions J2 and J3, but unwilling to assume voting rights for governance decision J1. Optionally, when the entrustment request includes a entrusted governance period, the entrusted governance entity can also refer to the entrusted governance period when determining which governance decisions to entrust.

[0086] In step S205, the entrusted governance entity generates and sends a trustee request to the blockchain. The trustee request includes a "proposed entrusted governance decision". In the example above, the "proposed entrusted governance decision" included in the trustee request generated by the entrusted governance entity S2 is J2 and J3. That is, the "proposed entrusted governance decision" represents the governance decision that the entrusted governance entity agrees to accept voting rights.

[0087] In step S206, the blockchain executes the smart contract to verify the delegation request. The smart contract can verify whether the delegated administrator falls within the scope of delegation, and whether the "proposed delegated governance decision" in the delegation request falls within the scope of its corresponding delegated governance decision. The smart contract can also verify whether the current time meets the requirements for delegated governance time. If necessary, the smart contract can further verify whether other delegated administrators have already obtained voting rights for the "proposed delegated governance decision." For example, in the above example, if delegated administrator S1 has already obtained voting rights for governance decisions J1 and J2, then of delegated administrator S2's "proposed delegated governance decisions" J2 and J3, only J3 can obtain voting rights. In this case, governance decision J3 is the "current delegated governance decision." Optionally, if the delegation request includes the private key signature of the delegating administrator, or if the delegation request includes the private key signature of the delegated administrator, the smart contract can verify both together.

[0088] If the smart contract passes verification, the generated trusteeship result includes trusteeship confirmation information, which indicates the "current delegated governance decision," i.e., governance decision J3 in the example above. If the smart contract fails verification, the generated trusteeship result includes trusteeship failure information, which indicates that the current delegated governancer cannot obtain the governance decision.

[0089] In step S207, blockchain users and nodes listen to the entrusted confirmation information on the blockchain. When the smart contract verification is successful, the delegating governance entity can know from the entrusted confirmation information that the voting right for the "current delegated governance decision" has been exercised by the entrusted governance entity; conversely, the entrusted governance entity can also know from the entrusted confirmation information that it has obtained the voting right for the "current delegated governance decision". When a vote is initiated on-chain based on the "current delegated governance decision", the entrusted governance entity can vote. For the specific voting process, please refer to [link to relevant documentation]. Figure 8 .

[0090] It is understandable that if no relevant entrusted governance entity is willing to assume voting rights for all or part of the governance decisions in the "delegated governance decisions" issued by the entrusting governance entity, or if the entrusted governance request fails to pass verification, or if the entrusted governance time has been reached, then the entrustment of the governance decision has not been completed, and the entrusting governance entity shall continue to carry out the governance itself.

[0091] Figure 3 A flowchart illustrating the operational sequence of another exemplary blockchain governance method according to at least one embodiment of the present disclosure is shown. Figure 3 yes Figure 2 An alternative to the flowchart describing the operational sequence of a blockchain governance method. Therefore, when describing... Figure 3 The method will not be elaborated further. Figure 2 The process is the same in the same way.

[0092] Figure 3 The system adopts a hierarchical governance approach, whereby the delegated governance entity acts as one level of governance, defining different levels of governance entities and the relevant levels of each governance decision, and determining the different levels of governance decisions that can be obtained for different levels of governance entities.

[0093] Figure 4 Figures 5 and 6 illustrate schematic diagrams of hierarchical governance strategies for two exemplary embodiments. Figure 4 As shown, the "tiered governance strategy" referred to in this disclosure refers to a tiered approach to governance, where "tiered" refers to the tiering of governance entities (including delegating and entrusted governance entities), and "tiered" refers to the tiering of governance decisions. Governing entities at different tiers can be entrusted with governance decisions at different tiers and can vote on them (e.g., ...). Figure 4 The arrows in the diagram indicate the scope of governance decisions entrusted to different governance entities. These two categories can correspond to each other; for example, a second-tier governance entity can be entrusted with governance of levels two and above ("above" includes...). Figure 4 The three levels of governance decision-making form a "three-tier, three-level" hierarchical governance strategy; however, the two may not be corresponding, such as... Figure 5A As shown, level 1 administrators manage governance decisions at level 1 and above, level 2 administrators manage decisions at level 3 and above, and level 3 administrators manage decisions at level 5 and above, thus forming a "three-tier, five-level" hierarchical governance strategy. Dividing governance decisions or administrators into more levels can increase the flexibility of delegated governance, for example... Figure 5A China has divided governance decision-making into more levels, allowing for greater flexibility and efficiency when changes to delegated governance authority are needed. Figure 5B This illustrates the scenario where a second-tier governing body adds a secondary governance decision (dashed arrow in the diagram). It's understandable that when the hierarchical structure lacks a direct correspondence, the same hierarchical structure can lead to different strategies. Figure 5A and 5B Both are "three-tier, five-level" hierarchical governance strategies, but the governance decisions of the administrators at each level may differ.

[0094] Therefore, establishing the correspondence between governance hierarchy and governance decision-making hierarchy can be achieved by using lists or other similar methods to determine different levels corresponding to different levels; alternatively, delegateable blockchain governance decision-making hierarchy thresholds can be set for different levels of governance, for example... Figure 5A In the middle, the governance decision-making threshold for second-tier governance is level 3. Figure 5B In this context, the governance decision threshold for second-tier governance is level 2. If the tiered and graded values ​​match (e.g., ...), ... Figure 4If so, then by default, different levels of governance correspond to different levels of governance decisions, and no separate settings are needed; or, optionally, for the "two-tier and one-tier" hierarchical governance strategy, it can also be assumed that the second-tier governance can govern all governance decisions, and no separate settings are needed.

[0095] It is understood that the "layering" in this disclosure includes at least two layers. For example, if a delegating terminal has two levels of governance decisions, namely Level 1 and Level 2, and it manages the Level 1 governance decisions itself while delegating the Level 2 governance decisions to a delegated terminal, then the delegating terminal is a Level 1 governance provider, and the delegated terminal is a Level 2 governance provider, forming a "two-layer, two-level" hierarchical governance strategy. "Hierarchical" can include one level or more. For example, if a delegating terminal only has Level 1 governance decisions and delegates them to a delegated terminal, then the delegating terminal is a Level 1 governance provider, and the delegated terminal is a Level 2 governance provider, forming a "two-layer, one-level" hierarchical governance strategy. In this case, since there is only one level of delegated governance and only one level of governance decisions, it can also be understood as not layering the delegated governance providers or hierarchically classifying the governance decisions. It is understood that in this case... Figure 3 The established hierarchical governance strategy and Figure 2 The entrusted governance strategy has the same effect.

[0096] Figure 6 A schematic diagram illustrating the delegation process of a hierarchical governance strategy according to at least one embodiment of this disclosure is shown. A first-level administrator 1a has governance authority including governance decisions A, B, and C, and determines a three-tier, four-level governance strategy. This governance strategy can be set by the first-level administrator 1a itself, based on its own needs or trust relationships with other administrators. Alternatively, the blockchain includes one or more hierarchical governance strategies, which the first-level administrator 1a can synchronously obtain from the chain as needed and choose to use. Table 2 exemplarily illustrates a three-tier, four-level governance strategy. Only one decision threshold and decision level may be listed; the specific decision level content can be determined in conjunction with the information in Table 1. In Table 2, the first-level administrator includes 1a, the second-level administrators include 2a and 2b, and the third-level administrators include 3a-3d. Governance decisions include four levels: A, D, and E. The decision threshold that a first-level administrator can govern is A, corresponding to decision levels A and D; the decision threshold that a second-level administrator can govern is B, corresponding to decision levels B and D; and the decision threshold that a third-level administrator can govern is D, corresponding to decision level D. Optionally, the tiered governance strategy may further include the timeframe for each decision-making delegation.

[0097] Table 2. Schematic Diagram of Three-Tier and Four-Level Governance Strategy

[0098] First-level administrator 1a A AD Second-tier governance 2a, 2b B BD Three-tiered governance 3a, 3b, 3c, 3d D D

[0099] In step S201', Level 1 governor 1a generates a blockchain governance delegation request, which includes a hierarchical governance strategy, such as the three-tier, four-level governance strategy shown in Table 2. Governance decision A must be made solely by Level 1 governor 1a and cannot be delegated; Level 2 governors 2a and 2b can be entrusted with governance decisions corresponding to levels B and D. Optionally, the delegation request may include a signature of Level 1 governor 1a's private key to prove its identity.

[0100] Step S204': Taking the second-level governance provider 2a as an example, it listens to the blockchain governance delegation request issued by the first-level governance provider 1a, determines that it belongs to the scope of entrusted governance, and determines the decision level that it can be entrusted with governance, which is the governance decision BD.

[0101] In step S205', the second-level administrator 2a can determine, according to its own wishes, which governance decisions it will make, for example, Figure 6 In this scenario, the "delegated governance decision" sent by Level 1 administrator 1a to Level 2 administrator 2a includes governance decisions B and D. However, at this point, Level 2 administrator 2a is only willing to vote on the relevant content of decisions C and D. Therefore, the delegated governance decisions in the delegated request it generates and sends only include decisions C and D. Optionally, the delegated request can be signed using the private key of Level 2 administrator 2a to prove its identity.

[0102] Furthermore, after verification by the smart contract, if the second-level governance entity 2a can obtain governance authority over governance decisions C and D, it can generate a delegation confirmation message. At this point, the second-level governance entity 2a will obtain governance authority over governance decisions C and D; it can then delegate the obtained governance decision D to the third-level governance entities 3a-3d according to the content of the hierarchical governance strategy. The specific delegation process can be found in [link to relevant documentation]. Figure 2 This will not be elaborated upon here. Finally, for example... Figure 6 As shown, the voting rights for governance decision D are obtained by the three-tiered governance entity 3a. It is understood that this disclosure may further delegate authority should there be further stratification of governance entities and hierarchical classification of governance decisions, which is not limited here.

[0103] It is understandable that the governing bodies at each level are not limited to one party, such as... Figure 6As shown, when the second-level governance includes 2a and 2b, if governance 2b is willing to assume the voting rights of governance decision AC (i.e., the "proposed entrusted governance decision" AC), it can also issue a delegation request. In this case, the blockchain executes a smart contract for verification. First, the level of "delegable blockchain governance decisions" is determined based on the hierarchy of the second-level governance, which is BD. Therefore, only B and C in the "proposed entrusted governance decisions" AC belong to "delegable blockchain governance decisions." Governance decision A can only be governed by first-level governance. Second-level governance 2b does not have governance authority and does not meet the hierarchical governance strategy, so the verification fails. Governance decision C has already been granted governance authority by second-level governance 2a, so the verification also fails. Ultimately, second-level governance 2b only obtains the voting rights for governance decision B. Optionally, when the hierarchical governance strategy includes a delegated governance time, the smart contract verification process can also verify whether the current delegated governance time is met. Figure 6 The example shows the first-level administrator 1a, the second-level administrators 2a and 2b, and the third-level administrator 3a (shown in gray circles) who ultimately obtain the voting rights for governance decisions after the delegation process.

[0104] In some embodiments of this disclosure, the governance decisions with voting rights held by a first-tier administrator can be determined by their governance status or obtained through delegation from other delegated terminals. In the second case, the hierarchical governance strategy set by the first-tier administrator should meet the delegation requirements of other delegated terminals.

[0105] Optionally, the blockchain governance system may also include a query function, which allows blockchain users and nodes to synchronize the current governance status on the blockchain, including the current governance holders who hold voting rights and one or more blockchain governance decisions they hold; they may also query the current governance holders of relevant governance decisions or the current governance progress of a certain governance decision.

[0106] Optionally, when a delegated administrator wishes to reclaim voting rights for one or more governance decisions, they can generate a delegation termination request and upload it to the blockchain. The termination request includes the governance decisions to be terminated. The blockchain executes a smart contract, verifies the delegation termination request, and generates a termination result. If the verification passes, the delegation of the corresponding governance decision to be terminated is terminated, and the delegated administrator governs it independently. If the verification fails, the delegated administrator continues to vote on the governance decisions to be terminated.

[0107] In some embodiments of this disclosure, after determining the hierarchical governance strategy, each second-level governance participant can be notified via blockchain. The second-level governance participants then select which governance rights they wish to grant, submitting applications, for example, using a first-come, first-served approach to ensure that each governance right can only be obtained by one second-level governance participant. Other governance participants can simultaneously receive notifications of governance right delegation confirmation information, ensuring that they can check whether relevant governance participants have voting rights as needed. For first-level governance participants, they only need to formulate the hierarchical governance strategy; there is no need to assign governance rights separately each time. Furthermore, the hierarchical governance strategy can be easily adjusted as needed, such as changing the level of governance participants, the hierarchy of governance decisions, and the time of delegation. This can be achieved by regenerating a blockchain governance delegation request, or by generating a delegation change request for specific decisions, decision levels, or decision thresholds related to the delegation change. For example, the delegation governance strategy can be changed from... Figure 5A Change to Figure 5B When the governance decision threshold of the second-level governance entity is changed from level 3 to level 2, a delegation change request can be generated and uploaded to the blockchain. The delegation change request includes the governance threshold or governance level of the second-level governance entity. The blockchain executes a smart contract to verify the delegation change request.

[0108] Figure 7 A flowchart of a blockchain governance method according to at least one embodiment of the present disclosure is shown. The method is applied to a delegated governance system for a blockchain, wherein an on-chain governance smart contract is deployed on the blockchain. The governance system further includes a blockchain governance delegation terminal and one or more blockchain governance delegation terminals. The governance method includes:

[0109] Step S701: The blockchain governance delegation terminal generates a blockchain governance delegation request and uploads it to the blockchain. The delegation request includes a delegation governance strategy, which indicates the delegation rules for delegating one or more voting rights for governance decisions to the blockchain governance delegation terminal.

[0110] Step S702: The entrusted terminal synchronizes the entrusted governance strategy from the blockchain, generates a blockchain governance entrusted request and uploads it to the blockchain. The entrusted request includes the proposed entrusted governance decision, which is the entrusted governance decision in which the entrusted terminal agrees to receive voting rights.

[0111] In step S703, the blockchain executes the smart contract, verifies the entrusted request based on the delegated governance strategy, and generates the entrusted result.

[0112] Figure 8 A flowchart illustrating the operational sequence of a blockchain governance voting method according to at least one embodiment of this disclosure is provided. In the flowchart, both Governor 1 and Governor 2 currently possess voting rights for a certain governance decision; however, these voting rights are obtained based on their governance status, or through other means such as… Figure 2 or Figure 3 The voting rights obtained through the governance delegation process are not limited. For example... Figure 8 The governance voting method shown mainly includes the following steps:

[0113] In step S801, the proposer obtains or generates a governance proposal (i.e., an on-chain governance request) for blockchain governance. Governance proposals are typically initiated by a party with governance authority, but can also be set to allow any node or user to act as the proposer; this is not limited here. The governance proposal includes the decisions to be made in governance.

[0114] In step S802, the proposer sends the governance proposal to the blockchain.

[0115] In step S803 (S803'), blockchain users and nodes listen to the governance proposal sent by the proposer on the blockchain.

[0116] Step S804 (S804'): The governance decision is made by voting members of the governing body who have voting rights.

[0117] Step S805: Execute the smart contract to verify the administrator's identity and count votes. Specifically, verify whether the administrator has voting rights for the governance decision, such as whether the delegation period has been met, and whether they have voting rights for the governance decision themselves or have been delegated to do so. If the administrator is a delegated administrator, it is necessary to verify whether the decision to be governed belongs to the currently delegated governance decision. If the verification is successful, the votes of each administrator are tallied. The strategy for passing a proposal can be set or adjusted, such as setting a 1 / 2 or 2 / 3 voting weight for approval. The above voting process can be implemented using basic capabilities such as blockchain consensus services, and is not limited here. It is understood that the smart contract executed here is different from the smart contract executed during the delegation process (e.g., Figure 2 The functions are different. Different functions can be executed by the same smart contract or by different smart contracts; this is not limited here.

[0118] Step S806: After the vote is passed, the smart contract is executed to complete the blockchain configuration according to the governance proposal.

[0119] It should be noted that the above application scenarios are merely exemplary, intended to describe one or more aspects of this disclosure in specific scenarios. However, these aspects are not essential, and various modifications can be made to the application scenario. It is readily understood that the specific application scenarios described in this disclosure are not limited.

[0120] At least some embodiments of this disclosure also provide an electronic device. Figure 9 A schematic diagram of an electronic device 900 according to at least one embodiment of the present disclosure is shown.

[0121] like Figure 9 As shown, the electronic device 900 includes one or more processors 910 and a memory 920. The memory 920 includes one or more computer program modules 921. The one or more computer program modules 921 are stored in the memory 920 and configured to be executed by the processor 910. These computer program modules 921 include instructions for executing a blockchain governance method and its additional aspects according to at least one embodiment of the present disclosure. When executed by the processor 910, they can perform one or more steps of the blockchain governance method and its additional aspects according to at least one embodiment of the present disclosure. The memory 920 and the processor 910 can be interconnected via a bus system and / or other forms of connection mechanism (not shown). For example, the bus can be a Peripheral Component Interconnect Standard (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0122] For example, processor 910 may be a central processing unit (CPU), a digital signal processor (DSP), or other processing unit with data processing and / or program execution capabilities, such as a field-programmable gate array (FPGA). Processor 910 may be a general-purpose processor or a special-purpose processor, capable of controlling other components in electronic device 900 to perform desired functions.

[0123] Exemplarily, memory 920 may include any combination of one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, erasable programmable read-only memory (EPROM), portable compact disc read-only memory (CD-ROM), USB memory, flash memory, etc. One or more computer program modules 921 may be stored on the computer-readable storage medium, and processor 910 may run one or more computer program modules 921 to implement various functions of electronic device 900. The computer program modules include multiple computer-executable instructions. Various application programs and various data, as well as various data used and / or generated by the application programs, may also be stored in the computer-readable storage medium.

[0124] For example, electronic device 900 may also include input devices such as touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, and gyroscopes; output devices such as liquid crystal displays, speakers, and vibrators; storage devices such as magnetic tapes and hard disks (HDDs or SDDs); and communication devices such as network interface cards like LAN cards and modems. The communication devices allow electronic device 900 to communicate wirelessly or wiredly with other devices to exchange data and perform communication processing via networks such as the Internet. A drive is connected to the I / O interface as needed. Removable storage media, such as disks, optical disks, magneto-optical disks, and semiconductor memories, are installed on the drive as needed so that computer programs read from them can be installed into the storage device as required.

[0125] For example, the electronic device 900 may further include a peripheral interface (not shown in the figure). This peripheral interface can be various types of interfaces, such as a USB interface, a Lightning interface, etc. The communication device can communicate wirelessly with networks and other devices, such as the Internet, intranets and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs). Wireless communication can use any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wi-Fi (e.g., based on IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n standards), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email, instant messaging, and / or Short Message Service (SMS), or any other suitable communication protocol.

[0126] The electronic device 900 can be, for example, a system-on-a-chip (SoC) or a device including the SoC. For instance, it can be any device such as a mobile phone, tablet, laptop, e-reader, game console, television, digital photo frame, navigator, home appliance, communication base station, industrial controller, server, etc., or any combination of data processing devices and hardware. The embodiments of this disclosure do not limit this. The specific functions and technical effects of the electronic device 900 can be found in the description above regarding blockchain governance and its additional aspects according to at least one embodiment of this disclosure, and will not be repeated here.

[0127] Figure 10 A schematic diagram of a readable storage medium 1000 according to at least one embodiment of the present disclosure is shown.

[0128] like Figure 10 As shown, the readable storage medium 1000 stores computer instructions 1010, which is a computer-readable storage medium. When the computer instructions 1010 are executed by the processor, they perform one or more steps of the blockchain governance and its additional aspects as described above.

[0129] For example, when the program code is read by a computer, the computer can execute the program code stored in the computer storage medium to perform one or more steps to implement, for example, blockchain governance and its additional aspects according to at least one embodiment of the present disclosure.

[0130] For example, the readable storage medium may include a memory card of a smartphone, a storage component of a tablet computer, a hard disk of a personal computer, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), portable compact disc read-only memory (CD-ROM), flash memory, and other readable storage media or any combination thereof. The readable storage medium 1000 may be a non-transitory readable storage medium.

[0131] At least some of the embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other.

[0132] It should be noted that, in this disclosure, relational terms such as "first," "second," etc., are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0133] 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, or they may sometimes be executed in reverse order, depending on the functions involved; that is, the preceding or following operations are not necessarily executed precisely in sequence. Instead, various steps may be processed in reverse order or simultaneously as needed. Furthermore, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0134] The units described in the embodiments of this disclosure can be implemented in software or hardware. The described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0135] The following points should be noted regarding this disclosure:

[0136] (1) The accompanying drawings of the embodiments of this disclosure only involve the structures involved in the embodiments of this disclosure. Other structures can be referred to the general design.

[0137] (2) Where there is no conflict, the embodiments of this disclosure and the features in the embodiments can be combined with each other to obtain new embodiments.

[0138] The above description is merely an exemplary embodiment of this disclosure and is not intended to limit the scope of protection of this disclosure, which is determined by the appended claims.

Claims

1. A delegated governance method for blockchain, characterized in that, An on-chain governance smart contract is deployed on the blockchain, and the method includes: A blockchain governance delegation terminal generates a blockchain governance delegation request and uploads it to the blockchain. The delegation request includes a delegation governance strategy, which indicates the delegation rules for delegating one or more voting rights for governance decisions to one or more blockchain governance delegation terminals. The entrusted terminal synchronizes the entrusted governance strategy from the blockchain, generates a blockchain governance entrusted request and uploads it to the blockchain, wherein the entrusted request includes a proposed entrusted governance decision, which is the entrusted governance decision in which the entrusted terminal agrees to receive voting rights; The blockchain executes the smart contract, verifies the entrusted request based on the delegated governance strategy, and generates the entrusted result.

2. The method according to claim 1, characterized in that, The delegated governance strategy is a hierarchical governance strategy, which indicates the delegation rules for delegating one or more hierarchical voting rights for governance decisions to one or more hierarchical blockchain governance delegated terminals.

3. The method according to claim 2, characterized in that, The hierarchical governance strategy further includes the correspondence between the hierarchical structure of the entrusted terminal and the hierarchical structure of the governance decision to be entrusted.

4. The method according to claim 3, characterized in that, The blockchain executes the smart contract and verifies the entrusted request based on the delegated governance strategy, further including: Based on the aforementioned correspondence, the level of blockchain governance decision that can be delegated is determined according to the level of the delegated terminal that generated the delegation request. Determine whether the proposed entrusted governance decision level fully or partially meets the level of the blockchain governance decision that can be entrusted.

5. The method according to claim 4, characterized in that, If the proposed entrusted governance decision level fully or partially meets the level of the delegated blockchain governance decision, it is further determined whether the voting rights of the governance decision meeting the level have not been fully delegated to other entrusted terminals.

6. The method according to claim 1, characterized in that, The voting rights for one or more blockchain governance decisions held by the delegated terminal are obtained by delegation from other delegated terminals.

7. The method according to any one of claims 1-6, characterized in that, The blockchain executes the smart contract, verifies the entrusted request based on the delegated governance strategy, and generates an entrusted result, further including: If the smart contract passes verification, the generated trusteeship result includes trusteeship confirmation information, which indicates the current delegation governance decision. or, If the smart contract fails verification, the generated trusteeship result includes trusteeship failure information.

8. The method according to claim 7, characterized in that, The method further includes: the entrusted terminal receiving entrusted confirmation information; The entrusted terminal receives an on-chain governance request, which includes a decision to be governed; determines whether the decision to be governed belongs to the current delegated governance decision; and if the decision to be governed belongs to the current delegated governance decision, votes are cast on the decision to be governed.

9. The method according to claim 7, characterized in that, The method further includes: The request for delegation further includes the timeframe for delegation of governance; The entrusted governance time includes the length of the entrusted period or the deadline of the entrusted period. When the length of the entrusted period is reached or the deadline of the entrusted period is reached, the entrusted terminal no longer holds the voting right for the current entrusted governance decision.

10. The method according to claim 9, characterized in that, The method further includes: The entrusted governance time includes one or more, which are set separately for the one or more entrusted governance decisions.

11. The method according to claim 7, characterized in that, The method further includes: The delegated terminal generates a delegated termination request and uploads it to the blockchain, wherein the delegated termination request includes the governance decision or governance decision level to be terminated; The blockchain executes the smart contract, verifies the delegation termination request, and generates a termination result; And / or, The delegated terminal generates a delegated change request and uploads it to the blockchain, wherein the delegated change request includes the governance decision or governance decision level to be changed; The blockchain executes the smart contract, verifies the delegation change request, and generates the change result.

12. The method according to claim 2, characterized in that, The hierarchical governance strategy is set separately by the entrusted terminal; or, The blockchain includes one or more hierarchical governance strategies, and the delegated terminal selects one hierarchical governance strategy as needed.

13. The method according to claim 11, characterized in that, The method further includes: One or more of the blockchain governance delegation request, the delegation termination request, and the delegation change request include a signature of the delegation terminal private key; And / or, The blockchain governance trustee request includes the signature of the private key of the trustee terminal.

14. The method according to claim 1, 2, or 6, characterized in that, The method further includes: The current governance status is synchronized from the blockchain, including the various governance terminals that currently hold voting rights, as well as one or more blockchain governance decisions they hold.

15. A blockchain-based delegated governance system, characterized in that, The blockchain deploys on-chain governance smart contracts, and the governance system also includes a blockchain governance delegation terminal and one or more blockchain governance delegation terminals, wherein: The delegated terminal is configured to generate a blockchain governance delegated request and upload it to the blockchain. The delegated request includes a delegated governance strategy, which indicates the delegated rules for delegating one or more voting rights for governance decisions to one or more blockchain governance delegated terminals. The entrusted terminal is configured to synchronize the entrusted governance strategy from the blockchain, generate a blockchain governance entrusted request and upload it to the blockchain, wherein the entrusted request includes a proposed entrusted governance decision, which is the entrusted governance decision in which the entrusted terminal agrees to receive voting rights; The blockchain is configured to execute the smart contract, verify the entrusted request based on the delegated governance strategy, and generate the entrusted result.

16. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-14.

17. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-14.

Images