Number authentication method and system based on block chain

Abstract

The invention discloses a block chain-based number authentication method and system, and relates to the technical field of block chains. The method comprises the following steps: generating a number identifier according to number information of a user and a real name identifier according to real name information, and generating an anti-quantum public and private key pair by using a quantum resistance encryption algorithm; according to the number identifier, the real name identifier and the anti-quantum public key, generating a digital identity identifier of the user, and recording the digital identity identifier in the block chain based on the smart contract; when a number authentication request is carried out, an operation request is signed to generate an anti-quantum signature value, and a zero-knowledge proof file is generated based on an anti-quantum private key and a zero-knowledge proof protocol; transmitting the anti-quantum signature value and the zero-knowledge proof file to an authentication node, and verifying the number information of the user to obtain an authentication result; and if the number authentication is passed, updating the state of the number information according to the operation request, and broadcasting to other nodes of the block chain. The security and efficiency of number authentication are effectively improved, and the number state is updated and synchronized in time.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a blockchain-based number authentication method and system. Background Art

[0002] With the rapid development of mobile internet and digital identity management technologies, mobile phone numbers have become a core credential for user authentication, widely used in key scenarios such as financial transactions, social platforms, and government services. However, the relevant mobile phone number authentication system relies on centralized management by operators or platforms, which poses significant security risks and efficiency bottlenecks. On the one hand, traditional identity authentication methods rely heavily on mechanisms such as SMS verification codes and SIM card binding. Attackers can illegally obtain user numbers through methods such as SMS sniffing, SIM card hijacking, and social engineering attacks, and then impersonate users to perform sensitive operations, causing serious financial losses and a crisis of trust. On the other hand, there is a lack of a unified, real-time synchronization mechanism for updating number status. After users actively deactivate or cancel their numbers, the services associated with them are often not promptly unlinked due to information lags, posing a potential security risk.

[0003] Furthermore, existing number management systems often rely on manual review processes or centralized database maintenance, resulting in slow response times and insufficient transparency, making them difficult to adapt to the dynamic needs of large-scale users. While blockchain technology has demonstrated tremendous potential in decentralized identity authentication and trusted data storage in recent years, and its immutability and distributed consensus mechanism offer new avenues for identity management, it still faces numerous challenges in addressing complex scenarios requiring high security, high concurrency, and the threat of future quantum computing. Therefore, there is an urgent need to propose a new number authentication method that balances security, scalability, and real-time responsiveness to effectively address core pain points such as identity fraud, delayed status updates, and excessive reliance on centralization, thereby driving the evolution of number authentication systems towards a more trustworthy, open, and intelligent approach. Summary of the Invention

[0004] This application aims to solve at least one of the technical problems existing in the prior art. To this end, the embodiments of this application provide a blockchain-based number authentication method and system that can effectively improve the security and efficiency of number authentication and timely update and synchronize number status.

[0005] In a first aspect, an embodiment of the present application provides a blockchain-based number authentication method, comprising:

[0006] Generate a number identifier based on the user's number information, generate a real-name identifier based on the user's real-name information, and generate a quantum-resistant public-private key pair using a quantum-resistant encryption algorithm; wherein the quantum-resistant public-private key pair includes a quantum-resistant public key and a quantum-resistant private key;

[0007] Generate a digital identity of the user based on the number identifier, the real-name identifier, and the quantum-resistant public key, and record the digital identity in a blockchain based on a smart contract;

[0008] When making a number authentication request, the user's operation request is signed using the quantum-resistant signature algorithm and the quantum-resistant private key to generate a quantum-resistant signature value, and a zero-knowledge proof document of the user is generated based on the quantum-resistant private key and the zero-knowledge proof protocol; wherein the zero-knowledge proof document is used to prove that the user possesses the digital identity identifier;

[0009] Transmitting the quantum-resistant signature value and the zero-knowledge proof file to an authentication node of the blockchain, where the authentication node verifies the user's number information according to the smart contract to obtain an authentication result;

[0010] If the authentication result indicates that the number authentication is passed, the status of the number information is updated according to the operation request using the smart contract and broadcast to other nodes of the blockchain.

[0011] In some embodiments of the present application, generating a number identifier based on the user's number information, and generating a real-name identifier based on the user's real-name information and the quantum-resistant private key, include:

[0012] Performing a one-way hash process on the user's number information using a quantum attack-resistant hash algorithm to generate a unique and irreversible number identifier;

[0013] Performing standardized preprocessing on the user's real-name information and extracting key identity fields to obtain structured real-name data;

[0014] Performing data perturbation processing on the real-name data using differential privacy technology to obtain perturbed real-name data;

[0015] The real-name data is subjected to one-way hash processing using a hash algorithm that is resistant to quantum attacks to generate a unique and irreversible real-name identification.

[0016] In some embodiments of the present application, when making a number authentication request, the user's operation request is signed using a quantum-resistant signature algorithm and the quantum-resistant private key to generate a quantum-resistant signature value, and a zero-knowledge proof file of the user is generated based on the quantum-resistant private key and the zero-knowledge proof protocol, including:

[0017] Performing standardized preprocessing on the operation request of the user and extracting key request fields to obtain data to be signed;

[0018] Performing hash processing on the data to be signed to generate a message digest, and signing the message digest using the quantum-resistant private key based on the quantum-resistant signature algorithm to generate a quantum-resistant signature value;

[0019] Construct an input statement for zero-knowledge proof based on the user's real-name identifier and the quantum-resistant public key, and use the quantum-resistant private key as witness information;

[0020] Based on the zero-knowledge proof protocol, a zero-knowledge proof file is generated according to the input statement and the witness information.

[0021] In some embodiments of the present application, the transmitting the quantum-resistant signature value and the zero-knowledge proof file to the authentication node of the blockchain, the authentication node verifying the user's number information according to the smart contract to obtain an authentication result, includes:

[0022] The authentication node verifies the validity of the quantum-resistant signature value according to the smart contract and the quantum-resistant public key to obtain a first verification result;

[0023] The authentication node verifies the validity of the zero-knowledge proof document according to the smart contract and the zero-knowledge proof protocol to obtain a second verification result;

[0024] An authentication result of the user's number information is generated according to the first verification result and the second verification result.

[0025] In some embodiments of the present application, the operation request includes an authorization request, a cancellation request, a transfer request, and / or a freeze request. If the authentication result indicates that the number authentication is successful, then using the smart contract to update the status of the number information according to the operation request includes:

[0026] If the operation request is an authorization request, the smart contract is used to parse the authorization request to obtain authorization parameters, and an authorization relationship is established for the number information according to the authorization parameters;

[0027] If the operation request is a deregistration request, the smart contract is used to parse the deregistration request to obtain deregistration parameters, and a deregistration operation is performed on the number information according to the deregistration parameters;

[0028] If the operation request is a transfer request, the smart contract is used to parse the transfer request to obtain transfer parameters, and the number information is transferred according to the transfer parameters;

[0029] If the operation request is a freeze request, the smart contract is used to parse the freeze request to obtain a freeze parameter, and a freeze operation is performed on the number information according to the freeze parameter.

[0030] In some embodiments of the present application, the method further comprises:

[0031] If the operation request meets the preset high-risk condition, the operation request will be marked as a high-risk request and the multi-signature threshold consensus mechanism will be triggered;

[0032] The high-risk request is sent to each authorized participant, and the authorized participant verifies and signs the high-risk request using the corresponding quantum-resistant private key to obtain an authorized signature;

