A method and system for supporting DID cross-chain registration mutual recognition of enterprise personal level

Abstract

The present application relates to the technical field of identity authentication, in particular to a DID cross-chain registration mutual recognition method supporting enterprise personal level, which comprises the following steps: when a user does not have enterprise and personal DID in double chains, filling in enterprise and personal information according to system requirements, chain A generates enterprise and personal DID according to a preset algorithm, and synchronously generates identity information into network VC data containing double information and double DID; after the system positions the VC data, the VC data is encrypted and transmitted to chain B through a cross-chain contract, chain B generates enterprise and personal DID according to the synchronized encrypted VC data, the double-chain VC data contains the DID of both parties, forms a two-way binding, generates DID and VC data according to the rule that the enterprise is prior to the individual, encrypts and stores sensitive information, verifies by using minimum disclosure proof, sets a version number and a state field in the VC data, ensures that the data is consistent and traceable, and obtains a DID cross-chain registration mutual recognition module. The present application solves the problem that the identity information of enterprises and individuals is isolated on different blockchains and cannot be cross-chain registered and mutually recognized.

Description

Technical Field

[0001] This invention belongs to the field of identity authentication technology, specifically relating to a method and system for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels. Background Technology

[0002] With the widespread adoption of blockchain technology in government affairs, finance, and the industrial internet, decentralized identity (DID) is gradually becoming a crucial foundation for digital identity management. DIDs can provide trusted identity identifiers across different systems and scenarios, and record information such as control rights, public keys, and server endpoints through DID documents, enabling self-management and verifiability of identity. However, in practical applications, multiple blockchains often operate in parallel, such as blockchain systems from different departments, regions, or consortia. The DIDs maintained by these systems cannot directly recognize each other, leading to duplicate identity registration, difficulties in cross-chain interaction, and a lack of identity consistency.

[0003] Existing cross-chain identity recognition solutions suffer from the following shortcomings: First, the anchoring method for identities lacks uniformity, making it difficult to guarantee the uniqueness and consistency of identities across different chains. Second, the hierarchical relationship between enterprises and individuals is often not strictly constrained, making it difficult to restore the complete identity hierarchy after cross-chain transactions. Third, privacy protection measures during the cross-chain process are insufficient, potentially leading to the leakage of sensitive information such as ID card numbers and unified social credit codes. Fourth, when the peer chain does not yet have an identity, there is a lack of an automated synchronous registration mechanism, and cross-chain recognition cannot cover all business scenarios. Therefore, a new DID cross-chain recognition method is needed to ensure identity consistency and privacy security while handling both scenarios of synchronous registration without an identity and mutual recognition of existing identities. Summary of the Invention

[0004] To address the aforementioned issues, this invention provides a method and system for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels. This solves the problem of isolated identity information for enterprises and individuals on different blockchains, hindering cross-chain registration and mutual recognition. To achieve the above objectives, this invention adopts the following technical solution: The method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels includes the following steps: When a user does not have enterprise and individual DIDs on either chain, they fill in enterprise and individual information as required by the system. Chain A generates enterprise and individual DIDs according to a preset algorithm, and simultaneously generates identity information VC data containing both information and DIDs. After the identity information VC data is generated, the cross-chain contract mechanism is triggered. The contract encrypts the VC data and transmits it to Chain B. Chain B uses a decryption algorithm to obtain the original data, resulting in decrypted original VC data. Based on the received VC data, Chain B generates enterprise and individual DIDs according to its own rules, adds them to the VC data, and sends them back to Chain A, ensuring consistency of VC data between the two chains, thus achieving consistent data across the two chains. VC data: When a user has a DID on chain A, a query is initiated using the personal DID as the identifier. After the system locates the VC data, it is encrypted and transmitted to chain B via a cross-chain contract to ensure secure data transmission, resulting in encrypted VC data synchronized with chain A. Chain B generates enterprise and personal DIDs based on the synchronized encrypted VC data, adds them to the VC data, and then transmits them back to chain A. The dual-chain VC data contains the DIDs of both parties, forming a two-way binding and achieving mutual recognition of dual-chain DIDs, resulting in VC data containing dual-chain DIDs. Following the rule that enterprises generate DIDs before individuals, sensitive information is encrypted and stored, and verification is performed using proof of least disclosure. The VC data includes a version number and status field to ensure data consistency and traceability, resulting in the DID cross-chain registration and mutual recognition module.

