CN112950201A - Node management method and related device applied to block chain system - Google Patents
Node management method and related device applied to block chain system Download PDFInfo
- Publication number
- CN112950201A CN112950201A CN202110180263.5A CN202110180263A CN112950201A CN 112950201 A CN112950201 A CN 112950201A CN 202110180263 A CN202110180263 A CN 202110180263A CN 112950201 A CN112950201 A CN 112950201A
- Authority
- CN
- China
- Prior art keywords
- node
- request
- real
- cross
- name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 189
- 238000012545 processing Methods 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 12
- 238000000034 method Methods 0.000 claims description 9
- 230000000694 effects Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000004146 energy storage Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/33—User authentication using certificates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
Abstract
The application discloses a node management method applied to a block chain system, which relates to the technical field of block chains, and comprises the following steps: when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; judging whether the real-name digital certificate is legal or not; if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote; and if the number of votes in the voting result reaches the target number, allowing the node to manage the request. Based on the technical scheme of this application, can effectively improve the security of block chain.
Description
Technical Field
The present invention relates to the field of blockchain technologies, and in particular, to a node management method and a related apparatus for a blockchain system.
Background
With the development of the era, the blockchain technology has been paid more and more attention, and how to reasonably manage the nodes in the blockchain system has become the focus of research in the field.
In the prior art, no special node management method exists for a blockchain system including a cross-chain structure, and only corresponding management operations (such as adding members having a cross-chain service function, reducing members having a cross-chain service function, or updating information of members having a cross-chain service function) can be performed on members having a cross-chain service function in the blockchain system through third-party software, which violates the principle of decentralization of the blockchain technology, and cannot determine whether an issuing party of a corresponding node management request is legal, thereby reducing the security of the blockchain.
Disclosure of Invention
The application discloses a node management method and a related device applied to a block chain system, which can effectively improve the safety of a block chain.
In order to achieve the above technical effect, a first aspect of the present application provides a node management method applied to a blockchain system, where the blockchain system includes: the relay chain comprises more than one relay node, and each relay node is respectively connected with one node of each service chain;
the node management method comprises the following steps:
when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; the request node is a relay node of a member sending the node management request, the node management request is used for requesting corresponding processing to the corresponding member, and one member comprises the relay node and a node connected with the relay node;
judging whether the real-name digital certificate is legal or not;
if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote;
and if the number of votes voted in the voting result reaches the target number, allowing the node to manage the request.
Based on the first aspect of the present application, in a first possible implementation manner, when the node management request is a join request, the allowing the node management request includes: determining the request node and the node connected with the request node as the nodes contained in a cross-chain member, and writing the nodes into a cross-chain member list; wherein, the cross-chain member list comprises nodes contained by each cross-chain member;
when the node management request is an exit request, the allowing the node management request includes: determining the request node and the node connected with the request node as nodes contained in non-cross-chain members, and deleting the nodes from the cross-chain member list;
when the node management request is an update request, the allowing the node management request includes: and updating the information of the cross-chain member corresponding to the request node in the cross-chain member list based on the updating request.
Based on the first possible implementation manner of the first aspect of the present application, in a second possible implementation manner, before determining a real-name address of a requesting node based on the node management request, the node management method further includes:
judging whether the request node is a node of the cross-chain member;
when the node management request is the join request, the determining a real-name address of the requesting node based on the node management request includes:
if the requesting node is not a node of the cross-link member, determining a real-name system address of the requesting node based on the node management request;
after the determining whether the requesting node is a node of the cross-link member, the node management method further includes:
and if the request node is a node of the cross-link member, rejecting the join request.
Based on the second possible implementation manner of the first aspect of the present application, in a third possible implementation manner, when the node management request is the exit request or the update request, the determining a real-name address of the requesting node based on the node management request includes:
determining a real-name address of the requesting node based on the exit request or the update request if the requesting node is a node of the cross-link member;
after the determining whether the requesting node is a node of the cross-link member, the node management method further includes:
and if the requesting node is not a node of the cross-link member, rejecting the exit request or the update request.
Based on the first aspect of the present application or the first, second, or third possible implementation manner of the first aspect of the present application, in a fourth possible implementation manner, each of the relay nodes is configured with a real-name address, one of the real-name addresses corresponds to one of the real-name digital certificates, and the real-name digital certificate is a digital certificate that includes real-name identity information of the corresponding node.
Based on the first aspect of the present application or the first, second, or third possible implementation manner of the first aspect of the present application, in a fifth possible implementation manner, after determining whether the real-name digital certificate is legal, the node management method further includes:
and if the real-name digital certificate is illegal, rejecting the node management request.
Based on the first aspect of the present application or the first, second, or third possible implementation manner of the first aspect of the present application, in a sixth possible implementation manner, after the triggering the voting of the relay nodes of all current cross-link members, the node management method further includes:
and if the number of votes voted in the voting result does not reach the target number, rejecting the node management request.
A second aspect of the present application provides a node management apparatus applied to a blockchain system, where the blockchain system includes: the relay chain comprises more than one relay node, and each relay node is respectively connected with one node of each service chain;
the node management apparatus includes:
a determination unit configured to: when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; the request node is a relay node of a member sending the node management request, the node management request is used for requesting corresponding processing to the corresponding member, and one member comprises the relay node and a node connected with the relay node;
a judging unit, configured to judge whether the real-name digital certificate is legal;
a processing unit to: if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote; and if the number of votes voted in the voting result reaches the target number, allowing the node to manage the request.
A third aspect of the present application provides a node management apparatus applied to a blockchain system, where the blockchain system includes: a relay chain and one or more service chains, wherein the relay chain includes one or more relay nodes, each of the relay nodes is connected to a node of each of the service chains, and the node management apparatus includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the node management method according to the first aspect or any one of the possible implementation manners of the first aspect when executing the computer program.
A fourth aspect of the present application provides a computer-readable storage medium, which stores a computer program that, when executed by a processor, implements the steps of the node management method mentioned in the first aspect or any one of the possible implementations of the first aspect.
It can be seen from the above that the technical scheme of this application includes: when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; judging whether the real-name digital certificate is legal or not; if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote; and if the number of votes in the voting result reaches the target number, allowing the node to manage the request. Based on the technical scheme of the application, whether the corresponding real-name digital certificate is legal or not can be determined based on the node management request received by the intelligent contract of the cross-link service, if the corresponding real-name digital certificate is legal, voting is performed to determine whether the node management request is allowed or not, the node management request sent by the relay node of the cross-link member with illegal identity information can be avoided being responded, the decentralized effect of the block link can be ensured by adopting a mode that the intelligent contract of the cross-link service responds to the node management request, and the safety of the block link is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed for the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic flowchart illustrating an embodiment of a node management method applied to a blockchain system according to the present invention;
FIG. 2 is a block chain system according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an embodiment of a node management device applied to a blockchain system according to the present invention;
fig. 4 is a schematic structural diagram of a node management apparatus applied to a blockchain system according to another embodiment of the present disclosure.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
The technical solutions in the embodiments of the present application are clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application, but the present application may be practiced in other ways than those described herein, and it will be apparent to those of ordinary skill in the art that the present application is not limited by the specific embodiments disclosed below.
Example one
The present application provides a node management method applied to a blockchain system, where the blockchain system includes: the relay chain comprises more than one relay node, and each relay node is respectively connected with one node of each service chain;
as shown in fig. 1, the node management method includes:
step 101, when receiving a node management request based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address;
the request node is a relay node of a member sending the node management request, the node management request is used for requesting corresponding processing to the corresponding member, and one member comprises the relay node and a node connected with the relay node;
in an embodiment of the application, a member comprises: a relay node and a node connected to the relay node and located on each service chain, wherein each node of a member may specifically be a host/device controlled by a company/group, based on the structure of the blockchain system, a member can establish contact with each service chain through the relay node, and the members authenticated as cross-chain members can implement required cross-chain actions (such as performing cross-chain transactions) through the structure; each relay node is respectively provided with a preset program for enabling cross-chain transaction between nodes connected with the relay node on each service chain.
Optionally, each relay node is configured with a real-name address, one real-name address corresponds to one real-name digital certificate, and the real-name digital certificate is a digital certificate including real-name identity information of the corresponding node.
Specifically, the node management request may be a transaction including a real-name address and a corresponding real-name digital certificate, the corresponding real-name digital certificate may be obtained through querying the real-name address in the transaction, and the queried real-name digital certificate includes real-name identity information of the corresponding member.
in this embodiment, the node other than the request node in the relay link may verify the real-name digital certificate based on the inter-link service intelligent contract to determine whether the real-name digital certificate is legal;
103, if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote;
in this embodiment, if it is determined that the real-name digital certificate is valid through the judgment in the previous step, it may be determined that the real-name identity information of the member corresponding to the real-name digital certificate included in the real-name digital certificate is real and valid information, and then, the current relay nodes of all cross-link members may be continuously triggered to perform voting, so as to determine whether to allow the node management request.
Optionally, after the determining determines whether the real-name digital certificate is legal, the node management method further includes:
and if the real-name digital certificate is illegal, rejecting the node management request.
And 104, if the number of votes approved in the voting result reaches the target number, allowing the node to manage the request.
In this embodiment of the application, the target number may be a preset number, or may be a number determined according to the number of current members across links, and when the number of votes approved reaches the target number, the node management request may be allowed to perform a corresponding operation on the member that sends the node management request (for example, authenticate the member as a member across links, cancel authentication of a member across links, or update information of the member).
Optionally, when the node management request is a join request, the allowing the node management request includes: determining the request node and the node connected with the request node as the nodes contained in a cross-chain member, and writing the nodes into a cross-chain member list; wherein, the cross-chain member list comprises nodes contained by each cross-chain member;
when the node management request is an exit request, the allowing the node management request includes: determining the request node and the node connected with the request node as nodes contained in non-cross-chain members, and deleting the nodes from the cross-chain member list;
when the node management request is an update request, the allowing the node management request includes: and updating the information of the cross-chain member corresponding to the request node in the cross-chain member list based on the updating request.
Specifically, the cross-chain member list includes information of all current cross-chain members and nodes included in each cross-chain member, and the list may be a data file in a storage space (e.g., a state of an intelligent contract) corresponding to the cross-chain service intelligent contract.
Further, before determining the real-name address of the requesting node based on the node management request, the node management method further includes:
judging whether the request node is a node of the cross-chain member;
when the node management request is the join request, the determining a real-name address of the requesting node based on the node management request includes:
if the requesting node is not a node of the cross-link member, determining a real-name system address of the requesting node based on the node management request;
after the determining whether the requesting node is a node of the cross-link member, the node management method further includes:
and if the request node is a node of the cross-link member, rejecting the join request.
Further, when the node management request is the exit request or the update request, the determining a real-name address of the requesting node based on the node management request includes:
determining a real-name address of the requesting node based on the exit request or the update request if the requesting node is a node of the cross-link member;
after the determining whether the requesting node is a node of the cross-link member, the node management method further includes:
and if the requesting node is not a node of the cross-link member, rejecting the exit request or the update request.
Optionally, after the triggering of voting by the relay node of all current cross-link members, the node management method further includes:
and if the number of votes voted in the voting result does not reach the target number, rejecting the node management request.
Optionally, after the triggering of voting by the relay node of all current cross-link members, the node management method further includes:
based on the current number of cross-chain members, a target number is determined.
Further, the determining the target number based on the current number of cross-chain members includes:
the current number of members across the chain is divided by two to obtain a quotient, and then the quotient is rounded up to obtain the target number.
In a practical application scenario, as shown in fig. 2, the blockchain system includes an a service chain, a B service chain, a C service chain, and a relay chain, where the a service chain includes: a first service node a, a second service node a and a third service node a, where the service chain B includes: a first B service node, a second B service node, and a third B service node, where the C service chain includes: a first C service node, a second C service node, and a third C service node, where the relay chain includes: a first relay node, a second relay node, and a third relay node, wherein the first relay node is connected to the first a service node, the first B service node, and the first C service node, the second relay node is connected to the second a service node, the second B service node, and the second C service node, and the third relay node is connected to the third a service node, the third B service node, and the third C service node, respectively, wherein the first relay node, the first a service node, the first B service node, and the first C service node belong to a first member, the second relay node, the second a service node, the second B service node, and the second C service node belong to a second member, and the third relay node, the third a service node, the third C service node, and the third relay node, The third B service node and the third C service node belong to a third member, the first member and the second member are both cross-link members capable of performing cross-link transactions among the a service link, the B service link and the C service link, and the third member is not a cross-link member;
the third member may send a join request to the relay link based on the third relay node (the node management request at this time is the join request);
the relay chain can extract a real-name address of the third relay node of the number of the third relay nodes from the joining request based on a cross-chain service intelligent contract, and then obtain a corresponding real-name digital certificate based on the real-name address, wherein the real-name digital certificate comprises real-name identity information of a third member;
verifying the real-name digital certificate to judge whether the real-name digital certificate is legal or not;
if the real-name digital certificate is legal, the real-name identity information contained in the real-name digital certificate can be determined to be legal information, and the first relay node, the second relay node and the third relay node can be triggered to vote for the join request;
and if the number of votes in the voting result reaches the target number, allowing the joining request.
In another practical application scenario, the structure of the blockchain system is the same as that of the previous practical application scenario, but the first member, the second member and the third member are cross-chain members;
the third member may send an exit request to the relay chain based on the third relay node (the node management request at this time is the exit request);
the relay chain can extract a real-name address of the third relay node from the quit request based on a cross-chain service intelligent contract, and then obtain a corresponding real-name digital certificate based on the real-name address, wherein the real-name digital certificate comprises real-name identity information of a third member;
verifying the real-name digital certificate to judge whether the real-name digital certificate is legal or not;
if the real-name digital certificate is legal, the real-name identity information contained in the real-name digital certificate can be determined to be legal information, and the first relay node, the second relay node and the third relay node can be triggered to vote for the quitting request;
and if the number of votes in the voting result reaches the target number, allowing the quitting request.
Specifically, in an actual application scenario, the service chain a, the service chain B, and the service chain C may be three service chains for performing the same or different service transactions, where the service may be an energy storage transaction related service or other types of services, and are not limited herein; the three service chains can be connected through the relay chain, the first member can be an enterprise A, the second member can be an enterprise B, and the third member can be an enterprise C;
for example, when the member a is a cross-link member and the member a wants to use the accounting data on the service chain a on the service chain B to settle the bill, the first service node a based on the member a can perform a downlink on the corresponding accounting data, and then the relay node a based on the member a and the corresponding cross-link service program can perform a relay, and the first service node B based on the member a can perform an uplink on the corresponding accounting data to store the corresponding accounting data in the service chain B; after the steps in the above example, the member a can use the accounting data on the service chain a on the service chain B; the above accounting data is only an example, and the data that the member a wants to use on the service chain B may also be other recorded data on the service chain a, may also be data of a transaction initiated by a node on the service chain a, and may be any other type of data, which is not limited herein, and the step of transmitting various types of data across the chain is the same as the step in the above example, and is not described herein again.
Optionally, the node management method further includes:
when a cross-chain member query request is received based on a cross-chain service intelligent contract, the current relevant information of all cross-chain members is output.
It can be seen from the above that the technical scheme of this application includes: when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; judging whether the real-name digital certificate is legal or not; if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote; and if the number of votes in the voting result reaches the target number, allowing the node to manage the request. Based on the technical scheme of the application, whether the corresponding real-name digital certificate is legal or not can be determined based on the node management request received by the intelligent contract of the cross-link service, if the corresponding real-name digital certificate is legal, voting is performed to determine whether the node management request is allowed or not, the node management request sent by the relay node of the cross-link member with illegal identity information can be avoided being responded, the decentralized effect of the block link can be ensured by adopting a mode that the intelligent contract of the cross-link service responds to the node management request, and the safety of the block link is improved.
Example two
The present application provides a node management apparatus applied to a blockchain system, where the blockchain system includes: the relay chain comprises more than one relay node, and each relay node is respectively connected with one node of each service chain;
as shown in fig. 3, the node management apparatus 30 includes:
a determining unit 301, configured to: when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; the request node is a relay node of a member sending the node management request, the node management request is used for requesting corresponding processing to the corresponding member, and one member comprises the relay node and a node connected with the relay node;
a determining unit 302, configured to determine whether the real-name digital certificate is legal;
a processing unit 303 for: if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote; and if the number of votes voted in the voting result reaches the target number, allowing the node to manage the request.
Optionally, the processing unit 303 is specifically configured to: when the node management request is a joining request, determining the request node and a node connected with the request node as nodes contained in a cross-chain member, and writing the nodes into a cross-chain member list; wherein, the cross-chain member list comprises nodes contained by each cross-chain member;
when the node management request is an exit request, determining the request node and a node connected with the request node as nodes contained in non-cross-chain members, and deleting the nodes from the cross-chain member list;
and when the node management request is an update request, updating information of the cross-chain member corresponding to the request node in the cross-chain member list based on the update request.
Further, the determining unit 301 is further specifically configured to:
judging whether the request node is a node of the cross-chain member;
determining a real-name address of the requesting node based on the node management request if the requesting node is not a node of the cross-link member when the node management request is the join request; and if the request node is a node of the cross-link member, rejecting the join request.
Further, the determining unit 301 is specifically further configured to: determining a real-name address of the requesting node based on the logout request or the update request if the requesting node is a node of the cross-link member when the node management request is the logout request or the update request; and if the requesting node is not a node of the cross-link member, rejecting the exit request or the update request.
Optionally, each relay node is configured with a real-name address, one real-name address corresponds to one real-name digital certificate, and the real-name digital certificate is a digital certificate including real-name identity information of the corresponding node.
Optionally, the processing unit 303 is further specifically configured to:
and if the real-name digital certificate is illegal, rejecting the node management request.
Optionally, the processing unit 303 is further specifically configured to:
and if the number of votes voted in the voting result does not reach the target number, rejecting the node management request.
It can be seen from the above that the technical scheme of this application includes: when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; judging whether the real-name digital certificate is legal or not; if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote; and if the number of votes in the voting result reaches the target number, allowing the node to manage the request. Based on the technical scheme of the application, whether the corresponding real-name digital certificate is legal or not can be determined based on the node management request received by the intelligent contract of the cross-link service, if the corresponding real-name digital certificate is legal, voting is performed to determine whether the node management request is allowed or not, the node management request sent by the relay node of the cross-link member with illegal identity information can be avoided being responded, the decentralized effect of the block link can be ensured by adopting a mode that the intelligent contract of the cross-link service responds to the node management request, and the safety of the block link is improved.
EXAMPLE III
The present application also provides another node management apparatus applied to a blockchain system, where the blockchain system includes: as shown in fig. 4, a node management apparatus in an embodiment of the present invention includes: a memory 401, a processor 402, and a computer program stored in the memory 401 and executable on the processor 402, wherein: the memory 401 is used to store software programs and modules, the processor 402 executes various functional applications and data processing by operating the software programs and modules stored in the memory 401, and the memory 401 and the processor 402 are connected by a bus 403.
Specifically, the processor 402 implements the following steps by running the above-mentioned computer program stored in the memory 401:
when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; the request node is a relay node of a member sending the node management request, the node management request is used for requesting corresponding processing to the corresponding member, and one member comprises the relay node and a node connected with the relay node;
judging whether the real-name digital certificate is legal or not;
if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote;
and if the number of votes voted in the voting result reaches the target number, allowing the node to manage the request.
Assuming that the node management request is a join request, in a second possible implementation manner based on the first possible implementation manner, the allowing the node management request includes: determining the request node and the node connected with the request node as the nodes contained in a cross-chain member, and writing the nodes into a cross-chain member list; wherein, the cross-chain member list comprises nodes contained by each cross-chain member;
when the node management request is an exit request, the allowing the node management request includes: determining the request node and the node connected with the request node as nodes contained in non-cross-chain members, and deleting the nodes from the cross-chain member list;
when the node management request is an update request, the allowing the node management request includes: and updating the information of the cross-chain member corresponding to the request node in the cross-chain member list based on the updating request.
In a third possible implementation manner based on the second possible implementation manner, before determining the real-name address of the requesting node based on the node management request, the node management method further includes:
judging whether the request node is a node of the cross-chain member;
when the node management request is the join request, the determining a real-name address of the requesting node based on the node management request includes:
if the requesting node is not a node of the cross-link member, determining a real-name system address of the requesting node based on the node management request;
after the determining whether the requesting node is a node of the cross-link member, the node management method further includes:
and if the request node is a node of the cross-link member, rejecting the join request.
In a fourth possible implementation manner based on the third possible implementation manner, when the node management request is the logout request or the update request, the determining a real-name address of the requesting node based on the node management request includes:
determining a real-name address of the requesting node based on the exit request or the update request if the requesting node is a node of the cross-link member;
after the determining whether the requesting node is a node of the cross-link member, the node management method further includes:
and if the requesting node is not a node of the cross-link member, rejecting the exit request or the update request.
In a fifth possible implementation manner based on the first, second, third, or fourth possible implementation manner, each relay node is configured with a real-name address, one real-name address corresponds to one real-name digital certificate, and the real-name digital certificate is a digital certificate containing real-name identity information of the corresponding node.
In a sixth possible implementation manner based on the first, second, third, or fourth possible implementation manner, after the determining whether the real-name digital certificate is legitimate, the node management method further includes:
and if the real-name digital certificate is illegal, rejecting the node management request.
In a seventh possible implementation manner based on the first, second, third, or fourth possible implementation manner, after the triggering the voting of the relay nodes of all current cross-link members, the node management method further includes:
and if the number of votes voted in the voting result does not reach the target number, rejecting the node management request.
It can be seen from the above that the technical scheme of this application includes: when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; judging whether the real-name digital certificate is legal or not; if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote; and if the number of votes in the voting result reaches the target number, allowing the node to manage the request. Based on the technical scheme of the application, whether the corresponding real-name digital certificate is legal or not can be determined based on the node management request received by the intelligent contract of the cross-link service, if the corresponding real-name digital certificate is legal, voting is performed to determine whether the node management request is allowed or not, the node management request sent by the relay node of the cross-link member with illegal identity information can be avoided being responded, the decentralized effect of the block link can be ensured by adopting a mode that the intelligent contract of the cross-link service responds to the node management request, and the safety of the block link is improved.
Example four
The present application also provides a computer readable storage medium having a computer program stored thereon, which when executed, can implement the steps provided by the above-described embodiments. Specifically, the computer program includes computer program code, which may be in one of a source code form, an object code form, an executable file or some intermediate form, and is not limited herein; the computer readable storage medium can be any entity or device capable of carrying the above computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium, and is not limited herein. It should be noted that the contents contained in the computer-readable storage medium can be increased or decreased as required by legislation and patent practice in the jurisdiction.
It can be seen from the above that the technical scheme of this application includes: when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; judging whether the real-name digital certificate is legal or not; if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote; and if the number of votes in the voting result reaches the target number, allowing the node to manage the request. Based on the technical scheme of the application, whether the corresponding real-name digital certificate is legal or not can be determined based on the node management request received by the intelligent contract of the cross-link service, if the corresponding real-name digital certificate is legal, voting is performed to determine whether the node management request is allowed or not, the node management request sent by the relay node of the cross-link member with illegal identity information can be avoided being responded, the decentralized effect of the block link can be ensured by adopting a mode that the intelligent contract of the cross-link service responds to the node management request, and the safety of the block link is improved.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned functions may be distributed as different functional units and modules according to needs, that is, the internal structure of the apparatus may be divided into different functional units or modules to implement all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
It should be noted that, the methods and the details thereof provided by the foregoing embodiments may be combined with the apparatuses and devices provided by the embodiments, which are referred to each other and are not described again.
Those of ordinary skill in the art would appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described apparatus/device embodiments are merely illustrative, and for example, the division of the above-described modules or units is only one logical functional division, and the actual implementation may be implemented by another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed.
The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A node management method applied to a blockchain system, wherein the blockchain system comprises: the relay chain comprises more than one relay node, and each relay node is respectively connected with one node of each service chain;
the node management method comprises the following steps:
when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; the request node is a relay node of a member sending the node management request, the node management request is used for requesting corresponding processing on the corresponding member, and one member comprises the relay node and a node connected with the relay node;
judging whether the real-name digital certificate is legal or not;
if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote;
and if the number of votes voted in the voting result reaches the target number, allowing the node to manage the request.
2. The node management method according to claim 1, wherein when the node management request is a join request, the allowing the node management request comprises: determining the request node and the node connected with the request node as the nodes contained in a cross-chain member, and writing the nodes into a cross-chain member list; wherein, the cross-chain member list comprises nodes contained by each cross-chain member;
when the node management request is an exit request, the allowing the node management request includes: determining the request node and the nodes connected with the request node as nodes contained in non-cross-chain members, and deleting the nodes from the cross-chain member list;
when the node management request is an update request, the allowing the node management request includes: and updating the information of the cross-chain members corresponding to the request nodes in the cross-chain member list based on the updating request.
3. The node management method according to claim 2, wherein before said determining a real-name address of a requesting node based on the node management request, the node management method further comprises:
judging whether the request node is a node of the cross-chain member;
when the node management request is the join request, the determining the real-name address of the requesting node based on the node management request includes:
if the request node is not a node of the cross-chain member, determining a real-name system address of the request node based on the node management request;
after the determining whether the requesting node is a node of the cross-chain member, the node management method further includes:
and if the request node is a node of the cross-chain member, rejecting the join request.
4. The node management method according to claim 3, wherein when the node management request is the exit request or the update request, the determining a real-name address of the requesting node based on the node management request comprises:
if the requesting node is a node of the cross-link member, determining a real-name system address of the requesting node based on the quit request or the update request;
after the determining whether the requesting node is a node of the cross-chain member, the node management method further includes:
and if the requesting node is not a node of the cross-chain member, rejecting the exit request or the update request.
5. The node management method according to any one of claims 1 to 4, wherein each of the relay nodes is configured with a real-name address, and one of the real-name addresses corresponds to one of the real-name digital certificates, and the real-name digital certificate is a digital certificate containing real-name identity information of the corresponding node.
6. The node management method according to any one of claims 1 to 4, wherein after the determining whether the real-name digital certificate is legitimate, the node management method further includes:
and if the real-name digital certificate is illegal, rejecting the node management request.
7. The node management method according to any one of claims 1 to 4, wherein after the triggering of voting by the relay nodes of all current cross-chain members, the node management method further comprises:
and if the number of votes voted in the voting result does not reach the target number, rejecting the node management request.
8. A node management apparatus applied to a blockchain system, the blockchain system comprising: the relay chain comprises more than one relay node, and each relay node is respectively connected with one node of each service chain;
the node management apparatus includes:
a determination unit configured to: when a node management request is received based on a cross-chain service intelligent contract, determining a real-name system address of a request node based on the node management request, and then determining a corresponding real-name system digital certificate based on the real-name system address; the request node is a relay node of a member sending the node management request, the node management request is used for requesting corresponding processing on the corresponding member, and one member comprises the relay node and a node connected with the relay node;
the judging unit is used for judging whether the real-name digital certificate is legal or not;
a processing unit to: if the real-name digital certificate is legal, triggering the relay nodes of all current cross-link members to vote; and if the number of votes voted in the voting result reaches the target number, allowing the node to manage the request.
9. A node management apparatus applied to a blockchain system, the blockchain system comprising: the node management device comprises a memory and a processor, wherein the memory stores computer programs, and the processor realizes the steps of the method of any one of claims 1 to 7 when executing the computer programs.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110180263.5A CN112950201B (en) | 2021-02-08 | 2021-02-08 | Node management method and related device applied to block chain system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110180263.5A CN112950201B (en) | 2021-02-08 | 2021-02-08 | Node management method and related device applied to block chain system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112950201A true CN112950201A (en) | 2021-06-11 |
| CN112950201B CN112950201B (en) | 2023-10-27 |
Family
ID=76245057
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110180263.5A Active CN112950201B (en) | 2021-02-08 | 2021-02-08 | Node management method and related device applied to block chain system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112950201B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113347050A (en) * | 2021-08-04 | 2021-09-03 | 支付宝(杭州)信息技术有限公司 | Method and device for block chain node to exit node set |
| CN113783899A (en) * | 2021-11-12 | 2021-12-10 | 中国信息通信研究院 | Node exit method and blockchain |
| WO2023011241A1 (en) * | 2021-08-06 | 2023-02-09 | 支付宝(杭州)信息技术有限公司 | Registration of blockchain node to node set |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170061398A1 (en) * | 2014-06-19 | 2017-03-02 | Jim Austin Joseph | Cryptographic currency block chain based voting system |
| CN109067553A (en) * | 2018-10-17 | 2018-12-21 | 杭州趣链科技有限公司 | A kind of management method of the block chain distributed certificate based on intelligent contract |
| CN110517043A (en) * | 2019-08-13 | 2019-11-29 | 上海威尔立杰网络科技发展有限公司 | A method of realizing block chain transaction system of real name |
| CN110766554A (en) * | 2019-09-29 | 2020-02-07 | 南京金宁汇科技有限公司 | Intelligent contract consensus method, system and storage medium based on multi-centralization management |
| CN110868308A (en) * | 2018-08-28 | 2020-03-06 | 傲为信息技术(江苏)有限公司 | Block chain network access method and system |
| CN110992035A (en) * | 2019-12-13 | 2020-04-10 | 中国工商银行股份有限公司 | Block chain link point management method, device and system |
| CN111369730A (en) * | 2020-02-20 | 2020-07-03 | 腾讯科技（深圳）有限公司 | Voting processing method and device based on block chain |
| CN111741114A (en) * | 2020-06-24 | 2020-10-02 | 陈鹏 | System, method and equipment capable of monitoring cross-chain interaction based on block chain |
| CN111753334A (en) * | 2020-07-02 | 2020-10-09 | 卓尔智联(武汉)研究院有限公司 | Method and device for verifying consistency of data across alliance chains and electronic equipment |
| CN112291327A (en) * | 2020-10-23 | 2021-01-29 | 中化能源股份有限公司 | Block link point management method and device and electronic equipment |
-
2021
- 2021-02-08 CN CN202110180263.5A patent/CN112950201B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170061398A1 (en) * | 2014-06-19 | 2017-03-02 | Jim Austin Joseph | Cryptographic currency block chain based voting system |
| CN110868308A (en) * | 2018-08-28 | 2020-03-06 | 傲为信息技术(江苏)有限公司 | Block chain network access method and system |
| CN109067553A (en) * | 2018-10-17 | 2018-12-21 | 杭州趣链科技有限公司 | A kind of management method of the block chain distributed certificate based on intelligent contract |
| CN110517043A (en) * | 2019-08-13 | 2019-11-29 | 上海威尔立杰网络科技发展有限公司 | A method of realizing block chain transaction system of real name |
| CN110766554A (en) * | 2019-09-29 | 2020-02-07 | 南京金宁汇科技有限公司 | Intelligent contract consensus method, system and storage medium based on multi-centralization management |
| CN110992035A (en) * | 2019-12-13 | 2020-04-10 | 中国工商银行股份有限公司 | Block chain link point management method, device and system |
| CN111369730A (en) * | 2020-02-20 | 2020-07-03 | 腾讯科技（深圳）有限公司 | Voting processing method and device based on block chain |
| CN111741114A (en) * | 2020-06-24 | 2020-10-02 | 陈鹏 | System, method and equipment capable of monitoring cross-chain interaction based on block chain |
| CN111753334A (en) * | 2020-07-02 | 2020-10-09 | 卓尔智联(武汉)研究院有限公司 | Method and device for verifying consistency of data across alliance chains and electronic equipment |
| CN112291327A (en) * | 2020-10-23 | 2021-01-29 | 中化能源股份有限公司 | Block link point management method and device and electronic equipment |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113347050A (en) * | 2021-08-04 | 2021-09-03 | 支付宝(杭州)信息技术有限公司 | Method and device for block chain node to exit node set |
| WO2023011241A1 (en) * | 2021-08-06 | 2023-02-09 | 支付宝(杭州)信息技术有限公司 | Registration of blockchain node to node set |
| CN113783899A (en) * | 2021-11-12 | 2021-12-10 | 中国信息通信研究院 | Node exit method and blockchain |
| CN113783899B (en) * | 2021-11-12 | 2022-03-08 | 中国信息通信研究院 | Node exit method and blockchain system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112950201B (en) | 2023-10-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112950201B (en) | Node management method and related device applied to block chain system | |
| CN109670801B (en) | Digital encryption money transfer method for block chain | |
| CN110958111B (en) | Block chain-based identity authentication mechanism of electric power mobile terminal | |
| CN110855777B (en) | Node management method and device based on block chain | |
| CN107908979B (en) | Method and electronic device for configuration and endorsement in blockchain | |
| KR20170013305A (en) | Secure wireless charging | |
| CN109388957B (en) | Block chain-based information transfer method, device, medium and electronic equipment | |
| CN105160226A (en) | Method, apparatus and system of user identity verification and smart home | |
| CN114553540B (en) | Zero trust-based Internet of things system, data access method, device and medium | |
| CN110619222A (en) | Authorization processing method, device, system and medium based on block chain | |
| CN107256479B (en) | Transaction mode classification execution method and device | |
| CN112448956A (en) | Authority processing method and device of short message verification code and computer equipment | |
| CN113890739B (en) | Cross-blockchain authentication method and device, electronic equipment and medium | |
| CN111182527B (en) | OTA (over the air) firmware upgrading method and device, terminal equipment and storage medium thereof | |
| CN114244568A (en) | Security access control method, device and equipment based on terminal access behavior | |
| CN112037055B (en) | Transaction processing method, device, electronic equipment and readable storage medium | |
| CN113328854A (en) | Service processing method and system based on block chain | |
| CN113132976A (en) | Differential protection method and system for distributed wireless communication power distribution network | |
| CN112202564A (en) | Transaction transfer method and device, electronic equipment and readable storage medium | |
| CN113055886B (en) | Terminal authentication method, system, server and medium in edge computing network | |
| CN113890751A (en) | Method, apparatus and readable storage medium for controlling voting of alliance link authority | |
| CN111369246B (en) | Calling authentication method and device of intelligent contract, electronic equipment and storage medium | |
| CN106487776B (en) | Method, network entity and system for protecting machine type communication equipment | |
| CN112801662A (en) | Business link access management method and system based on intelligent block chain contract | |
| CN111694899A (en) | Blacklist sharing method and system based on block chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |