Method, device and electronic device for dynamic node access in alliance chain

Abstract

The present application discloses a method, device and electronic device for dynamic node access in a consortium chain. In the technical solution of the embodiments of the present application, if a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain is monitored, all existing blockchain nodes in the consortium chain receive the node dynamic access request initiated by the dynamic blockchain node to be added to the consortium chain, and add the timestamp of the received node dynamic access request to the node dynamic access request; each existing blockchain node in the consortium chain verifies the received node dynamic access request annotated with the reception timestamp to generate a corresponding node dynamic access request authentication result message; based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the consortium chain, it is determined whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the consortium chain, thereby effectively realizing dynamic expansion of the consortium chain.

Description

Technical Field

[0001] The present application relates to the technical field of alliance chains, and in particular to a method, device, and electronic device for dynamically accessing nodes in an alliance chain. Background Art

[0002] Blockchain, due to its unique traceability and immutability, has gained widespread adoption and is a popular platform for data storage and sharing. Consortium chains, among other blockchains, offer fast processing speeds and low transaction costs due to their relatively small number of nodes. However, precisely because of their small number of nodes, consortium chains are prone to congestion. Therefore, achieving dynamic capacity expansion for consortium chains has become a pressing technical challenge to meet the needs of demanding interactive scenarios. Summary of the Invention

[0003] Based on the above problems, the embodiments of the present application provide a method, device and electronic device for dynamic access of nodes in a consortium chain.

[0004] The embodiments of this application disclose the following technical solutions:

[0005] According to a first aspect of an embodiment of the present application, a method for dynamic node access in a consortium chain is provided, characterized by comprising:

[0006] Determining whether a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain is monitored in real time;

[0007] If a node dynamic access request is detected from a dynamic blockchain node to be added to the alliance chain, all existing blockchain nodes in the alliance chain receive the node dynamic access request from the dynamic blockchain node to be added to the alliance chain, and append the timestamp of the node dynamic access request to the node dynamic access request;

[0008] Each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with the reception timestamp to generate a corresponding node dynamic access request authentication result message;

[0009] According to the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, determine whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0010] Optionally, it is characterized in that each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with the receiving timestamp to generate a corresponding node dynamic access request authentication result message, including: obtaining the subject information of the node dynamic access request received by each existing blockchain node in the alliance chain; for each existing blockchain node in the alliance chain, using the subject information of the node dynamic access request received as the key of a key-value pair, and using the receiving timestamp as the value of the key-value pair to generate multiple key-value pairs; based on the multiple key-value pairs, verifying the received node dynamic access request annotated with the receiving timestamp to generate a corresponding node dynamic access request authentication result message.

[0011] Optionally, it is characterized in that the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain is used to determine whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the alliance chain, including: generating a node dynamic access request authentication result message based on all existing blockchain nodes in the alliance chain;

[0012] The node dynamic access request authentication result message is generated to generate a node dynamic access request authentication map; according to the node dynamic access request authentication map, it is judged whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0013] Optionally, it is characterized in that the method for dynamic node access in a consortium chain further includes: in response to allowing the dynamic blockchain node to be added to the consortium chain and the dynamic blockchain node is successfully added to the consortium chain, the dynamic blockchain node generates a data synchronization request to synchronize the data stored on all existing blockchain nodes in the consortium chain to the dynamic blockchain node.

[0014] Optionally, it is characterized in that the method for dynamic access of nodes in a consortium chain further includes: in response to successfully synchronizing the data stored on all existing blockchain nodes in the consortium chain to the dynamic blockchain node, the dynamic blockchain node generates a consensus identity request and broadcasts it to all existing blockchain nodes in the consortium chain, so that all existing blockchain nodes in the consortium chain perform trustworthy authentication on the dynamic blockchain node, generate a trustworthy value of the dynamic blockchain node, and determine whether to assign a consensus identity to the dynamic blockchain node.

[0015] Optionally, it is characterized in that the method for dynamic node access in a consortium chain further includes: in response to assigning a consensus identity to the dynamic blockchain node, recalculating the number of nodes in the consortium chain and generating a new consortium chain view, and updating it to the blockchain node with the master node identity in the consortium chain.

[0016] Optionally, it is characterized in that the method for dynamic node access in a consortium chain further includes: viewing the new consortium chain view Figure 1 Consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced.

[0017] Optionally, it is characterized in that the new alliance chain view is viewed Figure 1 The consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced, including: performing a trusted calculation on all blockchain nodes in the alliance chain to obtain a trust value; visually analyzing the new alliance chain view based on the trust value; Figure 1 Consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced.

[0018] Optionally, it is characterized in that the new alliance chain view is viewed according to the trust value. Figure 1 The consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced, including: generating a trust binary tree based on all the trust values, wherein the distance between adjacent tree nodes along the trunk direction from the root to the top of the tree in the trust binary tree represents the approximation of the trust values ​​from small to large; comparing the trust binary tree with the trust value of the master node to determine whether the blockchain node with the master node identity needs to be replaced; if the trust value of the master node is greater than the height of the trust binary tree, then do not replace the blockchain node with the master node identity; otherwise, the blockchain node with the master node identity needs to be replaced.

[0019] According to a second aspect of an embodiment of the present application, a device for dynamic node access in a consortium chain is provided, characterized by comprising:

[0020] The first program unit is configured to determine whether a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain is monitored in real time;

[0021] The second program unit is configured to, upon monitoring a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain, cause all existing blockchain nodes in the consortium chain to receive the node dynamic access request initiated by the dynamic blockchain node to be added to the consortium chain, and append a timestamp of receipt of the node dynamic access request to the node dynamic access request;

[0022] A third program unit is configured to enable each existing blockchain node in the consortium chain to verify the received node dynamic access request annotated with the reception timestamp, so as to generate a corresponding node dynamic access request authentication result message;

[0023] The fourth program unit is used to determine whether to respond to the node dynamic access request based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, so as to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0024] Optionally, it is characterized in that the third program unit is further used to: obtain the subject information of the node dynamic access request received by each existing blockchain node in the alliance chain; for each existing blockchain node in the alliance chain, use the subject information of the node dynamic access request received as the key of the key-value pair, and use the receiving timestamp as the value of the key-value pair to generate multiple key-value pairs; based on the multiple key-value pairs, verify the received node dynamic access request annotated with the receiving timestamp to generate a corresponding node dynamic access request authentication result message.

[0025] Optionally, it is characterized in that the fourth program unit is further used to: generate a node dynamic access request authentication map based on the node dynamic access request authentication result messages generated by all existing blockchain nodes in the alliance chain; and determine whether to respond to the node dynamic access request based on the node dynamic access request authentication map to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0026] Optionally, the device is characterized in that the device further includes: a first data generation unit, for, in response to allowing the dynamic blockchain node to be added to the alliance chain and the dynamic blockchain node being successfully added to the alliance chain, the dynamic blockchain node generates a data synchronization request to synchronize the data stored on all existing blockchain nodes in the alliance chain to the dynamic blockchain node.

[0027] Optionally, the device is characterized in that the device also includes: a second data generation unit, which is used to generate a consensus identity request in response to successfully synchronizing the data stored on all existing blockchain nodes in the alliance chain to the dynamic blockchain node, and broadcast it to all existing blockchain nodes in the alliance chain, so that all existing blockchain nodes in the alliance chain can perform trustworthy authentication on the dynamic blockchain node and generate a trustworthy value of the dynamic blockchain node to determine whether to assign a consensus identity to the dynamic blockchain node.

[0028] Optionally, it is characterized in that the device also includes: a third data generation unit, which is used to recalculate the number of nodes in the alliance chain and generate a new alliance chain view in response to assigning a consensus identity to the dynamic blockchain node, and update it to the blockchain node with the master node identity in the alliance chain.

[0029] Optionally, the device further comprises: a judgment generating unit for visually analyzing the new alliance chain view; Figure 1 Consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced.

[0030] Optionally, it is characterized in that the judgment generation unit is further used to: perform trust calculation on all blockchain nodes in the alliance chain to obtain a trust value; and visually analyze the new alliance chain view based on the trust value. Figure 1 Consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced.

