Digital asset management method and system based on asynchronous settlement and ownership lock

By employing asynchronous settlement and ownership locking methods, the problem of double-spending in digital asset management is solved, enabling efficient, secure, and flexible ownership transfer, increasing transaction throughput, and ensuring the security and privacy of digital assets.

CN122434518APending Publication Date: 2026-07-21MARVEL RES LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
MARVEL RES LTD
Filing Date
2026-04-23
Publication Date
2026-07-21

AI Technical Summary

Technical Problem

Existing digital asset management technologies suffer from performance bottlenecks, high system complexity, and centralized trust risks in preventing double-spending, making it difficult to achieve efficient, secure, and flexible ownership transfer.

Method used

By employing asynchronous settlement and ownership locking, ownership change requests are received and verified with trusted timestamps. Ownership transfers are processed asynchronously in batches. Combined with cryptographic credentials and periodic settlement cycles, transaction ordering and settlement are decoupled, thus preventing double-spending.

Benefits of technology

It enables efficient, secure, and flexible transfer of digital asset ownership, increases transaction throughput, avoids complex global state consensus processes, and ensures the security and privacy of digital assets.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122434518A_ABST
    Figure CN122434518A_ABST
Patent Text Reader

Abstract

The application is suitable for the technical field of computer and financial technology, and provides a digital asset management method and system based on asynchronous settlement and ownership locking, which comprises the following steps: receiving an ownership change request of a target asset unit from a requestor; giving a trusted timestamp to the received ownership change request; determining the sequence of the ownership change request according to the trusted timestamp, and entering an ownership verification process; after reaching a predetermined settlement time point, asynchronously processing all locked target asset units in the current settlement period, generating a new asset unit controlled by a second ownership certificate for each locked target asset unit to replace the old asset unit; and unlocking the asset unit to complete the ownership transfer. The application can realize efficient, safe, certain and flexible ownership transfer, and significantly improve the transaction throughput.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention belongs to the fields of computer technology and financial technology, and in particular relates to a digital asset management method and system based on asynchronous settlement and ownership locking. Background Technology

[0002] The core challenge of digital asset ownership transfer technology lies in how to securely and effectively prevent double-spending. Existing digital asset management technologies offer different solutions, but their underlying paradigms all have inherent flaws, forcing compromises in performance, efficiency, or trust models. In particular, public blockchain systems based on global consensus generally face transaction confirmation delays and scalability bottlenecks. While layer-two solutions exist, they are typically complex in architecture and require conditions such as fund locking. Furthermore, many systems require recording a complete and publicly traceable transaction history, which is not optimal in certain privacy-conscious scenarios. The following are examples of existing technologies:

[0003] I. Blockchain systems based on global consensus (represented by enterprise-level consortium blockchains):

[0004] Double-spending prevention mechanism: Transactions are globally sorted and verified through a consensus algorithm (such as Byzantine fault tolerance algorithm) among pre-selected node groups, and a unified ledger state machine is maintained to ensure that any change in the state of an asset must be approved by a majority of the network, thereby preventing double-spending.

[0005] Inherent flaw: The mechanism that relies on "global collaborative consensus" is the root cause of the bottleneck in this type of technology.

[0006] Performance bottleneck: Maintaining a globally consistent state machine requires all transactions to go through a complex multi-step process (such as endorsement, sorting, and submission verification), resulting in low transaction throughput and high confirmation latency, making it difficult to support high-concurrency scenarios.

[0007] The system is highly complex: all nodes in the network need to maintain a complete global state synchronously, and any state change involves heavy protocol overhead and network-wide synchronization, which severely limits the system's scalability.

[0008] II. Centralized hosting services (such as various usage rights management platforms):

[0009] Anti-double-spending mechanism: Relies on a single trusted central authority (custodian) to serialize transactions and prevents double-spending through consistency checks of a centralized ledger.

[0010] Inherent flaws: The nature of this mechanism determines that it has the following problems:

[0011] Centralized trust risk: When the allocation of asset usage rights is carried out within a trusted custodian, the security of the system depends entirely on the integrity and capability of the custodian, which poses a single point of failure and trust risk.