[0033] If the number of authorized signatures meets a preset threshold, the smart contract is used to update the status of the number information according to the high-risk request.

[0034] In some embodiments of the present application, the high-risk request is sent to each authorized participant, and the authorized participant uses the corresponding quantum-resistant private key to verify and sign the high-risk request to obtain an authorized signature, including:

[0035] Utilizing the smart contract to obtain the authorized participant from the permission control list stored on the chain according to the number identifier; wherein the authorized participant includes the user, the operator and / or the third-party platform;

[0036] Encrypting the high-risk request and sending it to each authorized participant, and the authorized participant using the quantum-resistant private key to verify the authority of the high-risk request;

[0037] If the high-risk request meets the permission conditions of the authorized participant, the high-risk request is signed using the quantum-resistant private key to obtain the authorized signature.

[0038] In a second aspect, the present application also provides a blockchain-based number authentication system, including:

[0039] An identifier generation module, configured to generate a number identifier based on the user's number information, generate a real-name identifier based on the user's real-name information, and generate a quantum-resistant public-private key pair using a quantum-resistant encryption algorithm; wherein the quantum-resistant public-private key pair includes a quantum-resistant public key and a quantum-resistant private key;

[0040] An identity generation module, configured to generate a digital identity of the user based on the number identifier, the real-name identifier, and the quantum-resistant public key, and record the digital identity in a blockchain based on a smart contract;

[0041] an authentication generation module, configured to, when making a number authentication request, sign the user's operation request using a quantum-resistant signature algorithm and the quantum-resistant private key to generate a quantum-resistant signature value, and generate a zero-knowledge proof document for the user based on the quantum-resistant private key and a zero-knowledge proof protocol; wherein the zero-knowledge proof document is used to prove that the user possesses the digital identity;

[0042] A number authentication module, configured to transmit the quantum-resistant signature value and the zero-knowledge proof file to an authentication node of the blockchain, wherein the authentication node verifies the user's number information according to the smart contract and obtains an authentication result;

[0043] A status update module is used to update the status of the number information according to the operation request using the smart contract if the authentication result indicates that the number authentication is passed, and broadcast it to other nodes of the blockchain.

[0044] In a third aspect, an embodiment of the present application further provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, it implements the blockchain-based number authentication method as described in the embodiment of the first aspect of the present application.

[0045] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores a program, and the program is executed by a processor to implement the blockchain-based number authentication method as described in the embodiment of the first aspect of the present application.

[0046] The embodiments of the present application include at least the following beneficial effects:

[0047] The embodiment of the present application provides a number authentication method and system based on blockchain. In the method, a number identifier is first generated according to the user's number information, and a real-name identifier is generated according to the user's real-name information, and a quantum-resistant encryption algorithm is used to generate a quantum-resistant public-private key pair. The public-private key pair generated by the quantum-resistant encryption algorithm ensures the security of user data even in the era of quantum computing, preventing identity theft and data leakage. Then, the digital identity generated by combining the number identifier, real-name identifier and quantum-resistant public key is recorded on the blockchain, realizing decentralized storage and tamper-proof verification of identity information, and improving the transparency and credibility of management. When making a number authentication request, the quantum-resistant signature value and zero-knowledge proof file are generated respectively according to the quantum-resistant private key using the quantum-resistant signature algorithm and the zero-knowledge proof protocol, thereby effectively protecting user privacy while meeting high security requirements and avoiding the leakage of sensitive information. Based on smart contracts, authentication nodes perform dual verification of received quantum-resistant signature values and zero-knowledge proof documents, significantly enhancing the accuracy and anti-forgery capabilities of identity authentication. Once authentication is successful, the number status is updated based on the operation request and broadcast to other nodes, achieving real-time synchronization and multi-party consensus confirmation of number status changes, resolving the residual risk caused by information lags in traditional systems. This approach not only ensures security and privacy, but also balances authentication efficiency and allows for timely updates and synchronization of number status, making it suitable for a variety of highly sensitive scenarios such as financial transactions and IoT access.

[0048] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become obvious from the description below, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0050] Figure 1 This is a flowchart of a blockchain-based number authentication method provided by an embodiment of the present application;

[0051] Figure 2 yes Figure 1 Flow diagram of step S101;

[0052] Figure 3 yes Figure 1 Flow diagram of step S103;

[0053] Figure 4 yes Figure 1 Flow chart of step S104;

[0054] Figure 5 yes Figure 1 Flow diagram of step S105;

[0055] Figure 6 This is a flowchart of a blockchain-based number authentication method provided by another embodiment of the present application;

[0056] Figure 7 yes Figure 6 Flow diagram of step S602;

[0057] Figure 8 This is a schematic diagram of a blockchain-based number authentication system provided by an embodiment of the present application;

[0058] Figure 9 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0059] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0060] The following describes in detail embodiments of the present application. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application and are not to be construed as limiting the present application.

[0061] In the description of this application, it should be understood that descriptions involving orientations, such as up, down, front, back, left, right, etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, they cannot be understood as limitations on this application.

[0062] In the description of this application, "several" means one or more, "many" means more than two, "greater than," "less than," and "exceed" are understood to exclude the number itself, while "above," "below," and "within" are understood to include the number itself. The terms "first" and "second" are used solely to distinguish technical features and are not to be construed as indicating or implying relative importance, or as implicitly specifying the number or order of the technical features indicated.

[0063] In the description of this application, unless otherwise clearly defined, terms such as setting, installing, and connecting should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in this application based on the specific content of the technical solution.

[0064] The embodiments of the present application provide a blockchain-based number authentication method and system, which are specifically illustrated by the following embodiments. First, the blockchain-based number authentication method in the embodiments of the present application is described.

[0065] The blockchain-based number authentication method provided in the embodiment of the present application relates to the field of blockchain technology, and in particular to the field of number authentication technology. The blockchain-based number authentication method provided in the embodiment of the present application can be applied to a terminal, can be applied to a server, and can also be a computer program running in a terminal or a server. For example, the computer program can be a native program or software module in the operating system; it can be a local application, that is, a program that needs to be installed in the operating system before it can run, such as a client that supports classified SMS sending based on spatiotemporal portraits, that is, a program that can be run only after being downloaded to a browser environment. In short, the above-mentioned computer program can be any form of application, module or plug-in. Among them, the terminal communicates with the server through a network. The blockchain-based number authentication method can be executed by the terminal or the server, or by the terminal and the server in collaboration.

[0066] The following describes a blockchain-based number authentication method in an embodiment of the present invention.

[0067] Reference Figure 1 As shown, an embodiment of the present application provides a blockchain-based number authentication method, which may include but is not limited to the following steps S101 to S105.

[0068] Step S101: Generate a number identifier based on the user's number information, generate a real-name identifier based on the user's real-name information, and generate a quantum-resistant public-private key pair using a quantum-resistant encryption algorithm.

[0069] In some embodiments, during identity registration, a corresponding number identifier is generated based on the user's number information (such as a mobile phone number), and a corresponding real-name identifier is generated based on the user's real-name information (such as name, ID number, etc.). It is understandable that in the current digital security environment, traditional encryption algorithms (such as RSA, ECC, etc.) may face the threat of quantum computing attacks in the future. In some embodiments, a quantum-resistant encryption algorithm (such as CRYSTALS-Dilithium or Kyber) is selected to generate a quantum-resistant public-private key pair, where the quantum-resistant public-private key pair includes a quantum-resistant public key and a quantum-resistant private key.