[0031] Optionally, it is characterized in that the judgment generation unit is further used to: generate a trustworthiness binary tree based on all the trustworthiness values, wherein the distance between adjacent tree nodes along the trunk direction from the root to the top of the tree in the trustworthiness binary tree represents the approximation of the trustworthiness values ​​from small to large; compare the trustworthiness binary tree with the trustworthiness value of the master node to determine whether it is necessary to replace the blockchain node with the master node identity; if the trustworthiness value of the master node is greater than the height of the trustworthiness binary tree, do not replace the blockchain node with the master node identity; otherwise, the blockchain node with the master node identity needs to be replaced.

[0032] According to a third aspect of the embodiments of the present application, an electronic device is provided, characterized in that it includes a memory and a processor, wherein an executable program is stored on the memory, and when the processor runs the executable program, the following is performed:

[0033] step:

[0034] Determining whether a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain is monitored in real time;

[0035] If a node dynamic access request is detected from a dynamic blockchain node to be added to the alliance chain, all existing blockchain nodes in the alliance chain receive the node dynamic access request from the dynamic blockchain node to be added to the alliance chain, and append the timestamp of the node dynamic access request to the node dynamic access request;

[0036] Each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with the reception timestamp to generate a corresponding node dynamic access request authentication result message;

[0037] According to the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, determine whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0038] In the technical solution of the embodiment of the present application, it is determined whether a node dynamic access request initiated by a dynamic blockchain node to be added to the alliance chain is monitored in real time; if a node dynamic access request initiated by a dynamic blockchain node to be added to the alliance chain is monitored, all existing blockchain nodes in the alliance chain receive the node dynamic access request initiated by the dynamic blockchain node to be added to the alliance chain, and add the timestamp of receiving the node dynamic access request to the node dynamic access request; each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with the reception timestamp to generate a corresponding node dynamic access request authentication result message; based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, it is determined whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the alliance chain, thereby effectively realizing dynamic expansion of the alliance chain. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0040] Figure 1 This is a flowchart of a method for dynamically accessing nodes in a consortium chain according to an embodiment of the present application;

[0041] Figure 2 This is a structural diagram of a device for dynamic node access in a consortium chain according to an embodiment of the present application;

[0042] Figure 3 This is another structural diagram of a device for dynamic node access in a consortium chain according to an embodiment of the present application;

[0043] Figure 4 This is a schematic diagram of the structure of an electronic device in an embodiment of the present application;

[0044] Figure 5 Schematic diagram of the hardware structure of the electronic device in the embodiment of the present application. DETAILED DESCRIPTION

[0045] The implementation of any technical solution in the embodiments of the present application does not necessarily require achieving all of the above advantages at the same time.

[0046] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts shall fall within the scope of protection of the present invention.

[0047] In the technical solution of the embodiment of the present application, it is determined whether a node dynamic access request initiated by a dynamic blockchain node to be added to the alliance chain is monitored in real time; if a node dynamic access request initiated by a dynamic blockchain node to be added to the alliance chain is monitored, all existing blockchain nodes in the alliance chain receive the node dynamic access request initiated by the dynamic blockchain node to be added to the alliance chain, and add the timestamp of receiving the node dynamic access request to the node dynamic access request; each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with the reception timestamp to generate a corresponding node dynamic access request authentication result message; based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, it is determined whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the alliance chain, thereby effectively realizing dynamic expansion of the alliance chain.

[0048] Figure 1 This is a flow chart of a method for dynamically accessing nodes in a consortium chain according to an embodiment of the present application; Figure 1 As shown, it includes:

[0049] S101. Determine whether a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain is monitored in real time;

[0050] In this embodiment, a monitoring node may be set to execute step S101.

[0051] S102. If a node dynamic access request is detected from a dynamic blockchain node to be added to the consortium chain, all existing blockchain nodes in the consortium chain receive the node dynamic access request from the dynamic blockchain node to be added to the consortium chain, and append a timestamp of when the node dynamic access request was received to the node dynamic access request.

[0052] In this embodiment, the specific form of the timestamp is not limited. For example, the timestamp is encrypted and then appended to the node dynamic access request.

[0053] S103. Each existing blockchain node in the consortium chain verifies the received node dynamic access request annotated with the reception timestamp to generate a corresponding node dynamic access request authentication result message;

