A Blockchain-Based Metaverse Digital Identity Attack-Resistant Consensus Method and System
By combining multi-factor digital identity with node spatiotemporal information, the single point of failure and forgery problem of blockchain digital identity system is solved, realizing end-to-end trusted consensus process and improving system security and reliability.
Patent Information
- Application Number
- CN202611456351.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-18
- Publication Date
- 2026-11-17
AI Technical Summary
Existing blockchain digital identity systems face problems such as single point of failure, forgeryability, and insufficient scalability. Traditional consensus mechanisms rely on logical nodes, which are vulnerable to attacks, and fail to effectively integrate the spatiotemporal attributes of nodes with the consensus process.
By generating multi-factor digital identities bound to distributed identifiers, and combining verifiable delay functions and node spatiotemporal information, spatiotemporal credibility assessment is performed, and an end-to-end trust enhancement chain from identity registration to consensus process is constructed to achieve trusted verification of consensus nodes and block timestamps.
It enhances the anti-counterfeiting capabilities of digital identities, prevents single-dimensional attacks, and constructs a spatiotemporal trust foundation in the physical world and an unforgeable guarantee at the cryptographic level, forming a synergistic enhancement effect.
Smart Images

Figure CN123122969A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of metaverse digital identity technology, specifically relating to a blockchain-based metaverse digital identity anti-attack consensus method and system. Background Technology
[0002] With the rapid development of Web 3.0 and metaverse technologies, decentralized digital identity (DID) systems have gained widespread attention due to their significant advantages in user autonomy, interoperability, and openness. Blockchain technology, as the core infrastructure supporting digital identity management, provides a trustless technological foundation for the registration, verification, and credential management of digital identities through distributed ledgers, smart contracts, and consensus mechanisms. However, existing DID solutions still face serious challenges such as single points of failure, forgeryability, and insufficient scalability, limiting their applicability in large-scale ecosystems. Meanwhile, current blockchain consensus algorithms primarily rely on logical nodes in P2P networks for consensus decisions. This model has significant security vulnerabilities—node identity information and timestamps are easily forged by malicious attackers, leading to frequent transaction fraud attacks. For example, in February 2026, a critical consensus layer vulnerability codenamed "Tachyon" was disclosed in the CometBFT consensus engine driving the Cosmos ecosystem. Malicious proposers could exploit this vulnerability to manipulate block timestamps, thereby compromising time-sensitive applications. These security vulnerabilities demonstrate that traditional consensus mechanisms that rely solely on logical nodes and digital signatures cannot fundamentally guarantee the reliability and security of the consensus process.
[0003] To address the aforementioned issues, existing technologies, particularly CometBFT, introduce the "BFT Time" mechanism for timestamp security. This mechanism determines the block time by calculating the weighted median of timestamps in the validator's pre-committed messages, ensuring that a malicious minority cannot deviate from the blockchain time. In digital identity management, researchers have proposed a multi-layered blockchain-based DID framework, enhancing the system's decentralized robustness and unforgeability through a Redundant Byzantine Fault-Tolerant (RBFT) consensus protocol and a threshold signature algorithm. However, these solutions still have significant technical shortcomings: while the BFT Time mechanism can resist time manipulation by Byzantine validators, its time verification relies on the pre-committed messages of the validator set. Attackers can still indirectly influence time calculation by controlling a sufficient number of validator nodes or manipulating message propagation delays at the network level. Furthermore, most existing DID identity management schemes separate authentication from the consensus process, failing to incorporate the physical and spatiotemporal attributes of nodes (such as geographical coordinates and signal propagation delays) as a metric for consensus credibility into a unified authentication framework. Furthermore, Verifiable Delay Functions (VDFs), as cryptographic primitives capable of generating unforgeable time-based proofs, have been initially applied to consensus mechanisms such as Proof of History. However, existing solutions have failed to organically integrate them with the DID system and the spatiotemporal information verification of nodes to construct a trusted and enhanced chain from the source of identity to the entire consensus process. Therefore, there is an urgent need for a novel attack-resistant consensus method that can integrate distributed digital identity identifiers with node spatiotemporal information to simultaneously enhance the security and reliability of blockchain systems from both the source of identity authentication and the consensus process. Summary of the Invention
[0004] This invention addresses the shortcomings of existing technologies by providing a blockchain-based metaverse digital identity anti-attack consensus method and system.
[0005] To solve the above-mentioned technical problems, the present invention provides the following technical solution: A blockchain-based metaverse digital identity anti-attack consensus method includes the following steps: An identity registration request is submitted to the blockchain network. The registration node in the blockchain network receives the identity registration request and generates a distributed identifier based on the distributed digital identity specification. The registration node uses an asymmetric encryption algorithm to generate a public key and a private key that are paired with the distributed identifier, and combines the distributed identifier to generate and register the distributed digital identity identifier. The consensus management node in the blockchain network obtains the spatiotemporal information data of each candidate node in the network and performs spatiotemporal credibility evaluation on each candidate node to obtain a spatiotemporal credibility score. Based on the spatiotemporal credibility score, the master node of the current consensus round is selected. The master node receives transaction data and verifies its legality; if the verification passes, the transaction data is packaged into a candidate block, and the master node broadcasts the candidate block and its digital signature within the blockchain network to initiate a consensus proposal. Each consensus participating node receives a candidate block and performs basic verification. If the verification is successful, each consensus participating node independently verifies the consensus timestamp of the fused spatiotemporal information in the candidate block header based on the spatiotemporal information database. If the independent verification is successful, the block is considered a valid block. The identity status synchronization node in the blockchain network parses the digital identity-related transactions in the legitimate blocks; based on the parsing results, the identity status synchronization node updates the digital identity status database and synchronizes the updated identity status data to other nodes in the network, generating auditable operation logs and writing them to the audit log area of the blockchain ledger.
[0006] As one possible implementation method, the generation and registration of the distributed digital identity identifier includes the following steps: The registration node generates a distributed identifier document based on the W3C Distributed Identifier Core Specification. The distributed identifier document contains the distributed identifier, public key information, authentication method set, and server endpoint list. The registration node uses an asymmetric encryption system based on elliptic curve digital signature algorithm or national cryptographic SM2 algorithm to generate public and private key pairs. The public key is bound to a distributed identifier and written into the distributed identity management contract of the blockchain ledger, while the private key is stored locally securely by the user terminal device through a secure hardware module or trusted execution environment. The registration node receives an identity registration request, which includes the user's biometric information, device hardware fingerprint information, and user identity attribute declaration; the biometric information includes any one or more combinations of the user's fingerprint features, facial features, or iris features; the device hardware fingerprint information includes any one or more combinations of the terminal device's central processing unit serial number, network card MAC address, and trusted platform module identifier. The registration node uses a convolutional neural network model to extract feature vectors from biometric information, obtaining fixed-dimensional biometric feature vectors. The biometric feature vectors are then hashed to generate biometric hash values. The registration node constructs a tuple from the distributed identifier, biometric hash value, device hardware fingerprint information, and user identity attribute declaration. After digitally signing the tuple with the private key, the node submits the signature data and the tuple together to the distributed identity management contract of the blockchain network. After the signature is verified, the distributed identity management contract writes the association mapping relationship between the tuple and the distributed identifier into the state database of the blockchain ledger, thus completing the generation and registration of the distributed digital identity identifier.
[0007] As one possible implementation, the consensus management node in the blockchain network obtains spatiotemporal information data of each candidate node in the network and performs spatiotemporal credibility assessment on each candidate node. Based on the spatiotemporal credibility assessment results, it selects the master node for the current consensus round, including the following steps: Acquire the spatiotemporal information data of the candidate nodes, including the real-time geographic coordinates of each candidate node, network latency parameters, system timestamps, and signal propagation delay between the node and its neighboring nodes; The spatial distance matrix between candidate nodes is calculated based on the real-time geographic coordinates of the candidate nodes. The spatial distribution of each candidate node is then used to determine whether it meets the preset uniform distribution threshold, and the spatial distribution uniformity judgment result is obtained. The time synchronization deviation is calculated based on the system timestamp and the global reference time of the blockchain network. The time synchronization deviation of each candidate node is determined to be less than the preset time deviation tolerance threshold, and the time synchronization condition judgment result is obtained. The consensus management node integrates the spatial distribution uniformity judgment results and the time synchronization condition judgment results of each candidate node to generate a spatiotemporal credibility score for each candidate node. The candidate node obtains the highest score when it simultaneously meets the spatial distribution uniformity condition and the time synchronization condition. For candidate nodes that simultaneously satisfy the conditions of spatial distribution uniformity and time synchronization deviation, they are included in the consensus participation node candidate set. The consensus management node selects a predetermined number of candidate nodes from the consensus participation node candidate set according to a preset screening rule as consensus participation nodes for the current consensus round. The preset screening rule includes weighted sorting based on the reliability score of the node's historical consensus participation record, and selecting a predetermined number of nodes with the highest score.
[0008] As one possible implementation, the spatial distance matrix is calculated as follows: for any two candidate nodes i and j, the Euclidean distance or geodetic distance is calculated based on their real-time geographic coordinates, and a spatial distance matrix D is constructed, where D_ij represents the spatial distance between node i and node j. The consensus management node calculates the mean μ and standard deviation σ of the spatial distance between all pairs of candidate nodes. When the spatial distance between all pairs of candidate nodes is within the range of μ±kσ and the standard deviation σ is less than the preset spatial distribution dispersion threshold, the candidate node set is determined to meet the spatial distribution uniformity condition, where k is the preset confidence coefficient. The time synchronization deviation is calculated as follows: for each candidate node, the difference Δt between the timestamp reported by it and the global reference time maintained locally by the consensus management node is calculated. When |Δt| is less than the preset time deviation tolerance threshold T_tol, the candidate node is determined to meet the time synchronization condition.
[0009] As one possible implementation, the consensus timestamp that integrates spatiotemporal information includes a standard timestamp of the master node's local system time after synchronization calibration and a time proof value generated based on a verifiable delay function. The time proof value is obtained through the following steps: Before executing a consensus proposal, the master node pre-selects a safe prime number p and a primitive root g, and determines the number of iteration rounds T, which corresponds to a preset time delay target. The master node uses the concatenation of the current consensus round number R and the hash value H_prev of the previous block as the input seed, performs the T-round modulo exponentiation operation, and finally obtains the time proof value v_T; The master node writes the time proof value v_T, the iteration round number T, the safe prime number p, the primitive root g, and the input seed into the consensus timestamp field of the fused spatiotemporal information in the candidate block header; When verifying the time proof value, any verification node only needs to perform logarithmic-level modular operations using a fast verification algorithm based on the input seed, the safe prime number p, the primitive root g, and the number of iterations T. This can confirm the correctness of v_T in a time much less than T rounds of modular exponential operations, thereby ensuring that the time proof value has indeed undergone T rounds of continuous operations and has an unforgeable time attribute.
[0010] As one possible implementation, it also includes: The correctness of the time proof value is verified using a verification algorithm with a verifiable delay function, and the standard timestamp is compared with the reference time synchronized locally by each consensus participating node via NTP to determine whether the time deviation is less than the preset consensus time tolerance threshold. If the time proof value is verified and the time deviation is within the tolerance threshold, then each consensus participating node casts a vote in favor of the candidate block and broadcasts the vote with its own digital signature to the blockchain network. Each consensus participating node continuously collects voting information broadcast by other consensus participating nodes. When the number of votes in favor of a candidate block reaches a preset consensus threshold, the candidate block is confirmed as a valid block. Each consensus participating node then adds the valid block to its local blockchain ledger, completing the block confirmation for the current consensus round.
[0011] As one possible implementation, the independent verification also includes abnormal node detection and handling, with voting nodes voting on the candidate nodes, specifically including: Each consensus participating node collects voting information from voting nodes and records spatiotemporal information data of each voting node. The spatiotemporal information data includes the geographical coordinates of the voting nodes, the voting timestamp, and the network propagation path delay of the voting information. Consensus participating nodes perform spatiotemporal behavior consistency analysis on each voting node based on the recorded spatiotemporal information data. The spatiotemporal behavior consistency analysis includes: determining whether the geographical coordinates of the voting node are within a preset legal geographical area; determining whether the difference between the voting timestamp and the consensus timestamp in the candidate block header is less than a preset maximum voting delay threshold; and determining whether the network propagation path delay of the voting information matches the theoretical transmission delay corresponding to the geographical coordinates of the voting node. If any item in the spatiotemporal behavior consistency analysis of a voting node fails to meet the preset conditions, the voting of that voting node is marked as an abnormal vote. When the number of abnormal votes exceeds the preset abnormal threshold, the abnormal node reporting mechanism is triggered. The information of the relevant abnormal nodes is packaged into a reporting transaction and submitted to the blockchain network. The blockchain network then uses a distributed identity management contract to verify the identity of the abnormal nodes and deduct their reputation.
[0012] As one possible implementation, the transaction data includes digital identity authentication requests, issuance and verification operations of verifiable credentials, and identity status update operations; the trusted update and synchronization of the digital identity status by the identity status synchronization node also includes lifecycle management of the verifiable credentials, including the following steps: The verifiable credential is generated by the credential issuing authority in accordance with the W3C Verifiable Credential Data Model Specification, and includes credential context, credential type, credential subject identifier, credential issuer identifier, credential issuance time, credential validity period, and credential declaration content; the credential issuing authority uses its private key to digitally sign the verifiable credential and submits the signed verifiable credential to the credential management contract of the blockchain network; After the certificate management contract verifies the validity of the digital signature of the certificate issuing authority, it writes the metadata information of the verifiable certificate into the blockchain ledger. At the same time, the complete content of the verifiable certificate is stored through an off-chain distributed storage system, and a mapping relationship is established between the storage address pointer and the certificate identity identifier. When a verifiable credential needs to be revoked, the credential issuing authority submits a revocation request to the credential management contract. After verifying the validity of the signature of the revocation request, the credential management contract records the corresponding credential identifier in the credential revocation list and generates a revocation record containing the revocation time, revocation reason and revoker information, which is then written into the blockchain ledger. When a digital identity owner uses verifiable credentials for authentication, the verifier confirms the validity of the credentials and their status as not revoked by querying the credential metadata information and the credential revocation list in the blockchain ledger.
[0013] A blockchain-based metaverse digital identity anti-attack consensus system includes: The digital identity registration module submits an identity registration request to the blockchain network. The registration nodes in the blockchain network receive the identity registration request and generate a distributed identifier based on the distributed digital identity specification. The registration nodes use an asymmetric encryption algorithm to generate a public key and a private key that are paired with the distributed identifier, and combine the distributed identifier to generate and register the distributed digital identity identifier. The spatiotemporal information acquisition and evaluation module involves the consensus management node in the blockchain network acquiring spatiotemporal information data of each candidate node in the network and evaluating the spatiotemporal credibility of each candidate node to obtain a spatiotemporal credibility score. Based on the spatiotemporal credibility score, the master node of the current consensus round is selected. The consensus proposal building module involves the master node receiving transaction data and verifying its legality. If the verification passes, the transaction data is packaged into candidate blocks, and the master node broadcasts the candidate blocks and their digital signatures within the blockchain network to initiate a consensus proposal. In the consensus voting and confirmation module, each consensus participating node receives candidate blocks and performs basic verification. If the verification is successful, each consensus participating node independently verifies the consensus timestamp of the fused spatiotemporal information in the candidate block header based on the spatiotemporal information database. If the independent verification is successful, the block is considered a valid block. The identity status synchronization module involves identity status synchronization nodes in the blockchain network parsing digital identity-related transactions in the legitimate blocks; based on the parsing results, the identity status synchronization nodes update the digital identity status database and synchronize the updated identity status data to other nodes across the network, generating auditable operation logs and writing them to the audit log area of the blockchain ledger.
[0014] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method steps described below: An identity registration request is submitted to the blockchain network. The registration node in the blockchain network receives the identity registration request and generates a distributed identifier based on the distributed digital identity specification. The registration node uses an asymmetric encryption algorithm to generate a public key and a private key that are paired with the distributed identifier, and combines the distributed identifier to generate and register the distributed digital identity identifier. The consensus management node in the blockchain network obtains the spatiotemporal information data of each candidate node in the network and performs spatiotemporal credibility evaluation on each candidate node to obtain a spatiotemporal credibility score. Based on the spatiotemporal credibility score, the master node of the current consensus round is selected. The master node receives transaction data and verifies its legality; if the verification passes, the transaction data is packaged into a candidate block, and the master node broadcasts the candidate block and its digital signature within the blockchain network to initiate a consensus proposal. Each consensus participating node receives a candidate block and performs basic verification. If the verification is successful, each consensus participating node independently verifies the consensus timestamp of the fused spatiotemporal information in the candidate block header based on the spatiotemporal information database. If the independent verification is successful, the block is considered a valid block. The identity status synchronization node in the blockchain network parses the digital identity-related transactions in the legitimate blocks; based on the parsing results, the identity status synchronization node updates the digital identity status database and synchronizes the updated identity status data to other nodes in the network, generating auditable operation logs and writing them to the audit log area of the blockchain ledger.
[0015] Compared with the prior art, the solution proposed in this invention has the following beneficial effects: First, this invention breaks through the technical paradigm of separating identity verification from the consensus process in existing DID schemes. Existing DID solutions generally face challenges such as single point of failure (SPOF), forgeryability, and insufficient scalability. While multi-layered blockchain DID frameworks such as MDID enhance the decentralized robustness and unforgeability of the system through Redundant Byzantine Fault-Tolerant (RBFT) consensus protocols and threshold signature algorithms, their identity binding still mainly relies on a single cryptographic credential, failing to establish a verifiable association mapping between multi-factor information such as user biometrics and device hardware fingerprints and distributed identifiers. This invention binds biometric hash values and device hardware fingerprint information to DID through multi-factor authentication, constructing a three-dimensional trusted anchor of "biometrics-device-cryptography" from the source of identity registration. This prevents attackers from passing the dual verification of biometrics and device fingerprints even if they steal the user's private key, thus improving the anti-forgery capability of digital identities.
[0016] Second, this invention incorporates the physical spatiotemporal attributes of nodes as a quantifiable dimension of consensus credibility into the consensus mechanism. Existing consensus algorithms' timestamp protection mechanisms have inherent limitations—while CometBFT's BFT Time mechanism can calculate block time using the weighted median of validator pre-committed messages, its time verification essentially still relies on the pre-committed messages of the validator set. Attackers can still indirectly influence time calculation by controlling a sufficient number of validator nodes or manipulating message propagation delays at the network level. This invention combines the unforgeable time proof generated by the verifiable delay function (VDF) with the verification of the spatial distribution uniformity of node geographic coordinates. Through this dual "space-time" constraint, it achieves reliable verification of consensus nodes and block timestamps, preventing single-dimensional attacks.
[0017] Third, this invention constructs an end-to-end trusted enhancement chain from identity registration, node selection, block construction to voting confirmation. In existing technologies, VDF has been initially applied to consensus mechanisms such as Proof of History to generate immutable time records, and spatiotemporal information has also been attempted for consensus node selection in specific scenarios such as the Internet of Vehicles. However, no solution has yet organically integrated the DID system, node spatiotemporal information verification, and VDF time proof. This invention achieves real-time detection and isolation of abnormal nodes through spatiotemporal behavior consistency analysis, and achieves the survival of the fittest among consensus participants through a dynamic reputation scoring mechanism. This ensures that the entire consensus process possesses both a spatiotemporal trusted foundation in the physical world and cryptographic unforgeability guarantees, forming a synergistic enhancement effect. Attached Figure Description
[0018] Figure 1 This is a schematic flowchart of the method of the present invention; Figure 2 This is a system architecture diagram of the present invention. Detailed Implementation
[0019] To clearly illustrate the present invention and make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings, so that those skilled in the art can implement the invention based on the description. The technology of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.
[0020] Example 1: To facilitate understanding of this invention, each step S100 to S500 in this embodiment is summarized, and the summary is placed at the beginning of each step. These summaries constitute the technical content embodying this invention and fall within the protection scope of this invention. A blockchain-based metaverse digital identity anti-attack consensus method, such as... Figure 1As shown, it includes the following steps: Step S100: Generation and Registration of Distributed Digital Identity Identifier: The digital identity owner submits an identity registration request to the blockchain network through the user terminal device. The identity registration request includes the user's biometric information, device hardware fingerprint information, and the identity attribute declaration set by the user. After receiving the identity registration request, the registration node in the blockchain network generates a distributed identifier (DID) uniquely corresponding to the user based on the Distributed Digital Identity (DID) specification. The distributed identifier consists of three parts: a method identifier, a specific identifier string, and a check code. The registration node uses an asymmetric encryption algorithm to generate a public-private key pair that matches the distributed identifier. The public key is bound to the distributed identifier and written into the distributed identity management contract of the blockchain ledger. The private key is stored securely locally by the user terminal device through a secure hardware module or a trusted execution environment (TEE). In step S100 above, after the registration node extracts the feature vector from the identity biometric information, it generates a biometric hash value using a hash algorithm. The biometric hash value and the device hardware fingerprint information are used as auxiliary verification factors for identity binding. A multi-factor association mapping relationship is established with the distributed identifier, and this mapping relationship is recorded in the blockchain ledger, completing the generation and registration of the digital identity distributed identifier. The specific method for generating the distributed identifier and establishing the multi-factor association mapping relationship is as follows: S101: The registration node generates a DID document according to the W3C DID Core specification. The DID document contains a DID identifier, public key information, a set of authentication methods, and a list of server endpoints. S102: The registered node uses an asymmetric encryption system based on Elliptic Curve Digital Signature Algorithm (ECDSA) or Chinese national cryptographic algorithm SM2 to generate a public-private key pair, wherein the public key is embedded in the public key field of the DID document in JSON Web Key (JWK) format; S103: The biometric information includes any one or more combinations of the user's fingerprint features, facial features, or iris features. The registration node uses a convolutional neural network model to extract feature vectors from the biometric information to obtain fixed-dimensional biometric vectors. Then, the SHA-256 or SM3 hash algorithm is used to perform hash operations on the biometric vectors to generate biometric hash values. S104: The device hardware fingerprint information includes any one or more combinations of the terminal device's central processing unit serial number, network card MAC address, and Trusted Platform Module (TPM) identifier; S105: The registration node constructs a tuple from the distributed identifier, biometric hash value, device hardware fingerprint information, and user identity attribute declaration. After digitally signing the tuple with the private key, the node submits the signature data and the tuple together to the distributed identity management contract of the blockchain network. S106: After the signature verification is successful, the distributed identity management contract writes the association mapping relationship between the tuple and the distributed identifier into the state database of the blockchain ledger.
[0021] Step S200: Consensus Participant Node Screening Based on Spatiotemporal Information: The consensus management node in the blockchain network periodically acquires spatiotemporal information data of each candidate node in the network. This spatiotemporal information data includes the real-time geographical coordinates of each candidate node, network latency parameters, system timestamps, and signal propagation delays between the node and its neighbors. Based on the acquired spatiotemporal information data, the consensus management node performs a spatiotemporal credibility assessment on each candidate node. This assessment includes: evaluation based on geographical coordinates... The system calculates the spatial distance matrix between candidate nodes and determines whether the spatial distribution of each candidate node meets a preset uniform distribution threshold. It then calculates the time synchronization deviation based on the system timestamp and the global reference time of the blockchain network, determining whether the time synchronization deviation of each candidate node is less than a preset time deviation tolerance threshold. For candidate nodes that simultaneously meet both the spatial distribution uniformity condition and the time synchronization deviation condition, they are included in the consensus participant node candidate set. The consensus management node selects a predetermined number of nodes from the consensus participant node candidate set according to preset screening rules as consensus participant nodes for the current consensus round. These preset screening rules include weighted sorting based on the reliability scores of the nodes' historical consensus participation records, selecting the predetermined number of nodes with the highest scores. In step S200 above, the specific implementation of the spatiotemporal reliability assessment further includes: S201: The spatial distance matrix is calculated as follows: For any two candidate nodes i and j, calculate the Euclidean distance or geodetic distance based on their geographic coordinates, and construct the spatial distance matrix D, where D_ij represents the spatial distance between node i and node j; S202: The consensus management node calculates the mean μ and standard deviation σ of the spatial distance between all pairs of candidate nodes. When the spatial distance between all pairs of candidate nodes is within the range of μ±kσ and the standard deviation σ is less than the preset spatial distribution dispersion threshold, the candidate node set is determined to meet the spatial distribution uniformity condition, where k is the preset confidence coefficient. S203: The time synchronization deviation calculation method is as follows: For each candidate node, calculate the difference Δt between the timestamp reported by it and the global reference time maintained locally by the consensus management node. When |Δt| is less than the preset time deviation tolerance threshold T_tol, it is determined that the candidate node meets the time synchronization condition. S204: The consensus management node integrates the spatial distribution uniformity judgment results and the time synchronization condition judgment results of each candidate node to generate a spatiotemporal credibility score for each candidate node. The spatiotemporal credibility score is a binary value or a continuous value. The candidate node obtains the highest score when it simultaneously meets the spatial distribution uniformity condition and the time synchronization condition.
[0022] Step S300: Construction of Consensus Proposal Blocks Integrating Spatiotemporal Information: The master node selected for the current consensus round receives transaction data from the blockchain network. This transaction data includes digital identity authentication requests, issuance and verification operations of Verifiable Credentials (VCs), and identity status update operations. The master node performs legality verification on the received transaction data. This verification includes digital signature verification of the transaction initiator, transaction format compliance checks, and consistency checks between the transaction content and the current blockchain state. After successful verification, the master node packages the legitimate transactions into candidate blocks and writes the current consensus round number, the previous block hash value, the Merklegen hash value, and a consensus timestamp integrating spatiotemporal information into the block header of the candidate blocks. This consensus timestamp includes two time dimensions: one is the standard timestamp after the master node's local system time is synchronized and calibrated using the Network Time Protocol (NTP); the other is based on a Verifiable Delay function. The unforgeable time proof value is generated by the Function (VDF); the unforgeable time proof value is generated by the master node performing a preset number of rounds of modulo exponential operation, the output of which has time determinism, and any node can quickly verify the correctness of the time proof value through a preset verification algorithm without re-executing all operations; the master node broadcasts the completed candidate block and its digital signature in the blockchain network and initiates a consensus proposal; The specific method for generating an unforgeable time proof value using the verifiable delay function in step S300 is as follows: 301: Before executing a consensus proposal, the master node pre-selects a secure prime number p and a primitive root g, and determines the iteration round number T, which corresponds to the preset time delay target. The master node uses the concatenation value of the current consensus round number R and the hash value H_prev of the previous block as the input seed, and performs the T-round modulo exponentiation operation: v_0 = g^{seed} mod p, v_{k+1} = v_k^2 mod p, k=0,1,...,T-1, and finally obtains the time proof value v_T. 302: The master node writes the time proof value v_T, the iteration round number T, the safe prime number p, the primitive root g, and the input seed into the consensus timestamp field of the fused spatiotemporal information in the candidate block header; 303: When verifying the time proof value, any verification node only needs to perform logarithmic-level modular operations using a fast verification algorithm based on the input seed, the safe prime number p, the primitive root g, and the number of iterations T. This will confirm the correctness of v_T in a time much less than T rounds of modular exponential operations, thereby ensuring that the time proof value has indeed undergone T rounds of continuous operations and has an unforgeable time attribute.
[0023] Step S400: Consensus Voting and Confirmation Based on Spatiotemporal Information Verification: After receiving the candidate blocks broadcast by the master node, each consensus participating node first performs basic verification on the candidate blocks. The basic verification includes candidate block format verification, transaction Merklegen hash value verification, and verification of the validity of the master node's digital signature. After the basic verification is passed, each consensus participating node independently verifies the consensus timestamp with integrated spatiotemporal information in the candidate block header using its locally maintained spatiotemporal information database. The independent verification includes: verifying the correctness of the unforgeable time proof value using a verification algorithm with a verifiable delay function, and comparing the standard timestamp with the reference time synchronized locally by each consensus participating node via NTP to determine whether the time deviation is less than a preset consensus time tolerance threshold; if the time proof value is verified and the time deviation is within the tolerance threshold range, each consensus participating node casts a vote in favor of the candidate block and broadcasts the vote with its own digital signature to the blockchain network; each consensus participating node simultaneously continues to collect voting information broadcast by other consensus participating nodes, and when the number of votes collected for a candidate block reaches a preset consensus threshold, the candidate block is confirmed as a valid block, and each consensus participating node appends the valid block to its local blockchain ledger to complete the block confirmation for the current consensus round; The consensus voting and confirmation based on spatiotemporal information verification in step S400 also includes an abnormal node detection and handling mechanism, where voting nodes vote for the candidate nodes. Specific steps include: S401: When collecting voting information from other nodes, each consensus participating node also records the spatiotemporal information data of each voting node. The spatiotemporal information data includes the geographical coordinates of the voting node, the voting timestamp, and the network propagation path delay of the voting information. S402: Consensus participating nodes perform spatiotemporal behavior consistency analysis on each voting node based on the recorded spatiotemporal information data. The spatiotemporal behavior consistency analysis includes: determining whether the geographical coordinates of the voting node are within a preset legal geographical area; determining whether the difference between the voting timestamp and the consensus timestamp in the candidate block header is less than a preset maximum voting delay threshold; and determining whether the network propagation path delay of the voting information matches the theoretical transmission delay corresponding to the geographical coordinates of the voting node. S403: If any item in the spatiotemporal behavior consistency analysis of a voting node fails to meet the preset conditions, the voting of that voting node is marked as an abnormal vote. S404: When the number of abnormal votes exceeds the preset abnormal threshold, the abnormal node reporting mechanism is triggered. The information of the relevant abnormal nodes is packaged into a reporting transaction and submitted to the blockchain network. The blockchain network then uses a distributed identity management contract to verify the identity and deduct reputation of the abnormal nodes.
[0024] Step S500: Trusted Update and Synchronization of Digital Identity Status: After a legitimate block is confirmed and appended to the blockchain ledger, the identity status synchronization node in the blockchain network parses all digital identity-related transactions contained in the legitimate block. These digital identity-related transactions include the creation, update, and revocation of DID documents, the issuance and revocation of verifiable credentials, and the addition and modification of identity attribute declarations. Based on the parsing results, the identity status synchronization node updates the locally maintained digital identity status database and synchronizes the updated identity status data to other nodes across the network through the blockchain network's P2P propagation mechanism. Simultaneously, the identity status synchronization node writes the block height, transaction index, and spatiotemporal information verification records used for this identity status update as auditable operation logs into the audit log area of the blockchain ledger, forming a complete and traceable chain of digital identity status changes. Specifically, the trusted update and synchronization of digital identity status in step S500 also includes lifecycle management of verifiable credentials: 501: The verifiable credential is generated by the credential issuing authority in accordance with the W3C Verifiable Credentials Data Model specification, and includes the credential context, credential type, credential subject identifier, credential issuer identifier, credential issuance time, credential validity period, and credential declaration content. 502: The issuing authority uses its private key to digitally sign the verifiable credential and submits the signed verifiable credential to the credential management contract of the blockchain network. 503: After the certificate management contract verifies the validity of the digital signature of the certificate issuing authority, it writes the metadata information of the verifiable certificate (including certificate ID, issuer DID, holder DID, issuance time, validity period, certificate type and certificate hash value) into the blockchain ledger. At the same time, it stores the complete content of the verifiable certificate through an off-chain distributed storage system (such as IPFS) and establishes a mapping relationship between the storage address pointer and the certificate ID. 504: When a verifiable credential needs to be revoked, the credential issuing authority submits a revocation request to the credential management contract. After verifying the validity of the signature of the revocation request, the credential management contract records the corresponding credential ID in the credential revocation list and generates a revocation record containing the revocation time, revocation reason and revoker information, which is then written to the blockchain ledger. 505: When a digital identity owner uses verifiable credentials for authentication, the verifier confirms the validity and non-revocation status of the credentials by querying the credential metadata information and credential revocation list in the blockchain ledger.
[0025] Example 2: A blockchain-based metaverse digital identity anti-attack consensus system, such as Figure 2 As shown, the modules work together to support the method described in this invention. For details of the method, please refer to Embodiment 1, which will not be repeated here. The system of this invention includes: The digital identity registration module 100 is configured to receive an identity registration request submitted by a digital identity owner through a user terminal device. The identity registration request includes the user's biometric information, device hardware fingerprint information, and a user-defined identity attribute declaration. Based on the distributed digital identity specification, a distributed identifier (DID) uniquely corresponding to the user is generated. An asymmetric encryption algorithm is used to generate a public-private key pair paired with the distributed identifier. The public key is bound to the distributed identifier and written into a distributed identity management contract in the blockchain ledger. The private key is securely stored locally by the user terminal device through a secure hardware module or a trusted execution environment. Furthermore, the module extracts feature vectors from the biometric information to generate a biometric hash value. The biometric hash value and device hardware fingerprint information are used as auxiliary verification factors for identity binding. A multi-factor association mapping relationship is established with the distributed identifier, and this mapping relationship is recorded in the blockchain ledger. The spatiotemporal information acquisition and evaluation module 200 is configured to periodically acquire spatiotemporal information data of each candidate node in the blockchain network. This spatiotemporal information data includes the real-time geographic coordinates, network latency parameters, system timestamps, and signal propagation delays between nodes and their neighbors. Based on the acquired spatiotemporal information data, the module performs a spatiotemporal credibility evaluation on each candidate node. This evaluation includes: calculating the spatial distance matrix between candidate nodes based on their geographic coordinates and determining the uniformity of spatial distribution; calculating the time synchronization deviation based on the system timestamp and the global reference time and determining the time synchronization conditions; including candidate nodes that simultaneously meet both the uniformity of spatial distribution and the time synchronization deviation conditions in the consensus participant node candidate set; and selecting a predetermined number of nodes from the consensus participant node candidate set according to preset screening rules as consensus participant nodes for the current consensus round. The spatiotemporal information acquisition and evaluation module 200 further includes a node reputation management submodule. This submodule is configured to maintain a reputation score record for each candidate node, including the node's historical consensus participation count, historical voting accuracy, historical spatiotemporal information verification pass rate, and historical abnormal behavior records. After each consensus round, the reputation score of the corresponding node is dynamically updated based on the actual behavior of each consensus participating node in that round. The dynamic update rules are as follows: nodes that correctly complete consensus voting and pass spatiotemporal information verification are given reputation bonuses; nodes that vote abnormally, fail spatiotemporal information verification, or are reported as abnormal nodes are given reputation deductions. When a node's reputation score is lower than a preset reputation threshold, the node is included in the low-reputation node list and excluded from the consensus participating node selection in subsequent consensus rounds. When a node's reputation score is consistently higher than a preset excellent threshold in multiple consecutive consensus rounds, the node is included in the high-reputation node list and given priority in the consensus participating node selection in subsequent consensus rounds. The consensus proposal construction module 300 is configured to receive transaction data from the blockchain network and verify the legality of the transaction data in the master node selected for the current consensus round; after the verification is passed, the legal transactions are packaged into candidate blocks, and the round number of the current consensus round, the hash value of the previous block, the Merklegen hash value, and a consensus timestamp that integrates spatiotemporal information are written into the block header of the candidate blocks. The consensus timestamp that integrates spatiotemporal information includes a standard timestamp and an unforgeable time proof value generated based on a verifiable delay function; and broadcast the constructed candidate blocks and their digital signatures within the blockchain network to initiate a consensus proposal. The consensus voting and confirmation module 400 is configured to perform basic verification on the received candidate blocks in each consensus participating node. The basic verification includes candidate block format verification, transaction Merklegen hash value verification, and master node digital signature validity verification. After the basic verification is passed, the consensus timestamp with fused spatiotemporal information in the candidate block header is independently verified using a locally maintained spatiotemporal information database. If the verification is passed, a vote of approval is cast for the candidate block and the vote of approval with its own digital signature is broadcast to the blockchain network. The module also continuously collects voting information broadcast by other consensus participating nodes. When the number of votes of approval collected for a candidate block reaches a preset consensus threshold, the candidate block is confirmed as a valid block and appended to the local blockchain ledger. The identity status synchronization module 500 is configured to, after a valid block is confirmed and appended to the blockchain ledger, parse all digital identity-related transactions contained in the valid block. These digital identity-related transactions include the creation, updating, and revocation of DID documents, the issuance and revocation of verifiable credentials, and the addition and modification of identity attribute declarations. Based on the parsing results, the module updates the locally maintained digital identity status database and synchronizes the updated identity status data to other nodes across the blockchain network through the P2P propagation mechanism. It also writes the block height, transaction index, and spatiotemporal information verification records used for this identity status update as auditable operation logs into the audit log area of the blockchain ledger.
[0026] Another embodiment of the present invention provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the steps of any one of steps S100 to S500 (including sub-steps) of the method of the present invention: a consensus method for anti-attack based on trusted blockchain-based distributed digital identity fusion and spatiotemporal information enhancement. The computer-readable storage medium includes a non-volatile storage medium, which is any one of read-only memory (ROM), flash memory, solid-state drive (SSD), hard disk drive (HDD), or removable storage card. The computer program includes a digital identity registration module. The program code includes a spatiotemporal information acquisition and evaluation module, a consensus proposal construction module, a consensus voting and confirmation module, and an identity status synchronization module. When the program code is executed by the processor, the digital identity registration module generates a distributed identifier unique to the user and establishes a multi-factor association mapping relationship; the spatiotemporal information acquisition and evaluation module evaluates the spatiotemporal credibility of each candidate node and selects consensus participating nodes; the consensus proposal construction module constructs candidate blocks containing consensus timestamps that integrate spatiotemporal information; the consensus voting and confirmation module performs consensus voting and block confirmation based on spatiotemporal information verification; and the identity status synchronization module performs trusted updates and network-wide synchronization of digital identity status.
[0027] The above description of the embodiments is provided to enable those skilled in the art to understand and apply the present invention. It will be apparent to those skilled in the art that various modifications can be made to the above embodiments, and the general principles described herein can be applied to other embodiments without inventive effort. Therefore, the present invention is not limited to the above embodiments, and any improvements and modifications made to the present invention by those skilled in the art based on the disclosure thereof should be within the scope of protection of the present invention.
Claims
1. A blockchain-based anti-attack consensus method for a metaverse digital identity, characterized in that, Includes the following steps: An identity registration request is submitted to the blockchain network, and the registration node in the blockchain network receives the identity registration request and generates a distributed identifier based on the distributed digital identity specification. The registration node uses an asymmetric encryption algorithm to generate a public key and a private key that are paired with the distributed identifier, and combines the distributed identifier to generate and register a digital identity distributed identifier; The consensus management node in the blockchain network obtains the spatiotemporal information data of each candidate node in the network and performs spatiotemporal credibility evaluation on each candidate node to obtain a spatiotemporal credibility score. Based on the spatiotemporal credibility score, the master node of the current consensus round is selected. The master node receives transaction data and verifies its validity; If the verification passes, the transaction data is packaged into a candidate block, and the master node broadcasts the candidate block and its digital signature within the blockchain network to initiate a consensus proposal. Each consensus participating node receives a candidate block and performs basic verification. If the verification is successful, each consensus participating node independently verifies the consensus timestamp of the fused spatiotemporal information in the candidate block header based on the spatiotemporal information database. If the independent verification is successful, the block is considered a valid block. The identity status synchronization node in the blockchain network parses digital identity-related transactions in the legitimate blocks; The identity status synchronization node updates the digital identity status database based on the parsing results, and synchronizes the updated identity status data to other nodes across the network, generating auditable operation logs that are written to the audit log area of the blockchain ledger.
2. The blockchain-based metaverse digital identity attack-resistant consensus method according to claim 1, characterized in that, The generation and registration of the distributed digital identity includes the following steps: The registration node generates a distributed identifier document based on the W3C Distributed Identifier Core Specification. The distributed identifier document contains the distributed identifier, public key information, authentication method set, and server endpoint list. The registration node uses an asymmetric encryption system based on elliptic curve digital signature algorithm or national cryptographic SM2 algorithm to generate public and private key pairs. The public key is bound to a distributed identifier and written into the distributed identity management contract of the blockchain ledger, while the private key is stored locally securely by the user terminal device through a secure hardware module or trusted execution environment. The registration node receives an identity registration request, which includes the user's biometric information, device hardware fingerprint information, and user identity attribute declaration; the biometric information includes any one or more combinations of the user's fingerprint features, facial features, or iris features; the device hardware fingerprint information includes any one or more combinations of the terminal device's central processing unit serial number, network card MAC address, and trusted platform module identifier. The registration node uses a convolutional neural network model to extract feature vectors from biometric information, obtaining fixed-dimensional biometric feature vectors. The biometric feature vectors are then hashed to generate biometric hash values. The registration node constructs a tuple from the distributed identifier, biometric hash value, device hardware fingerprint information, and user identity attribute declaration. After digitally signing the tuple with the private key, the node submits the signature data and the tuple together to the distributed identity management contract of the blockchain network. After the signature is verified, the distributed identity management contract writes the association mapping relationship between the tuple and the distributed identifier into the state database of the blockchain ledger, thus completing the generation and registration of the distributed digital identity identifier.
3. The blockchain-based metaverse digital identity attack-resistant consensus method according to claim 1, characterized in that, The consensus management node in the blockchain network obtains spatiotemporal information data of each candidate node in the network and performs spatiotemporal credibility assessment on each candidate node. Based on the spatiotemporal credibility assessment results, it selects the master node for the current consensus round, including the following steps: Acquire the spatiotemporal information data of the candidate nodes, including the real-time geographic coordinates of each candidate node, network latency parameters, system timestamps, and signal propagation delay between the node and its neighboring nodes; The spatial distance matrix between candidate nodes is calculated based on the real-time geographic coordinates of the candidate nodes. The spatial distribution of each candidate node is then used to determine whether it meets the preset uniform distribution threshold, and the spatial distribution uniformity judgment result is obtained. The time synchronization deviation is calculated based on the system timestamp and the global reference time of the blockchain network. The time synchronization deviation of each candidate node is determined to be less than the preset time deviation tolerance threshold, and the time synchronization condition judgment result is obtained. The consensus management node integrates the spatial distribution uniformity judgment results and the time synchronization condition judgment results of each candidate node to generate a spatiotemporal credibility score for each candidate node. The candidate node obtains the highest score when it simultaneously meets the spatial distribution uniformity condition and the time synchronization condition. For candidate nodes that simultaneously satisfy the conditions of spatial distribution uniformity and time synchronization deviation, they are included in the consensus participation node candidate set. The consensus management node selects a predetermined number of candidate nodes from the consensus participation node candidate set according to a preset screening rule as consensus participation nodes for the current consensus round. The preset screening rule includes weighted sorting based on the reliability score of the node's historical consensus participation record, and selecting a predetermined number of nodes with the highest score.
4. The blockchain-based metaverse digital identity attack-resistant consensus method according to claim 1 or 3, characterized in that, The spatial distance matrix is calculated as follows: for any two candidate nodes i and j, the Euclidean distance or geodetic distance is calculated based on their real-time geographic coordinates, and a spatial distance matrix D is constructed, where D_ij represents the spatial distance between node i and node j. The consensus management node calculates the mean μ and standard deviation σ of the spatial distance between all pairs of candidate nodes. When the spatial distance between all pairs of candidate nodes is within the range of μ±kσ and the standard deviation σ is less than the preset spatial distribution dispersion threshold, the candidate node set is determined to meet the spatial distribution uniformity condition, where k is the preset confidence coefficient. The time synchronization deviation is calculated as follows: for each candidate node, the difference Δt between the timestamp reported by it and the global reference time maintained locally by the consensus management node is calculated. When |Δt| is less than the preset time deviation tolerance threshold T_tol, the candidate node is determined to meet the time synchronization condition.
5. The blockchain-based metaverse digital identity attack-resistant consensus method according to claim 1, characterized in that, The consensus timestamp that integrates spatiotemporal information includes a standard timestamp of the master node's local system time after synchronization and calibration, and a time proof value generated based on a verifiable delay function. The time proof value is obtained through the following steps: Before executing a consensus proposal, the master node pre-selects a safe prime number p and a primitive root g, and determines the number of iteration rounds T, which corresponds to a preset time delay target. The master node uses the concatenation of the current consensus round number R and the hash value H_prev of the previous block as the input seed, performs the T-round modulo exponentiation operation, and finally obtains the time proof value v_T; The master node writes the time proof value v_T, the iteration round number T, the safe prime number p, the primitive root g, and the input seed into the consensus timestamp field of the fused spatiotemporal information in the candidate block header; When verifying the time proof value, any verification node only needs to perform logarithmic-level modular operations using a fast verification algorithm based on the input seed, the safe prime number p, the primitive root g, and the number of iterations T. This can confirm the correctness of v_T in a time much less than T rounds of modular exponential operations, thereby ensuring that the time proof value has indeed undergone T rounds of continuous operations and has an unforgeable time attribute.
6. The blockchain-based metaverse digital identity attack-resistant consensus method according to claim 5, characterized in that, Also includes: The correctness of the time proof value is verified using a verification algorithm with a verifiable delay function, and the standard timestamp is compared with the reference time synchronized locally by each consensus participating node via NTP to determine whether the time deviation is less than the preset consensus time tolerance threshold. If the time proof value is verified and the time deviation is within the tolerance threshold, then each consensus participating node casts a vote in favor of the candidate block and broadcasts the vote with its own digital signature to the blockchain network. Each consensus participating node continuously collects voting information broadcast by other consensus participating nodes. When the number of votes in favor of a candidate block reaches a preset consensus threshold, the candidate block is confirmed as a valid block. Each consensus participating node then adds the valid block to its local blockchain ledger, completing the block confirmation for the current consensus round.
7. The blockchain-based metaverse digital identity attack-resistant consensus method according to claim 1, characterized in that, The independent verification also includes abnormal node detection and handling, with voting nodes voting on the candidate nodes, specifically including: Each consensus participating node collects voting information from voting nodes and records spatiotemporal information data of each voting node. The spatiotemporal information data includes the geographical coordinates of the voting nodes, the voting timestamp, and the network propagation path delay of the voting information. Consensus participating nodes perform spatiotemporal behavior consistency analysis on each voting node based on the recorded spatiotemporal information data. The spatiotemporal behavior consistency analysis includes: determining whether the geographical coordinates of the voting node are within a preset legal geographical area; determining whether the difference between the voting timestamp and the consensus timestamp in the candidate block header is less than a preset maximum voting delay threshold; and determining whether the network propagation path delay of the voting information matches the theoretical transmission delay corresponding to the geographical coordinates of the voting node. If any item in the spatiotemporal behavior consistency analysis of a voting node fails to meet the preset conditions, the voting of that voting node is marked as an abnormal vote. When the number of abnormal votes exceeds the preset abnormal threshold, the abnormal node reporting mechanism is triggered. The information of the relevant abnormal nodes is packaged into a reporting transaction and submitted to the blockchain network. The blockchain network then uses a distributed identity management contract to verify the identity of the abnormal nodes and deduct their reputation.
8. The blockchain-based metaverse digital identity attack-resistant consensus method according to claim 1, characterized in that, The transaction data includes digital identity authentication requests, issuance and verification operations of verifiable credentials, and identity status update operations; the trusted update and synchronization of digital identity status by the identity status synchronization node also includes lifecycle management of the verifiable credentials, including the following steps: The verifiable credential is generated by the credential issuing authority in accordance with the W3C Verifiable Credential Data Model Specification, and includes credential context, credential type, credential subject identifier, credential issuer identifier, credential issuance time, credential validity period, and credential declaration content; the credential issuing authority uses its private key to digitally sign the verifiable credential and submits the signed verifiable credential to the credential management contract of the blockchain network; After the certificate management contract verifies the validity of the digital signature of the certificate issuing authority, it writes the metadata information of the verifiable certificate into the blockchain ledger. At the same time, the complete content of the verifiable certificate is stored through an off-chain distributed storage system, and a mapping relationship is established between the storage address pointer and the certificate identity identifier. When a verifiable credential needs to be revoked, the credential issuing authority submits a revocation request to the credential management contract. After verifying the validity of the signature of the revocation request, the credential management contract records the corresponding credential identifier in the credential revocation list and generates a revocation record containing the revocation time, revocation reason and revoker information, which is then written into the blockchain ledger. When a digital identity owner uses verifiable credentials for authentication, the verifier confirms the validity of the credentials and their status as not revoked by querying the credential metadata information and the credential revocation list in the blockchain ledger. 9.A blockchain-based anti-attack consensus system for a metaverse digital identity, characterized in that, include: The digital identity registration module submits an identity registration request to the blockchain network. The registration nodes in the blockchain network receive the identity registration request and generate a distributed identifier based on the distributed digital identity specification. The registration node uses an asymmetric encryption algorithm to generate a public key and a private key that are paired with the distributed identifier, and combines the distributed identifier to generate and register a digital identity distributed identifier; The spatiotemporal information acquisition and evaluation module involves the consensus management node in the blockchain network acquiring spatiotemporal information data of each candidate node in the network and evaluating the spatiotemporal credibility of each candidate node to obtain a spatiotemporal credibility score. Based on the spatiotemporal credibility score, the master node of the current consensus round is selected. The consensus proposal building module involves the master node receiving transaction data and verifying its legality. If the verification passes, the transaction data is packaged into a candidate block, and the master node broadcasts the candidate block and its digital signature within the blockchain network to initiate a consensus proposal. In the consensus voting and confirmation module, each consensus participating node receives candidate blocks and performs basic verification. If the verification is successful, each consensus participating node independently verifies the consensus timestamp of the fused spatiotemporal information in the candidate block header based on the spatiotemporal information database. If the independent verification is successful, the block is considered a valid block. The identity status synchronization module is used by identity status synchronization nodes in the blockchain network to parse digital identity-related transactions in the legitimate blocks. The identity status synchronization node updates the digital identity status database based on the parsing results, and synchronizes the updated identity status data to other nodes across the network, generating auditable operation logs that are written to the audit log area of the blockchain ledger.
10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 8.