[0070] Understandably, the quantum-resistant public key can be publicly stored on the blockchain for subsequent authentication, while the quantum-resistant private key is securely kept by the user and used to sign various operation requests, ensuring the authenticity and non-repudiation of all operations. This ensures that even in future quantum computing environments, users' sensitive information can still be effectively protected, preventing the risk of identity fraud and data leakage.

[0071] Step S102: Generate a digital identity of the user based on the number identifier, real-name identifier, and quantum-resistant public key, and record the digital identity in the blockchain based on the smart contract.

[0072] In some embodiments, a user's digital identity (DID) is generated based on the number identifier, real-name identifier, and quantum-resistant public key, and securely recorded in the blockchain network to achieve decentralized identity management. Specifically, the number identifier, real-name identifier, and quantum-resistant public key are used as input parameters, and a structured combination calculation is performed using a quantum-resistant hash algorithm (such as SHA-3 or SHAKE) to generate a unique and unforgeable digital identity (DID). This process can be expressed as follows:

[0073] DID=Hash(NumberHash||RealNameHash||PublicKey)

[0074] Here, "||" represents data concatenation, NumberHash represents the number identifier, RealNameHash represents the real-name identifier, and PublicKey represents the quantum-resistant public key. The DID generated in this way is not only globally unique but also has excellent collision resistance and security, effectively preventing identity fraud and forgery.

[0075] Furthermore, the smart contract interface deployed on the blockchain is called to write the generated DID and its corresponding identity metadata (including fields such as number identifier, real-name identifier, and quantum-resistant public key) to the blockchain ledger. Smart contracts ensure that all identity data operations are executed according to pre-set rules and guarantee the authenticity and consistency of the written data through a consensus mechanism. It is understood that each digital ID registration operation triggers an on-chain event record, facilitating subsequent auditing and tracking.

[0076] Step S103: When making a number authentication request, the user's operation request is signed using the quantum-resistant signature algorithm and the quantum-resistant private key to generate a quantum-resistant signature value, and the user's zero-knowledge proof file is generated based on the quantum-resistant private key and the zero-knowledge proof protocol.

[0077] In some embodiments, when a number authentication request is made, an efficient, secure, and privacy-friendly identity authentication process is achieved by combining a quantum-resistant signature mechanism with a zero-knowledge proof protocol. It is understood that a quantum-resistant signature refers to signing data using a cryptographic algorithm with quantum computing resistance (such as CRYSTALS-Dilithium, Falcon, etc.) to prevent future quantum computers from damaging traditional digital signature systems. The operation request is signed using the quantum-resistant private key to generate a quantum-resistant signature value, which can prove the authenticity of the user's identity and the legitimacy of the operation.

[0078] In some embodiments, a zero-knowledge proof document is used to prove that a user possesses a digital identity. To complete identity authentication without disclosing sensitive user information, embodiments of the present application utilize zero-knowledge proof (ZKP) technology. Zero-knowledge proof is a cryptographic protocol that allows one party (e.g., a user) to prove to another party (e.g., an authentication node) that they possess secret information (e.g., a quantum-resistant private key) without revealing any actual information.

[0079] Step S104: Transmit the quantum-resistant signature value and zero-knowledge proof file to the authentication node of the blockchain. The authentication node verifies the user's number information according to the smart contract and obtains the authentication result.

[0080] In some embodiments, the generated quantum-resistant signature value and zero-knowledge proof file are packaged into a standard format message body and sent to the authentication node in the blockchain network through a secure communication channel (such as a TLS encrypted connection). The authentication node uses the user's publicly disclosed quantum-resistant public key to verify the validity of the received quantum-resistant signature value based on the verification logic preset in the smart contract, and verifies the zero-knowledge proof file using the verification algorithm corresponding to the zero-knowledge proof protocol to obtain the authentication result of the user number information. It is understandable that if both the quantum-resistant signature verification and the zero-knowledge proof verification pass, an authentication result indicating successful authentication is generated; conversely, if any verification link fails, a corresponding error prompt or rejection reason is returned.

[0081] Furthermore, regardless of the authentication result, the authentication node will trigger an on-chain event log for subsequent audit and tracking. This records the details of each authentication operation, making it easier for system administrators or third-party auditors to review.

[0082] In step S105, if the authentication result indicates that the number authentication is successful, the status of the number information is updated according to the operation request using the smart contract and broadcast to other nodes of the blockchain.

[0083] In some embodiments, after the authentication node completes the verification of the anti-quantum signature value and the zero-knowledge proof document and confirms that the authentication is successful, it automatically performs the corresponding status update operation based on the operation request initiated by the user (such as authorization, cancellation, transfer or freezing, etc.), and records these updates on the blockchain to ensure the transparency and immutability of the data.

[0084] Specifically, the smart contract interface deployed on the blockchain is called. Based on the user's operation request type (e.g., authorization request, cancellation request, transfer request, or freeze request), the smart contract parses the specific operation parameters. For example, for an authorization request, the smart contract needs to parse key information such as the authorized party's identity and the scope of authorization. Based on the specific content of the operation request, the smart contract updates the user's phone number information and related attributes.

[0085] As you can understand, after the state update is complete, the smart contract generates a new transaction record containing detailed information about the operation request (such as operation type, target number, timestamp, etc.). This record, as a new block transaction, awaits confirmation by the blockchain network's consensus mechanism. Once the transaction record is generated, it is broadcast to all nodes in the blockchain network. Each node verifies the transaction to ensure that it complies with the smart contract's provisions and has not been tampered with. Once verified by the consensus mechanism (such as PoW or PoS), the transaction is included in a new block and written to the blockchain ledger.

[0086] Because all nodes in the blockchain network synchronize the latest status updates, global state consistency is ensured. Regardless of which node a user queries their number's status, they receive the latest, accurate information. Even if a node fails or goes offline, other nodes can still operate normally and process transaction requests, ensuring high availability and reliability. In summary, this embodiment provides an efficient, secure, and reliable number authentication method that allows for timely updates and synchronization of number status. It is applicable to identity authentication and permission control requirements in a variety of highly sensitive scenarios, such as financial transactions and IoT device access.

[0087] Reference Figure 2 As shown, in some embodiments of the present application, the above step S101: generating a number identifier based on the user's number information, and generating a real-name identifier based on the user's real-name information and quantum-resistant private key, may include but is not limited to the following steps S201 to S204.

[0088] Step S201: Use a quantum attack-resistant hash algorithm to perform one-way hashing on the user's number information to generate a unique and irreversible number identifier.

[0089] In some embodiments, in order to ensure the uniqueness and security of user number information in the digital identity system, a hash algorithm with quantum computing resistance is used to perform a one-way hash operation on the user's original number information (such as mobile phone number), thereby generating a fixed-length, globally unique number identifier.

[0090] Specifically, the number information is passed as input to a quantum-resistant hash function module. This module uses currently recommended algorithms for post-quantum cryptography, such as SHA-3, SHAKE256, or SPHINCS+ with a built-in hash component. These algorithms are highly resistant to future quantum computing attacks. The hashing process is a one-way operation, meaning that only the corresponding hash value can be derived from the original number information; the hash value cannot be used to reverse engineer the original number information. This feature effectively prevents attackers from reversing the user's actual number using a known number identifier, thereby enhancing the system's security and privacy protection capabilities.