[0054] S104. Determine whether to respond to the node dynamic access request based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, so as to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0055] Optionally, each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with the receiving timestamp to generate a corresponding node dynamic access request authentication result message, including: obtaining the subject information of the node dynamic access request received by each existing blockchain node in the alliance chain; for each existing blockchain node in the alliance chain, using the subject information of the node dynamic access request received as the key of a key-value pair, and using the receiving timestamp as the value of the key-value pair to generate multiple key-value pairs; based on the multiple key-value pairs, verifying the received node dynamic access request annotated with the receiving timestamp to generate a corresponding node dynamic access request authentication result message.

[0056] In this embodiment, the resource space for data storage can be saved based on the key-value pair, and at the same time, the management of the dynamic access request of the node can be efficiently implemented.

[0057] Optionally, judging whether to respond to the node dynamic access request based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain to determine whether to allow the dynamic blockchain node to be added to the alliance chain includes: generating a node dynamic access request authentication graph based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain; judging whether to respond to the node dynamic access request based on the node dynamic access request authentication graph to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0058] In this embodiment, the node dynamic access request authentication map can quickly determine whether to respond to the node dynamic access request, thereby improving the efficiency of algorithm execution.

[0059] Optionally, the method for dynamic node access in a consortium chain further includes: in response to allowing the dynamic blockchain node to be added to the consortium chain and the dynamic blockchain node is successfully added to the consortium chain, the dynamic blockchain node generates a data synchronization request to synchronize the data stored on all existing blockchain nodes in the consortium chain to the dynamic blockchain node.

[0060] In this embodiment, based on the data synchronization request generated by the dynamic blockchain node, the data stored on all existing blockchain nodes in the alliance chain can be synchronized to the dynamic blockchain node in real time.

[0061] Optionally, the method for dynamic node access in a consortium chain further includes: in response to successfully synchronizing the data stored on all existing blockchain nodes in the consortium chain to the dynamic blockchain node, the dynamic blockchain node generates a consensus identity request and broadcasts it to all existing blockchain nodes in the consortium chain, so that all existing blockchain nodes in the consortium chain perform trustworthy authentication on the dynamic blockchain node, generate a trustworthy value for the dynamic blockchain node, and determine whether to assign a consensus identity to the dynamic blockchain node.

[0062] In this embodiment, the trust value of the dynamic blockchain node is generated by performing trustworthy certification on the dynamic blockchain node, thereby ensuring that the nodes participating in the consensus are trustworthy, and further ensuring the security of the data.

[0063] Optionally, the method for dynamic node access in a consortium chain further includes: in response to assigning a consensus identity to the dynamic blockchain node, recalculating the number of nodes in the consortium chain and generating a new consortium chain view, and updating it to the blockchain node with the master node identity in the consortium chain.

[0064] In this embodiment, by responding to the assignment of a consensus identity to the dynamic blockchain node, the dynamic update of the alliance chain view can be achieved, thereby ensuring the timeliness of the alliance chain view based on which the next consensus is based.

[0065] Optionally, the method for dynamically accessing nodes in a consortium chain further includes: viewing the new consortium chain view. Figure 1 Consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced.

[0066] Optionally, the new alliance chain view is viewed Figure 1 The consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced, including: performing a trusted calculation on all blockchain nodes in the alliance chain to obtain a trust value; visually analyzing the new alliance chain view based on the trust value; Figure 1 Consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced.

[0067] In this embodiment, the new alliance chain view is viewed based on the trust value. Figure 1 Consistency verification ensures the authority of the blockchain node with master node identity and improves the security of node dynamic accounting.

[0068] Optionally, the new alliance chain view is viewed based on the trust value. Figure 1 The consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced, including: generating a trust binary tree based on all the trust values, wherein the distance between adjacent tree nodes along the trunk direction from the root to the top of the tree in the trust binary tree represents the approximation of the trust values ​​from small to large; comparing the trust binary tree with the trust value of the master node to determine whether the blockchain node with the master node identity needs to be replaced; if the trust value of the master node is greater than the height of the trust binary tree, then do not replace the blockchain node with the master node identity; otherwise, the blockchain node with the master node identity needs to be replaced.

