Multi-signature verification method and device for digital currency wallet

Abstract

The invention discloses a multi-signature verification method and device for a digital currency wallet, and relates to the technical field of risk management, and the method comprises the steps: initializing user information, generating a public key for each user in a user queue, and configuring a signature utility value according to the function level and the work attribute of each user; a multi-signature script is generated by using the public key, and a multi-signature address is generated according to the multi-signature script and used for receiving funds of the digital currency wallet; and generating a multi-signature verification strategy, and verifying the real-time transaction of the digital currency wallet according to the updated multi-signature verification strategy when detecting that the user queue changes. The technical problem that in the prior art, due to attribute change of a user, the safety and the flexibility of transaction verification through fixed multiple signatures are insufficient is solved, and the technical effects that the signature strategy is intelligently replaced according to the real condition of personnel flow, and the safety and the flexibility of multi-signature verification are improved are achieved.

Description

Multi-signature verification method and device for digital currency wallets Technical Field

[0001] This invention relates to the field of risk management technology, and more specifically to a multi-signature verification method and apparatus for digital currency wallets. Background Technology

[0002] In cryptocurrency transactions, multi-signature technology is widely used to enhance wallet security. By requiring multiple private key holders to sign, asset loss due to the theft or loss of a single private key can be prevented. In enterprises, multi-signature technology can be used to manage funds, ensuring their security and compliance. For example, a company can designate multiple executives or department managers as private key holders to jointly decide on fund expenditures. However, in departmental collaboration, a complete project cycle typically involves continuous user changes. In such cases, using a fixed multi-signature verification method cannot meet the required security and flexibility. Summary of the Invention

[0003] This application provides a multi-signature verification method and apparatus for digital currency wallets, which solves the technical problem of insufficient security and flexibility in the prior art when using fixed multi-signatures for transaction verification due to changes in user attributes.

[0004] The first aspect of this application provides a multi-signature verification method for a digital currency wallet. The method includes: initializing user information, wherein the initialization generates a public key for each user in a user queue and records each user's job level and work attributes; configuring a signature utility value based on each user's job level and work attributes; creating a multi-signature address, wherein the multi-signature address includes generating a multi-signature script using the public key, generating a multi-signature address based on the multi-signature script, and using this multi-signature address to receive funds from the digital currency wallet; generating a multi-signature verification strategy, wherein the multi-signature verification strategy includes a dynamic adjustment module, which updates the multi-signature verification strategy when it detects a change in the user queue; and verifying real-time transactions of the digital currency wallet according to the updated multi-signature verification strategy to obtain verification results.

[0005] A second aspect of this application provides a multi-signature verification device for a digital currency wallet. The device includes: a user information initialization module, used to initialize user information, generating a public key for each user in a user queue and recording each user's job level and work attributes; a signature utility value configuration module, used to configure a signature utility value based on each user's job level and work attributes; a multi-signature address creation module, used to create a multi-signature address, which includes generating a multi-signature script using a public key and generating the multi-signature address based on the script, for receiving funds from the digital currency wallet; a multi-signature verification strategy update module, used to generate a multi-signature verification strategy, which includes a dynamic adjustment module that updates the strategy when it detects a change in the user queue; and a real-time transaction verification module, used to verify real-time transactions of the digital currency wallet according to the updated multi-signature verification strategy and obtain verification results.

[0006] One or more technical solutions provided in this application have at least the following technical effects or advantages: The multi-signature verification method and apparatus for digital currency wallets provided in this application relate to the field of risk management technology. By initializing user information, a public key is generated for each user in the user queue, and a signature utility value is configured. A multi-signature address is generated according to the multi-signature script, and a multi-signature verification strategy is generated simultaneously. When a change in the user queue is detected, the multi-signature verification strategy is updated, and real-time transactions of the digital currency wallet are verified. This solves the technical problem of insufficient security and flexibility in the prior art when using fixed multi-signatures for transaction verification due to changes in user attributes. It realizes the technical effect of intelligently changing the signature strategy according to the actual flow of personnel, thereby improving the security and flexibility of multi-signature verification. Attached Figure Description

[0007] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0008] Figure 1 is a flowchart illustrating the multi-signature verification method for a digital currency wallet provided in an embodiment of this application; Figure 2 is a flowchart illustrating the generation of signature utility values ​​in the multi-signature verification method for a digital currency wallet provided in an embodiment of this application; Figure 3 is a structural diagram illustrating the multi-signature verification device for a digital currency wallet provided in an embodiment of this application.

[0009] Figure labeling: User information initialization module 11, signature utility value configuration module 12, multi-signature address creation module 13, multi-signature verification strategy update module 14, real-time transaction verification module 15. Detailed Implementation

[0010] This application provides a multi-signature verification method and apparatus for digital currency wallets, which solves the technical problem of insufficient security and flexibility in the prior art when using fixed multi-signatures for transaction verification due to changes in user attributes.

[0011] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0012] It should be noted that the terms "first," "second," etc., in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or modules not explicitly listed or inherent to such processes, methods, products, or devices.

[0013] As shown in Figure 1, this application provides a multi-signature verification method for digital currency wallets. The method includes: P10: Initializing user information, wherein the initializing user information generates a public key for each user in the user queue and records the job level and work attributes of each user.

[0014] Furthermore, step P10 in this embodiment of the application also includes: P11: generating a private key for the public key, and storing the public key and the private key as a public-private key pair; P12: generating a multi-signature script based on the public key, and decrypting the funds received from the digital currency wallet based on the private key.

[0015] Optionally, user information is initialized, including generating a public key for each user in the user queue and recording each user's job level and work attributes, thereby ensuring that the identity and permissions of each user in the system are clearly recorded and managed. Specifically, when a new user is added to the user queue, the system first generates a public and private key pair for each user. The public key is public and used to encrypt information or verify signatures, while the private key is kept secret and used to decrypt information or generate signatures. The generation of public and private key pairs typically relies on strong encryption algorithms, such as RSA and ECDSA, which ensure the security and uniqueness of the public and private key pairs. After generation, the system securely stores this public and private key pair, ensuring that only authorized users can access their private keys.

[0016] Furthermore, a multi-signature script is generated based on the public keys of all users. This script defines the number and conditions required for transaction verification, i.e., which users' signatures are required and how many signatures are needed to confirm the validity of the transaction. For example, assuming there are 5 users (A, B, C, D, E), the system can generate a 3-of-5 multi-signature script, meaning that any 3 signatures from these 5 users are required for successful verification. The creation of the multi-signature script is the core of the multi-signature mechanism, ensuring that only signature combinations that meet specific conditions can unlock funds in a cryptocurrency wallet.

[0017] Furthermore, the private key is used to decrypt funds received from a cryptocurrency wallet. However, the private key is not directly used to decrypt the funds; instead, it generates a digital signature to prove that the initiator of the transaction request indeed possesses the private key corresponding to the public key, thereby verifying the authenticity and intent of the transaction. When a transaction is sent to the blockchain network, the transaction initiator signs the transaction information using their private key, and this signature is then broadcast along with the transaction to other nodes in the network. Other nodes use the transaction initiator's public key to verify the validity of the signature, thus confirming whether the transaction was initiated by the legitimate owner. For example, the signature combination of users A, B, and C decrypts the received funds, thus completing a transaction.

[0018] P20: Configure signature utility value based on each user's job level and work attributes.

[0019] Furthermore, as shown in Figure 2, step P20 of this embodiment further includes: P21: obtaining the functional level type and work attribute type of the user queue; P22: generating a functional level-utility value based on the functional level type; P23: generating a work attribute-utility value based on the work attribute type; P24: training a utility value configuration model using the identification information of the functional level-utility value, the work attribute-utility value, and the identification signature utility value; P25: configuring the signature utility value of each user based on the utility value configuration model.

[0020] It should be understood that the signature utility value in the multi-signature verification process should be configured based on the user's functional level and job attributes to ensure that the weight and utility of the signature match the user's role and responsibilities. Specifically, firstly, the functional level type (e.g., senior management, middle management, general staff) and job attribute type (e.g., finance, technology, administration) of each user are obtained. The functional level type reflects the user's position and scope of responsibilities within the organization, determining the importance of the user's signature in multi-signature verification. The job attribute type reflects the user's professional field and specific job content, further refining the configuration of the user's signature utility value.

[0021] Furthermore, based on the user's job level type, a corresponding job level-utility value is generated, that is, each job level type is mapped to a specific utility value. For example, senior management may be mapped to a higher utility value, middle management to a medium utility value, and ordinary employees to a lower utility value. Similarly, based on the user's job attribute type, a corresponding job attribute-utility value is generated. For example, the finance department may be mapped to a higher utility value, the technical department to a medium utility value, and the administrative department to a lower utility value.

[0022] Furthermore, by combining the functional level-utility value and the job attribute-utility value, along with the identifier information that identifies the signature utility value, the model ensures that it can uniquely identify each user when generating utility values. Using machine learning or statistical methods, a utility value configuration model is trained. This model comprehensively considers different utility values ​​related to functional level and job attribute to generate a comprehensive utility value for each user. Then, based on the trained utility value configuration model, a specific signature utility value is configured for each user. This value determines the weight and influence of the user's signature in multi-signature verification.

[0023] For example, suppose an organization has users at different functional levels, including senior management, middle management, and general employees. Each functional level corresponds to a different utility value: senior management has the highest utility value, followed by middle management, and general employees have the lowest. Meanwhile, users in this organization have different job attributes, such as finance, technical, and administrative. Each job attribute also corresponds to a different utility value: finance has the highest utility value because they are directly involved in fund management; technical is second; and administrative is the lowest. By inputting information about functional level type and job attribute type into the utility value configuration model, the system can generate a comprehensive signature utility value. For example, a senior-level finance employee would have a very high signature utility value, while a general administrative employee would have a lower signature utility value.

[0024] P30: Create a multi-signature address, which includes generating a multi-signature script using a public key, generating a multi-signature address based on the multi-signature script, and using it to receive funds from a digital currency wallet.

[0025] Specifically, multi-signature addresses are created, requiring approval from multiple signers for a transaction to proceed, significantly enhancing fund security and management flexibility. First, the public keys of all users participating in the multi-signature process are collected. Then, using these public keys, a multi-signature script is generated according to preset multi-signature rules (such as the M-of-N rule, meaning that signatures from any M out of N users are sufficient to confirm a transaction). This script defines the number of signatures required for transaction verification and which users' signatures are valid. For example, assuming 5 users (A, B, C, D, E), the system can generate a 3-of-5 multi-signature script, indicating that signatures from any 3 out of these 5 public keys are required to approve the transaction.

[0026] Furthermore, a multi-signature address is generated based on the multi-signature script. This multi-signature address is a special encrypted address that can only be used if the requirements of the multi-signature script are met. It is calculated using the multi-signature script and differs from a standard single-signature address. This multi-signature address is used to receive cryptocurrency funds, requiring multiple signatories to jointly approve the transaction, significantly improving fund security and making it suitable for scenarios requiring high security and complex management.

[0027] P40: Generate a multi-signature verification strategy, which includes a dynamic adjustment module. When the dynamic adjustment module detects a change in the user queue, it updates the multi-signature verification strategy.

[0028] Optionally, a multi-signature verification strategy is generated. This strategy dynamically adjusts the rules of multi-signature verification based on changes in the actual operating environment to enhance the system's adaptability and security. The multi-signature verification strategy includes a dynamic adjustment module that can detect changes in the user queue in real time and update the verification strategy to adapt to the constantly changing environment. When the user queue changes, the dynamic adjustment module updates the multi-signature verification strategy based on the specific changes. It recalculates the signature utility value based on the latest user information and adjusts the signature verification strategy accordingly. For example, if a new user joins, it may be necessary to add a new public key to the multi-signature script or adjust the signature weight. Through dynamic adjustment, the system's security and reliability are ensured to remain unaffected even when users change. All transaction verifications must satisfy the updated multi-signature verification strategy.

[0029] Furthermore, in generating a multi-signature verification strategy, step P40 of this embodiment further includes: P41: The multi-signature verification strategy includes a preset number of signatures, a preset signature utility value, and a feature signature address; wherein, the preset number of signatures is used to verify whether the sum of the number of user signatures meets a preset minimum number, the preset signature utility value is used to verify whether the sum of the user signature utility values ​​meets a preset minimum signature utility value, and the feature signature address is used to verify whether the current user signature address matches the preset feature signature address successfully.

[0030] It should be understood that the specific process of generating a multi-signature verification strategy can be as follows: First, the multi-signature verification strategy includes a preset number of signatures, a preset signature utility value, and a signature address. The preset number of signatures refers to the minimum number of signatures required to complete a transaction or document verification, and this number is less than the total number of users in the queue, N. This number can be preset according to business needs and security requirements; for example, at least 3 out of 5 signatures may be required for a transaction. This number is dynamically adjusted according to security requirements and user levels to ensure transaction security. When a transaction occurs, the system counts the number of signatures from all participating users and compares it with the preset number of signatures. Only when the actual number of signatures reaches or exceeds the preset value is the transaction considered valid. This mechanism effectively prevents transaction risks caused by an insufficient number of signers.

[0031] The preset signature utility value is a weighted value configured based on each user's job level and work attributes. It is used to verify whether the sum of users' signature utility values ​​meets the preset minimum signature utility value. For example, senior management may have a higher signature utility value, middle management a medium value, and ordinary employees a lower value. When verifying signatures, the system not only checks the number of signatures but also checks whether the sum of these signatures reaches the preset minimum utility value, ensuring the participation of high-weight users and improving transaction security.

[0032] The signature address is one or more pre-defined signature addresses with special permissions or functions, typically held by specific high-privilege users, including special senior management users and core audit users (such as finance managers). During the verification process, the system will check whether the submitted signature comes from a signature address to ensure that critical transactions must have the signature of a specific user.

[0033] Furthermore, step P41 in this embodiment of the application also includes: P41-1: obtaining real-time transactions of the digital currency wallet; P41-2: assessing the transaction risk level of the real-time transactions, including transaction amount, transaction frequency of the transaction object and transaction cycle, and outputting real-time transaction risk indicators; P41-3: updating the multi-signature verification strategy according to the real-time transaction risk indicators, including the updated preset signature quantity, preset signature utility value and feature signature address, wherein the updated preset signature quantity and preset signature utility value are greater than the original preset signature quantity and preset signature utility value, and the updated feature signature address is more than the original feature signature address.

[0034] Optionally, this application further introduces a dynamic adjustment mechanism to ensure that the multi-signature verification strategy can flexibly respond to real-time risk changes in digital currency wallet transactions. First, the system captures and obtains real-time transaction data from each digital currency wallet by integrating the API of the digital currency trading platform or the listening mechanism of the blockchain network. This data includes, but is not limited to, key information such as transaction amount, transaction counterparty (i.e., payee or payer), and transaction time.

[0035] Furthermore, after acquiring real-time transaction data, a series of risk assessment algorithms are used to conduct in-depth analysis of each transaction. Assessment dimensions include, but are not limited to, transaction amount (i.e., the size of the transaction; large transactions may be accompanied by higher risk), transaction frequency of the trading counterpart (accounts that frequently interact with high-risk accounts may have higher risk), and transaction cycle (transactions during abnormal time periods, such as late at night or holidays, may increase risk). Machine learning models (such as logistic regression, random forest, etc.) or custom risk assessment rule sets are used to perform multi-dimensional analysis of the transaction data to output accurate real-time transaction risk indicators, which intuitively reflect the current risk level of the transaction.

[0036] Furthermore, based on the assessment results of real-time transaction risk indicators, the multi-signature verification strategy is updated, dynamically adjusting key parameters in the strategy, including the updated preset number of signatures, preset signature utility value, and signature address. For example, when the transaction risk indicator is high, the preset number of signatures and preset signature utility value are increased, requiring more signers to participate in verification and each signer to have a higher utility value, thereby improving transaction security. Simultaneously, the number of signature addresses is increased, requiring transactions to include signature addresses from specific high-risk, sensitive areas to ensure transaction compliance and traceability. In other words, the updated preset number of signatures and utility value are greater than before, and there are also more signature addresses, ensuring higher security for high-risk transactions.

[0037] For example, if the real-time transaction risk indicator Rtotal = 0.505, the original preset number of signatures... =3, the updated preset signature count : If the original preset signature effectiveness value =10, the updated preset signature utility value : If the original signature address Add a new signature address, assuming the new one is... : Furthermore, when the dynamic adjustment module detects a change in the user queue, it updates the multi-signature verification strategy. In this embodiment, step P40 further includes: P42: when the dynamic adjustment module detects a change in the user queue, it reconfigures the signature utility value for each user in the updated user queue; P43: it updates the value of the preset signature utility value in the multi-signature verification strategy according to the reconfigured signature utility value.

[0038] Specifically, when the dynamic adjustment module detects a change in the user queue, it reconfigures the signature utility value for each user in the updated user queue, referring to the method described above. For example, when the dynamic adjustment module recognizes a change in the user queue (such as a new user joining, an existing user leaving, or a change in user permissions), the system first obtains the job level type and work attribute type of the newly formed user queue. Based on the job level type and work attribute type, it reconfigures the signature utility value for each user in the queue. The signature utility value represents the user's importance and credibility in the multi-signature verification process and is one of the key factors determining whether a transaction can successfully pass verification.

[0039] Furthermore, the preset signature utility value in the multi-signature verification strategy is updated according to the reconfigured signature utility value. The preset signature utility value is a threshold or standard defined in the strategy to determine whether a transaction has received sufficient quantity and quality of signature support. By updating this value, it can be ensured that the multi-signature verification strategy maintains its original security and effectiveness even if the user queue changes. For example, P50: The real-time transactions of the digital currency wallet are verified according to the updated multi-signature verification strategy to obtain the verification result.

[0040] Furthermore, step P50 in this embodiment of the application also includes: P51: if the verification result is successful, the real-time transaction is stored in the transaction blockchain for storage management; P52: if the verification result is unsuccessful, the real-time transaction is stored in the transaction exception log for storage management.

[0041] It should be understood that each real-time transaction in a digital currency wallet is verified according to the updated multi-signature verification strategy. The verification process checks whether the transaction meets all the conditions defined in the strategy, including but not limited to the number of signatures, the identity of the signer, and whether the signature utility value meets the preset standard. Once all conditions are met, the system considers the transaction to have passed verification; otherwise, the verification result is failed.

[0042] Specifically, once a real-time transaction passes multi-signature verification, the system considers it a valid transaction and submits it to the blockchain network for storage and management. As a decentralized, immutable, distributed ledger technology, blockchain ensures the transparency, security, and traceability of transactions. Once a transaction is recorded on the blockchain, any tampering or deletion becomes extremely difficult, thus protecting the authenticity and integrity of the transaction.

[0043] If the verification result is a failure, the real-time transaction that fails multi-signature verification is considered an abnormal transaction and is automatically recorded in the transaction anomaly log. The transaction anomaly log is a database or file system specifically designed to store and manage records of transactions that have failed verification. By recording these abnormal transactions, system administrators can conduct regular reviews and analyses to identify potential security risks, system vulnerabilities, or user errors, and take appropriate measures for remediation and improvement.

[0044] In summary, the embodiments of this application have at least the following technical effects: This application generates a public key for each user in the user queue by initializing user information and configuring a signature utility value, generates a multi-signature address according to the multi-signature script, and generates a multi-signature verification strategy. When a change in the user queue is detected, the multi-signature verification strategy is updated, and real-time transactions of the digital currency wallet are verified.

[0045] This achieves the technical effect of intelligently changing signature strategies based on real-time personnel movement, thereby improving the security and flexibility of multi-signature verification.

[0046] Example 2 is based on the same inventive concept as the multi-signature verification method for digital currency wallets in the foregoing examples. As shown in Figure 3, this application provides a multi-signature verification device for digital currency wallets. The device and method examples in this application are based on the same inventive concept. The device includes: a user information initialization module 11, which initializes user information, generates a public key for each user in the user queue, and records each user's job level and work attributes; a signature utility value configuration module 12, which configures a signature utility value according to each user's job level and work attributes; a multi-signature address creation module 13, which creates a multi-signature address, which includes generating a multi-signature script using a public key and generating a multi-signature address based on the multi-signature script, for receiving funds from a digital currency wallet; a multi-signature verification strategy update module 14, which generates a multi-signature verification strategy, which includes a dynamic adjustment module that updates the multi-signature verification strategy when it detects a change in the user queue; and a real-time transaction verification module 15, which verifies real-time transactions of the digital currency wallet according to the updated multi-signature verification strategy and obtains the verification results.

[0047] Furthermore, the user information initialization module 11 is also used to perform the following steps: generating a private key of the public key, storing the public key and the private key as a public-private key pair; generating a multi-signature script based on the public key, and decrypting the funds received from the digital currency wallet based on the private key.

[0048] Furthermore, the signature utility value configuration module 12 is also used to perform the following steps: obtaining the functional level type and work attribute type of the user queue; generating a functional level-utility value according to the functional level type; generating a work attribute-utility value according to the work attribute type; training a utility value configuration model using the functional level-utility value, the work attribute-utility value, and the identifier information of the signature utility value; and configuring the signature utility value of each user according to the utility value configuration model.

[0049] Furthermore, the multi-signature verification strategy update module 14 is also used to perform the following steps: generating a multi-signature verification strategy, the multi-signature verification strategy including a preset number of signatures, a preset signature utility value, and a feature signature address; wherein, the preset number of signatures is used to verify whether the sum of the number of user signatures meets a preset minimum number, the preset signature utility value is used to verify whether the sum of the user signature utility values ​​meets a preset minimum signature utility value, and the feature signature address is used to verify whether the current user signature address matches the preset feature signature address successfully.

[0050] Furthermore, the multi-signature verification strategy update module 14 is also used to perform the following steps: obtaining real-time transactions of the digital currency wallet; assessing the transaction risk level of the real-time transactions, including transaction amount, transaction frequency of the transaction object and transaction cycle, and outputting real-time transaction risk indicators; updating the multi-signature verification strategy according to the real-time transaction risk indicators, including the updated preset signature quantity, preset signature utility value and feature signature address, wherein the updated preset signature quantity and preset signature utility value are greater than the original preset signature quantity and preset signature utility value, and the updated feature signature address is more than the original feature signature address.

[0051] Furthermore, the multi-signature verification strategy update module 14 is also used to perform the following steps: when the dynamic adjustment module detects a change in the user queue, it reconfigures the signature utility value for each user in the updated user queue; and updates the value of the preset signature utility value in the multi-signature verification strategy according to the reconfigured signature utility value.

[0052] Furthermore, the real-time transaction verification module 15 is also used to perform the following steps: if the verification result is successful, the real-time transaction is stored in the transaction blockchain for storage management; if the verification result is unsuccessful, the real-time transaction is stored in the transaction exception log for storage management.

[0053] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, the above description focuses on specific embodiments of this specification. Additionally, the processes depicted in the accompanying drawings do not necessarily require a specific or sequential order to achieve the desired results. In some implementations, multitasking and parallel processing are possible or may be advantageous.

[0054] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

[0055] This specification and accompanying drawings are merely illustrative examples of this application and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Therefore, if such modifications and variations fall within the scope of this application and its equivalents, this application intends to include such modifications and variations.

Claims

1. A multi-signature verification method for digital currency wallets, characterized in that, The method includes: initializing user information, wherein the initialization of user information generates a public key for each user in the user queue and records the job level and work attributes of each user; configuring a signature utility value according to the job level and work attributes of each user; creating a multi-signature address, wherein the multi-signature address includes generating a multi-signature script using the public key, generating a multi-signature address according to the multi-signature script, and using it to receive funds from a digital currency wallet; generating a multi-signature verification strategy, wherein the multi-signature verification strategy includes a dynamic adjustment module, which updates the multi-signature verification strategy when it detects a change in the user queue; and verifying real-time transactions of the digital currency wallet according to the updated multi-signature verification strategy to obtain verification results.

2. The multi-signature verification method for digital currency wallets as described in claim 1, characterized in that, The method further includes generating a signature utility value based on each user's job level and work attribute, and obtaining the job level type and work attribute type of the user queue; generating a job level-utility value based on the job level type; generating a work attribute-utility value based on the work attribute type; training a utility value configuration model using the job level-utility value, the work attribute-utility value, and the identifier information of the signature utility value; and configuring the signature utility value for each user based on the utility value configuration model.

3. The multi-signature verification method for digital currency wallets as described in claim 1, characterized in that, The method of initializing user information to generate a public key for each user in the user queue also includes: generating a private key for the public key, storing the public key and the private key as a public-private key pair; generating a multi-signature script based on the public key; and decrypting the funds received from the digital currency wallet based on the private key.

4. The multi-signature verification method for digital currency wallets as described in claim 1, characterized in that, A multi-signature verification strategy is generated, which includes a preset number of signatures, a preset signature utility value, and a feature signature address. The preset number of signatures is used to verify whether the sum of the number of user signatures meets a preset minimum number. The preset signature utility value is used to verify whether the sum of the user signature utility values ​​meets a preset minimum signature utility value. The feature signature address is used to verify whether the current user signature address matches the preset feature signature address.

5. The multi-signature verification method for digital currency wallets as described in claim 4, characterized in that, The method further includes: acquiring real-time transactions of the digital currency wallet; assessing the transaction risk level of the real-time transactions, including transaction amount, transaction frequency of the transaction object, and transaction cycle, and outputting real-time transaction risk indicators; updating the multi-signature verification strategy according to the real-time transaction risk indicators, including the updated preset signature quantity, preset signature utility value, and feature signature address, wherein the updated preset signature quantity and preset signature utility value are greater than the original preset signature quantity and preset signature utility value, and the updated feature signature address is more than the original feature signature address.

6. The multi-signature verification method for digital currency wallets as described in claim 4, characterized in that, When the dynamic adjustment module detects a change in the user queue, it updates the multi-signature verification strategy. The method includes: when the dynamic adjustment module detects a change in the user queue, reconfiguring the signature utility value for each user in the updated user queue; and updating the value of the preset signature utility value in the multi-signature verification strategy according to the reconfigured signature utility value.

7. The multi-signature verification method for digital currency wallets as described in claim 1, characterized in that, The method further includes verifying real-time transactions of the digital currency wallet according to the updated multi-signature verification strategy and obtaining verification results. If the verification result is successful, the real-time transaction is stored in the transaction blockchain for storage management. If the verification result is unsuccessful, the real-time transaction is stored in the transaction anomaly log for storage management.

8. A multi-signature verification device for digital currency wallets, characterized in that, The device includes: a user information initialization module, used to initialize user information, generating a public key for each user in the user queue and recording each user's job level and work attributes; a signature utility value configuration module, used to configure a signature utility value according to each user's job level and work attributes; a multi-signature address creation module, used to create a multi-signature address, the multi-signature address including generating a multi-signature script using a public key, generating a multi-signature address according to the multi-signature script, used to receive funds from a digital currency wallet; a multi-signature verification strategy update module, used to generate a multi-signature verification strategy, the multi-signature verification strategy including a dynamic adjustment module, which updates the multi-signature verification strategy when it detects a change in the user queue; and a real-time transaction verification module, used to verify real-time transactions of the digital currency wallet according to the updated multi-signature verification strategy and obtain verification results.

Images