CN116384997A - DID contract management method, DID contract management system, electronic device and readable storage medium - Google Patents

DID contract management method, DID contract management system, electronic device and readable storage medium Download PDF

Info

Publication number
CN116384997A
CN116384997A CN202310275696.8A CN202310275696A CN116384997A CN 116384997 A CN116384997 A CN 116384997A CN 202310275696 A CN202310275696 A CN 202310275696A CN 116384997 A CN116384997 A CN 116384997A
Authority
CN
China
Prior art keywords
signature information
account
node
target
contract
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.)
Pending
Application number
CN202310275696.8A
Other languages
Chinese (zh)
Inventor
王耿
曹崇瑞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Netease Hangzhou Network Co Ltd
Original Assignee
Netease Hangzhou Network Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Netease Hangzhou Network Co Ltd filed Critical Netease Hangzhou Network Co Ltd
Priority to CN202310275696.8A priority Critical patent/CN116384997A/en
Publication of CN116384997A publication Critical patent/CN116384997A/en
Pending legal-status Critical Current

Links

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/3825—Use of electronic 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/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • 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
    • G06Q20/4014—Identity check for transactions
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • 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
    • G06Q20/4014—Identity check for transactions
    • G06Q20/40145—Biometric identity checks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0861—Network architectures or network communication protocols for network security for authentication of entities using biometrical features, e.g. fingerprint, retina-scan

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Signal Processing (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The embodiment of the application discloses a DID contract management method, a system, electronic equipment and a computer readable storage medium, wherein the method receives a second account address sent by a target account node to be added into a target DID contract through an account node, signs first transaction content containing the second account address, and obtains first signature information; the first signature information is sent to the target account node so as to trigger the target account node to sign second transaction content containing the first signature information, second signature information is obtained, and the second signature information is sent to the account node; receiving second signature information sent by a target account node, and sending the first signature information and the second signature information to an intelligent contract node; the intelligent contract node receives the first signature information and the second signature information, and introduces a second account address for the target DID contract based on the first signature information and the second signature information. The embodiment of the application can improve the security of the account address when the account address is added into the DID contract.

Description

DID contract management method, DID contract management system, electronic device and readable storage medium
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a DID contract management method, a system, an electronic device, and a computer readable storage medium.
Background
Under the wave of the internet, the application of blockchain technology in life of people is becoming more and more widespread, and intelligent contracts are generally deployed on blockchains to satisfy corresponding transactions, for example, a rights shareable DID (Decentralized Identity ) contract between different accounts is deployed on blockchains.
At present, if an account address is added to a DID contract, the signature held by the account address is obtained, and since the signature is a fixed signature for random information, the signature is easy to be induced by a hacker, so that the signature is used to share the right of the account to which the account address corresponding to the signature belongs, and the security of the account address added to the DID contract is low.
Disclosure of Invention
The embodiment of the application provides a DID contract management method, a DID contract management system, electronic equipment and a computer readable storage medium, which can improve the security of account addresses when the account addresses join in a DID contract.
In a first aspect, an embodiment of the present application provides a DID contract management method applied to a blockchain, where the blockchain includes an account node and an intelligent contract node, a first account address of the account node is added to a target DID contract of the intelligent contract node, the target DID contract is configured to store a plurality of account addresses, and account information is shared between account addresses in the target DID contract, and the method includes:
The account node receives a second account address sent by a target account node to be added into the target DID contract, signs first transaction content containing the second account address, and obtains first signature information;
the account node sends the first signature information to the target account node to trigger the target account node to sign second transaction content containing the first signature information to obtain second signature information, and sends the second signature information to the account node;
the account node receives the second signature information sent by the target account node and sends the first signature information and the second signature information to the intelligent contract node;
the smart contract node receives the first signature information and the second signature information and introduces the second account address for the target DID contract based on the first signature information and the second signature information.
In a second aspect, an embodiment of the present application further provides a DID contract management system applied to a blockchain, where the blockchain includes an account node and an intelligent contract node, a first account address of the account node has been added to a target DID contract of the intelligent contract node, the target DID contract is configured to store a plurality of account addresses, and account information is shared between account addresses in the target DID contract, and the system includes:
The first signature module is applied to the account node, and is used for receiving a second account address sent by a target account node to be added into the target DID contract, and signing first transaction content containing the second account address to obtain first signature information;
the second signature module is applied to the account node, and is used for sending the first signature information to the target account node so as to trigger the target account node to sign second transaction content containing the first signature information to obtain second signature information, and sending the second signature information to the account node;
the information sending module is applied to the account node, and is used for receiving the second signature information sent by the target account node and sending the first signature information and the second signature information to the intelligent contract node;
and the address introducing module is applied to the intelligent contract node, and is used for receiving the first signature information and the second signature information and introducing the second account address for the target DID contract based on the first signature information and the second signature information.
In a third aspect, embodiments of the present application further provide an electronic device, including a memory storing a plurality of instructions; the processor loads instructions from the memory to perform steps in any of the DID contract management methods provided by the embodiments of the present application.
In a fourth aspect, embodiments of the present application further provide a computer readable storage medium storing a plurality of instructions adapted to be loaded by a processor to perform steps in any of the DID contract management methods provided by the embodiments of the present application.
The embodiment of the application is applied to a blockchain, the blockchain comprises an account node and an intelligent contract node, a first account address of the account node is added to a target DID contract of the intelligent contract node, the target DID contract is configured to store a plurality of account addresses, account information is shared among the account addresses in the target DID contract, the account node receives a second account address sent by a target account node to be added to the target DID contract, and a signature is carried out on first transaction content containing the second account address to obtain first signature information; the account node sends the first signature information to the target account node so as to inform the target account node that the target account node is about to apply address introduction to the intelligent contract node for the target account node, so that the target account node is triggered to sign second transaction content containing the first signature information to obtain second signature information, and the second signature information is sent to the account node, namely the target account node authorizes the account node to apply address introduction to the intelligent contract node; the account node receives the second signature information sent by the target account node and sends the first signature information and the second signature information to the intelligent contract node; the intelligent contract node receives the first signature information and the second signature information, and introduces the second account address for the target DID contract based on the first signature information and the second signature information, so that the security of adding the account address into the DID contract is improved as a whole.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic view of a scenario of a DID contract management method provided in an embodiment of the present application;
FIG. 2 is a flowchart illustrating an embodiment of a DID contract management method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a DID contract management system provided in an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
Before explaining the embodiments of the present application in detail, some terms related to the embodiments of the present application are explained.
Wherein in the description of embodiments of the present application, the terms "first," "second," and the like may be used herein to describe various concepts, but such concepts are not limited by these terms unless otherwise specified. These terms are only used to distinguish one concept from another. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Wherein, the blockchain: is a decentralized distributed database that consists of blocks one after the other. Each block holds certain information which is linked in a chain according to the time sequence of their respective generation.
Wherein, the blockchain node: refers to devices participating in the construction of a blockchain, such as personal computers, web servers, database servers, smartphones, etc., without limitation, e.g., each blockchain node on the blockchain may be deployed on one server or on a different server. Point-to-point communication can be performed between any two blockchain nodes on a blockchain, so that corresponding transactions, such as transactions of deploying intelligent contracts, updating stored data or generating new stored data, are realized.
It should be noted that, in the DID contract management method provided in the embodiment of the present application, corresponding steps may be executed by a blockchain node on a blockchain, that is, an account node, a target account node, and an intelligent contract node, which may be located on the same blockchain, and the target account node and the intelligent contract node may be located on the same blockchain, or may be located on different blockchains. Correspondingly, the DID contract management system provided in the embodiment of the present application may generally also include modules corresponding to the account node, the target account node, and the intelligent contract node.
The embodiment of the application provides a DID contract management method, a DID contract management system, electronic equipment and a computer readable storage medium. Specifically, the DID contract management method in the embodiment of the present application may be executed by an electronic device, that is, the account node and the intelligent contract node on the blockchain to which the DID contract management method in the embodiment of the present application is applied are respectively electronic devices, and the two may be located on the same electronic device or may be located on different electronic devices. The electronic device may be a terminal or a server. The terminal may be a terminal device such as a smart phone, a tablet computer, a notebook computer, a touch screen, a game console, a personal computer (PC, personal Computer), a personal digital assistant (Personal Digital Assistant, PDA), and the like, and the terminal may further include a client, which may be a game application client, a browser client carrying a game program, or an instant messaging client, and the like. The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligent platforms.
For example, as shown in fig. 1, the electronic device is illustrated by taking a terminal as an example, and the terminal 10 corresponding to the account node may receive a second account address sent by a target account node to be added to the target DID contract, sign a first transaction content including the second account address, and obtain first signature information; the first signature information is sent to the target account node to trigger the terminal 20 corresponding to the target account node to sign second transaction content containing the first signature information, so as to obtain second signature information, and the second signature information is sent to the account node; and receiving the second signature information sent by the target account node, and sending the first signature information and the second signature information to the intelligent contract node. The terminal 30 corresponding to the smart contract node may receive the first signature information and the second signature information, and may introduce the second account address for the target DID contract based on the first signature information and the second signature information.
Based on the above problems, embodiments of the present application provide a DID contract management method, system, electronic device, and computer readable storage medium, which can improve security when an account address joins a DID contract.
The following detailed description is provided with reference to the accompanying drawings. The following description of the embodiments is not intended to limit the preferred embodiments. Although a logical order is depicted in the flowchart, in some cases the steps shown or described may be performed in an order different than depicted in the figures.
In this embodiment, taking a terminal as an example for explanation, the present embodiment provides a DID contract management method applied to a blockchain, where the blockchain includes an account node and an intelligent contract node, a first account address of the account node is added to a target DID contract of the intelligent contract node, the target DID contract is configured to store a plurality of account addresses, and account information is shared between account addresses in the target DID contract, as shown in fig. 2, a specific flow of the DID contract management method may be as follows:
201. and the account node receives a second account address sent by a target account node to be added into the target DID contract, signs the first transaction content containing the second account address, and obtains first signature information.
The target account node is a node where an account address of a target account to be added in the target DID contract is located, and the account address to be added in the target DID contract is the second account address.
It will be appreciated that, in the above-described characteristics of the target DID contract, after the second account address of the target account is added to the target DID contract, the second account address may share account information, such as asset information, of other address accounts in the target DID contract, so as to implement sharing rights held by the other address accounts.
Illustratively, the target DID contract may be an aggregate wallet address DID contract.
It can be understood that, since the second account address is not currently in the target DID contract, if the second account address is to be requested from the target DID contract, the second account address needs to be introduced into the target DID contract according to the account address that has been added to the target DID contract, that is, the first account address, which is in the account node, that is, in this embodiment, the target account may request address addition to the target DID contract for the target account according to the account node to which the first account address that has been added to the target DID contract belongs.
In addition, in the process that the account node requests the target account to join the address in the target DID contract, if the target account node only sends the signature by using the private key to the account node to which the first account address belongs, the account node to which the first account address belongs initiates a transaction by using the private key of the first account address, so that the signature of the target account node and the related information of the signature are sent to the intelligent contract node, a great potential safety hazard exists, that is, a hacker can acquire the signature of the target account node by using the private key in a phishing manner, and based on the signature, the second account address of the target account node is added into the DID contract which can attack the user asset, that is, because account information can be shared between different account addresses in the target DID contract, the hacker can enjoy the rights of the account to which other account addresses in the target DID contract together with the target account by using the characteristics of the target DID contract, and thus the loss of the rights of the target account occurs.
In this embodiment, the account node is caused to obtain the first transaction content in advance based on the second account address required to be requested, and signs the first transaction content to obtain the first signature information, so that the security when the address joins the target DID contract is improved through the signature of the account node on the transaction content.
The first transaction content may further include a current transaction event, a block height when signing the first transaction content, a transaction number or a timestamp, etc., where the transaction event is description information of the current transaction and is used to indicate the current transaction; the transaction number is the total number of transactions performed by the account node under the current transaction, and the timestamp is used for indicating the time of the current transaction.
The first signature information may include the first transaction content and a signature performed on the first transaction content.
Specifically, when the account node signs the first transaction content including the second account address, the account node may sign the first transaction content based on a private key corresponding to the first account address corresponding to the account node.
In some embodiments, in order to improve security of the target DID contract, to avoid adding an inconsistent address to the target DID contract, identity verification may be performed on a target account node to which the second account address to be added in the target DID contract belongs, so as to ensure security of the target DID contract.
Specifically, before signing the first transaction content including the second account address, the method may further include: and the account node performs identity verification on the target account node based on the second account address to obtain an identity verification result, wherein the identity verification result comprises that the identity verification passes and the identity verification fails, and then the identity verification result is judged, if the identity verification passes, the first transaction content containing the second account address is signed, and if the identity verification fails, rejection information is sent to the target account node, and the rejection information can comprise the reason of the identity verification failure, so that the reminding of the target account node is realized.
Illustratively, the account node may perform identity verification on the target account node in a social manner.
202. The account node sends the first signature information to the target account node to trigger the target account node to sign second transaction content containing the first signature information to obtain second signature information, and sends the second signature information to the account node.
In this embodiment, the account node is prompted to sign the first transaction content, and the obtained first signature information is sent to the target account node, so as to implement the re-signature of the target account node, that is, the target account node performs further confirmation on the process that the account node is about to request the target DID contract for address joining, so as to ensure security, that is, the target account node signs the second transaction content including the first signature information, so as to obtain the second signature information that needs to be sent to the intelligent contract node by the account node, so as to improve security when the address joins the target DID contract.
The second transaction content may further include a current transaction event, a block height when signing the second transaction content, a transaction number or a timestamp, etc., where the transaction event is description information of the current transaction and is used to indicate the current transaction; the transaction number is the total number of transactions performed by the target account node under the current transaction, and the timestamp is used for indicating the time of the current transaction.
The second signature information may include the second transaction content and a signature performed on the second transaction content.
Specifically, when the target account node signs the second transaction content including the first signature information, the second transaction content may be signed based on a private key corresponding to a second account address corresponding to the target account node.
203. The account node receives the second signature information sent by the target account node, and sends the first signature information and the second signature information to the intelligent contract node.
In this embodiment, when the account node receives the second signature information signed by the target account node, the second signature information may be sent to the intelligent contract node by calling the DID contract function corresponding to the address introducing event through the private key corresponding to the first account address corresponding to the account node, so that the intelligent contract node performs corresponding processing based on the target DID contract deployed therein.
The address introducing event is the event of the current transaction, namely, the event of introducing the address of the second account into the target DID contract. It can be appreciated that different DID contract functions may correspond to different processing manners, so that the processing speed of the intelligent contract node may be increased by calling the DID contract function corresponding to the address import event.
204. The smart contract node receives the first signature information and the second signature information and introduces the second account address for the target DID contract based on the first signature information and the second signature information.
In this embodiment, after the smart contract node receives the first signature information and the second signature information, to ensure security, the smart contract node may perform verification based on the first signature information and the second signature information to obtain a verification result, and when the verification result meets a preset legal condition, the smart contract node introduces the second account address for the target DID contract based on the first signature information and the second signature information.
The plurality of addresses in the target DID contract may exist in the form of an address list, and the introducing the second account address for the target DID contract may include: and adding the second account address into an address list of the target DID contract.
In some embodiments, the introducing the second account address for the target DID contract based on the first signature information and the second signature information includes: verifying based on the first signature information and the second signature information; and when the verification is passed, introducing the second account address for the target DID contract.
In some embodiments, at least one verification manner may be designed when the validity verification is performed, so as to obtain a verification result corresponding to the at least one verification manner, where the verification result includes a verification passing result and a verification failure result, so that when the verification result of the at least one verification manner meets a preset legal condition, a subsequent process is performed.
The preset legal conditions may be all verification passing results, that is, when the verification results corresponding to at least one verification mode are all verification passing results, verification passing is performed; the preset legal conditions may also be a preset number of verification passing results, that is, when a preset number of verification results exist in the verification results corresponding to at least one verification mode as verification passing results, the verification passing results are verified, wherein the number of the verification modes is greater than or equal to the preset number; the preset legal conditions may also be a preset number of verification passing results with the highest priority, that is, the priority corresponding to each verification mode is set, so that when the verification result corresponding to the preset number of verification modes with the highest priority needs to be the verification passing result, verification passes.
In some embodiments, the first signature information may include the first transaction content, the second signature information may include the second transaction content, the first transaction content may further include a block height when signing the first transaction content, and the second transaction content may further include a block height when signing the second transaction content, so that a time difference between a time when the first signature information is explicitly generated and a time when the second signature information is generated is determined by the block height when signing the first transaction content and the block height when signing the second transaction content, so as to increase a cost required for hacking by limiting a time difference between the first signature information and the second signature information, thereby reducing a risk of hacking and improving security.
Specifically, the verifying based on the first signature information and the second signature information may include: calculating a first block height difference between the block height corresponding to the first transaction content and the block height corresponding to the second transaction content to judge the size between the first block height difference and a height threshold, if the first block height difference is smaller than or equal to a preset height threshold, determining that the verification passes, and if the first block height difference is larger than the height threshold, determining that the verification fails.
In some embodiments, the verifying based on the first signature information and the second signature information may further include: acquiring the block height during verification, wherein the block height during verification represents the block height at the current moment; and calculating a second block height difference value between the block height during verification and the block height corresponding to the second transaction content, wherein the second block height difference value represents the time difference between the moment of generating the second signature information and the current moment so as to limit the time difference between the current moment and the moment of generating the second signature information and ensure the safety. Specifically, the size between the second block height difference value and the height threshold value is judged, if the second block height difference value is smaller than or equal to the height threshold value, the verification is determined to pass, and if the second block height difference value is larger than the height threshold value, the verification is determined to fail.
In some embodiments, the above-mentioned intelligent contract node may further determine, by means of address restoration, whether the address of the current signature is consistent with the address in the signature content, or the address of the current signature is consistent with the address of the transmitted message, or whether the address in the signature content is consistent with the address of the transmitted message, so as to ensure security.
Specifically, the verifying based on the first signature information and the second signature information may include: and restoring a first target account address for signing the second transaction content based on the second signature information, and judging the first target account address, namely, because the first target account address is the signature of the target account node on the second transaction content, the first target account address is consistent with the second account address in the first transaction content, so that the first target account address is required to be judged to be consistent with the second account address in the first transaction content, if the first target account address is consistent with the second account address in the first transaction content, the verification is determined to pass, and if the first target account address is inconsistent with the second account address in the first transaction content, the verification is determined to fail.
Specifically, the verifying based on the first signature information and the second signature information may include: and restoring a second target account address for signing the first transaction content based on the first signature information, and judging along with the second target account address, namely, because the account node signs the first transaction content, the second target account address is consistent with the first account address of the account node, so that the second target account address is required to be judged to be consistent with the first account address of the account node, if the second target account address is consistent with the first account address of the account node, the verification is determined to pass, and if the second target account address is inconsistent with the first account address of the account node, the verification is determined to fail.
In some embodiments, the smart contract node may further verify whether the first account address of the account node is in a target DID contract of the smart contract node.
In some embodiments, the transaction content may further include a transaction number or a timestamp, so as to enable the smart contract node to verify the transaction information based on the transaction number or the timestamp, so as to prevent the re-protection attack.
As can be seen from the above, the embodiment of the present application is applied to a blockchain, where the blockchain includes an account node and an intelligent contract node, a first account address of the account node is added to a target DID contract of the intelligent contract node, the target DID contract is configured to store a plurality of account addresses, account information is shared between the account addresses in the target DID contract, the account node receives a second account address sent by a target account node to be added to the target DID contract, and signs a first transaction content including the second account address to obtain first signature information; the account node sends the first signature information to the target account node so as to inform the target account node that the target account node is about to apply address introduction to the intelligent contract node for the target account node, so that the target account node is triggered to sign second transaction content containing the first signature information to obtain second signature information, and the second signature information is sent to the account node, namely the target account node authorizes the account node to apply address introduction to the intelligent contract node; the account node receives the second signature information sent by the target account node and sends the first signature information and the second signature information to the intelligent contract node; the intelligent contract node receives the first signature information and the second signature information, and introduces the second account address for the target DID contract based on the first signature information and the second signature information, so that the security of adding the account address into the DID contract is improved as a whole.
In order to better implement the above method, the embodiment of the present application further provides a DID contract management system, where the DID contract management system may be specifically integrated in an electronic device, for example, a computer device, where the computer device may be a terminal, a server, or a device.
The terminal can be a mobile phone, a tablet personal computer, an intelligent Bluetooth device, a notebook computer, a personal computer and other devices; the server may be a single server or a server cluster composed of a plurality of servers.
For example, in this embodiment, taking a specific integration of a DID contract management system in a terminal as an example, the method of this embodiment will be described in detail, where this embodiment provides a DID contract management system applied to a blockchain, where the blockchain includes an account node and an intelligent contract node, a first account address of the account node is added to a target DID contract of the intelligent contract node, the target DID contract is configured to store a plurality of account addresses, and account information is shared between account addresses in the target DID contract, as shown in fig. 3, the DID contract management system may include:
the first signing module 301 is applied to the account node, and is configured to receive a second account address sent by a target account node to be added to the target DID contract, and sign a first transaction content including the second account address to obtain first signature information;
A second signature module 302, where the second signature module is applied to the account node, and the second signature module is configured to send the first signature information to the target account node, so as to trigger the target account node to sign a second transaction content containing the first signature information, obtain second signature information, and send the second signature information to the account node;
an information sending module 303, where the information sending module is applied to the account node, and the information sending module is configured to receive the second signature information sent by the target account node, and send the first signature information and the second signature information to the intelligent contract node;
the address introducing module 304 is applied to the smart contract node, and is configured to receive the first signature information and the second signature information, and introduce the second account address for the target DID contract based on the first signature information and the second signature information.
In some embodiments, the address introducing module 304 is specifically configured to:
verifying based on the first signature information and the second signature information;
And when the verification is passed, introducing the second account address for the target DID contract.
In some embodiments, the first signature information includes the first transaction content, the second signature information includes the second transaction content, the first transaction content further includes a block height when signing the first transaction content, and the second transaction content further includes a block height when signing the second transaction content; the address introducing module 304 is specifically configured to:
calculating a first block height difference between the block height corresponding to the first transaction content and the block height corresponding to the second transaction content;
and if the first block height difference value is smaller than or equal to a preset height threshold value, determining that the verification passes.
In some embodiments, the address introducing module 304 is specifically configured to:
acquiring the block height during verification;
calculating a second block height difference between the block height at the time of the verification and the block height corresponding to the second transaction content;
and if the second block height difference value is smaller than or equal to the height threshold value, determining that the verification passes.
In some embodiments, the address introducing module 304 is specifically configured to:
Restoring a first target account address for signing the second transaction content based on the second signature information;
and if the first target account address is consistent with the second account address in the first transaction content, determining that the verification is passed.
In some embodiments, the address introducing module 304 is specifically configured to:
restoring a second target account address for signing the first transaction content based on the first signature information;
and if the second target account address is consistent with the first account address of the account node, determining that the verification is passed.
In some embodiments, the DID contract management system further includes an identity verification module, where the identity verification module is applied to the account node, and the identity verification module is specifically configured to:
the account node performs identity verification on the target account node based on the second account address:
and if the identity verification is passed, signing the first transaction content containing the second account address.
As can be seen from the above, the DID contract management system of the present embodiment is applied to a blockchain, where the blockchain includes an account node and an intelligent contract node, a first account address of the account node is added to a target DID contract of the intelligent contract node, the target DID contract is configured to store a plurality of account addresses, and account information is shared between the account addresses in the target DID contract. The first signing module 301 is applied to the account node, and is configured to receive a second account address sent by a target account node to be added to the target DID contract, and sign a first transaction content including the second account address to obtain first signature information; the second signature module 302 is configured to apply the second signature module to the account node, where the second signature module is configured to send the first signature information to the target account node, so as to inform the target account node that the target account node will apply for address introduction to the intelligent contract node for the target account node, trigger the target account node to sign the second transaction content including the first signature information, obtain second signature information, and send the second signature information to the account node, that is, instruct the target account node to authorize the account node to apply for address introduction to the intelligent contract node; the information sending module 303 is applied to the account node, and is configured to receive the second signature information sent by the target account node, and send the first signature information and the second signature information to the intelligent contract node; the address introducing module 304 is applied to the intelligent contract node, and the address introducing module is configured to receive the first signature information and the second signature information, and introduce the second account address for the target DID contract based on the first signature information and the second signature information, thereby improving security when the account address joins the DID contract as a whole.
Correspondingly, the embodiment of the application also provides electronic equipment, which can be a terminal, and the terminal can be terminal equipment such as a smart phone, a tablet personal computer, a notebook computer, a touch screen, a game machine, a personal computer (PC, personal Computer), a personal digital assistant (Personal Digital Assistant, PDA) and the like. As shown in fig. 4, fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application. The electronic device 400 includes a processor 401 having one or more processing cores, a memory 402 having one or more computer readable storage media, and a computer program stored on the memory 402 and executable on the processor. The processor 401 is electrically connected to the memory 402. It will be appreciated by those skilled in the art that the electronic device structure shown in the figures is not limiting of the electronic device and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
The processor 401 is a control center of the electronic device 400, connects various parts of the entire electronic device 400 using various interfaces and lines, and performs various functions of the electronic device 400 and processes data by running or loading software programs and/or modules stored in the memory 402, and calling data stored in the memory 402, thereby performing overall monitoring of the electronic device 400.
In the embodiment of the present application, the processor 401 in the electronic device 400 loads the instructions corresponding to the processes of one or more application programs into the memory 402 according to the following steps, and the processor 401 executes the application programs stored in the memory 402, so as to implement various functions:
the account node receives a second account address sent by a target account node to be added into the target DID contract, signs first transaction content containing the second account address, and obtains first signature information;
the account node sends the first signature information to the target account node to trigger the target account node to sign second transaction content containing the first signature information to obtain second signature information, and sends the second signature information to the account node;
the account node receives the second signature information sent by the target account node and sends the first signature information and the second signature information to the intelligent contract node;
the smart contract node receives the first signature information and the second signature information and introduces the second account address for the target DID contract based on the first signature information and the second signature information.
In some embodiments, the introducing the second account address for the target DID contract based on the first signature information and the second signature information includes:
verifying based on the first signature information and the second signature information;
and when the verification is passed, introducing the second account address for the target DID contract.
In some embodiments, the first signature information includes the first transaction content, the second signature information includes the second transaction content, the first transaction content further includes a block height when signing the first transaction content, and the second transaction content further includes a block height when signing the second transaction content;
the verifying based on the first signature information and the second signature information includes:
calculating a first block height difference between the block height corresponding to the first transaction content and the block height corresponding to the second transaction content;
and if the first block height difference value is smaller than or equal to a preset height threshold value, determining that the verification passes.
In some embodiments, the verifying based on the first signature information and the second signature information further includes:
Acquiring the block height during verification;
calculating a second block height difference between the block height at the time of the verification and the block height corresponding to the second transaction content;
and if the second block height difference value is smaller than or equal to the height threshold value, determining that the verification passes.
In some embodiments, the verifying based on the first signature information and the second signature information includes:
restoring a first target account address for signing the second transaction content based on the second signature information;
and if the first target account address is consistent with the second account address in the first transaction content, determining that the verification is passed.
In some embodiments, the verifying based on the first signature information and the second signature information includes:
restoring a second target account address for signing the first transaction content based on the first signature information;
and if the second target account address is consistent with the first account address of the account node, determining that the verification is passed.
In some embodiments, prior to signing the first transaction content including the second account address, further comprising:
The account node performs identity verification on the target account node based on the second account address:
and if the identity verification is passed, signing the first transaction content containing the second account address.
Thus, the electronic device 400 provided in this embodiment may have the following technical effects: the security of the account address when joining the DID contract is improved.
The specific implementation of each operation above may be referred to the previous embodiments, and will not be described herein.
Optionally, as shown in fig. 4, the electronic device 400 further includes: a touch display 403, a radio frequency circuit 404, an audio circuit 405, an input unit 406, and a power supply 407. The processor 401 is electrically connected to the touch display 403, the radio frequency circuit 404, the audio circuit 405, the input unit 406, and the power supply 407, respectively. Those skilled in the art will appreciate that the electronic device structure shown in fig. 4 is not limiting of the electronic device and may include more or fewer components than shown, or may combine certain components, or may be arranged in different components.
The touch display 403 may be used to display a graphical user interface and receive operation instructions generated by a user acting on the graphical user interface. The touch display screen 403 may include a display panel and a touch panel. Wherein the display panel may be used to display information entered by a user or provided to a user as well as various graphical user interfaces of the electronic device, which may be composed of graphics, text, icons, video, and any combination thereof. Alternatively, the display panel may be configured in the form of a liquid crystal display (LCD, liquid Crystal Display), an Organic Light-Emitting Diode (OLED), or the like. The touch panel may be used to collect touch operations on or near the user (such as operations on or near the touch panel by the user using any suitable object or accessory such as a finger, stylus, etc.), and generate corresponding operation instructions, and the operation instructions execute corresponding programs. Alternatively, the touch panel may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends the touch point coordinates to the processor 401, and can receive and execute commands sent from the processor 401. The touch panel may overlay the display panel, and upon detection of a touch operation thereon or thereabout, the touch panel is passed to the processor 401 to determine the type of touch event, and the processor 401 then provides a corresponding visual output on the display panel in accordance with the type of touch event. In the embodiment of the present application, the touch panel and the display panel may be integrated into the touch display screen 403 to implement the input and output functions. In some embodiments, however, the touch panel and the touch panel may be implemented as two separate components to perform the input and output functions. I.e. the touch-sensitive display 403 may also implement an input function as part of the input unit 406.
The radio frequency circuitry 404 may be used to transceive radio frequency signals to establish wireless communication with a network device or other electronic device via wireless communication.
The audio circuitry 405 may be used to provide an audio interface between a user and an electronic device through a speaker, microphone. The audio circuit 405 may transmit the received electrical signal after audio data conversion to a speaker, where the electrical signal is converted into a sound signal for output; on the other hand, the microphone converts the collected sound signals into electrical signals, which are received by the audio circuit 405 and converted into audio data, which are processed by the audio data output processor 401 and sent via the radio frequency circuit 404 to e.g. another electronic device, or which are output to the memory 402 for further processing. The audio circuit 405 may also include an ear bud jack to provide communication of the peripheral headphones with the electronic device.
The input unit 406 may be used to receive input numbers, character information, or user characteristic information (e.g., fingerprint, iris, facial information, etc.), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.
The power supply 407 is used to power the various components of the electronic device 400. Alternatively, the power supply 407 may be logically connected to the processor 401 through a power management system, so as to implement functions of managing charging, discharging, and power consumption management through the power management system. The power supply 407 may also include one or more of any of a direct current or alternating current power supply, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
Although not shown in fig. 4, the electronic device 400 may further include a camera, a sensor, a wireless fidelity module, a bluetooth module, etc., which are not described herein.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that all or a portion of the steps of the various methods of the above embodiments may be performed by instructions, or by instructions controlling associated hardware, which may be stored in a computer-readable storage medium and loaded and executed by a processor.
To this end, the present embodiments provide a computer readable storage medium in which a plurality of computer programs are stored, the computer programs being capable of being loaded by a processor to perform steps in any of the DID contract management methods provided in the embodiments of the present application. For example, the computer program may perform the steps of:
The account node receives a second account address sent by a target account node to be added into the target DID contract, signs first transaction content containing the second account address, and obtains first signature information;
the account node sends the first signature information to the target account node to trigger the target account node to sign second transaction content containing the first signature information to obtain second signature information, and sends the second signature information to the account node;
the account node receives the second signature information sent by the target account node and sends the first signature information and the second signature information to the intelligent contract node;
the smart contract node receives the first signature information and the second signature information and introduces the second account address for the target DID contract based on the first signature information and the second signature information.
In some embodiments, the introducing the second account address for the target DID contract based on the first signature information and the second signature information includes:
verifying based on the first signature information and the second signature information;
And when the verification is passed, introducing the second account address for the target DID contract.
In some embodiments, the first signature information includes the first transaction content, the second signature information includes the second transaction content, the first transaction content further includes a block height when signing the first transaction content, and the second transaction content further includes a block height when signing the second transaction content;
the verifying based on the first signature information and the second signature information includes:
calculating a first block height difference between the block height corresponding to the first transaction content and the block height corresponding to the second transaction content;
and if the first block height difference value is smaller than or equal to a preset height threshold value, determining that the verification passes.
In some embodiments, the verifying based on the first signature information and the second signature information further includes:
acquiring the block height during verification;
calculating a second block height difference between the block height at the time of the verification and the block height corresponding to the second transaction content;
and if the second block height difference value is smaller than or equal to the height threshold value, determining that the verification passes.
In some embodiments, the verifying based on the first signature information and the second signature information includes:
restoring a first target account address for signing the second transaction content based on the second signature information;
and if the first target account address is consistent with the second account address in the first transaction content, determining that the verification is passed.
In some embodiments, the verifying based on the first signature information and the second signature information includes:
restoring a second target account address for signing the first transaction content based on the first signature information;
and if the second target account address is consistent with the first account address of the account node, determining that the verification is passed.
In some embodiments, prior to signing the first transaction content including the second account address, further comprising:
the account node performs identity verification on the target account node based on the second account address:
and if the identity verification is passed, signing the first transaction content containing the second account address.
It can be seen that the computer program can be loaded by a processor to execute the steps in any of the DID contract management methods provided in the embodiments of the present application, thereby bringing about the following technical effects: the security of the account address when joining the DID contract is improved.
The specific implementation of each operation above may be referred to the previous embodiments, and will not be described herein.
Wherein the computer-readable storage medium may comprise: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.
Since the computer program stored in the computer readable storage medium may execute the steps in any kind of DID contract management method provided in the embodiments of the present application, the beneficial effects that any kind of DID contract management method provided in the embodiments of the present application can be achieved, which is detailed in the previous embodiments and will not be described herein.
The foregoing describes in detail a DID contract management method, system, electronic device and computer readable storage medium provided in the embodiments of the present application, and specific examples are applied to illustrate the principles and embodiments of the present application, where the foregoing examples are only used to help understand the method and core idea of the present application; meanwhile, those skilled in the art will have variations in the specific embodiments and application scope in light of the ideas of the present application, and the present description should not be construed as limiting the present application in view of the above.

Claims (10)

1. A DID contract management method applied to a blockchain including an account node and an intelligent contract node, a first account address of the account node having been added to a target DID contract of the intelligent contract node, the target DID contract configured to deposit a plurality of account addresses and share account information among the account addresses in the target DID contract, the method comprising:
the account node receives a second account address sent by a target account node to be added into the target DID contract, signs first transaction content containing the second account address, and obtains first signature information;
the account node sends the first signature information to the target account node to trigger the target account node to sign second transaction content containing the first signature information to obtain second signature information, and sends the second signature information to the account node;
the account node receives the second signature information sent by the target account node and sends the first signature information and the second signature information to the intelligent contract node;
The intelligent contract node receives the first signature information and the second signature information and introduces the second account address for the target DID contract based on the first signature information and the second signature information.
2. The DID contract management method of claim 1, wherein the introducing the second account address for the target DID contract based on the first signature information and the second signature information comprises:
verifying based on the first signature information and the second signature information;
and when the verification is passed, introducing the second account address for the target DID contract.
3. The DID contract management method of claim 2, wherein the first signature information includes the first transaction content, the second signature information includes the second transaction content, the first transaction content further includes a block height when the first transaction content is signed, the second transaction content further includes a block height when the second transaction content is signed;
the verifying based on the first signature information and the second signature information includes:
calculating a first block height difference between the block height corresponding to the first transaction content and the block height corresponding to the second transaction content;
And if the first block height difference value is smaller than or equal to a preset height threshold value, determining that the verification passes.
4. The DID contract management method of claim 3, wherein the verifying based on the first signature information and the second signature information further comprises:
acquiring the block height during verification;
calculating a second block height difference between the block height at the time of verification and the block height corresponding to the second transaction content;
and if the second block height difference value is smaller than or equal to the height threshold value, determining that the verification passes.
5. The DID contract management method of claim 2, wherein the verifying based on the first signature information and the second signature information comprises:
restoring a first target account address for signing the second transaction content based on the second signature information;
and if the first target account address is consistent with the second account address in the first transaction content, determining that the verification is passed.
6. The DID contract management method of claim 2, wherein the verifying based on the first signature information and the second signature information comprises:
Restoring a second target account address for signing the first transaction content based on the first signature information;
and if the second target account address is consistent with the first account address of the account node, determining that the verification is passed.
7. The DID contract management method of any one of claims 1 to 6, further comprising, prior to signing the first transaction content including the second account address:
the account node performs identity verification on the target account node based on the second account address:
and if the identity verification is passed, signing the first transaction content containing the second account address.
8. A DID contract management system, applied to a blockchain including an account node and an intelligent contract node, a first account address of the account node having been added to a target DID contract of the intelligent contract node, the target DID contract configured to house a plurality of account addresses and share account information among the account addresses in the target DID contract, the system comprising:
the first signature module is applied to the account node, and is used for receiving a second account address sent by a target account node to be added into the target DID contract, and signing first transaction content containing the second account address to obtain first signature information;
The second signature module is applied to the account node, and is used for sending the first signature information to the target account node so as to trigger the target account node to sign second transaction content containing the first signature information to obtain second signature information, and sending the second signature information to the account node;
the information sending module is applied to the account node and is used for receiving the second signature information sent by the target account node and sending the first signature information and the second signature information to the intelligent contract node;
the address introducing module is applied to the intelligent contract node, and is used for receiving the first signature information and the second signature information and introducing the second account address for the target DID contract based on the first signature information and the second signature information.
9. An electronic device comprising a processor and a memory, the memory storing a plurality of instructions; the processor loads instructions from the memory to perform the steps in the DID contract management method as claimed in any one of claims 1 to 7.
10. A computer readable storage medium storing a plurality of instructions adapted to be loaded by a processor to perform the steps in the DID contract management method of any one of claims 1 to 7.
CN202310275696.8A 2023-03-14 2023-03-14 DID contract management method, DID contract management system, electronic device and readable storage medium Pending CN116384997A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310275696.8A CN116384997A (en) 2023-03-14 2023-03-14 DID contract management method, DID contract management system, electronic device and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310275696.8A CN116384997A (en) 2023-03-14 2023-03-14 DID contract management method, DID contract management system, electronic device and readable storage medium

Publications (1)

Publication Number Publication Date
CN116384997A true CN116384997A (en) 2023-07-04

Family

ID=86970444

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310275696.8A Pending CN116384997A (en) 2023-03-14 2023-03-14 DID contract management method, DID contract management system, electronic device and readable storage medium

Country Status (1)

Country Link
CN (1) CN116384997A (en)

Similar Documents

Publication Publication Date Title
US11663577B2 (en) Resource transfer method and apparatus and storage medium
CN110365491B (en) Service processing method, device, equipment, storage medium and data sharing system
US11057376B2 (en) Method, apparatus, and system for controlling intelligent device, and storage medium
US11126981B2 (en) Resource transferring method and apparatus
US10993090B2 (en) Network access method, apparatus, and system
CN104901805B (en) A kind of identification authentication methods, devices and systems
CN110601858B (en) Certificate management method and device
US20190205976A1 (en) Account number registration method, apparatus, and system
US11233897B1 (en) Secure call center communications
CN112380552A (en) Data processing method and device, storage medium and computer equipment
CN113506100A (en) Alliance link data processing method and device, computer equipment and storage medium
CN111723163B (en) Information processing method, device and system
CN112153032A (en) Information processing method, device, computer readable storage medium and system
CN114092101B (en) Transaction verification method and device, storage medium and electronic equipment
CN116384997A (en) DID contract management method, DID contract management system, electronic device and readable storage medium
CN116384998A (en) DID contract management method, DID contract management device, electronic equipment and readable storage medium
CN114844629A (en) Verification method and device of block chain account, computer equipment and storage medium
CN113746640A (en) Digital certificate using method and device, computer equipment and storage medium
CN104899730B (en) Mobile terminal data processing method, terminal and system
CN106778297B (en) Application program running method and device and mobile terminal
CN116233130A (en) Block chain-based registration method, device, electronic equipment and readable storage medium
CN116308786A (en) Processing method, system, electronic equipment and readable storage medium for blockchain transaction
CN113360883B (en) Intelligent contract processing method and device, computer equipment and storage medium
CN114745374B (en) File transmission method and device, electronic equipment and storage medium
CN117041372A (en) Protocol switching method, device and equipment of passive equipment and readable storage medium

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