[0012] Functional limitations: It focuses on improving capital efficiency and does not provide a universal ownership transfer rule engine that emphasizes settlement finality and whose security does not depend on a single custodian.

[0013] III. Layer 2 Expansion Schemes (such as state channels, sidechains):

[0014] Anti-double-spending mechanism: By moving most transaction activities to a processing layer (channel or sidechain) outside the main chain, the asset anchoring and settlement are ultimately completed through the main chain, in order to alleviate the pressure on the underlying network.

[0015] Inherent drawbacks: In attempting to optimize performance, this architecture introduces new complexities and limitations.

[0016] Complex architecture: State channels require pre-deposited funds and complex challenge / response mechanisms; sidechains involve multiple steps such as locking main chain assets and issuing mapped assets, which significantly increases system complexity and the barrier to entry for users.

[0017] Insufficient flexibility: It usually still relies on the transparent ledger model of the underlying blockchain, which forces the public disclosure of transaction history and lacks flexibility in scenarios that require a balance between transparency and privacy.

[0018] In summary, existing technologies all attempt to solve the double-spending problem through global collaboration and consensus (whether network-wide consensus or centralized custody). While this "global competition" paradigm addresses security issues to some extent, it inevitably introduces inherent flaws in performance, complexity, and architecture, hindering the large-scale and efficient application of digital assets. Therefore, there is a current need for a digital asset management system that can guarantee security and fairness, achieve efficient ownership transfer, and also consider privacy. Summary of the Invention

[0019] The purpose of this invention is to provide a digital asset management method and system based on asynchronous settlement and ownership locking, in order to solve the above-mentioned technical problems.

[0020] This invention is implemented as follows: a digital asset management method based on asynchronous settlement and ownership locking, comprising the following steps:

[0021] The receiving party requests a change of ownership for the target asset unit; the change of ownership request includes a unique asset identifier and a first ownership certificate;

[0022] Assign a trusted timestamp to the received ownership change request;

[0023] The order of ownership change requests is determined based on the trusted timestamps, and the ownership verification process begins.

[0024] Ownership verification process: Verify whether the first ownership certificate matches the current control of the target asset unit, and check whether the target asset unit is in an unlocked state during the current settlement cycle; if the verification is successful and the target asset unit is in an unlocked state, then set the state of the target asset unit to locked, return an acceptance receipt to the requester, and enter the asynchronous batch settlement process;

[0025] Asynchronous batch settlement process: After the scheduled settlement time is reached, all locked target asset units in the current settlement cycle are processed asynchronously in batches. A new asset unit controlled by a second ownership certificate is generated for each locked target asset unit to replace the old asset unit; the locking status of the asset unit is released, and the ownership transfer is completed.

[0026] Furthermore, each asset unit represents a digital asset and contains three key attributes:

[0027] A unique identifier for an asset, used to identify a specific asset;

[0028] A certificate of ownership is a piece of confidential information and is the sole basis for verifying the legitimacy of ownership.

[0029] Encrypted content is a piece of content protected by cryptography.

[0030] Furthermore, the encrypted content begins with the asset's unique identifier, and subsequent appended content includes one or more of the following: an immutable timestamp and transfer records, forming a historical log of the digital asset; the encrypted content is encrypted using the public key currently controlling the asset unit.

[0031] Furthermore, in the ownership verification process, for the same asset unit within the same settlement cycle, only the first valid ownership change request that passes verification will be responded to, and subsequent ownership change requests will be rejected.

[0032] Furthermore, the ownership verification process includes a compliance check step before verifying whether the first ownership certificate matches the current control of the target asset unit; the compliance check includes at least one of the following: blacklist check, business rule check, and debtor confirmation.

[0033] Furthermore, the unique asset identifier of the new asset unit is consistent with that of the old asset unit, and its encrypted content is supplemented with new transfer records on the basis of the encrypted content of the old asset unit. The new asset unit is controlled by the second ownership certificate.

[0034] Another objective of this invention is to provide a digital asset management system based on asynchronous settlement and ownership lock-in, for implementing the aforementioned digital asset management method based on asynchronous settlement and ownership lock-in, comprising:

[0035] The request receiving module is used to receive a request from a requester for a change of ownership of a target asset unit; the change of ownership request includes a unique asset identifier and a first ownership certificate;

[0036] The timestamp service module is used to assign a trusted timestamp to received ownership change requests;

[0037] The request processing module is used to determine the order of ownership change requests based on the trusted timestamps and to proceed to the ownership verification process;

[0038] The ownership verification module is used to verify whether the first ownership certificate matches the current control of the target asset unit, and to check whether the target asset unit is in an unlocked state during the current settlement cycle; if the verification is successful and the target asset unit is in an unlocked state, the status of the target asset unit is set to locked, and an acceptance receipt is returned to the requester, and the asynchronous batch settlement process is initiated.

[0039] The asynchronous batch settlement module is used to asynchronously batch process all locked target asset units in the current settlement cycle after the predetermined settlement time point is reached. It generates a new asset unit controlled by a second ownership certificate for each locked target asset unit to replace the old asset unit; releases the locking status of the asset unit and completes the transfer of ownership.

[0040] Furthermore, the aforementioned digital asset management system based on asynchronous settlement and ownership lock-in also includes:

[0041] The asset registration module is used to register and maintain the status of all asset units.

[0042] The digital asset management method based on asynchronous settlement and ownership locking provided by this invention achieves highly efficient, secure, deterministic, and flexible ownership transfer through a core mechanism that combines a unique request sorting mechanism based on submission time ("first-come, first-served"), unique asset identifiers, cryptographic ownership certificates and digital asset locking, and periodic asynchronous batch settlement cycles. By decoupling transaction sorting from transaction settlement, it avoids complex global state consensus processes, eliminates double-spending at its source, and significantly improves transaction throughput. Attached Figure Description

[0043] Figure 1 This is a flowchart illustrating a digital asset management method based on asynchronous settlement and ownership locking, provided in an embodiment of the present invention. Detailed Implementation

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

[0045] like Figure 1 As shown, in one embodiment of the present invention, a digital asset management method based on asynchronous settlement and ownership locking is provided, which is also applicable to centralized and decentralized environments. It achieves the secure transfer of ownership of digital assets (including but not limited to virtual currencies, digital equity certificates, digital securities, etc.) through cryptographic verification, request ordering based on trusted timestamps, and periodic batch settlement. Specifically, it includes the following steps:

[0046] S1. Receive the requesting party's request for change of ownership of the target asset unit; the request for change of ownership includes the asset's unique identifier and the first ownership certificate;

[0047] S2. Assign a trusted timestamp to the received ownership change request; a trusted timestamp refers to an authoritative and tamper-proof timestamp.

[0048] S3. Determine the order of ownership change requests based on the trusted timestamps, and proceed to the ownership verification process;

[0049] S4. Ownership Verification Process: Verify whether the first ownership certificate matches the current control of the target asset unit, and check whether the target asset unit is in an unlocked state during the current settlement cycle; if the verification is successful and the target asset unit is in an unlocked state, then set the state of the target asset unit to locked, return an acceptance receipt to the requester, and enter the asynchronous batch settlement process;

[0050] S5. Asynchronous Batch Settlement Process: Upon reaching the predetermined settlement time, asynchronous batch processing is performed on all locked target asset units within the current settlement cycle. A new asset unit controlled by a second ownership certificate is generated for each locked target asset unit to replace the old asset unit; the locked status of the asset unit is released, and the ownership transfer is completed.

[0051] It should be noted that the method provided in this embodiment of the invention has a wide range of applications, and is particularly applicable to, but not limited to, digital asset notarization, digital collectibles, digital bills, virtual currencies, and any specific digital rights or value certificates, asset forms, and scenarios. It is important to note that the digital assets managed in this embodiment of the invention strictly comply with relevant national and international regulatory policies and laws and regulations in their issuance and circulation, and do not involve the issuance, trading, or clearing of any non-fiat currencies.