[0005] Furthermore, when the user does not possess enterprise and personal DIDs on either chain, they fill in enterprise and personal information as required by the system. Chain A generates enterprise and personal DIDs according to a preset algorithm, and simultaneously generates identity information VC data containing both information and DIDs for network access. This includes the following steps: When the user does not possess enterprise and personal DIDs on either chain, the user must accurately fill in the enterprise's name, unified social credit code, registered address information, and the individual's name, ID number, and contact information as required. Upon receiving the information, Chain A generates enterprise DIDs and personal DIDs for the enterprise and individual respectively according to preset algorithms and rules. Chain A will simultaneously generate identity information containing enterprise information fields, personal information fields, and the generated enterprise and personal DIDs based on the collected information.

[0006] Furthermore, once the waiting identity information VC data for network entry is generated, the cross-chain contract mechanism is triggered. The contract encrypts the VC data and transmits it to chain B. Chain B uses a decryption algorithm to obtain the original data, resulting in the decrypted original VC data. This process includes the following steps: Upon completion of the waiting identity information VC data generation, the cross-chain contract mechanism is immediately triggered; the cross-chain contract acts as a bridge connecting the two chains, responsible for securely and accurately transmitting the identity information VC from chain A to chain B; the cross-chain contract encrypts the VC data to ensure its confidentiality and integrity during transmission; chain B receives the encrypted VC data and uses a decryption algorithm to obtain the decrypted original VC data.

[0007] Furthermore, based on the received VC data, Chain B generates enterprise and individual DIDs according to its own rules, adds them to the VC data, and then sends them back to Chain A to obtain consistent VC data across both chains. This process includes the following steps: Chain B automatically generates enterprise and individual DIDs on Chain B based on its own DID generation rules from the received VC data containing enterprise and individual information; Chain B adds the two fields to the received VC data, ensuring that the new VC data simultaneously contains enterprise and individual DIDs from both Chain A and Chain B; Chain B triggers a cross-chain contract to send the updated VC data back to Chain A, ensuring that the VC data on Chain A and Chain B remain consistent, resulting in consistent VC data across both chains.

[0008] Furthermore, the process of a user initiating a query using their personal DID as an identifier when they have a DID on Chain A, locating the VC data, and then encrypting and transmitting it to Chain B via a cross-chain contract to ensure secure data transmission and obtain encrypted VC data synchronized with Chain A, includes the following steps: When a user already has both an enterprise DID and a personal DID on Chain A, the user can initiate a query request to the system using their personal DID as a query identifier; the system quickly locates the corresponding identity information and VC data using the personal DID provided by the user; the system encrypts the VC data and transmits it synchronously to Chain B via a cross-chain contract to obtain encrypted VC data synchronized with Chain A.

[0009] Furthermore, the process of generating DID and VC data following the rule of "enterprise first, individual first," encrypting and storing sensitive information, verifying with proof of least disclosure, and ensuring data consistency and traceability by including version and status fields in the VC data, results in the DID cross-chain registration and mutual recognition module. This module includes the following steps: generating DID and VC data containing reference fields following the rule of "enterprise first, individual first," resulting in a clear enterprise-individual hierarchical structure; storing sensitive information such as ID card numbers and unified social credit codes in the VC data in encrypted form; using the proof of least disclosure mechanism to provide only the necessary information for verification, preventing complete data leakage; and ensuring consistency and traceability of identity data across the two chains by automatically triggering a synchronization update mechanism when DID or VC data is updated or revoked, thus obtaining the DID cross-chain registration and mutual recognition module.

[0010] The second aspect of this invention provides a cross-chain registration and mutual recognition system for DIDs at the enterprise and individual levels. This system includes the following modules: An information collection module: When a user does not possess enterprise and individual DIDs on either chain, they fill in their enterprise and individual information as required by the system. Chain A generates enterprise and individual DIDs according to a preset algorithm, simultaneously generating identity information VC data containing both information and DIDs; A cross-chain contract module: After the identity information VC data generation is complete, a cross-chain contract mechanism is triggered. The contract encrypts the VC data and transmits it to Chain B. Chain B uses a decryption algorithm to obtain the original data, resulting in decrypted original VC data; A DID generation module: Existing identity cross-chain mutual recognition module: Chain B generates enterprise and individual DIDs based on the received VC data according to its own rules, adds them to the VC data, and transmits them back to Chain A, ensuring consistency between the two chains' VC data, resulting in consistent VC data across both chains; An identity query module: When a user has a DID on Chain A, they initiate a query using their individual DID as the identifier. After locating the VC data, the system encrypts and transmits it to Chain B via a cross-chain contract, ensuring secure data transmission, and obtaining encrypted VC data synchronized with Chain A. Two-way binding module: Chain B generates enterprise and individual DIDs based on synchronized encrypted VC data, adds them to the VC data, and then sends them back to Chain A. The dual-chain VC data contains the DIDs of both parties, forming a two-way binding and achieving mutual recognition of dual-chain DIDs, resulting in VC data containing dual-chain DIDs; Privacy protection and auditing module: Following the rule that enterprises take precedence over individuals, DIDs and VC data are generated, sensitive information is encrypted and stored, and verification is performed using proof of least disclosure. The VC data includes version numbers and status fields to ensure data consistency and traceability, resulting in the DID cross-chain registration and mutual recognition module.