[0091] Furthermore, the generated number identifier is represented in a string or hexadecimal format, which is globally unique and immutable. For example, if user A's mobile phone number is "13800001111", the number identifier obtained after processing with the SHA-3-256 algorithm may be: numberId=

[0092] "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855". It is understood that this number identifier will be used in subsequent identity authentication, permission control, and status management processes. It serves as an encrypted mapping of user number information, avoiding direct exposure of the real number and improving the security level of the overall system.

[0093] Step S202 : performing standardization preprocessing on the user's real-name information and extracting key identity fields to obtain structured real-name data.

[0094] In some embodiments, to ensure the consistency and resolvability of user real-name information, it is necessary to perform standardized pre-processing on the real-name information (such as name, ID number, address, etc.). This not only helps improve the accuracy of subsequent operations, but also enhances the compatibility and scalability of the system.

[0095] Specifically, perform preliminary data cleaning on real-name information to remove invalid characters and format errors. For example, remove extra spaces, punctuation marks, or special characters to ensure that the data format of each field meets the expected standards. Perform format verification on each field according to predefined rules to ensure that it complies with national or industry standards. For example, for ID card numbers, verify whether its length is correct (usually 18 digits) and check whether the check code is legal; for name fields, require the use of Chinese characters or specific character sets to avoid illegal character input.

[0096] Furthermore, after completing data cleaning and format verification, the key identity fields in the real-name information are extracted and mapped to a predefined data structure. For example, a standard data structure containing multiple fields is defined to store the user's name, ID number, date of birth, gender and other information. The real-name information after standardized preprocessing is converted into a structured data format for subsequent processing and storage. It is understandable that common structured formats include JSON, XML or Protocol Buffers. These formats are not only easy to parse and transmit, but also support cross-platform data exchange requirements. Those skilled in the art can choose settings according to actual needs, and this embodiment does not limit this.

[0097] Step S203: Perform data perturbation processing on the real-name data using differential privacy technology to obtain perturbed real-name data.

[0098] In some embodiments, to prevent privacy leakage caused by reverse inference or correlation analysis of user real-name information during subsequent use, this embodiment introduces differential privacy technology to perform data perturbation operations on structured real-name data after standardization, thereby effectively enhancing the anonymity and security of the data while retaining its statistical usability. It can be understood that differential privacy is a mathematically defined privacy protection mechanism that introduces controlled random noise into the original data or calculation results, making it impossible for attackers to determine whether a specific record exists in the data set, thereby achieving strong privacy protection.

[0099] Specifically, a privacy budget parameter ε can be set based on the actual application scenario. This parameter is used to control the balance between privacy protection and data availability: the smaller ε, the stronger the privacy protection, but also the greater the degree of data distortion. Conversely, the larger ε, the closer the data is to the true value, but the privacy protection capability decreases. Key fields that require privacy protection are selected from structured real-name data, such as ID number, date of birth, and address. These fields are often highly identifiable and may pose privacy risks if used directly. A differential privacy mechanism is applied to the selected fields, using either the Laplace or Gaussian mechanism, adding a certain amount of random noise to the data to obtain the corresponding perturbed real-name data.

[0100] Step S204: Perform one-way hashing on the real-name data using a quantum attack-resistant hash algorithm to generate a unique and irreversible real-name identifier.

[0101] In some embodiments, the perturbation real-name data may contain multiple fields. To unify the input format and enhance anti-tampering capabilities, the fields are concatenated in sequence according to preset rules and encoded using UTF-8 or universal character encoding to form a byte stream as the original input data. A quantum-resistant hash function module (such as the SHA-3-256 algorithm) is called to perform a one-way hash on the received byte stream to generate a unique and irreversible real-name identifier.

[0102] By performing quantum-resistant hashing on the user's phone number and real-name information, a unique and irreversible number and real-name identifier is generated, ensuring the tamper-proof and anti-forgery protection of identity data during storage and transmission. Furthermore, by combining standardized preprocessing with differential privacy techniques, structured cleansing and data perturbation of real-name information further enhances the anonymity of sensitive information and reduces the risk of privacy leaks. This not only meets the number authentication requirements in high-security scenarios, but also provides a solid foundation for building a trusted and verifiable decentralized digital identity system.

[0103] Reference Figure 3 As shown, in some embodiments of the present application, the above step S103: when making a number authentication request, the user's operation request is signed using the quantum-resistant signature algorithm and the quantum-resistant private key to generate a quantum-resistant signature value, and the user's zero-knowledge proof file is generated based on the quantum-resistant private key and the zero-knowledge proof protocol, which may include but is not limited to the following steps S301 to S304.

[0104] Step S301 : performing standardized pre-processing on the user's operation request, and extracting key request fields to obtain data to be signed.

[0105] In some embodiments, the received operation request content is standardized and pre-processed to ensure the consistency and executability of the subsequent signature and verification process. Specifically, the user's operation request is parsed into a structured format (such as JSON, XML or Protocol Buffers), and the fields therein are cleaned, verified and normalized according to preset rules. For example, redundant spaces are removed, the time format is unified, the value range of the verification parameter is verified, etc., to prevent signature failure or verification anomalies due to format errors or illegal input. Key request fields are extracted from the standardized operation request to form a representative, fixed-format data to be signed.

[0106] It is understood that the key request fields may include the operation type (such as authorization, cancellation, transfer, etc.),

[0107] The operation target (such as the target number identifier or digital identity identifier DID), the timestamp (used to prevent replay attacks) and the random number or one-time verification code (used to enhance the uniqueness of the signature) are not limited in this embodiment.

[0108] Step S302: Hash the data to be signed to generate a message digest, and sign the message digest using the quantum-resistant private key based on the quantum-resistant signature algorithm to generate a quantum-resistant signature value.

[0109] In some embodiments, the data to be signed is used as input and a fixed-length message digest is generated through a SHA-3-256 hash operation. This message digest is then signed using a quantum-resistant private key based on a quantum-resistant signature algorithm (such as CRYSTALS-Dilithium or Falcon) to generate a quantum-resistant signature value. It is understood that the quantum-resistant signature value is typically a long string or byte array used in subsequent authentication processes, thereby providing strong security protection in quantum computing environments to prevent signature forgery or tampering.

[0110] Step S303: construct an input statement for zero-knowledge proof based on the user's real-name identification and quantum-resistant public key, and use the quantum-resistant private key as witness information.

[0111] In some embodiments, the goal of zero-knowledge proof is to prove to the authentication node that the user does possess secret information (such as a quantum-resistant private key) corresponding to his or her digital identity, without exposing any actual identity information. Therefore, it is necessary to clearly state the specific assertions or conditions to be proved. For example, "proving that the user holds a private key that matches a given public key." Specifically, the input statement of the zero-knowledge proof is constructed based on the user's real-name identification and quantum-resistant public key, representing the public assertion that needs to be verified. Witness information refers to secret information known only to the prover. In this embodiment, the quantum-resistant private key is used as witness information to generate a valid zero-knowledge proof.

[0112] Step S304: Based on the zero-knowledge proof protocol, a zero-knowledge proof file is generated according to the input statement and witness information.

[0113] In some embodiments, based on the Zero-Knowledge Proof (ZKP) protocol, the input statement and witness information are used to generate a corresponding zero-knowledge proof file. This file can prove the authenticity of the user's identity and the legitimacy of the operation request to the authentication node without revealing the user's real identity information.

[0114] Mathematical modeling and polynomial processing are performed on the input statement and witness information to generate a structured zero-knowledge proof file. Specifically, the problem to be proved is converted into an arithmetic circuit or constraint system; a polynomial expression is constructed to represent the proof objective; verifiable but irreversible proof data is generated through techniques such as hash functions and error-correcting codes; and the final zero-knowledge proof file is output. It is understood that a zero-knowledge proof file is a structured data object, typically in binary or Base64-encoded form, which is not limited in this embodiment.

[0115] By standardizing operation requests and generating quantum-resistant signature values, the authenticity and immutability of the operation source are ensured. Furthermore, by constructing input statements and generating proof documents based on a zero-knowledge proof protocol, users can complete identity verification without revealing any sensitive identity information. The combination of quantum-resistant signatures and zero-knowledge proofs not only enhances defenses against quantum computing attacks but also provides a solid foundation for trusted number authentication in blockchain environments, offering excellent security, scalability, and application prospects.

[0116] Reference Figure 4 As shown, in some embodiments of the present application, the above step S104: transmitting the quantum-resistant signature value and the zero-knowledge proof file to the authentication node of the blockchain, the authentication node verifies the user's number information according to the smart contract, and obtains the authentication result, which may include but is not limited to the following steps S401 to S403.

[0117] In step S401, the authentication node verifies the validity of the quantum-resistant signature value based on the smart contract and the quantum-resistant public key to obtain a first verification result.

[0118] In some embodiments, the authentication node first retrieves the user's quantum-resistant public key from the smart contract, uses it as a verification key, and, in conjunction with a verification function corresponding to a quantum-resistant signature algorithm (such as the verification interface of CRYSTALS-Dilithium or Falcon), performs a mathematical verification operation on the received quantum-resistant signature value and the operation request data. This process typically involves recalculating the hash digest of the operation request and decrypting the signature value using the public key to determine whether the two match.

[0119] If a match is successful, the quantum-resistant signature is valid, indicating that the user possesses the quantum-resistant private key corresponding to the quantum-resistant public key and that the operation request content has not been tampered with. The authentication node then generates a first verification result indicating that the verification has passed. Conversely, if there is a mismatch, the signature is deemed invalid, a verification failure result is returned, and the corresponding security audit mechanism is triggered. This first verification result serves as one of the important bases for subsequent comprehensive authentication judgments, ensuring the security and reliability of the digital signature link in the identity authentication process.

[0120] In step S402, the authentication node verifies the validity of the zero-knowledge proof document according to the smart contract and the zero-knowledge proof protocol to obtain a second verification result.

[0121] In some embodiments, the authentication node obtains public parameters related to the user (such as real-name identification and quantum-resistant public key) from the smart contract. These public parameters serve as the basic input for verifying the zero-knowledge proof, ensuring the transparency and repeatability of the verification process. Next, the authentication node processes the received zero-knowledge proof file using the verification algorithm corresponding to the selected zero-knowledge proof protocol. The verification algorithm is based on mathematical proof theory and can efficiently determine whether the proof document correctly proves that the user possesses the specified secret information (i.e., quantum-resistant private key) without directly accessing the quantum-resistant private key.

[0122] If the verification is successful, it means that the user does have the private key that matches his or her public key and has not leaked any actual identity information. At this time, the authentication node generates a second verification result indicating that the verification is successful. Conversely, if the verification fails, it means that the provided zero-knowledge proof is invalid and may involve forgery or erroneous operation. The authentication node will return a verification failure result and trigger the corresponding security mechanism.

[0123] Step S403: Generate an authentication result of the user's number information based on the first verification result and the second verification result.

[0124] In some embodiments, the first verification result can confirm whether the user possesses the private key that matches their quantum-resistant public key and that the operation request has not been tampered with. Simultaneously, the second verification result can confirm that the user possesses the identity credentials corresponding to the digital identity, without disclosing any sensitive information. If both verification results are "passed," the user's identity is authentic and the operation source is trustworthy, and a corresponding authentication result indicating successful authentication is generated. If either verification result is "failed," the number authentication is deemed unsuccessful, and a corresponding error message or rejection reason is returned.

[0125] It is understandable that in order to enhance auditability and transparency, regardless of whether the authentication result is successful or failed, the authentication node will trigger an on-chain event record and write the authentication result and related operation information into the blockchain ledger.

[0126] Smart contracts automatically verify the validity of quantum-resistant signatures, ensuring the authenticity and integrity of operation requests. Furthermore, zero-knowledge proof protocols are used to verify supporting documents, ensuring identity verification without exposing user privacy. Ultimately, a comprehensive assessment of these two verification results generates an authentication result, enhancing the ability to defend against identity forgery attacks and quantum computing threats.

[0127] In some embodiments of the present application, the operation request includes an authorization request, a cancellation request, a transfer request and / or a freeze request. Figure 5 As shown, in the above step S105: if the authentication result indicates that the number authentication is passed, the status of the number information is updated according to the operation request using the smart contract, which may include but is not limited to the following steps S501 to S504.

[0128] Step S501: If the operation request is an authorization request, the authorization request is parsed using the smart contract to obtain authorization parameters, and an authorization relationship is established for the number information based on the authorization parameters.

[0129] In some embodiments, when the authentication result indicates that the number authentication is successful and the operation request is an authorization request, the smart contract deployed on the blockchain is used to automatically parse the authorization request and extract relevant authorization parameters.

[0130] Specifically, the authorization parameters may include but are not limited to the following fields:

[0131] The identity of the authorized party (such as DID): specifies which entity or user will obtain the corresponding permission;

[0132] Authorization scope: defines the specific resource types or functions that the authorized party can access or operate;

[0133] Validity period: Set the validity period of the authorization relationship. After this period, the authorization will automatically become invalid;

[0134] Operation type: specifies the specific behavior to be authorized (such as read, write, etc.).

[0135] Smart contracts perform standardized parsing of received authorization requests and extract the aforementioned authorization parameters. Based on these parameters, a new authorization relationship is established for the target number information. Specifically, the smart contract adds a record to the number information's data structure, indicating that a specific authorized party (identified by its DID) has certain permissions to operate on that number information within a specified timeframe. This enables fine-grained permission control and ensures that all authorization relationships are securely recorded on the blockchain, preventing tampering and forgery.

[0136] In step S502, if the operation request is a deregistration request, the smart contract is used to parse the deregistration request to obtain deregistration parameters, and a deregistration operation is performed on the number information according to the deregistration parameters.

[0137] In some embodiments, when the authentication result indicates that the number authentication is passed and the operation request is a deregistration request, the smart contract deployed on the blockchain is used to automatically parse the deregistration request and extract relevant deregistration parameters.

[0138] Specifically, the logout parameters may include but are not limited to the following fields:

[0139] Target number ID: specifies the specific number that needs to be cancelled;

[0140] Cancellation reason: Describe the reason or background information for the number cancellation;

[0141] Timestamp: records the time when the logout operation occurs;

[0142] The smart contract performs standardized parsing of the received deregistration request, extracts the deregistration parameters, and executes the deregistration operation on the target number information based on the deregistration parameters. Specifically, the smart contract marks the number as deregistered in the number information data structure and revokes all authorizations and other associated data associated with the number.

[0143] Step S503: If the operation request is a transfer request, the smart contract is used to parse the transfer request to obtain transfer parameters, and the number information is transferred according to the transfer parameters.

[0144] In some embodiments, when the authentication result indicates that the number authentication is passed and the operation request is a transfer request, the smart contract deployed on the blockchain is used to automatically parse the transfer request and extract relevant transfer parameters.

[0145] Specifically, the transfer parameters may include but are not limited to the following fields:

[0146] Target number ID: specifies the specific number to be transferred;

[0147] The recipient's identity (e.g., DID): indicates the new user or entity that owns the receiving number;

[0148] Transfer reason: Describe the reason or background information for the number transfer;

[0149] Timestamp: records the time when the transfer operation occurs;

[0150] The smart contract performs standardized parsing of the received transfer request, extracts the transfer parameters, and executes the transfer operation on the target number information based on the transfer parameters. Specifically, the smart contract updates the ownership information in the number information data structure, transferring ownership of the number from the current holder to the new recipient.

[0151] Step S504: If the operation request is a freeze request, the smart contract is used to parse the freeze request to obtain freeze parameters, and the number information is frozen according to the freeze parameters.

[0152] In some embodiments, when the authentication result indicates that the number authentication is passed and the operation request is a freeze request, the smart contract deployed on the blockchain is used to automatically parse the freeze request and extract relevant freeze parameters.

[0153] Specifically, the logout parameters may include but are not limited to the following fields:

[0154] Target number ID: specifies the specific number to be frozen;

[0155] Blocking reason: Describe the reason or background information for blocking the number;

[0156] Timestamp: records the time when the freeze operation occurs;

[0157] Validity period: Set the effective period of the freeze. After this period, the freeze status may be automatically lifted or require reassessment;

[0158] The smart contract performs standardized parsing of the received freeze request, extracts the freeze parameters, and then performs the freeze operation on the target number information based on the freeze parameters. Specifically, the smart contract marks the number as frozen in the number information data structure and restricts all related operation permissions.

[0159] Smart contracts automatically parse and execute authorization, cancellation, transfer, and freeze requests, ensuring the authenticity and immutability of every operation. Furthermore, by securely storing all operation records on the blockchain, the system enhances transparency and auditability. This not only effectively prevents unauthorized operations but also supports flexible response to number management needs in various business scenarios, such as permission allocation, ownership changes, and risk control.

[0160] Reference Figure 6 As shown, in some embodiments of the present application, the method may also include but is not limited to the following steps S601 to S603.

[0161] Step S601: If the operation request meets the preset high-risk condition, the operation request is marked as a high-risk request and the multi-signature threshold consensus mechanism is triggered.

[0162] In some embodiments, to enhance security protection against potentially risky operations, when a user-initiated operation request meets pre-set high-risk criteria, it is automatically marked as a high-risk request and an additional security verification process, the Multi-Signature Threshold Consensus Mechanism, is initiated. This mechanism ensures the legitimacy and security of high-risk operations by introducing multiple verification nodes to jointly make decisions.

[0163] Exemplarily, high-risk conditions may include modifying the permission settings of number information multiple times in a short period of time, attempting to access or modify highly sensitive personal information, and operation requests coming from a geographical location that does not match the user's historical records; they may also include cancellation, transfer, freezing, unfreezing and other operation requests. This embodiment does not limit this, and those skilled in the art can set it according to actual needs.

[0164] In step S602, the high-risk request is sent to each authorized participant. The authorized participant uses the corresponding quantum-resistant private key to verify and sign the high-risk request to obtain an authorized signature.

[0165] In some embodiments, high-risk requests are sent via a secure channel to all pre-designated authorized participants. These authorized participants are typically users or nodes with higher levels of authority, responsible for reviewing and approving critical or sensitive operational requests. For example, assume five authorized participants are configured, each located in different geographic locations or organizations to increase system redundancy and security.

[0166] Furthermore, upon receiving a high-risk request, each authorized participant is required to independently verify its legitimacy and integrity. Specifically, verification may include, but is not limited to, checking the request format and integrity; verifying the operation type and parameters; and recalculating the hash digest and comparing it with the provided quantum-resistant signature value. If all of these verifications pass, the authorized participant signs the high-risk request using its own quantum-resistant private key, certifying that it has reviewed and approved the request.

[0167] Step S603: If the number of authorized signatures meets the preset threshold, the status of the number information is updated according to the high-risk request using the smart contract.

[0168] In some embodiments, if the number of authorized signatures meets a preset threshold, the high-risk request is confirmed to have been fully verified and supported. For example, the system checks whether the number of authorized signatures from authorized parties has reached a preset threshold. For example, suppose there are five authorized parties, and at least three authorized signatures are required to process the request. If the number of authorized signatures exceeds three, the smart contract further verifies the validity of each authorization signature to ensure it was generated by the designated authorized party. This verification triggers the smart contract to execute the corresponding action, updating the status of the number information based on the high-risk request.

[0169] When an operation request is detected to meet pre-set high-risk conditions, the multi-signature threshold consensus mechanism is automatically triggered, requiring multiple authorized parties to jointly verify and sign, significantly improving the credibility and security of the operation. On this basis, the smart contract executes the status update of the number information based on the authorized signatures that meet the threshold value, ensuring that key operations are completed under the premise of multi-party consensus and auditability, effectively preventing security risks caused by illegal or abnormal operations.

[0170] Reference Figure 7 As shown, in some embodiments of the present application, the above step S602: sending the high-risk request to each authorized participant, the authorized participant uses the corresponding quantum-resistant private key to verify and sign the high-risk request to obtain an authorized signature, which may include but is not limited to the following steps S701 to S703.

[0171] Step S701: Use the smart contract to obtain the authorized participant from the permission control list stored on the chain according to the number identifier.

[0172] In some embodiments, a smart contract deployed on the blockchain uses the unique identifier of the target number (i.e., the number identifier) to query and extract the corresponding list of authorized participants from the access control list (ACL) stored on the chain. Authorized participants include users, operators, and / or third-party platforms.

[0173] In step S702, the high-risk request is encrypted and sent to each authorized participant, and the authorized participant uses the quantum-resistant private key to verify the authority of the high-risk request.

[0174] In some embodiments, to ensure the confidentiality and integrity of high-risk requests during transmission, the request data is encrypted before being distributed to each authorized party. Upon receiving the encrypted high-risk request, each authorized party uses its quantum-resistant private key to decrypt and verify the legitimacy and authority of the request, ensuring operational security and reliability.

[0175] High-risk requests are encrypted using quantum-safe encryption algorithms (such as Kyber or FrodoKEM). This provides protection against future quantum computing attacks, ensuring data security even in the future, when quantum computers become widespread. Specifically, for high-risk requests, a temporary session key is generated to encrypt the request data. To ensure that only designated authorized parties can decrypt the request data, the session key is encrypted using each authorized party's quantum-safe public key. The encrypted request data and each authorized party's encrypted session key are packaged into a complete encrypted package and sent to each authorized party.

[0176] The authorized party first retrieves the corresponding encrypted session key from the encrypted package and decrypts it using its quantum-resistant private key to obtain the original session key. The decrypted session key is then used to decrypt the encrypted request data, recovering the original high-risk request content. The authorized party then verifies its authority to approve the request. This includes checking the request type and whether the number identifier involved falls within its authority. For example, authorized party A may need to verify that it is authorized to approve this type of transfer.

[0177] Step S703: If the high-risk request meets the permission conditions of the authorized participant, the high-risk request is signed using the quantum-resistant private key to obtain an authorized signature.

[0178] In some embodiments, if the high-risk request meets the permission conditions of the authorized participant, the authorized participant uses its quantum-resistant private key to sign the high-risk request, generating a legally effective and unforgeable authorization signature, indicating that the authorized participant agrees to the high-risk request.

[0179] Smart contracts are used to dynamically retrieve authorized participants with approval authority from the on-chain permission control list, ensuring the flexibility and configurability of multi-party collaborative decision-making. Furthermore, quantum-resistant encryption technology is introduced during the request transmission process to protect the confidentiality and integrity of the data. After verifying that the request meets their permission conditions, the authorized participant uses a quantum-resistant private key to sign the request. This not only enhances the legitimacy and non-repudiation of the operation, but also effectively protects against the security threats posed by future quantum computing.

[0180] In some embodiments of this application, a dynamic key update mechanism is introduced to further enhance security protection capabilities and prevent potential leakage risks associated with the long-term use of fixed keys. This mechanism allows users or authorized parties to automatically update their quantum-resistant public and private key pairs periodically or upon specific event triggers. The new key information is recorded on the blockchain through a smart contract, ensuring the security, transparency, and traceability of the key management process.

[0181] Specifically, the dynamic key update process may include but is not limited to the following steps:

[0182] First, set the key update cycle (e.g., every 90 days) and trigger conditions (e.g., detecting abnormal login behavior or permission changes). When the update conditions are met, the user or authorized party initiates the key update process and generates a new quantum-resistant key pair, such as a new public-private key combination based on the CRYSTALS-Dilithium or SPHINCS+ algorithms.

[0183] Next, the user signs the update request using their currently valid quantum-resistant private key using a local signing tool. They then submit the newly generated quantum-resistant public key and signature value to the authentication node. The authentication node verifies the validity of the signature according to the smart contract rules and confirms that the update operation was initiated by a legitimate entity.

[0184] After verification, the smart contract writes the new public key into the on-chain identity credential data structure and marks it as the "currently valid public key." It also retains a record of historical public keys for audit and backtracking purposes. To ensure operational compatibility after key updates, a key version identification mechanism is also provided. In subsequent identity authentication and multi-signature verification scenarios, the smart contract can select the corresponding version of the public key for verification based on the operation timestamp, preventing historical data from being unverifiable due to key changes.

[0185] In some embodiments of the present application, smart contracts are used to automatically manage the status of number information and apply lifecycle rules, ensuring the legitimacy and security of the number throughout its lifecycle, and effectively preventing problems such as number impersonation and secondary release.

[0186] Specifically, the smart contract updates the status of the number information in real time based on user-initiated operation requests (such as cancellation and transfer), and broadcasts the changes to all platform nodes to ensure consistency and transparency of data across the entire network. For example, when a user initiates a cancellation request, the smart contract marks the number status as "cancelled" and prevents any new service binding or operation requests from using the number.

[0187] To further ensure the security and compliance of number usage, this embodiment sets detailed lifecycle rules to guide smart contracts on how to handle different types of number status changes. For example:

[0188] After cancellation: the number status is marked as "unavailable", and any new service attempts to bind to the number are prohibited to prevent misoperation or fraud.

[0189] During transfer: the original user's DID becomes invalid, and the new user needs to generate a new DID and rebind it to the number to ensure the transparency and immutability of the ownership transfer process.

[0190] In related technologies, after user B deactivated their number, the operator failed to synchronize the status in a timely manner, resulting in new user C receiving legacy service notifications. However, in this embodiment, the operator can mark the number as "deactivated" through a smart contract and record this change on the blockchain. When new user C registers, they query the blockchain to confirm the number's historical status, thus avoiding confusion caused by legacy service notifications from the old number and ensuring a smooth and accurate user experience.

[0191] The public-private key pairs generated using quantum-resistant encryption algorithms ensure the security of user data, even in the quantum computing era, preventing identity theft and data leakage. Blockchain technology enables decentralized storage and tamper-proof verification of identity information, enhancing management transparency and trustworthiness. While meeting high security requirements, it effectively protects user privacy and prevents the leakage of sensitive information. Smart contracts employ dual verification of quantum-resistant signature values and zero-knowledge proof documents, significantly enhancing the accuracy and anti-forgery capabilities of identity authentication. Once authentication is successful, the number status is updated based on the operation request and broadcast to other nodes, enabling real-time synchronization and multi-party consensus confirmation of number status changes, addressing the residual risk associated with information lags in traditional systems. This approach balances security and privacy with efficient authentication, enabling timely updates and synchronization of number status, making it suitable for a variety of highly sensitive scenarios, such as financial transactions and IoT access.

[0192] The present application also provides a blockchain-based number authentication system that can implement the above-mentioned blockchain-based number authentication method. Figure 8 As shown, in some embodiments of the present application, the blockchain-based number authentication system includes:

[0193] The identifier generation module 100 is used to generate a number identifier based on the user's number information, generate a real-name identifier based on the user's real-name information, and generate a quantum-resistant public-private key pair using a quantum-resistant encryption algorithm; wherein the quantum-resistant public-private key pair includes a quantum-resistant public key and a quantum-resistant private key;

[0194] The identity generation module 200 is used to generate a user's digital identity based on the number identifier, real-name identifier, and quantum-resistant public key, and record the digital identity in the blockchain based on a smart contract;

[0195] The authentication generation module 300 is used to sign the user's operation request using a quantum-resistant signature algorithm and a quantum-resistant private key to generate a quantum-resistant signature value when making a number authentication request, and to generate the user's zero-knowledge proof document based on the quantum-resistant private key and a zero-knowledge proof protocol; the zero-knowledge proof document is used to prove that the user has the digital identity;

[0196] The number authentication module 400 is used to transmit the quantum-resistant signature value and zero-knowledge proof file to the authentication node of the blockchain. The authentication node verifies the user's number information according to the smart contract and obtains the authentication result;

[0197] The status update module 500 is used to update the status of the number information according to the operation request using the smart contract if the authentication result indicates that the number authentication is passed, and broadcast it to other nodes of the blockchain.

[0198] The specific implementation of the blockchain-based number authentication system of this embodiment is basically the same as the specific implementation of the blockchain-based number authentication method described above, and will not be repeated here.

[0199] Figure 9 The electronic device 1000 provided in an embodiment of the present application is shown. The electronic device 1000 includes: a processor 1001, a memory 1002, and a computer program stored in the memory 1002 and executable on the processor 1001. When the computer program is executed, it is used to execute the above-mentioned blockchain-based number authentication method.

[0200] The processor 1001 and the memory 1002 may be connected via a bus or other means.

[0201] Memory 1002, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer executable programs, such as the blockchain-based number authentication method described in the embodiments of this application. Processor 1001 implements the blockchain-based number authentication method by executing the non-transitory software programs and instructions stored in memory 1002.

[0202] The memory 1002 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store and execute the above-mentioned blockchain-based number authentication method. In addition, the memory 1002 may include a high-speed random access memory 1002, and may also include a non-volatile memory 1002, such as at least one storage device memory device, a flash memory device, or other non-volatile solid-state memory device. In some embodiments, the memory 1002 may optionally include a memory 1002 remotely located relative to the processor 1001, and these remote memories 1002 may be connected to the electronic device 1000 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0203] The embodiment of the present application also provides a storage medium, which is a computer-readable storage medium, and the storage medium stores a computer program, which implements the above-mentioned blockchain-based number authentication method when executed by the processor. The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0204] The embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of this embodiment.

[0205] Those skilled in the art will appreciate that all or some of the steps and systems in the method disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disk (DVD), or other optical disk storage, magnetic cassette, magnetic tape, storage device storage, or other magnetic storage device, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0206] It should also be understood that the various implementations provided in the embodiments of this application can be arbitrarily combined to achieve different technical effects. The above is a specific description of the preferred implementation of this application, but this application is not limited to the above implementation. Those skilled in the art can also make various equivalent modifications or substitutions under the conditions that do not violate the spirit of this application.

Claims

1. A blockchain-based number authentication method, characterized in that: include: Generate a number identifier based on the user's number information, generate a real-name identifier based on the user's real-name information, and generate a quantum-resistant public-private key pair using a quantum-resistant encryption algorithm; wherein the quantum-resistant public-private key pair includes a quantum-resistant public key and a quantum-resistant private key; Generate a digital identity of the user based on the number identifier, the real-name identifier, and the quantum-resistant public key, and record the digital identity in a blockchain based on a smart contract; When making a number authentication request, the user's operation request is signed using the quantum-resistant signature algorithm and the quantum-resistant private key to generate a quantum-resistant signature value, and a zero-knowledge proof document of the user is generated based on the quantum-resistant private key and the zero-knowledge proof protocol; wherein the zero-knowledge proof document is used to prove that the user possesses the digital identity identifier; Transmitting the quantum-resistant signature value and the zero-knowledge proof file to an authentication node of the blockchain, where the authentication node verifies the user's number information according to the smart contract to obtain an authentication result; If the authentication result indicates that the number authentication is passed, the status of the number information is updated according to the operation request using the smart contract and broadcast to other nodes of the blockchain.

2. The blockchain-based number authentication method according to claim 1, characterized in that: Generating a number identifier based on the user's number information, and generating a real-name identifier based on the user's real-name information and the quantum-resistant private key, includes: Performing a one-way hash process on the user's number information using a quantum attack-resistant hash algorithm to generate a unique and irreversible number identifier; Performing standardized preprocessing on the user's real-name information and extracting key identity fields to obtain structured real-name data; Performing data perturbation processing on the real-name data using differential privacy technology to obtain perturbed real-name data; The real-name data is subjected to one-way hash processing using a hash algorithm that is resistant to quantum attacks to generate a unique and irreversible real-name identification.

3. The blockchain-based number authentication method according to claim 1, characterized in that: When making a number authentication request, the user's operation request is signed using the quantum-resistant signature algorithm and the quantum-resistant private key to generate a quantum-resistant signature value, and a zero-knowledge proof document of the user is generated based on the quantum-resistant private key and the zero-knowledge proof protocol, including: Performing standardized preprocessing on the operation request of the user and extracting key request fields to obtain data to be signed; Performing hash processing on the data to be signed to generate a message digest, and signing the message digest using the quantum-resistant private key based on the quantum-resistant signature algorithm to generate a quantum-resistant signature value; Construct an input statement for zero-knowledge proof based on the user's real-name identifier and the quantum-resistant public key, and use the quantum-resistant private key as witness information; Based on the zero-knowledge proof protocol, a zero-knowledge proof file is generated according to the input statement and the witness information.

4. The blockchain-based number authentication method according to claim 3, characterized in that: The step of transmitting the quantum-resistant signature value and the zero-knowledge proof file to an authentication node of the blockchain, wherein the authentication node verifies the user's number information according to the smart contract to obtain an authentication result, includes: The authentication node verifies the validity of the quantum-resistant signature value according to the smart contract and the quantum-resistant public key to obtain a first verification result; The authentication node verifies the validity of the zero-knowledge proof document according to the smart contract and the zero-knowledge proof protocol to obtain a second verification result; An authentication result of the user's number information is generated according to the first verification result and the second verification result.

5. The blockchain-based number authentication method according to claim 1, characterized in that: The operation request includes an authorization request, a cancellation request, a transfer request, and / or a freeze request. If the authentication result indicates that the number authentication is passed, the state of the number information is updated according to the operation request using the smart contract, including: If the operation request is an authorization request, the smart contract is used to parse the authorization request to obtain authorization parameters, and an authorization relationship is established for the number information according to the authorization parameters; If the operation request is a deregistration request, the smart contract is used to parse the deregistration request to obtain deregistration parameters, and a deregistration operation is performed on the number information according to the deregistration parameters; If the operation request is a transfer request, the smart contract is used to parse the transfer request to obtain transfer parameters, and the number information is transferred according to the transfer parameters; If the operation request is a freeze request, the smart contract is used to parse the freeze request to obtain a freeze parameter, and a freeze operation is performed on the number information according to the freeze parameter.

6. The blockchain-based number authentication method according to any one of claims 1 to 5, characterized in that: The method further comprises: If the operation request meets the preset high-risk condition, the operation request will be marked as a high-risk request and the multi-signature threshold consensus mechanism will be triggered; The high-risk request is sent to each authorized participant, and the authorized participant verifies and signs the high-risk request using the corresponding quantum-resistant private key to obtain an authorized signature; If the number of authorized signatures meets a preset threshold, the smart contract is used to update the status of the number information according to the high-risk request.

7. The blockchain-based number authentication method according to any one of claim 6, characterized in that: The high-risk request is sent to each authorized participant, and the authorized participant uses the corresponding quantum-resistant private key to verify and sign the high-risk request to obtain an authorized signature, including: Utilizing the smart contract to obtain the authorized participant from the permission control list stored on the chain according to the number identifier; wherein the authorized participant includes the user, the operator and / or the third-party platform; Encrypting the high-risk request and sending it to each authorized participant, and the authorized participant using the quantum-resistant private key to verify the authority of the high-risk request; If the high-risk request meets the permission conditions of the authorized participant, the high-risk request is signed using the quantum-resistant private key to obtain the authorized signature.

8. A blockchain-based number authentication system, characterized in that: include: An identifier generation module, configured to generate a number identifier based on the user's number information, generate a real-name identifier based on the user's real-name information, and generate a quantum-resistant public-private key pair using a quantum-resistant encryption algorithm; wherein the quantum-resistant public-private key pair includes a quantum-resistant public key and a quantum-resistant private key; An identity generation module, configured to generate a digital identity of the user based on the number identifier, the real-name identifier, and the quantum-resistant public key, and record the digital identity in a blockchain based on a smart contract; an authentication generation module, configured to, when making a number authentication request, sign the user's operation request using a quantum-resistant signature algorithm and the quantum-resistant private key to generate a quantum-resistant signature value, and generate a zero-knowledge proof document for the user based on the quantum-resistant private key and a zero-knowledge proof protocol; wherein the zero-knowledge proof document is used to prove that the user possesses the digital identity; A number authentication module, configured to transmit the quantum-resistant signature value and the zero-knowledge proof file to an authentication node of the blockchain, wherein the authentication node verifies the user's number information according to the smart contract and obtains an authentication result; A status update module is used to update the status of the number information according to the operation request using the smart contract if the authentication result indicates that the number authentication is passed, and broadcast it to other nodes of the blockchain.

9. An electronic device, characterized in that: It includes a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, it implements the blockchain-based number authentication method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The storage medium stores a program, and the program is executed by a processor to implement the blockchain-based number authentication method as described in any one of claims 1 to 7.

Images