[0052] This invention shifts from "global state consensus" to "individual asset sequence control," achieving secure and efficient ownership transfer of digital assets through a unique "request locking, batch settlement" mechanism. The authority of this mechanism is based on the "submission time" of the ownership change request rather than the "processing time," ensuring that the first valid request for any specific asset within the same settlement cycle has exclusive rights, thereby eliminating double-spending at its source.

[0053] In practical applications, each asset unit represents a digital asset and contains three key attributes:

[0054] A unique asset identifier is a globally unique name within the system used to identify a specific asset.

[0055] A certificate of ownership is a piece of secret information (such as an encrypted private key or digital signature). Possessing it means possessing control of the asset and is the sole basis for verifying the legitimacy of ownership.

[0056] The encrypted content is a piece of content protected by cryptography. The beginning of the encrypted content contains the asset's unique identifier itself, and the subsequent appended content includes one or more of the following: an immutable timestamp and transfer records, forming a historical log of the digital asset. The encrypted content is encrypted using the public key that currently controls the asset unit, and only the owner holding the corresponding private key (i.e., ownership certificate) can decrypt and access it. This protection method ensures that the integrity of the encrypted content is associated with the current ownership certificate.

[0057] In a preferred embodiment of the present invention, in the ownership verification process, for the same asset unit within the same settlement period, only the first valid ownership change request that passes verification is responded to, and subsequent ownership change requests are rejected.

[0058] The core logic of this invention is as follows: for the same asset unit, within the same settlement cycle, it only accepts the first valid ownership change request that passes verification. Once verification is successful, the asset unit is immediately placed in a locked state, and a real-time deterministic receipt of acceptance is returned to the requester. The locked state means that within this settlement cycle, the system will reject all subsequent ownership change requests for that asset.

[0059] In practical applications, when asset owner A wishes to transfer an asset to owner B, they submit the unique identifier of the target asset unit and the current ownership certificate (i.e., the first ownership certificate) to the system. Upon receiving the ownership change request, the system records the submission timestamp and then proceeds to the ownership verification process to verify: a) whether the first ownership certificate is correct; b) whether the asset is locked. If the verification passes and the asset is not locked, the system immediately locks the asset unit and returns a confirmation receipt to A. The system does not process ownership transfers in real-time upon request. Instead, it asynchronously batch-processes all locked asset units within a predetermined settlement period after the predetermined settlement time point: generating a new asset unit protected by a new second ownership certificate for each locked asset unit to replace the old one. Specifically, after the predetermined settlement time point, for each locked asset unit, a "replacement" operation is performed: the old asset unit is removed, and a new asset unit is generated. The unique identifier of the new asset unit remains unchanged. The encrypted content is supplemented with new information (such as the transfer record) on top of the old encrypted content. Most importantly, its control is updated to a new ownership certificate (i.e., a second ownership certificate) held by the new owner B. At this point, the transfer of asset ownership from A to B is officially completed, the asset unit is unlocked, and it is ready to receive the next ownership change request.

[0060] The authoritative order of the method provided in this invention strictly follows the "submission time" of the request. For multiple ownership change requests for the same asset within the same settlement cycle, the system strictly follows the "first-come, first-served" principle. The first ownership change request that passes verification will obtain exclusive processing rights, and subsequent ownership change requests will be directly rejected. This time-based mutual exclusion mechanism is the key to how this invention naturally prevents double-spending.

[0061] In a preferred embodiment of the present invention, the ownership verification process further includes a compliance check step before verifying whether the first ownership certificate matches the current control of the target asset unit; the compliance check includes at least one of the following: blacklist check, business rule check, and debtor confirmation.

[0062] In a preferred embodiment of the present invention, the unique asset identifier of the new asset unit is consistent with that of the old asset unit, its encrypted content is supplemented with new transfer records on the basis of the encrypted content of the old asset unit, and the new asset unit is controlled by the second ownership certificate.

[0063] In another embodiment of the present invention, a digital asset management system based on asynchronous settlement and ownership locking is also provided to implement the above-mentioned digital asset management method based on asynchronous settlement and ownership locking, specifically including:

[0064] The asset registration module, as the data cornerstone of the system, is a trusted data storage center with consensus among all participants, used to register and maintain the status of all asset units;

[0065] The request receiving module is used to receive a request from a requester for a change of ownership of a target asset unit; the change of ownership request includes a unique asset identifier and a first ownership certificate;

[0066] The timestamp service module is used to assign a reliable timestamp to the received ownership change requests, providing the system with an objective basis for determining the order of requests.

[0067] The request processing module is used to determine the order of ownership change requests based on the trusted timestamp and enter the ownership verification process; the request processing module is the system's scheduling center, which determines the order of ownership change requests based on the timestamp and calls the ownership verification module for verification.

[0068] The ownership verification module works in conjunction with the request processing module to verify whether the first ownership certificate matches the current control of the target asset unit and to check whether the target asset unit is in an unlocked state during the current settlement cycle. If the verification is successful and the target asset unit is in an unlocked state, the status of the target asset unit is set to locked, and an acceptance receipt is returned to the requester, thus entering the asynchronous batch settlement process.

[0069] The asynchronous batch settlement module is used to asynchronously batch process all locked target asset units within the current settlement period after reaching the predetermined settlement time. It generates a new asset unit controlled by a second ownership certificate for each locked target asset unit to replace the old asset unit; then, it unlocks the asset units, completing the ownership transfer. As the system's execution terminal, the asynchronous batch settlement module does not process requests immediately upon receipt, but is triggered according to a predetermined settlement period (e.g., every 10 minutes). At that time, it batch processes all valid ownership change requests for locked asset units within the current period, completing the final transfer of ownership.

[0070] Example 1: In this example, digital assets are digital accounts receivable vouchers in the supply chain. The corresponding digital asset management system is built on an enterprise-level consortium blockchain platform (such as Hyperledger Fabric), aiming to provide core enterprises, multi-level suppliers, and financial institutions with efficient, reliable, and compliant accounts receivable transfer services. Each asset unit represents a unique accounts receivable voucher, and its unique asset identifier is a globally unique voucher number generated when the core enterprise issues the voucher (such as "AR-2024-CORE1-SUPPLIER-A-001").

[0071] The ownership certificate is a user certificate private key generated based on a consortium blockchain cryptography system. Possessing this private key grants complete control and the right to the proceeds from the accounts receivable certificate. The system's Member Service Provider (MSP) module is responsible for managing the identity authentication of participating organizations.

[0072] Encrypted Content and Logs: The encrypted content of an asset unit is stored in encrypted form in the consortium blockchain's ledger. It begins with a unique credential number and records core information about the accounts receivable (such as amount, due date, debtor [core enterprise] information, etc.). Each time ownership is transferred (i.e., accounts receivable financing or transfer), the system appends a new record to the existing content, for example, "Transfer timestamp: <time>, Transferor: <Supplier A's identity certificate hash>, Recipient: <Supplier B or financial institution's identity certificate hash>, Transfer consideration: <amount>". This log is ensured through chaincode (smart contracts) that it can only be appended to, not deleted, forming a complete history of the accounts receivable's flow. Sensitive business information can be protected through Fabric's private data collection functionality.

[0073] Compliance Integration: Mandatory compliance checks are integrated into the ownership verification process. For example, before locking assets, the request processing chaincode invokes an external adapter query.

[0074] Blacklist check: Confirm that the recipient's certificate is not on the sanctions list.

[0075] Business rules check: Confirm that this transfer complies with internal risk control policies (such as restrictions on the number of transfers, discount rate range, etc.).

[0076] Debtor Confirmation: If necessary, a confirmation request can be initiated to the node representing the core enterprise. Only after all checks pass will the ownership transfer request be accepted and the assets locked. This demonstrates the flexibility and security of this invention in strictly regulated business scenarios.

[0077] When Tier 1 supplier A intends to transfer an account receivable from its core enterprise to Tier 2 supplier B or to bank C through financing, the following workflow is involved:

[0078] 1. A submits a transaction request, including the credential number of the target receivable and a digital signature (ownership certificate) generated with its private key, to the request processing chaincode deployed on the consortium blockchain through its application.

[0079] 2. The request processing chaincode performs the following operations: a. Compliance check: Invoke the compliance adapter to perform the series of checks mentioned above. b. Ownership verification: Verify that A's digital signature is valid. c. Lock check: Confirm that the accounts receivable document is not locked.

[0080] 3. If all verifications and checks pass, the chaincode immediately updates the status of the accounts receivable document to "Locked" on the ledger and returns a deterministic "Request accepted" receipt to A. This locked status is visible to all participants on the chain and cannot be tampered with.

[0081] 4. In the next settlement cycle (e.g., 2 hours after a commercially reasonable period), the asynchronous batch settlement module (which may be another chaincode triggered by a specific sorting service) is triggered. It processes all locked accounts receivable documents in the current cycle in batches: invalidates the old documents on the global ledger and generates a new document controlled by the recipient (B or C), while appending the current transaction record to the content.

[0082] 5. Once the transfer of ownership is formally completed, the new owner acquires full rights to the accounts receivable, and the asset is released from lock-up.

[0083] Example 2: In this example, the digital asset is a digital collectible (NFT). Each asset unit represents a unique digital collectible (such as a digital artwork), and its unique asset identifier is the fingerprint hash of that artwork.

[0084] The ownership certificate and its encrypted content are as follows: The ownership certificate is also a private key. In addition to the fingerprint hash, the encrypted content of the asset unit can also include information added during subsequent transfers, such as "Exhibition record: , <time>" or "Authentication information: <digital signature of authentication institution>", thereby establishing an immutable added value history for the digital collectible.

[0085] Example 3: In this example, digital assets are digital securities (such as tokens representing company equity). An asset unit refers to a certain number of digital securities, and its unique identifier can be a security code.

[0086] Compliance Integration: The system can integrate compliance checks into the ownership verification process. For example, before locking assets, the system will query a compliance database to confirm that the recipient B's address is not on a sanctions list and that the transfer complies with securities laws. Only after passing the check will the request be accepted. This demonstrates the system's flexibility in regulated scenarios.

[0087] Example 4: In this example, the digital asset is a compliant virtual currency. Each asset unit represents a fixed or variable denomination of virtual currency, and its unique asset identifier is a globally unique "check number" within the system.

[0088] The ownership certificate is a cryptographic key (such as the private key used by the elliptic curve digital signature algorithm); owning the ownership certificate means having complete control over the virtual currency.

[0089] Encrypted Content and Log: The encrypted content of the asset unit is stored in plaintext or ciphertext, and it must start with the "check number" itself. Each time ownership is transferred, the system appends a new record to the original content. For example, "Transfer timestamp: <time>, public key hash from owner A: <Hash value>, public key hash to owner B: <Hash value>". This log can only be appended and cannot be deleted or modified, forming a complete life cycle record of the virtual currency.

[0090] When user A wants to pay a virtual currency to user B, the following workflow is involved:

[0091] 1. A submits the "check number" of the virtual currency and a digital signature that can prove its current ownership to the system.

[0092] 2. When the system verifies that the signature is valid and the asset corresponding to the "check number" is not locked, it immediately locks the asset and returns a receipt of "Request Accepted" to A.

[0093] 3. In the next settlement cycle (e.g., 10 minutes later), the system processes the request: invalidates the old asset unit, generates a new asset unit encrypted with the private key controlled by B, and appends the transaction record to the content.

[0094] 4. The ownership transfer is completed, and B becomes the new owner of the virtual currency.

[0095] It should be noted that the above modules can be implemented in the form of a computer program. The computer program can run on a computer device, and the computer program composed of each module can be stored in the memory of the computer device so that the processor can execute each step of the above method.

[0096] It should be understood that although the steps in the flowcharts of the embodiments of the present invention are shown in sequence according to the arrows, these steps do not necessarily need to be executed in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in each embodiment may include multiple sub-steps or multiple stages. These sub-steps or stages do not necessarily need to be executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages does not necessarily need to be sequential, but can be executed alternately or in turn with at least a part of other steps or sub-steps or stages of other steps.

[0097] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory.