[0011] A third aspect of the present invention provides a DID cross-chain registration and mutual recognition device supporting enterprise and individual levels. The DID cross-chain registration and mutual recognition device supporting enterprise and individual levels includes a memory and at least one processor. The memory stores instructions. The at least one processor invokes the instructions in the memory to cause the DID cross-chain registration and mutual recognition device supporting enterprise and individual levels to perform the steps of the DID cross-chain registration and mutual recognition method supporting enterprise and individual levels as described in any of the preceding claims.

[0012] A fourth aspect of the present invention provides a computer-readable storage medium storing instructions, characterized in that, when executed by a processor, the instructions implement the steps of the cross-chain registration and mutual recognition method for DID at the enterprise-person level as described in any of the preceding claims.

[0013] In the technical solution provided by this invention, when a user does not possess enterprise and personal DIDs on the dual-chain system, they fill in enterprise and personal information as required by the system. Chain A generates enterprise and personal DIDs according to a preset algorithm, simultaneously generating identity information VC data containing both information and DIDs. After the identity information VC data generation is complete, the cross-chain contract mechanism is triggered. The contract encrypts the VC data and transmits it to Chain B. Chain B uses a decryption algorithm to obtain the original data, resulting in decrypted original VC data. Based on the received VC data, Chain B generates enterprise and personal DIDs according to its own rules, adds them to the VC data, and sends them back to Chain A, ensuring consistency between the two chains' VC data, thus obtaining consistent VC data across the two chains. When a user... When Chain A has a DID, a query is initiated using the individual DID as the identifier. After the system locates the VC data, it is encrypted and transmitted to Chain B via a cross-chain contract, ensuring secure data transmission and obtaining encrypted VC data synchronized with Chain A. Chain B generates enterprise and individual DIDs based on the synchronized encrypted VC data, adds them to the VC data, and then sends them back to Chain A. The dual-chain VC data contains the DIDs of both parties, forming a two-way binding and achieving mutual recognition of dual-chain DIDs, resulting in VC data containing dual-chain DIDs. Following the rule that enterprises generate DIDs before individuals, sensitive information is encrypted and stored, and verification is performed using proof of least disclosure. The VC data includes a version number and status field to ensure data consistency and traceability, resulting in the DID cross-chain registration and mutual recognition module. This invention solves the problem of isolated identity information for enterprises and individuals on different blockchains, preventing cross-chain registration and mutual recognition. Attached Figure Description

[0014] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention.

[0015] Figure 1This is a schematic diagram of a first embodiment of a method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels according to an embodiment of the present invention.

[0016] Figure 2 This is a schematic diagram of a second embodiment of a method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels according to the present invention.

[0017] Figure 3 This is a schematic diagram of a third embodiment of a method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels according to the present invention.

[0018] Figure 4 This is a schematic diagram of the fourth embodiment of a method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels in this invention.

[0019] Figure 5 This is a schematic diagram of the fifth embodiment of a method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels in this invention. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0021] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this specification means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0022] A method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels, such as... Figure 1As shown, the process includes the following steps: When a user does not have enterprise and personal DIDs on both chains, they fill in their enterprise and personal information as required by the system. Chain A generates enterprise and personal DIDs according to a preset algorithm, and simultaneously generates identity information VC data containing both information and DIDs. After the identity information VC data is generated, the cross-chain contract mechanism is triggered. The contract encrypts the VC data and transmits it to Chain B. Chain B uses a decryption algorithm to obtain the original data, resulting in decrypted original VC data. Based on the received VC data, Chain B generates enterprise and personal DIDs according to its own rules, adds them to the VC data, and sends them back to Chain A to ensure consistency between the two chains' VC data, resulting in consistent VC data between the two chains. When a user on Chain A... When a DID exists, a query is initiated using the individual's DID as the identifier. After the system locates the VC data, it is encrypted and transmitted to chain B via a cross-chain contract to ensure secure data transmission, resulting in encrypted VC data synchronized with chain A. Chain B generates enterprise and individual DIDs based on the synchronized encrypted VC data, adds them to the VC data, and then transmits them back to chain A. The dual-chain VC data contains the DIDs of both parties, forming a two-way binding and achieving mutual recognition of dual-chain DIDs, resulting in VC data containing dual-chain DIDs. Following the rule that enterprises generate DIDs before individuals, sensitive information is encrypted and stored, and verification is performed using proof of least disclosure. The VC data includes a version number and status field to ensure data consistency and traceability, resulting in the DID cross-chain registration and mutual recognition module.

[0023] like Figure 2 As shown in this embodiment, when a user does not possess enterprise and personal DIDs on either of the two chains, the user must accurately fill in the enterprise's name, unified social credit code, registered address information, and the individual's name, ID number, and contact information as required. Upon receiving the information, chain A generates enterprise DIDs and personal DIDs for the enterprise and individual respectively according to preset algorithms and rules. Chain A will synchronously generate identity information containing enterprise information fields, personal information fields, and the generated enterprise DIDs and personal DIDs based on the collected information.

[0024] like Figure 3 As shown in this embodiment, once the identity information VC data is generated, the cross-chain contract mechanism is immediately triggered. The cross-chain contract acts as a bridge connecting the two chains, responsible for securely and accurately transmitting the identity information VC from chain A to chain B. The cross-chain contract encrypts the VC data to ensure the confidentiality and integrity of the data during transmission. Chain B receives the encrypted VC data and obtains the decrypted original VC data through a decryption algorithm.

[0025] like Figure 4As shown in this embodiment, Chain B receives VC data containing enterprise and personal information and automatically generates enterprise DID and personal DID on Chain B according to its own DID generation rules. Chain B adds the two fields to the received VC data, so that the new VC data contains both enterprise DID and personal DID from both Chain A and Chain B. Chain B triggers a cross-chain contract to send the updated VC data back to Chain A, ensuring that the VC data on Chain A and Chain B are consistent, resulting in consistent VC data across both chains.

[0026] like Figure 5 As shown in this embodiment, when a user already has an enterprise DID and a personal DID on chain A, the user can use the personal DID as a query identifier to initiate a query request to the system; the system can quickly locate the corresponding identity information network VC data through the personal DID provided by the user; the system encrypts the VC data and transmits the VC data synchronously to chain B through a cross-chain contract to obtain the encrypted VC data synchronized with chain A.

[0027] In this embodiment, DID and VC data containing reference fields are generated following the rule that enterprises precede individuals, resulting in a clear enterprise-individual hierarchical structure. Sensitive information such as ID card numbers and unified social credit codes involved in the VC data are stored in encrypted form. A minimum disclosure proof mechanism is used to provide only the necessary information for verification, preventing the leakage of all data. The VC data contains version number and status fields. When DID or VC data is updated or revoked, the cross-chain contract will automatically trigger a synchronization update mechanism to ensure the consistency and traceability of identity data between the two chains, resulting in the DID cross-chain registration and mutual recognition module.

[0028] With the support of VC data, DID (Digital Identity) can achieve consistent expression and trusted mutual recognition across multiple chains while ensuring enterprise priority and individual affiliation. Using VC data as the carrier and transfer medium for identity information, the generation, synchronization, and updating of identity data can all be verified on-chain, preventing forgery and tampering. Sensitive information is handled through encryption and hashing, protecting privacy while meeting verification requirements. Synchronous updates of VC data are achieved through cross-chain contracts, supporting both automatic registration without an identity and rapid mutual recognition with an existing identity, providing comprehensive coverage. Furthermore, the solution supports version control and revocation management, giving the cross-chain identity system complete lifecycle management capabilities.

[0029] In summary, this solution technically achieves cross-chain identity anchoring, privacy protection, automatic registration, and mutual recognition binding based on VC data. In application, it improves the efficiency and security of cross-chain data interaction and identity management, and can provide strong technical support for various scenarios such as government collaboration, cross-border trade, and financial services.