[0069] In this embodiment, based on the comparison between the trustworthiness binary tree and the trustworthiness value of the master node, it can be quickly determined whether the blockchain node with the master node identity needs to be replaced.

[0070] Figure 2 This is a structural diagram of a node dynamic access device in a consortium chain according to an embodiment of the present application; Figure 2 As shown,

[0071] It includes:

[0072] The first program unit 201 is used to determine whether a node dynamic access request initiated by a dynamic blockchain node to be added to the alliance chain is monitored in real time;

[0073] The second program unit 202 is configured to, upon monitoring a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain, cause all existing blockchain nodes in the consortium chain to receive the node dynamic access request initiated by the dynamic blockchain node to be added to the consortium chain, and append a timestamp of when the node dynamic access request was received to the node dynamic access request;

[0074] The third program unit 203 is configured to enable each existing blockchain node in the consortium chain to verify the received node dynamic access request annotated with the receiving timestamp, so as to generate a corresponding node dynamic access request authentication result message;

[0075] The fourth program unit 204 is used to determine whether to respond to the node dynamic access request based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, so as to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0076] Optionally, the third program unit 203 is further used to: obtain the subject information of the node dynamic access request received by each existing blockchain node in the alliance chain; for each existing blockchain node in the alliance chain, use the subject information of the node dynamic access request received as the key of the key-value pair, and use the receiving timestamp as the value of the key-value pair to generate multiple key-value pairs; based on the multiple key-value pairs, verify the received node dynamic access request annotated with the receiving timestamp to generate a corresponding node dynamic access request authentication result message.

[0077] Optionally, the fourth program unit 204 is further used to: generate a node dynamic access request authentication map based on the node dynamic access request authentication result messages generated by all existing blockchain nodes in the alliance chain; and determine whether to respond to the node dynamic access request based on the node dynamic access request authentication map to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0078] Figure 3 This is a structural diagram of a node dynamic access device in a consortium chain according to an embodiment of the present application; Figure 3 As shown in the above Figure 2 Based on the embodiment, the characteristics of the node dynamic access device in the alliance chain of this embodiment are:

[0079] Optionally, the device also includes: a first data generation unit 205, which is used to generate a data synchronization request in response to allowing the dynamic blockchain node to be added to the alliance chain and the dynamic blockchain node is successfully added to the alliance chain, so as to synchronize the data stored on all existing blockchain nodes in the alliance chain to the dynamic blockchain node.

[0080] Optionally, the device further includes: a second data generation unit 206, configured to generate a consensus identity request in response to successfully synchronizing the data stored on all existing blockchain nodes in the alliance chain to the dynamic blockchain node, and broadcast it to all existing blockchain nodes in the alliance chain, so that all existing blockchain nodes in the alliance chain can perform trustworthy authentication on the dynamic blockchain node, generate a trustworthy value for the dynamic blockchain node, and determine whether to assign a consensus identity to the dynamic blockchain node.

[0081] Optionally, the device also includes: a third data generation unit 207, which is used to recalculate the number of nodes in the alliance chain and generate a new alliance chain view in response to assigning a consensus identity to the dynamic blockchain node, and update it to the blockchain node with the master node identity in the alliance chain.

[0082] Optionally, the device further includes: a judgment generating unit 208, configured to perform visual analysis on the new alliance chain view. Figure 1 Consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced.

[0083] Optionally, the judgment generation unit 208 is further configured to:

[0084] Trust calculation obtains a trust value; based on the trust value, the new alliance chain view is viewed. Figure 1 Consistency verification is performed to determine whether the blockchain node with the master node identity needs to be replaced.

[0085] Optionally, the judgment generation unit 208 is further used to: generate a trustworthiness binary tree based on all the trustworthiness values, wherein the distance between adjacent tree nodes along the trunk direction from the root to the top of the tree in the trustworthiness binary tree represents the approximation of the trustworthiness values ​​from small to large; compare the trustworthiness binary tree with the trustworthiness value of the master node to determine whether it is necessary to replace the blockchain node with the master node identity; if the trustworthiness value of the master node is greater than the height of the trustworthiness binary tree, do not replace the blockchain node with the master node identity; otherwise, the blockchain node with the master node identity needs to be replaced.