[0098] The above embodiments merely illustrate several implementation methods of the present invention, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the present invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these all fall within the protection scope of the present invention. Therefore, the protection scope of this patent should be determined by the appended claims.

Claims

1. A digital asset management method based on asynchronous settlement and ownership lock-in, characterized in that, Includes the following steps: The requesting party receives a request for a change of ownership of the target asset unit; The ownership transfer request includes a unique asset identifier and a primary ownership certificate; Assign a trusted timestamp to the received ownership change request; The order of ownership change requests is determined based on the trusted timestamps, and the ownership verification process begins. Ownership verification process: Verify whether the first ownership certificate matches the current control of the target asset unit, and check whether the target asset unit is in an unlocked state during the current settlement cycle; If the verification is successful and the target asset unit is in an unlocked state, the state of the target asset unit is set to locked, and an acceptance receipt is returned to the requester, thus initiating the asynchronous batch settlement process. Asynchronous batch settlement process: After the scheduled settlement time is reached, all locked target asset units in the current settlement cycle are processed asynchronously in batches. A new asset unit controlled by a second ownership certificate is generated for each locked target asset unit to replace the old asset unit; the locking status of the asset unit is released, and the ownership transfer is completed.

2. The digital asset management method based on asynchronous settlement and ownership locking according to claim 1, characterized in that, Each asset unit represents a digital asset and contains three key attributes: A unique identifier for an asset, used to identify a specific asset; A certificate of ownership is a piece of confidential information and is the sole basis for verifying the legitimacy of ownership. Encrypted content is a piece of content protected by cryptography.

3. The digital asset management method based on asynchronous settlement and ownership locking according to claim 2, characterized in that, The encrypted content begins with the asset's unique identifier, and subsequent appended content includes one or more of the following: an immutable timestamp and transfer records, forming a historical log of the digital asset; the encrypted content is encrypted using the public key currently controlling the asset unit.

4. The digital asset management method based on asynchronous settlement and ownership locking according to claim 1, characterized in that, In the ownership verification process, for the same asset unit within the same settlement period, only the first valid ownership change request that passes verification will be responded to, and subsequent ownership change requests will be rejected.

5. The digital asset management method based on asynchronous settlement and ownership locking according to claim 1, characterized in that, The ownership verification process includes a compliance check step before verifying whether the first ownership certificate matches the current control of the target asset unit; the compliance check includes at least one of the following: blacklist check, business rule check, and debtor confirmation.

6. The digital asset management method based on asynchronous settlement and ownership locking according to claim 3, characterized in that, The unique identifier of the new asset unit is consistent with that of the old asset unit. Its encrypted content is based on the encrypted content of the old asset unit, with new transfer records added. The new asset unit is controlled by the second ownership certificate.

7. A digital asset management system based on asynchronous settlement and ownership lock-up, used to implement the digital asset management method based on asynchronous settlement and ownership lock-up as described in any one of claims 1-6, characterized in that, include: The request receiving module is used to receive requests from requesters for changes in ownership of the target asset unit. The ownership transfer request includes a unique asset identifier and a primary ownership certificate; The timestamp service module is used to assign a trusted timestamp to received ownership change requests; The request processing module is used to determine the order of ownership change requests based on the trusted timestamps and to proceed to the ownership verification process; The ownership verification module is used to verify whether the first ownership certificate matches the current control of the target asset unit, and to check whether the target asset unit is in an unlocked state during the current settlement cycle. If the verification is successful and the target asset unit is in an unlocked state, the state of the target asset unit is set to locked, and an acceptance receipt is returned to the requester, thus initiating the asynchronous batch settlement process. The asynchronous batch settlement module is used to asynchronously batch process all locked target asset units in the current settlement cycle after the predetermined settlement time point is reached. It generates a new asset unit controlled by a second ownership certificate for each locked target asset unit to replace the old asset unit; releases the locking status of the asset unit and completes the transfer of ownership.

8. The digital asset management system based on asynchronous settlement and ownership locking according to claim 7, characterized in that, Also includes: The asset registration module is used to register and maintain the status of all asset units.