[0030] This invention also provides a cross-chain registration and mutual recognition system for DIDs at the enterprise and individual levels, comprising the following modules: Information collection module: When a user does not possess enterprise and personal DIDs on either chain, they fill in enterprise and personal information as required by the system. Chain A generates enterprise and personal DIDs according to a preset algorithm, simultaneously generating identity information VC data containing both information and DIDs; Cross-chain contract module: After the identity information VC data generation is complete, the cross-chain contract mechanism is triggered. The contract encrypts the VC data and transmits it to Chain B. Chain B uses a decryption algorithm to obtain the original data, resulting in decrypted original VC data; DID generation module: Existing identity cross-chain mutual recognition module: Chain B generates enterprise and personal DIDs based on the received VC data according to its own rules, adds them to the VC data, and transmits them back to Chain A, ensuring consistency between the two chains' VC data, resulting in consistent VC data between the two chains; Identity query module: When a user has a DID on Chain A, they initiate a query using their personal DID as the identifier. After locating the VC data, the system encrypts and transmits it to Chain B via a cross-chain contract, ensuring secure data transmission, and obtaining encrypted VC data synchronized with Chain A. Two-way binding module: Chain B generates enterprise and individual DIDs based on synchronized encrypted VC data, adds them to the VC data, and then sends them back to Chain A. The dual-chain VC data contains the DIDs of both parties, forming a two-way binding and achieving mutual recognition of dual-chain DIDs, resulting in VC data containing dual-chain DIDs; Privacy protection and auditing module: Following the rule that enterprises take precedence over individuals, DIDs and VC data are generated, sensitive information is encrypted and stored, and verification is performed using proof of least disclosure. The VC data includes version numbers and status fields to ensure data consistency and traceability, resulting in the DID cross-chain registration and mutual recognition module.

[0031] This invention also provides a device for cross-chain registration and mutual recognition of DIDs at the enterprise / personal level. This device may further include one or more power supplies, one or more wired or wireless network interfaces, one or more input / output interfaces, and / or one or more operating systems, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art will understand that the structure of the device supporting cross-chain registration and mutual recognition of DIDs at the enterprise / personal level does not constitute a limitation on the computer device provided by this invention, and may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0032] The present invention also provides a computer-readable storage medium, which can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the various steps of the cross-chain registration and mutual recognition method for DID at the enterprise and individual levels provided in the above embodiments.

[0033] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely preferred examples and are not intended to limit the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels, characterized in that, The method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels includes the following steps: When a user does not have a corporate and personal DID on the dual-chain, they fill in their corporate and personal information as required by the system. Chain A generates corporate and personal DIDs according to a preset algorithm, and simultaneously generates identity information VC data containing dual information and dual DIDs. The VC data includes a version number and a status field. Once the identity information is registered on the network and the VC data is generated, the cross-chain contract mechanism is triggered. The contract encrypts the VC data and transmits it to Chain B. Chain B uses a decryption algorithm to obtain the original data and gets the decrypted original VC data. Based on the received VC data, Chain B generates enterprise and individual DIDs according to its own rules, adds them to the VC data, and then sends them back to Chain A to ensure that the VC data of the two chains is consistent, thus obtaining VC data that is consistent between the two chains. When a user has a DID on chain A, they can initiate a query using their personal DID as the identifier. After locating the VC data, the system will encrypt and transmit it to chain B through a cross-chain contract to ensure secure data transmission and obtain encrypted VC data synchronized with chain A. Chain B generates enterprise and individual DIDs based on synchronized encrypted VC data, adds them to the VC data, and then sends them back to Chain A. The dual-chain VC data contains the DIDs of both parties, forming a two-way binding and realizing mutual recognition of dual-chain DIDs, thus obtaining VC data containing dual-chain DIDs.

2. The method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels according to claim 1, characterized in that, When a user does not possess enterprise and personal DIDs on the dual-chain system, they fill in their enterprise and personal information as required by the system. Chain A generates enterprise and personal DIDs based on a preset algorithm, and simultaneously generates identity information VC data containing both information and DIDs for network access, including the following steps: When a user does not have a corporate or personal DID on either of the two chains, the user must accurately fill in the company's name, unified social credit code, registered address information, and the individual's name, ID number, and contact information as required. Upon receiving the information, Chain A generates Enterprise DID and Individual DID for both the enterprise and the individual based on preset algorithms and rules. Chain A will synchronously generate VC data containing enterprise information fields, personal information fields, and the generated enterprise DID and personal DID identity information based on the collected information.