[0086] Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application; Figure 4 As shown, it includes a memory 301 and a processor 302. The memory stores an executable program. When the processor runs the executable program, the following steps are performed:

[0087] Determining whether a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain is monitored in real time;

[0088] If a node dynamic access request is detected from a dynamic blockchain node to be added to the alliance chain, all existing blockchain nodes in the alliance chain receive the node dynamic access request from the dynamic blockchain node to be added to the alliance chain, and append the timestamp of the node dynamic access request to the node dynamic access request;

[0089] Each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with the reception timestamp to generate a corresponding node dynamic access request authentication result message;

[0090] According to the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, determine whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

[0091] Figure 5 Schematic diagram of the hardware structure of the electronic device in the embodiment of the present application; Figure 5 As shown, the hardware structure of the electronic device may include: the electronic device 400 includes a computing unit 401, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 402 or a computer program loaded from a storage unit 408 into a random access memory (RAM) 403. Various programs and data required for the operation of the device 400 can also be stored in the RAM 403. The computing unit 401, ROM 402, and RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0092] Multiple components within electronic device 400 are connected to I / O interface 405, including an input unit 406, an output unit 407, a storage unit 408, and a communication unit 409. Input unit 406 can be any type of device capable of inputting information into electronic device 400. Input unit 406 can receive input numeric or character information and generate key input signals related to user settings and / or function control of the electronic device. Output unit 407 can be any type of device capable of presenting information and may include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. Storage unit 408 may include, but is not limited to, a magnetic disk or an optical disk. Communication unit 409 allows electronic device 400 to exchange information / data with other devices via computer networks such as the Internet and / or various telecommunication networks and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver and / or a chipset, such as a Bluetooth™ device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.

[0093] The computing unit 401 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 401 performs the various methods and processes described above. For example, in some embodiments, the above steps may be implemented as a computer software program that is tangibly included in a machine-readable medium, such as a storage unit 408. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 400 via the ROM 402 and / or the communication unit 409. In some embodiments, the computing unit 401 may be configured to perform the above steps in any other appropriate manner (e.g., by means of firmware).

[0094] The electronic devices of the embodiments of the present application exist in various forms, including but not limited to:

[0095] (1) Mobile communication devices: These devices are characterized by their mobile communication capabilities and are primarily designed to provide voice and data communications. These terminals include smartphones (e.g., iPhones), multimedia phones, feature phones, and low-end phones.

[0096] (2) Ultra-mobile personal computer devices: These devices fall under the category of personal computers, have computing and processing capabilities, and generally also have mobile Internet access. These terminals include PDAs, MIDs, and UMPCs, such as the iPad.

[0097] (3) Portable entertainment devices: These devices can display and play multimedia content. These devices include audio and video players (such as iPods), handheld game consoles, e-books, smart toys, and portable car navigation devices.

[0098] (4) Server: A device that provides computing services. The server consists of a processor 410, a hard disk, memory, a system bus, etc. The server is similar to a general computer architecture, but because it needs to provide highly reliable services, it has higher requirements in terms of processing power, stability, reliability, security, scalability, and manageability.

[0099] (5) Other electronic devices with data interaction functions.

[0100] It should be noted that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments. The device and system embodiments described above are merely schematic, wherein the modules described as separate components may or may not be physically separated, and the components indicated as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. A person of ordinary skill in the art can understand and implement it without paying any creative work.

[0101] The above is merely one specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for dynamic node access in a consortium chain, characterized in that: include: Determining whether a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain is monitored in real time; If a node dynamic access request is detected from a dynamic blockchain node to be added to the alliance chain, all existing blockchain nodes in the alliance chain receive the node dynamic access request from the dynamic blockchain node to be added to the alliance chain, and append the timestamp of the node dynamic access request to the node dynamic access request; Each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with a reception timestamp to generate a corresponding node dynamic access request authentication result message; According to the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, determine whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

2. The method for dynamic node access in a consortium chain according to claim 1, characterized in that: Each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with a receiving timestamp to generate a corresponding node dynamic access request authentication result message, including: obtaining the subject information of the node dynamic access request received by each existing blockchain node in the alliance chain; for each existing blockchain node in the alliance chain, using the subject information of the node dynamic access request received as the key of a key-value pair, and using the receiving timestamp as the value of the key-value pair to generate multiple key-value pairs; based on the multiple key-value pairs, verifying the received node dynamic access request annotated with the receiving timestamp to generate a corresponding node dynamic access request authentication result message.

3. The method for dynamic node access in a consortium chain according to claim 1, characterized in that: The determining whether to respond to the node dynamic access request based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain to determine whether to allow the dynamic blockchain node to be added to the alliance chain includes: generating a node dynamic access request authentication graph based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain; and determining whether to respond to the node dynamic access request based on the node dynamic access request authentication graph to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

4. The method for dynamic node access in a consortium chain according to claim 1, characterized in that: The method also includes: in response to allowing the dynamic blockchain node to be added to the alliance chain and the dynamic blockchain node is successfully added to the alliance chain, the dynamic blockchain node generates a data synchronization request to synchronize data stored on all existing blockchain nodes in the alliance chain to the dynamic blockchain node.

5. The method for dynamic node access in a consortium chain according to claim 4, characterized in that: The method also includes: in response to successfully synchronizing the data stored on all existing blockchain nodes in the alliance chain to the dynamic blockchain node, the dynamic blockchain node generates a consensus identity request and broadcasts it to all existing blockchain nodes in the alliance chain, so that all existing blockchain nodes in the alliance chain can perform trustworthy authentication on the dynamic blockchain node and generate a trustworthy value for the dynamic blockchain node to determine whether to assign a consensus identity to the dynamic blockchain node.

6. The method for dynamic node access in a consortium chain according to claim 5, characterized in that: The method also includes: in response to assigning a consensus identity to the dynamic blockchain node, recalculating the number of nodes in the alliance chain and generating a new alliance chain view, and updating it to the blockchain node with the master node identity in the alliance chain.

7. The method for dynamic node access in a consortium chain according to claim 6, characterized in that: The method also includes: performing view consistency verification on the new alliance chain view to determine whether the blockchain node with the master node identity needs to be replaced.

8. The method for dynamic node access in a consortium chain according to claim 7, characterized in that: The performing view consistency verification on the new consortium chain view to determine whether the blockchain node with the master node identity needs to be replaced includes: performing trusted calculation on all blockchain nodes in the consortium chain to obtain a trustworthiness value; and performing view consistency verification on the new consortium chain view based on the trustworthiness value to determine whether the blockchain node with the master node identity needs to be replaced.

9. The method for dynamic node access in a consortium chain according to claim 8, characterized in that: The method further comprises: performing view consistency verification on the new alliance chain view based on the trust value to determine whether the blockchain node with the master node identity needs to be replaced, including: generating a trust binary tree based on all the trust values, wherein the distance between adjacent tree nodes along the trunk direction from the root to the top of the tree in the trust binary tree represents the approximation of the trust value from small to large; comparing the trust binary tree with the trust value of the master node to determine whether the blockchain node with the master node identity needs to be replaced; if the trust value of the master node is greater than the height of the trust binary tree, then the blockchain node with the master node identity does not need to be replaced; otherwise, the blockchain node with the master node identity needs to be replaced.

10. A device for dynamically accessing nodes in a consortium chain, characterized in that: include: The first program unit is configured to determine whether a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain is monitored in real time; The second program unit is configured to, upon monitoring a node dynamic access request initiated by a dynamic blockchain node to be added to the consortium chain, cause all existing blockchain nodes in the consortium chain to receive the node dynamic access request initiated by the dynamic blockchain node to be added to the consortium chain, and append a timestamp of receipt of the node dynamic access request to the node dynamic access request; A third program unit is configured to enable each existing blockchain node in the consortium chain to verify the received node dynamic access request annotated with a reception timestamp, so as to generate a corresponding node dynamic access request authentication result message; The fourth program unit is used to determine whether to respond to the node dynamic access request based on the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, so as to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

11. The device for dynamic node access in a consortium chain according to claim 10, characterized in that: The third program unit is further configured to: obtain subject information of a node dynamic access request received by each existing blockchain node in the consortium chain; for each existing blockchain node in the consortium chain, use the subject information of the node dynamic access request received by the node as a key of a key-value pair and use the reception timestamp as a value of the key-value pair to generate multiple key-value pairs; The received node dynamic access request annotated with the receiving timestamp is verified according to the multiple key-value pairs to generate a corresponding node dynamic access request authentication result message.

12. The device for dynamic node access in a consortium chain according to claim 10, characterized in that: The fourth program unit is further used to: generate a node dynamic access request authentication map based on the node dynamic access request authentication result messages generated by all existing blockchain nodes in the alliance chain; and determine whether to respond to the node dynamic access request based on the node dynamic access request authentication map to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

13. The device for dynamic node access in a consortium chain according to claim 10, characterized in that: The device also includes: a first data generation unit, configured to, in response to allowing the dynamic blockchain node to be added to the alliance chain and the dynamic blockchain node being successfully added to the alliance chain, generate a data synchronization request by the dynamic blockchain node to synchronize the data stored on all existing blockchain nodes in the alliance chain to the dynamic blockchain node.

14. The device for dynamic node access in a consortium chain according to claim 13, characterized in that: The device also includes: a second data generation unit, configured to, in response to successfully synchronizing the data stored on all existing blockchain nodes in the alliance chain to the dynamic blockchain node, generate a consensus identity request by the dynamic blockchain node, and broadcast it to all existing blockchain nodes in the alliance chain, so that all existing blockchain nodes in the alliance chain can perform trustworthy authentication on the dynamic blockchain node, generate a trustworthy value for the dynamic blockchain node, and determine whether to assign a consensus identity to the dynamic blockchain node.

15. The device for dynamic node access in a consortium chain according to claim 14, characterized in that: The device also includes: a third data generation unit, which is used to recalculate the number of nodes in the alliance chain and generate a new alliance chain view in response to assigning a consensus identity to the dynamic blockchain node, and update it to the blockchain node with the master node identity in the alliance chain.

16. The device for dynamic node access in a consortium chain according to claim 15, characterized in that: The device also includes: a judgment generation unit, which is used to perform view consistency verification on the new alliance chain view and determine whether it is necessary to replace the blockchain node with the master node identity.

17. The device for dynamic node access in a consortium chain according to claim 16, characterized in that: The judgment generation unit is further used to: perform trusted calculation on all blockchain nodes in the alliance chain to obtain a trustworthiness value; and perform view consistency verification on the new alliance chain view based on the trustworthiness value to determine whether it is necessary to replace the blockchain node with the master node identity.

18. The device for dynamic node access in a consortium chain according to claim 16, characterized in that: The judgment generation unit is further configured to: generate a trustworthiness binary tree based on all trustworthiness values, wherein the distance between adjacent tree nodes along the trunk direction from the root to the top of the tree in the trustworthiness binary tree represents the approximation of the trustworthiness values ​​from small to large; and compare the trustworthiness binary tree with the trustworthiness value of the master node to determine whether the blockchain node having the master node identity needs to be replaced; If the trust value of the master node is greater than the height of the trust binary tree, do not replace the blockchain node with the master node identity; otherwise, the blockchain node with the master node identity needs to be replaced.

19. An electronic device, characterized in that: The system comprises a memory and a processor, wherein an executable program is stored in the memory, and the processor performs the following steps when running the executable program: Determine whether a node dynamic access request initiated by a dynamic blockchain node to be added to the alliance chain is monitored in real time; If a node dynamic access request is detected from a dynamic blockchain node to be added to the alliance chain, all existing blockchain nodes in the alliance chain receive the node dynamic access request from the dynamic blockchain node to be added to the alliance chain, and append the timestamp of the node dynamic access request to the node dynamic access request; Each existing blockchain node in the alliance chain verifies the received node dynamic access request annotated with a reception timestamp to generate a corresponding node dynamic access request authentication result message; According to the node dynamic access request authentication result message generated by all existing blockchain nodes in the alliance chain, determine whether to respond to the node dynamic access request to determine whether to allow the dynamic blockchain node to be added to the alliance chain.

Images