3. The method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels according to claim 1, characterized in that, Once the waiting identity information for network access VC data generation is complete, the cross-chain contract mechanism is triggered. The contract encrypts the VC data and transmits it to chain B. Chain B uses a decryption algorithm to obtain the original data, resulting in the decrypted original VC data, including the following steps: Once the identity information is registered and the VC data is generated, the cross-chain contract mechanism will be triggered immediately. Cross-chain contracts serve as a bridge connecting two chains, responsible for securely and accurately transmitting identity information from chain A to chain B via VC. Cross-chain contracts encrypt VC data to ensure its confidentiality and integrity during transmission. Chain B receives the encrypted VC data and uses a decryption algorithm to obtain the decrypted original VC data.

4. The method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels according to claim 1, characterized in that, Chain B generates enterprise and individual DIDs based on the received VC data according to its own rules, adds them to the VC data, and then sends them back to Chain A to ensure consistency between the two chains' VC data. The process of obtaining consistent VC data between the two chains includes the following steps: Chain B will receive VC data containing enterprise and personal information, and automatically generate enterprise DIDs and personal DIDs on Chain B according to its own DID generation rules; Chain B adds two fields to the received VC data, so that the new VC data contains both the enterprise DID and the personal DID of both Chain A and Chain B. Chain B triggers a cross-chain contract to send the updated VC data back to Chain A, ensuring that the VC data on Chain A and Chain B are consistent, resulting in consistent VC data across both chains.

5. The method for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels according to claim 1, characterized in that, When a user has a DID on chain A, a query is initiated using the user's personal DID as an identifier. After the system locates the VC data, it is encrypted and transmitted to chain B via a cross-chain contract to ensure secure data transmission and obtain the encrypted VC data synchronized with chain A. This process includes the following steps: When a user already has an enterprise DID and a personal DID in Chain A, the user can use the personal DID as a query identifier to initiate a query request to the system. The system uses the user's personal DID to locate the corresponding identity information and network access VC data; The system encrypts the VC data and transmits it synchronously to chain B via a cross-chain contract, thus obtaining the encrypted VC data synchronized with chain A.

6. A cross-chain registration and mutual recognition system for DIDs supporting enterprise and individual levels, characterized in that, The DID cross-chain registration and mutual recognition system that supports enterprise and individual levels includes the following modules: Information collection module: When a user does not have a corporate and personal DID on the dual chain, they fill in their corporate and personal information as required by the system. Chain A generates corporate and personal DIDs according to a preset algorithm, and simultaneously generates identity information VC data containing dual information and dual DIDs. The VC data includes a version number and status field. Cross-chain contract module: After the identity information network VC data is generated, the cross-chain contract mechanism is triggered. The contract encrypts the VC data and transmits it to chain B. Chain B uses a decryption algorithm to obtain the original data and gets the decrypted original VC data. DID generation module: Existing identity cross-chain mutual recognition module: Based on the received VC data, Chain B generates enterprise and individual DIDs according to its own rules, adds them to the VC data, and then sends them back to Chain A to ensure that the VC data of the two chains is consistent, thus obtaining VC data that is consistent between the two chains; Identity Query Module: When a user has a DID on Chain A, the system initiates a query using the user's DID as the identifier. After locating the VC data, the system transmits it to Chain B via a cross-chain contract in an encrypted manner, ensuring secure data transmission and obtaining encrypted VC data synchronized with Chain A. Two-way binding module: Chain B generates enterprise and individual DIDs based on synchronized encrypted VC data, adds them to the VC data, and sends them back to Chain A. The dual-chain VC data contains the DIDs of both parties, forming a two-way binding, realizing mutual recognition of dual-chain DIDs, and obtaining VC data containing dual-chain DIDs.

7. A device for cross-chain registration and mutual recognition of DIDs at the enterprise and individual levels, characterized in that, The enterprise-person level DID cross-chain registration and mutual recognition device includes a memory and at least one processor. The memory stores instructions, and the at least one processor invokes the instructions in the memory to cause the enterprise-person level DID cross-chain registration and mutual recognition device to perform the various steps of the enterprise-person level DID cross-chain registration and mutual recognition method as described in any one of claims 1-5.

8. A computer-readable storage medium storing instructions thereon, characterized in that, When the instructions are executed by the processor, they implement the various steps of the cross-chain registration and mutual recognition method for DID at the enterprise-person level as described in any one of claims 1-5.

Images