Methodology for building a platform that integrates digital asset issuance and trading

By receiving and reviewing the asset request data from the issuer, determining the initial lock-up time and data of both parties to the transaction, and calculating the transaction lock-up time, the problem of the disconnect between the issuance review and the transaction system in the digital asset platform is solved, and closed-loop management that is manageable, controllable, and traceable throughout the entire lifecycle is achieved.

CN122492340APending Publication Date: 2026-07-31SHANXI LIANRONG TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
SHANXI LIANRONG TECHNOLOGY CO LTD
Filing Date
2026-04-15
Publication Date
2026-07-31

AI Technical Summary

Technical Problem

Existing digital asset platforms lack comprehensive risk profiles, and the issuance review and trading systems are disconnected, resulting in uncontrollable risks in asset transfer, insufficient compliance and transaction security, and an inability to meet the closed-loop management requirements throughout the entire lifecycle.

Method used

By receiving and reviewing asset issuance request data from issuers, generating request review data, determining the initial lock-up time and data of both parties to the transaction, calculating the transaction lock-up time, and achieving deep linkage between issuance compliance results and transaction risk control, the platform's asset transactions are completed.

Benefits of technology

It has improved the platform's compliance, transaction security, and matching efficiency throughout the entire process, and achieved closed-loop management of digital assets that is manageable, controllable, and traceable throughout their entire lifecycle.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122492340A_ABST
    Figure CN122492340A_ABST
Patent Text Reader

Abstract

This invention provides a platform construction method integrating digital asset issuance and trading, belonging to the field of data processing technology. The method includes: receiving and reviewing asset issuance request data submitted by multiple issuers; generating request review data for each issuer; determining the initial lock time for each asset identifier in the platform identifier set; determining multiple matching transaction orders for each asset identifier in the platform identifier set; determining the transaction tag, the sender's historical asset sending data, and the sender's historical asset receiving data and the receiver's receiving tag for each matching transaction order for each asset identifier; calculating the transaction lock time for each matching transaction order for each asset identifier; and completing the platform asset transaction. This method enables deep linkage between issuance compliance results and transaction risk control, solving the problem of one-size-fits-all risk control, improving the platform's overall compliance, transaction security, and matching efficiency, and achieving closed-loop management of the entire digital asset lifecycle that is manageable, controllable, and traceable.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method for constructing a platform that integrates digital asset issuance and trading. Background Technology

[0002] Early digital asset platforms often consisted of single issuance or trading modules, with issuance review and trading systems completely separated. There was no systematic, end-to-end control over assets after they were listed. As the industry developed, platforms generally adopted a crude management model with fixed lock-up periods, failing to link the compliance review results on the issuance side with the risk control system on the trading side. Existing technology lacks a comprehensive risk profile for both parties in a transaction, and the fixed-duration, crude asset lock-up mechanism cannot adapt to the differentiated risk control needs of different users and assets. This results in a complete disconnect between issuance review and trading control, making asset transfer risks untraceable, and compromising platform compliance and transaction security, thus failing to meet the closed-loop management requirements for the entire lifecycle of digital assets.

[0003] Therefore, this invention provides a method for building a platform that integrates digital asset issuance and trading. Summary of the Invention

[0004] This invention provides a platform construction method integrating digital asset issuance and trading. It receives and reviews asset issuance request data submitted by multiple issuers, generates request review data for each issuer, determines the initial lock time for each asset identifier in the platform identifier set, obtains transaction data for each asset identifier, identifies multiple matching transaction orders for each asset identifier, determines the transaction tag, the sender's historical asset sending data and sending tag, and the receiver's historical asset receiving data and receiving tag for each matching transaction order of each asset identifier, calculates the transaction lock time for each matching transaction order of each asset identifier, and completes the platform asset transaction. This method enables deep linkage between issuance compliance results and transaction risk control, solving problems such as uncontrollable platform asset circulation risks, separation of review and transaction, and one-size-fits-all risk control. It improves the platform's overall compliance, transaction security, and matching efficiency, achieving closed-loop management of the entire digital asset lifecycle that is manageable, controllable, and traceable.

[0005] On the one hand, this invention provides a method for constructing a platform that integrates digital asset issuance and trading, including: Step 1: Receive and review asset issuance request data submitted by multiple issuers, and generate request review data for each issuer. The request review data includes review tags and review result data. Step 2: Based on the review tags in the request review data of each issuer, determine the initial lock time of each asset identifier in the platform identifier set, obtain the transaction data of each asset identifier in the platform identifier set, and determine multiple matching transaction orders for each asset identifier in the platform identifier set; Step 3: Based on each matching transaction order for each asset identifier in the platform identifier set, determine the transaction tag, the sender's historical asset sending data, the sending tag, and the receiver's historical asset receiving data and the receiving tag for each matching transaction order for each asset identifier; Step 4: Based on the initial lock time of each asset identifier in the platform identifier set and the historical asset sending data, sending tags of the sender, and the historical asset receiving data and receiving tags of the receiver for each matching transaction order, calculate the transaction lock time for each matching transaction order for each asset identifier; Step 5: Complete the platform asset transaction based on all matching transaction orders for all asset identifiers and the transaction lock-up time for each matching transaction order.

[0006] According to the platform construction method for integrating digital asset issuance and trading provided by the present invention, step 1 includes: It receives asset issuance request data submitted by multiple issuers, conducts compliance review on the asset issuance request data submitted by each issuer, and generates request review data for each issuer, where the review labels include pass and fail; If the review label is approved, the review result data includes asset identification, asset type, issuer information, initial issuance volume, issuance time, real asset information, and initial holding identification; If the review label is rejected, the review result data includes the reason for rejection, the basis for rejection, and adjustment suggestions.

[0007] According to the platform construction method for integrating digital asset issuance and trading provided by the present invention, step 2 includes: If the review tag in the review request data of the issuing entity is "not approved", the review result data in the review request data will be sent to the issuing entity; If the review label in the issuer's request review data is approved, obtain the asset flow data of the initial holding label in the corresponding review result data, and at the same time, obtain the label regulatory data of the asset label in the corresponding review result data; Based on the asset identifiers of all issuers whose review tags have passed, determine the platform identifier set; Based on each issuer's asset identifier, asset type, asset identifier regulatory data, and initial holding asset flow data, the initial lock-up time for each asset identifier in the platform's identifier set is determined. Obtain the transaction data of each asset identifier in the platform identifier set. The transaction data includes the asset holding identifiers and sending demand data of multiple senders, as well as the asset receiving identifiers and receiving demand data of multiple receivers. Based on the order matching engine, the transaction data of each asset identifier in the platform identifier set is matched to determine multiple matching transaction orders for each asset identifier in the platform identifier set. The matching transaction order includes the sender's asset holding identifier, the receiver's asset receiving identifier, the transaction quantity, and the transaction price.

[0008] According to the platform construction method for integrating digital asset issuance and trading provided by the present invention, step 3 includes: The system determines the initial holding identifier in the review result data of the request review data corresponding to each asset identifier in the platform identifier set and the asset holding identifier of the sender of each matching transaction order. If the initial holding identifier and the asset holding identifier are the same, the transaction tag of the sender of the matching transaction order of the asset identifier is determined to be a first-level transaction. If the initial holding identifier and the asset holding identifier are different, the transaction tag of the sender of the matching transaction order of the asset identifier is determined to be a second-level transaction. Based on each asset identifier in the platform identifier set, the asset type of the asset identifier, the asset holding identifier of the sender of each matching transaction order, and the transaction tag, the historical asset sending data of the sender of each matching transaction order for each asset identifier in the platform identifier set is obtained, and the sending tag of the sender of each matching transaction order for each asset identifier in the platform identifier set is determined. Based on each asset identifier in the platform identifier set, the asset type of the asset identifier, the asset receiving identifier of the recipient of each matched transaction order, and the transaction tag, the historical asset receiving data of the recipient of each matched transaction order for each asset identifier in the platform identifier set is obtained, and the receiving tag of the recipient of each matched transaction order for each asset identifier in the platform identifier set is determined.

[0009] According to the platform construction method for integrating digital asset issuance and trading provided by the present invention, step 3 further includes: Obtain the sender asset transaction set of each matching transaction order for each asset identifier in the platform identifier set, wherein the sender asset transaction set includes asset identifiers and asset types from multiple historical transactions; Determine whether the sender's asset transaction set of the matching transaction order for the asset identifier contains the asset identifier, and determine the first determination result of the recipient of the matching transaction order for the asset identifier; If the transaction tag of the sender of the matching transaction order of the asset identifier is a first-level transaction, and the first judgment result of the sender of the matching transaction order of the asset identifier is not included, and the historical asset sending data of the sender of the matching transaction order of the asset identifier is empty, then the sending tag of the sender of each matching transaction order of each asset identifier in the platform identifier set is determined to be not sent. If the transaction tag of the sender of the matching transaction order of the asset identifier is a first-level transaction, and the first judgment result of the sender of the matching transaction order of the asset identifier is inclusion, the historical asset sending data of the sender of the matching transaction order of the asset identifier includes the type identifier data of all asset identifiers corresponding to the asset type of the asset identifier, and the sending tag of the sender of each matching transaction order of each asset identifier in the platform identifier set is determined to be the first sending, wherein the type identifier data includes real-time holding quantity, change similarity value, first change time, and latest change time; If the transaction tag of the sender of the matching transaction order for an asset identifier is a secondary transaction, the sending asset transaction data of the sender of the matching transaction order for the asset identifier includes the sending identifier holding data of the asset identifier and the type identifier data of all asset identifiers other than the asset identifier corresponding to the asset type of the asset identifier. It is determined that the sending tag of the sender of each matching transaction order for each asset identifier in the platform identifier set is not the first sending. The sending identifier holding data includes the real-time holding quantity, holding change record, first change time, latest change time, and number of transactions. The holding change record includes the change quantity of multiple changes within a specified time period, historical counterparty identifier, historical change time, historical change unit price, and change tag. The change tag includes cross-chain transactions and non-cross-chain transactions.

[0010] According to the platform construction method for integrating digital asset issuance and trading provided by the present invention, step 3 further includes: Obtain the recipient asset transaction set for each matching transaction order for each asset identifier in the platform identifier set, wherein the recipient asset transaction set includes asset identifiers and asset types from multiple historical transactions; Determine whether the recipient's asset transaction set of the matching transaction order for the asset identifier contains the asset identifier, and determine the second determination result of the recipient of the matching transaction order for the asset identifier. At the same time, determine whether the recipient's asset transaction set contains the asset type of the asset identifier, and determine the third determination result of the recipient of the matching transaction order for the asset identifier. If the second judgment result of the recipient of the matching transaction order of the asset identifier is not included and the third judgment result is not included, the received asset transaction data of the recipient of the matching transaction order of the asset identifier is empty, and the receiving tag of the recipient of the matching transaction order of the asset identifier is determined to be not received. If the second judgment result of the recipient of the matching transaction order of the asset identifier is not included and the third judgment result is included, the received asset transaction data of the recipient of the matching transaction order of the asset identifier includes the type identifier data of all asset identifiers corresponding to the asset type, and the receiving tag of the recipient of the matching transaction order of the asset identifier is determined to be the first reception. If the second judgment result of the recipient of the matching transaction order of the asset identifier is inclusive and the third judgment result is inclusive, the received asset transaction data of the recipient of the matching transaction order of the asset identifier includes the receiving identifier holding data of the asset identifier and the type identifier data of all asset identifiers other than the asset identifier corresponding to the asset type. Among them, the receiving identifier holding data includes real-time holding quantity, holding change record, first change time, latest change time, number of transactions, number of purchases, and number of sales. It is determined that the receiving tag of the recipient of the matching transaction order of the asset identifier is not the first time receiving.

[0011] According to the platform construction method for integrating digital asset issuance and trading provided by the present invention, step 4 includes: Obtain the asset transaction data of each asset in the platform identifier set within a specified time period, extract features from the asset transaction data of each asset in the platform identifier set, and determine the asset transaction vector; For each asset identifier in the platform identifier set whose sending tag is a non-first-time sender, feature extraction is performed on the holding change records in the sending identifier holding data of the sending asset transaction data. This determines the change feature vector of each asset identifier in the platform identifier set whose sending tag is a non-first-time sender. For each asset identifier in the platform identifier set, the receiving label is a receiver who is not receiving for the first time. The holding change records in the receiving identifier holding data are extracted to determine the change feature vector of each asset identifier in the platform identifier set whose receiving label is a receiver who is not receiving for the first time. Based on the asset transaction vector of each asset identifier in the platform identifier set, the historical asset sending data of the sender of each matching transaction order, the sending tag, and the change feature vector of the sender whose sending tag is not the first sending, the sending adjustment factor of the sender of each matching transaction order for each asset identifier in the platform identifier set is calculated. Based on the asset transaction vector of each asset identifier in the platform identifier set, the historical asset receiving data of the recipient of each matching transaction order, the receiving tag, and the change feature vector of the recipient whose receiving tag is not the first time receiving, the receiving adjustment factor of the recipient of each matching transaction order of each asset identifier in the platform identifier set is calculated. Based on the initial lock time of each asset identifier in the platform identifier set and the sending adjustment factor of the sender and the receiving adjustment factor of each matching transaction order, the transaction lock time of each matching transaction order for each asset identifier in the platform identifier set is determined.

[0012] According to the platform construction method for integrating digital asset issuance and trading provided by the present invention, step 5 further includes: After the transaction lock time, for each matching transaction order of each asset identifier in the platform identifier set, the asset delivery and fund settlement are executed through smart contract. The result tag of each matching transaction order of each asset identifier in the platform identifier set is determined, and the transaction results of matching transaction orders with the result tag of completion are recorded on the blockchain. The result tag includes completion and incomplete. Based on all result tags of all asset identifiers in the platform identifier set that are incomplete matching transaction orders, the transaction data of both parties for each asset identifier in the platform identifier set are adjusted; Based on the order matching engine, the transaction data of each asset identifier in the adjusted platform identifier set is matched to determine multiple matching adjustment orders for each asset identifier in the platform identifier set. The matching adjustment order includes the sender's asset holding identifier, the receiver's asset receiving identifier, the transaction quantity, and the transaction price. Based on each matching adjustment order for each asset identifier in the platform's identifier set, asset delivery and fund settlement are executed through smart contracts, transferring asset ownership from the sender to the receiver, and recording the transaction results on the blockchain to complete the platform asset transaction.

[0013] Compared with the prior art, the beneficial effects of this application are as follows: By receiving and reviewing asset issuance request data submitted by multiple issuers, the system generates request review data for each issuer, determines the initial lock-up time for each asset identifier in the platform identifier set, obtains transaction data for both parties for each asset identifier in the platform identifier set, identifies multiple matching transaction orders for each asset identifier in the platform identifier set, determines the transaction tag, the sender's historical asset sending data and sending tag, and the receiver's historical asset receiving data and receiving tag for each matching transaction order for each asset identifier, calculates the transaction lock-up time for each matching transaction order for each asset identifier, and completes the platform asset transaction. This system enables deep linkage between issuance compliance results and transaction risk control, solving problems such as uncontrollable platform asset circulation risks, separation of review and transaction, and one-size-fits-all risk control. It improves the platform's overall compliance, transaction security, and matching efficiency, achieving closed-loop management of digital assets throughout their entire lifecycle that is manageable, controllable, and traceable. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0015] Figure 1 This is a flowchart illustrating the platform construction method for integrating digital asset issuance and trading provided in this embodiment of the invention. Detailed Implementation

[0016] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0017] Example 1: This invention provides a method for constructing a platform that integrates digital asset issuance and trading, such as... Figure 1 As shown, it includes: Step 1: Receive and review asset issuance request data submitted by multiple issuers, and generate request review data for each issuer. The request review data includes review tags and review result data. Step 2: Based on the review tags in the request review data of each issuer, determine the initial lock time of each asset identifier in the platform identifier set, obtain the transaction data of each asset identifier in the platform identifier set, and determine multiple matching transaction orders for each asset identifier in the platform identifier set; Step 3: Based on each matching transaction order for each asset identifier in the platform identifier set, determine the transaction tag, the sender's historical asset sending data, the sending tag, and the receiver's historical asset receiving data and the receiving tag for each matching transaction order for each asset identifier; Step 4: Based on the initial lock time of each asset identifier in the platform identifier set and the historical asset sending data, sending tags of the sender, and the historical asset receiving data and receiving tags of the receiver for each matching transaction order, calculate the transaction lock time for each matching transaction order for each asset identifier; Step 5: Complete the platform asset transaction based on all matching transaction orders for all asset identifiers and the transaction lock-up time for each matching transaction order.

[0018] In this embodiment, a unified application receiving port is established to receive asset issuance request data submitted by multiple issuers. Then, according to the preset regulatory rules and platform compliance standards, the authenticity, legality and compliance of each application data are verified item by item. Based on the verification results, corresponding review tags are generated. The review tags are integrated with the complete review conclusion content to finally generate the request review data corresponding to each issuer.

[0019] In this embodiment, the platform first reads the review tags in the review request data of each issuer, and assigns an initial lock-up time to each asset identifier that passes the review according to the risk level and control rules corresponding to the tags. Then, it obtains the transaction data of all potential transaction users under each asset identifier from the platform's transaction system, and matches the needs of the transaction parties according to the preset price priority and time priority matching rules, and finally generates multiple matching transaction orders corresponding to each asset identifier.

[0020] In this embodiment, the platform iterates through each asset identifier in the platform identifier set, then iterates through all matching transaction orders corresponding to that asset identifier, generates a corresponding transaction tag for each order, and then retrieves all historical asset transfer data of the sender in the order, generates a corresponding sending tag based on the historical data, and at the same time retrieves all historical asset transfer data of the receiver in the order, generates a corresponding receiving tag based on the historical data.

[0021] In this embodiment, the platform retrieves the initial lock time of the corresponding asset identifier, then reads the historical asset sending data and sending tags of the sender and the historical asset receiving data and receiving tags of the receiver in the matching transaction order, calculates the sending adjustment factor of the sender and the receiving adjustment factor of the receiver for each matching transaction order of each asset identifier in the platform identifier set, and obtains the transaction lock time corresponding to the matching transaction order by combining the initial lock time, and repeats the calculation of the transaction lock time of all matching transaction orders of all asset identifiers.

[0022] In this embodiment, the platform first collects all matching transaction orders corresponding to all asset identifiers, as well as the transaction lock time corresponding to each order. It then counts and waits for each order according to the corresponding transaction lock time. Within the transaction lock time, the transfer of ownership of the asset from the sender to the receiver is completed. At the same time, the account data of both parties to the transaction and the platform's asset ledger are updated. If the asset delivery and fund settlement are not completed within the transaction lock time, the matching transaction order automatically becomes invalid.

[0023] The beneficial effects of the above technical solution are as follows: By receiving and reviewing asset issuance request data submitted by multiple issuers, request review data for each issuer is generated; the initial lock time for each asset identifier in the platform identifier set is determined; transaction data of both parties for each asset identifier in the platform identifier set is obtained; multiple matching transaction orders for each asset identifier in the platform identifier set are determined; the transaction tag, historical asset sending data and sending tag of the sender, and historical asset receiving data and receiving tag of the receiver for each matching transaction order of each asset identifier are determined; the transaction lock time for each matching transaction order of each asset identifier is calculated; and the platform asset transaction is completed. This enables deep linkage between issuance compliance results and transaction risk control, solving the problems of uncontrollable platform asset circulation risks, separation of review and transaction, and one-size-fits-all risk control. It improves the platform's overall compliance, transaction security, and matching efficiency, achieving closed-loop management of digital assets throughout their entire lifecycle that is manageable, controllable, and traceable.

[0024] Example 2: This invention provides a method for constructing a platform that integrates digital asset issuance and trading. Step 1 includes: It receives asset issuance request data submitted by multiple issuers, conducts compliance review on the asset issuance request data submitted by each issuer, and generates request review data for each issuer, where the review labels include pass and fail; If the review label is approved, the review result data includes asset identification, asset type, issuer information, initial issuance volume, issuance time, real asset information, and initial holding identification; If the review label is rejected, the review result data includes the reason for rejection, the basis for rejection, and adjustment suggestions.

[0025] In this embodiment, the issuer refers to an institution or individual that initiates a digital asset issuance application on the digital asset issuance platform. The asset issuance request data is the complete set of application materials submitted by the issuer to the platform for applying to issue digital assets, including the issuer's qualification information, basic asset information, underlying asset proof, and compliance commitments for the issuance plan. The compliance review is a process by which the platform verifies the authenticity, legality, compliance, and completeness of the issuance application materials item by item according to preset regulatory rules and platform compliance standards. The request review data is a standardized collection of review results generated by the platform for each issuer after completing the compliance review. The review label is a binary classification label used to identify the final conclusion of the compliance review of the issuance application, containing only two categories: passed and failed, used to clearly distinguish the compliance status of the application. The platform first establishes a unified application receiving port to receive asset issuance request data submitted by multiple issuers. It verifies the uniqueness of the entity and asset for each received application data. Then, according to the preset compliance review rules, it performs item-by-item compliance verification on each asset issuance request data. After the verification is completed, it generates a corresponding review tag based on the verification results. Finally, it integrates the review tag with the complete review conclusion content to generate the request review data corresponding to each issuer.

[0026] In this embodiment, the asset identifier is a unique identification code assigned by the platform to approved digital assets, used to uniquely distinguish the digital asset throughout the platform's entire process. The asset type is an asset classification based on the underlying attributes, application scenarios, and circulation rules of the digital asset. The issuer information is the complete compliance qualification information of the approved issuer, used to clarify the responsible party for asset issuance. The initial issuance quantity is the total quantity of the digital asset issued for the first time, serving as the basic basis for asset circulation. The issuance time is the precise time node recorded by the platform when the digital asset passes review and is approved for issuance, used to clarify the time boundary and traceability of asset issuance. The real asset information is the detailed information of the underlying real asset corresponding to the digital asset, used to clarify the value anchor of the digital asset. The initial holding identifier is the marking information used to identify the initial holder of the digital asset after issuance, used to clarify the initial ownership relationship after asset issuance. When the review label is determined to be approved, the platform first generates a unique asset identifier for the digital asset corresponding to the issuance application, then determines the asset's classification attribute based on the application materials and review results, extracts and verifies the complete compliance information of the issuing entity, confirms the initial total issuance amount of the asset, records the precise time of approval for issuance to generate the issuance time, verifies and retains the complete information of the underlying real asset, marks the initial holding entity information of the asset, and finally integrates all the above information to form the review result data corresponding to the approval label.

[0027] In this embodiment, the reason for failure is a clear explanation by the platform of the specific issues that prevented the issuance application from passing the compliance review. This clarifies the specific problems with the application. The basis for failure is the regulatory rules, platform compliance clauses, and specific verified facts upon which the platform bases its decision, clarifying the compliance and factual support for the review conclusion. The adjustment suggestions are the actionable rectification and optimization directions and specific modification recommendations provided by the platform for the non-compliance issues in the application. When the review label is determined to be "failed," the platform first reviews all non-compliance issues discovered during the compliance review process, clarifying the specific issues for each item to form a complete reason for failure. Then, for each non-compliance issue, it matches the corresponding regulatory rules and platform compliance clauses, clarifying the legal and regulatory basis for the failure conclusion. Finally, for each non-compliance issue, it provides specific and actionable adjustment and optimization suggestions based on compliance requirements. All of the above content is then integrated to form the review result data corresponding to the "failed" label.

[0028] The beneficial effects of the above technical solution are as follows: receiving and reviewing asset issuance request data submitted by multiple issuers and generating request review data for each issuer can improve the compliance, transparency and efficiency of issuance review, build a solid compliance foundation for the full life cycle management of digital assets, and ensure that the entire issuance process is manageable, controllable and traceable.

[0029] Example 3: This invention provides a method for constructing a platform that integrates digital asset issuance and trading. Step 2 includes: If the review tag in the review request data of the issuing entity is "not approved", the review result data in the review request data will be sent to the issuing entity; If the review label in the issuer's request review data is approved, obtain the asset flow data of the initial holding label in the corresponding review result data, and at the same time, obtain the label regulatory data of the asset label in the corresponding review result data; Based on the asset identifiers of all issuers whose review tags have passed, determine the platform identifier set; Based on each issuer's asset identifier, asset type, asset identifier regulatory data, and initial holding asset flow data, the initial lock-up time for each asset identifier in the platform's identifier set is determined. Obtain the transaction data of each asset identifier in the platform identifier set. The transaction data includes the asset holding identifiers and sending demand data of multiple senders, as well as the asset receiving identifiers and receiving demand data of multiple receivers. Based on the order matching engine, the transaction data of each asset identifier in the platform identifier set is matched to determine multiple matching transaction orders for each asset identifier in the platform identifier set. The matching transaction order includes the sender's asset holding identifier, the receiver's asset receiving identifier, the transaction quantity, and the transaction price.

[0030] In this embodiment, the request review data of all issuing entities are traversed, the issuing entities with the review tag of "not approved" and their corresponding request review data are filtered out, the review result data in the request review data is extracted, and the complete review result data is sent to the corresponding issuing entity that submitted the issuance application through the platform's preset notification channel.

[0031] In this embodiment, asset flow data refers to the historical transfer records and holding status change data of the digital asset under the name of the entity corresponding to the initial holding identifier. Identifier regulatory data refers to data such as regulatory requirements, risk level control rules, and compliance constraints of the corresponding asset identifier. The process involves iterating through the request review data of all issuing entities, filtering out issuing entities with approved review tags and their corresponding request review data, extracting the initial holding identifier from the review result data, retrieving the full transfer and holding data of the asset under the corresponding entity's name to generate asset flow data, and simultaneously extracting the asset identifier from the review result data, retrieving the corresponding asset's regulatory rules and risk control data to generate identifier regulatory data.

[0032] In this embodiment, the platform identifier set is the total collection of all digital asset identifiers approved for issuance within the platform after compliance review. It serves as the unified management carrier for legally tradable digital assets within the platform. The process involves filtering out all issuing entities with approved review tags, extracting the unique asset identifier for each approved entity's corresponding digital asset, then performing deduplication and secondary compliance verification on all extracted asset identifiers to eliminate invalid or duplicate identifiers. Finally, all verified asset identifiers are integrated and aggregated according to fixed rules to form a complete platform identifier set.

[0033] In this embodiment, the initial lock-up time is the initial freeze duration set by the platform for each compliant digital asset after issuance. This duration controls the tradable time and circulation pace of the asset after its listing, and is positively correlated with the asset's compliance risk level. The platform retrieves the asset type identifier regulatory data and asset flow data corresponding to each asset identifier in its identifier set. This data is then combined with the basic control rules corresponding to the asset type, the risk level and regulatory constraints in the identifier regulatory data, and the historical circulation risks and holding stability in the asset flow data. A comprehensive assessment of the risk level and control requirements corresponding to each asset identifier is conducted, and an initial lock-up time is matched for each asset identifier based on the assessed asset risk level. The higher the risk level, the longer the initial lock-up time.

[0034] In this embodiment, the transaction data consists of real-time acquired data on all transactions involving the transferor and transferee of a compliant digital asset within the platform. The sender refers to the asset holder initiating the transfer intention. The asset holding identifier is a unique marker identifying the sender's ownership of the corresponding digital asset. The transfer request data is the transaction intention data submitted by the sender, including the quantity of the asset to be transferred, the proposed transfer price, and the transfer time. The receiver refers to the asset recipient initiating the transfer-in intention. The asset receiving identifier is a unique marker identifying the receiver's account receiving the corresponding digital asset. The receiving request data is the transaction intention data submitted by the receiver, including the quantity of the asset to be transferred in, the proposed transfer price, and the transfer time. The system retrieves all asset identifiers from the platform's identifier set. For each asset identifier, it extracts relevant data from the platform's trading system for all senders who have submitted transfer-out intentions and relevant data from all receivers who have submitted transfer-in intentions. Then, it integrates and aggregates all sender and receiver data under the same asset identifier to ultimately form the transaction data for each asset identifier.

[0035] In this embodiment, the order matching engine is a built-in algorithm system on the platform that automatically matches the trading intentions of both parties according to preset matching rules. A matched transaction order is an executable and valid transaction contract record generated by the matching engine after the matching is completed. The transaction quantity is the number of digital assets transferred in a single matched transaction. The transaction price is the unit transaction price of the digital asset in a single matched transaction. The order matching engine is activated, and for each asset identifier in the platform's identifier set, it retrieves the data of both parties corresponding to that asset identifier. Then, according to preset price-priority and time-priority matching rules, it automatically matches the sender's sending request data with the receiver's receiving request data. When the core conditions such as price and quantity of the sending and receiving requests match, a corresponding valid transaction record is generated. Simultaneously, the transaction quantity and transaction price of the sender's asset holding identifier and the receiver's asset receiving identifier corresponding to that transaction are recorded, ultimately forming multiple matched transaction orders corresponding to each asset identifier.

[0036] In this embodiment, the order matching engine is the core transaction matching algorithm system built into the platform. Its core principle is to follow the standardized matching rules of price priority and time priority, and to automatically sort and cross-match the valid transaction data of each compliant asset identifier within the platform. First, the seller's sell orders are sorted from low to high according to the declared price, and orders with the same declared price are sorted from early to late according to the order time. At the same time, the receiver's buy orders are sorted from high to low according to the declared price, and orders with the same declared price are sorted from early to late according to the order time. Then, the declared price and tradable quantity of the buyer and seller are verified one by one according to the sorting results. When the receiver's highest declared buy price is greater than or equal to the sender's lowest declared sell price, transaction matching is triggered. The transaction price and transaction quantity are determined according to the rules, and a matching adjustment order containing the transaction quantity and transaction price of the corresponding identifiers of the two parties is generated. The remaining tradable quantity and account status of the two parties are updated synchronously until there are no valid orders that meet the matching conditions.

[0037] The beneficial effects of the above technical solution are: determining the initial locking time of each asset identifier in the platform identifier set, obtaining the transaction data of each asset identifier in the platform identifier set, and determining multiple matching transaction orders for each asset identifier in the platform identifier set, which can improve the platform's overall compliance, transaction matching efficiency, and risk control capabilities.

[0038] Example 4: This invention provides a method for constructing a platform that integrates digital asset issuance and trading. Step 3 includes: The system determines the initial holding identifier in the review result data of the request review data corresponding to each asset identifier in the platform identifier set and the asset holding identifier of the sender of each matching transaction order. If the initial holding identifier and the asset holding identifier are the same, the transaction tag of the sender of the matching transaction order of the asset identifier is determined to be a first-level transaction. If the initial holding identifier and the asset holding identifier are different, the transaction tag of the sender of the matching transaction order of the asset identifier is determined to be a second-level transaction. Based on each asset identifier in the platform identifier set, the asset type of the asset identifier, the asset holding identifier of the sender of each matching transaction order, and the transaction tag, the historical asset sending data of the sender of each matching transaction order for each asset identifier in the platform identifier set is obtained, and the sending tag of the sender of each matching transaction order for each asset identifier in the platform identifier set is determined. Based on each asset identifier in the platform identifier set, the asset type of the asset identifier, the asset receiving identifier of the recipient of each matched transaction order, and the transaction tag, the historical asset receiving data of the recipient of each matched transaction order for each asset identifier in the platform identifier set is obtained, and the receiving tag of the recipient of each matched transaction order for each asset identifier in the platform identifier set is determined.

[0039] In this embodiment, a primary transaction refers to the first circulation transaction directly conducted by the digital asset issuer. A secondary transaction refers to a circulation transaction between users who are not issuers. The process iterates through each asset identifier in the platform identifier set, retrieves the review result data from the request review data corresponding to that asset identifier, extracts the initial holding identifier, then iterates through all matching transaction orders corresponding to that asset identifier, extracts the asset holding identifier of the sender in each order, and compares the initial holding identifier and the asset holding identifier corresponding to the same order for consistency. When the two identifiers are completely identical, the transaction tag of the order sender is determined as a primary transaction; when the two identifiers are different, the transaction tag of the order sender is determined as a secondary transaction.

[0040] The beneficial effects of the above technical solution are as follows: Based on each matching transaction order of each asset identifier in the platform identifier set, the transaction tag, the sender's historical asset sending data, the sending tag, and the receiver's historical asset receiving data and the receiving tag of each matching transaction order of each asset identifier can be determined. This enables hierarchical control of digital assets from issuance to circulation, improves the accuracy, compliance and traceability of transaction risk control, and lays a solid core foundation for differentiated transaction control.

[0041] Example 5: This invention provides a method for constructing a platform that integrates digital asset issuance and trading. Step 3 further includes: Obtain the sender asset transaction set of each matching transaction order for each asset identifier in the platform identifier set, wherein the sender asset transaction set includes asset identifiers and asset types from multiple historical transactions; Determine whether the sender's asset transaction set of the matching transaction order for the asset identifier contains the asset identifier, and determine the first determination result of the recipient of the matching transaction order for the asset identifier; If the transaction tag of the sender of the matching transaction order of the asset identifier is a first-level transaction, and the first judgment result of the sender of the matching transaction order of the asset identifier is not included, and the historical asset sending data of the sender of the matching transaction order of the asset identifier is empty, then the sending tag of the sender of each matching transaction order of each asset identifier in the platform identifier set is determined to be not sent. If the transaction tag of the sender of the matching transaction order of the asset identifier is a first-level transaction, and the first judgment result of the sender of the matching transaction order of the asset identifier is inclusion, the historical asset sending data of the sender of the matching transaction order of the asset identifier includes the type identifier data of all asset identifiers corresponding to the asset type of the asset identifier, and the sending tag of the sender of each matching transaction order of each asset identifier in the platform identifier set is determined to be the first sending, wherein the type identifier data includes real-time holding quantity, change similarity value, first change time, and latest change time; If the transaction tag of the sender of the matching transaction order for an asset identifier is a secondary transaction, the sending asset transaction data of the sender of the matching transaction order for the asset identifier includes the sending identifier holding data of the asset identifier and the type identifier data of all asset identifiers other than the asset identifier corresponding to the asset type of the asset identifier. It is determined that the sending tag of the sender of each matching transaction order for each asset identifier in the platform identifier set is not the first sending. The sending identifier holding data includes the real-time holding quantity, holding change record, first change time, latest change time, and number of transactions. The holding change record includes the change quantity of multiple changes within a specified time period, historical counterparty identifier, historical change time, historical change unit price, and change tag. The change tag includes cross-chain transactions and non-cross-chain transactions.

[0042] In this embodiment, each asset identifier in the platform identifier set is traversed, and then all matching transaction orders corresponding to the asset identifier are traversed. The unique identity identifier of the sender in each order is extracted. Using the identity identifier as a filtering condition, the asset identifiers and asset types corresponding to all completed transactions of the sender in the past are retrieved from the platform's historical transaction database. All retrieved information is integrated and collected to finally form the sender's asset transaction set.

[0043] In this embodiment, the first judgment result is a binary judgment result used to identify whether the sender's historical transaction asset set contains the asset identifier corresponding to the current transaction. It includes two categories: inclusion and exclusion. The unique code of the asset identifier corresponding to the current matching transaction order is retrieved, and then the sender's asset transaction set corresponding to the order sender is retrieved. The current asset identifier is compared one by one with all historical asset identifiers in the sender's asset transaction set to determine whether there is a code in the sender's asset transaction set that is completely identical to the current asset identifier. If it exists, the first judgment result is inclusion; if it does not exist, the first judgment result is exclusion. This first judgment result is then associated and bound with the recipient information of the corresponding order, ultimately determining the first judgment result associated with the recipient of the matching transaction order corresponding to the asset identifier.

[0044] In this embodiment, the sending tag is a classification identifier generated based on the sender's historical transaction behavior to identify the status of its asset transfer. "Not sent" is a tag used to identify that the sender has never conducted a transaction of the corresponding asset type. The transaction tag of the sender of the currently matching transaction order is retrieved, and then the first judgment result corresponding to that order is retrieved. If both the transaction tag and the first judgment result are met (both are level one transactions), the historical asset sending data is determined to be empty, and the sending tag of the order sender is determined to be "not sent." This process is repeated to determine the sending tags of matching transaction orders corresponding to all asset identifiers in the platform identifier set.

[0045] In this embodiment, the type identifier data is structured data showing the holding and circulation status of all assets under the corresponding asset type. The real-time holding quantity is the total quantity of the corresponding assets currently held by the sender. The change similarity value is the similarity between the sender's historical change behavior based on the corresponding asset identifier and the transaction change behavior of that asset identifier within a specified time period. The first change time is the precise time node when the sender's corresponding asset first undergoes a circulation operation. The latest change time is the precise time node when the sender's corresponding asset most recently underwent a circulation operation. The initial send is a tag used to identify the first time the issuing entity performs a corresponding asset transfer operation. The transaction tag of the sender of the currently matching transaction order is retrieved, and then the first judgment result corresponding to that order is retrieved. If both the transaction tag and the first judgment result are met (both are level one transactions), it is determined that the historical asset sending data contains all type identifier data of the corresponding asset type, and the sending tag of the order sender is determined as the initial send. This process is repeated to complete the determination of the sending tags for all asset identifiers corresponding to matching transaction orders in the platform identifier set.

[0046] In this embodiment, the sending identifier holding data is structured data of the sending party's corresponding asset holding status and historical transfer details. The holding change record is detailed data of all transfer changes of the sending party's corresponding asset within a specified period. The change quantity is the asset quantity corresponding to a single transfer operation. The historical counterparty identifier is the unique identity identifier of the counterparty in a single transfer operation. The historical change time is the precise time node of a single transfer operation. The historical change unit price is the asset unit transaction price corresponding to a single transfer operation. The change tag is a classification identifier used to identify whether a transfer transaction is a cross-chain operation. A cross-chain transaction refers to an asset transfer transaction occurring between different blockchain networks. A non-cross-chain transaction refers to an asset transfer transaction occurring within the same blockchain network. "Not the first time sending" is a tag used to identify that a user who is not the issuing entity has already performed a corresponding asset transfer operation. The transaction tag of the sending party of the currently matching transaction order is retrieved. When the transaction tag meets the requirement of a second-level transaction, it is determined that the sent asset transaction data includes the sending identifier holding data of the corresponding asset and the type identifier data of other assets of the same type, and the sending tag of the order sending party is determined to be "not the first time sending". The system iterates through all asset identifiers in the platform identifier set to determine the sending tags for matching transaction orders.

[0047] The beneficial effects of the above technical solution are as follows: determining the historical asset sending data and sending tags of the sender for each matching transaction order of each asset identifier in the platform identifier set can improve the accuracy of the sender's risk profile and provide a core basis for differentiated transaction management.

[0048] Example 6: This invention provides a method for constructing a platform that integrates digital asset issuance and trading. Step 3 further includes: Obtain the recipient asset transaction set for each matching transaction order for each asset identifier in the platform identifier set, wherein the recipient asset transaction set includes asset identifiers and asset types from multiple historical transactions; Determine whether the recipient's asset transaction set of the matching transaction order for the asset identifier contains the asset identifier, and determine the second determination result of the recipient of the matching transaction order for the asset identifier. At the same time, determine whether the recipient's asset transaction set contains the asset type of the asset identifier, and determine the third determination result of the recipient of the matching transaction order for the asset identifier. If the second judgment result of the recipient of the matching transaction order of the asset identifier is not included and the third judgment result is not included, the received asset transaction data of the recipient of the matching transaction order of the asset identifier is empty, and the receiving tag of the recipient of the matching transaction order of the asset identifier is determined to be not received. If the second judgment result of the recipient of the matching transaction order of the asset identifier is not included and the third judgment result is included, the received asset transaction data of the recipient of the matching transaction order of the asset identifier includes the type identifier data of all asset identifiers corresponding to the asset type, and the receiving tag of the recipient of the matching transaction order of the asset identifier is determined to be the first reception. If the second judgment result of the recipient of the matching transaction order of the asset identifier is inclusive and the third judgment result is inclusive, the received asset transaction data of the recipient of the matching transaction order of the asset identifier includes the receiving identifier holding data of the asset identifier and the type identifier data of all asset identifiers other than the asset identifier corresponding to the asset type. Among them, the receiving identifier holding data includes real-time holding quantity, holding change record, first change time, latest change time, number of transactions, number of purchases, and number of sales. It is determined that the receiving tag of the recipient of the matching transaction order of the asset identifier is not the first time receiving.

[0049] In this embodiment, each asset identifier in the platform identifier set is traversed, and then all matching transaction orders corresponding to the asset identifier are traversed. The unique identity identifier of the recipient in each order is extracted. Using the identity identifier as a filtering condition, the asset identifiers and asset types corresponding to all completed transactions of the recipient in the past are retrieved from the platform's historical transaction database. All retrieved information is integrated and collected to finally form the recipient's corresponding asset transaction set.

[0050] In this embodiment, the second judgment result is a binary judgment result used to identify whether the recipient's historical transaction asset set contains the asset identifier corresponding to the current transaction, and is divided into two categories: containing and not containing. The third judgment result is a binary judgment result used to identify whether the recipient's historical transaction asset set contains the asset type to which the asset corresponding to the current transaction belongs, and is also divided into two categories: containing and not containing. The unique code and asset type of the asset identifier corresponding to the current matching transaction order are retrieved, and then the recipient's asset transaction set corresponding to the order recipient is retrieved. First, the current asset identifier is compared one by one with all historical asset identifiers in the recipient's asset transaction set, and a second judgment result is generated based on the comparison result. Then, the asset type to which the current asset belongs is compared one by one with all historical asset types in the recipient's asset transaction set, and a third judgment result is generated based on the comparison result. The two judgment results are then associated and bound with the recipient information of the corresponding order.

[0051] In this embodiment, "not received" is a tag used to identify that the recipient has never accessed the current asset or any assets of the same type and has no related historical transaction records. The second and third judgment results corresponding to the recipient of the currently matched transaction order are retrieved. When both the second and third judgment results are met, and the received asset transaction data is determined to be empty, the recipient's receiving tag is determined to be "not received." This process is repeated to determine the receiving tags of all matching transaction orders corresponding to all asset identifiers in the platform identifier set.

[0052] In this embodiment, the type identifier data is structured data on the holding and circulation status of all assets under the corresponding asset type. "Initial receipt" is used to identify a recipient who has experience trading similar assets but has never handled the specific asset in the current transaction, and is applying to receive the asset for the first time. The system retrieves the second and third judgment results corresponding to the recipient of the current matching transaction order. When both the second and third judgment results are met ("not included") and the third judgment result is "included"), the received asset transaction data includes all type identifier data of the corresponding asset type, and the recipient's receipt tag is determined as "initial receipt." This process is repeated to determine the receipt tags for all asset identifiers corresponding to matching transaction orders in the platform's identifier set.

[0053] In this embodiment, the receiving identification holding data is the full structured data of the receiving party's holding status and historical transaction details of the corresponding current transaction asset. Real-time holding quantity is the total quantity of the corresponding asset currently held by the receiving party. Holding change record is the detailed data of all transaction changes of the receiving party's corresponding asset within a specified period. First change time is the precise time node when the receiving party's corresponding asset first underwent a transaction. Latest change time is the precise time node when the receiving party's corresponding asset most recently underwent a transaction. Transaction count is the total historical transaction count of the receiving party's corresponding asset. Purchase count is the total historical transfer count of the receiving party's corresponding asset. Sale count is the total historical transfer count of the receiving party's corresponding asset. Non-first-time receipt is used to identify that the receiving party has both experience trading similar assets and historical transaction records for the current asset. This is a tag indicating that the asset is not being received for the first time. Retrieve the second and third judgment results corresponding to the recipient of the current matching transaction order. When both the second and third judgment results are included, it is determined that the received asset transaction data includes the receiving identifier holding data of the corresponding asset and the type identifier data of other assets of the same type. The receiving tag of the order recipient is then determined as not being the first time receiving the asset. The receiving tag determination of the matching transaction order corresponding to all asset identifiers in the platform identifier set is completed in a loop.

[0054] The beneficial effects of the above technical solution are as follows: determining the historical asset receiving data and receiving tags of the recipient of each matching transaction order for each asset identifier in the platform identifier set can improve the accuracy of the recipient's risk profile and provide a core basis for differentiated transaction control and investor suitability management.

[0055] Example 7: This invention provides a method for constructing a platform that integrates digital asset issuance and trading. Step 4 includes: Obtain the asset transaction data of each asset in the platform identifier set within a specified time period, extract features from the asset transaction data of each asset in the platform identifier set, and determine the asset transaction vector; For each asset identifier in the platform identifier set whose sending tag is a non-first-time sender, feature extraction is performed on the holding change records in the sending identifier holding data of the sending asset transaction data. This determines the change feature vector of each asset identifier in the platform identifier set whose sending tag is a non-first-time sender. For each asset identifier in the platform identifier set, the receiving label is a receiver who is not receiving for the first time. The holding change records in the receiving identifier holding data are extracted to determine the change feature vector of each asset identifier in the platform identifier set whose receiving label is a receiver who is not receiving for the first time. Based on the asset transaction vector of each asset identifier in the platform identifier set, the historical asset sending data of the sender of each matching transaction order, the sending tag, and the change feature vector of the sender whose sending tag is not the first sending, the sending adjustment factor of the sender of each matching transaction order for each asset identifier in the platform identifier set is calculated. Based on the asset transaction vector of each asset identifier in the platform identifier set, the historical asset receiving data of the recipient of each matching transaction order, the receiving tag, and the change feature vector of the recipient whose receiving tag is not the first time receiving, the receiving adjustment factor of the recipient of each matching transaction order of each asset identifier in the platform identifier set is calculated. Based on the initial lock time of each asset identifier in the platform identifier set and the sending adjustment factor of the sender and the receiving adjustment factor of each matching transaction order, the transaction lock time of each matching transaction order for each asset identifier in the platform identifier set is determined.

[0056] In this embodiment, the specified time period is a fixed time interval preset by the platform for statistical analysis of asset transaction behavior. Asset identifier transaction data refers to the full transaction flow data of the corresponding asset identifier within the specified time period. The asset transaction vector is a standardized feature vector generated after feature extraction from the asset transaction data, which can be used for quantitative calculation. The platform's preset specified statistical time period is determined, and then each asset identifier in the platform's identifier set is traversed. The full transaction data of each asset identifier within the specified time period is retrieved from the platform's transaction database to form asset identifier transaction data. Then, core transaction features are extracted from the transaction data using preset feature extraction rules. The extracted features are standardized to ultimately generate the asset transaction vector corresponding to each asset identifier.

[0057] In this embodiment, the change feature vector is a standardized feature vector generated after extracting features from the holding change records. It is used to quantify the historical circulation behavior characteristics of the sender. The process involves traversing each asset identifier in the platform identifier set, filtering out all senders whose sending tag in the matching transaction order corresponding to that asset identifier is not the first sending, retrieving the sending asset transaction data of each eligible sender, extracting the sending identifier holding data, further extracting the holding change records, and then extracting the core circulation features from the holding change records using preset feature extraction rules. After standardization, the change feature vector corresponding to each eligible sender is finally generated.

[0058] In this embodiment, the change feature vector is a standardized feature vector generated after extracting features from the holding change records. It is used to quantify the historical circulation behavior characteristics of the recipient. The process involves iterating through each asset identifier in the platform identifier set, filtering out all recipients whose receiving tags in the matching transaction orders corresponding to that asset identifier are not initial recipients, retrieving the received asset transaction data for each eligible recipient, extracting the receiving identifier holding data, further extracting the holding change records, and then extracting core circulation features from the holding change records using preset feature extraction rules, followed by standardization. Finally, a change feature vector is generated for each eligible recipient.

[0059] In this embodiment, the asset transaction vector and change feature vector include transaction frequency, price volatility sensitivity, counterparty concentration, transaction interval variation coefficient, cross-chain transaction ratio, and transaction confirmation lag.

[0060] In this embodiment, based on the asset transaction vector of each asset identifier in the platform identifier set, the historical asset sending data of the sender of each matching transaction order, the sending tag, and the change feature vector of the sender whose sending tag is not the first sending, the sending adjustment factor of the sender of each matching transaction order for each asset identifier in the platform identifier set is calculated. The calculation formula is expressed as follows: ; ; ; ; ; ; ; in, This represents the sending risk factor of the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the first sending risk sub-factor of the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the second sending risk sub-factor of the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the type and experience adjustment factor for the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the type activity adjustment factor for the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the asset transaction vector of the i-th asset identifier in the platform identifier set. This represents the change feature vector of the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the sending tag of the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the real-time holding quantity, first change time, latest change time, and number of transactions in the historical asset sending data of the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the real-time holding quantity, change similarity value, first change time, and latest change time of the k-th type identifier data in the historical asset sending data of the sender of the j-th matching transaction order of the i-th asset identifier in the platform identifier set. This represents the number of type identifier data in the historical asset sending data of the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set, where Tc represents the current time. Indicates the decay half-life of holding experience. Indicates the threshold for the number of mature transactions. This represents the deviation value of the sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set, based on the change of the asset identifier. The sender of the j-th matching transaction order for the i-th asset identifier in the platform identifier set is based on the first weight of the asset identifier.

[0061] In this embodiment, the holding period decays half-life. A value of 90 can be used, which is the threshold for the number of mature transactions. It can take the value 10.

[0062] In this embodiment, based on the asset transaction vector of each asset identifier in the platform identifier set, the historical asset receiving data of the recipient of each matching transaction order, the receiving tag, and the change feature vector of the recipient whose receiving tag is not the first time receiving, the receiving adjustment factor of the recipient of each matching transaction order for each asset identifier in the platform identifier set is calculated. The calculation formula is expressed as follows: ; ; ; ; ; ; ; ; in, This represents the receiving risk factor of the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the first receiving risk sub-factor of the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the second receiving risk sub-factor of the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the type and experience adjustment factor for the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the type activity adjustment factor for the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the asset transaction vector of the i-th asset identifier in the platform identifier set. This represents the change feature vector of the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the receiving tag of the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the real-time holding quantity, first change time, latest change time, number of transactions, number of buys, and number of sells in the historical asset receiving data of the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the real-time holding quantity, change similarity value, first change time, and latest change time of the k-th type identifier data in the historical asset reception data of the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the number of type identifier data in the historical asset reception data of the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the deviation value of the j-th matching transaction order based on the asset identifier of the i-th asset identifier in the platform identifier set. This indicates that the recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set is based on the second weight of the asset identifier. This represents the number of transactions in the j-th matching transaction order for the i-th asset identifier in the platform identifier set. This represents the accumulated value of the j-th matching transaction order based on the i-th asset identifier in the platform identifier set.

[0063] In this embodiment, The recipient of the j-th matching transaction order for the i-th asset identifier in the platform identifier set is determined by a sub-weight based on the amount of the asset identifier held.

[0064] In this embodiment, the transaction lock time is the pre-execution freeze waiting time calculated separately for each matched and valid transaction order. The initial lock time of the corresponding asset identifier is retrieved, followed by the sender's adjustment factor and the receiver's adjustment factor for the matched transaction order. Using the initial lock time as the base value, a weighted adjustment calculation is performed using the two-way adjustment factors to obtain the transaction lock time corresponding to that matched transaction order. This process is repeated iteratively to calculate the transaction lock time for all matched transaction orders corresponding to all asset identifiers in the platform identifier set.

[0065] The beneficial effects of the above technical solution are as follows: Calculating the sender's adjustment factor, receiver's adjustment factor, and transaction lock-up time for each matching transaction order for each asset identifier can enable personalized customization of the lock-up time for each transaction, improve the granularity and accuracy of transaction risk control, realize dynamic compliance management of the entire chain from issuance to circulation, balance transaction efficiency and risk prevention, and comprehensively improve the platform's transaction security and compliance.

[0066] Example 8: This invention provides a method for constructing a platform that integrates digital asset issuance and trading. Step 5 further includes: After the transaction lock time, for each matching transaction order of each asset identifier in the platform identifier set, the asset delivery and fund settlement are executed through smart contract. The result tag of each matching transaction order of each asset identifier in the platform identifier set is determined, and the transaction results of matching transaction orders with the result tag of completion are recorded on the blockchain. The result tag includes completion and incomplete. Based on all result tags of all asset identifiers in the platform identifier set that are incomplete matching transaction orders, the transaction data of both parties for each asset identifier in the platform identifier set are adjusted; Based on the order matching engine, the transaction data of each asset identifier in the adjusted platform identifier set is matched to determine multiple matching adjustment orders for each asset identifier in the platform identifier set. The matching adjustment order includes the sender's asset holding identifier, the receiver's asset receiving identifier, the transaction quantity, and the transaction price. Based on each matching adjustment order for each asset identifier in the platform's identifier set, asset delivery and fund settlement are executed through smart contracts, transferring asset ownership from the sender to the receiver, and recording the transaction results on the blockchain to complete the platform asset transaction.

[0067] In this embodiment, after each matching transaction order corresponding to each compliant asset identifier reaches the preset transaction lock time, the platform automatically calls the deployed smart contract to start the execution process. The smart contract automatically completes the asset ownership transfer operation and related fund settlement and transfer operation of the corresponding order. After the contract execution is completed, a corresponding result label is generated for the matching transaction order based on whether the transfer and settlement are successfully completed. Completion means that the assets and funds have been transferred normally and the record is valid. Incomplete means that the transfer and settlement were not successfully triggered after the expiration or the mid-term verification failed, thereby clarifying the final execution status of each expired order.

[0068] In this embodiment, the transaction lock-up time is the freeze waiting period set for each matched transaction order before transaction execution. The transaction requests and asset shares corresponding to these unsuccessfully settled orders are re-entered into the real-time collected data of both parties. The data of both parties currently collected in real-time for each asset identifier in the platform's identifier set is comprehensively supplemented, restored, and adjusted. The originally valid transfer-out and transfer-in requests of incomplete orders are reinstated into the scope of eligible matching data, restoring the available assets and order quotas of the corresponding participants, thus making unexecuted requests valid matching content again.

[0069] In this embodiment, the matching adjustment order is an executable and valid transaction contract record generated by re-matching the adjusted transaction data. The platform's order matching engine is activated, iterating through each asset identifier in the platform's identifier set, retrieving the complete adjusted transaction data for each asset identifier, and automatically matching the adjusted sender's and receiver's transaction needs according to a preset price-priority and time-priority matching rule. When the core conditions such as transaction price and quantity between the sender and receiver match, a corresponding valid transaction record is generated. Simultaneously, the transaction quantity and price of the matched sender's asset holding identifier and receiver's asset receiving identifier are recorded, ultimately forming multiple matching adjustment orders for each asset identifier.

[0070] In this embodiment, a smart contract is a computer program deployed on the blockchain that can automatically execute preset transaction rules, featuring transparent, tamper-proof, and automatic execution. Asset delivery refers to the transfer of ownership of digital assets from the sender to the receiver. Fund settlement refers to the transfer of funds corresponding to a transaction from the receiver to the sender. The blockchain is a distributed, tamper-proof ledger system used to store the entire transaction process record. It iterates through all matching adjustment orders corresponding to each asset identifier in the platform identifier set, synchronously inputting the core transaction parameters of each matching adjustment order into a smart contract pre-deployed on the blockchain. The smart contract first verifies whether the asset holding status and fund account status of both parties meet the transaction execution conditions. After successful verification, it automatically executes the asset delivery operation, transferring ownership of the corresponding quantity of digital assets from the sender's account to the receiver's account, simultaneously completing the settlement and transfer of the corresponding transaction funds. Then, the complete execution result of the transaction is packaged and written into a blockchain block, completing on-chain notarization, and ultimately completing the entire platform asset transaction process corresponding to the order.

[0071] The beneficial effects of the above technical solution are as follows: Based on all matching transaction orders of all asset identifiers and the transaction lock time of each matching transaction order, the platform asset transaction can be completed. This can solve the problems of platform invalid orders occupying resources, low matching efficiency, high delivery risk, and poor transaction traceability. It can realize closed-loop management of the entire transaction process, improve transaction execution efficiency, security and compliance, and build an integrated transaction system from risk control lock to delivery and settlement.

[0072] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0073] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0074] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for constructing a platform integrating digital asset issuance and trading, characterized in that: include: Step 1: Receive and review asset issuance request data submitted by multiple issuers, and generate request review data for each issuer. The request review data includes review tags and review result data. Step 2: Based on the review tags in the request review data of each issuer, determine the initial lock time of each asset identifier in the platform identifier set, obtain the transaction data of each asset identifier in the platform identifier set, and determine multiple matching transaction orders for each asset identifier in the platform identifier set; Step 3: Based on each matching transaction order for each asset identifier in the platform identifier set, determine the transaction tag, the sender's historical asset sending data, the sending tag, and the receiver's historical asset receiving data and the receiving tag for each matching transaction order for each asset identifier; Step 4: Based on the initial lock time of each asset identifier in the platform identifier set and the historical asset sending data, sending tags of the sender, and the historical asset receiving data and receiving tags of the receiver for each matching transaction order, calculate the transaction lock time for each matching transaction order for each asset identifier; Step 5: Complete the platform asset transaction based on all matching transaction orders for all asset identifiers and the transaction lock-up time for each matching transaction order.

2. The method for constructing a platform integrating digital asset issuance and trading according to claim 1, characterized in that, Step 1 includes: It receives asset issuance request data submitted by multiple issuers, conducts compliance review on the asset issuance request data submitted by each issuer, and generates request review data for each issuer, where the review labels include pass and fail; If the review label is approved, the review result data includes asset identification, asset type, issuer information, initial issuance volume, issuance time, real asset information, and initial holding identification; If the review label is rejected, the review result data includes the reason for rejection, the basis for rejection, and adjustment suggestions.

3. The method for constructing a platform integrating digital asset issuance and trading according to claim 1, characterized in that, Step 2 includes: If the review tag in the review request data of the issuing entity is "not approved", the review result data in the review request data will be sent to the issuing entity; If the review label in the issuer's request review data is approved, obtain the asset flow data of the initial holding label in the corresponding review result data, and at the same time, obtain the label regulatory data of the asset label in the corresponding review result data; Based on the asset identifiers of all issuers whose review tags have passed, determine the platform identifier set; Based on each issuer's asset identifier, asset type, asset identifier regulatory data, and initial holding asset flow data, the initial lock-up time for each asset identifier in the platform's identifier set is determined. Obtain the transaction data of each asset identifier in the platform identifier set. The transaction data includes the asset holding identifiers and sending demand data of multiple senders, as well as the asset receiving identifiers and receiving demand data of multiple receivers. Based on the order matching engine, the transaction data of each asset identifier in the platform identifier set is matched to determine multiple matching transaction orders for each asset identifier in the platform identifier set. The matching transaction order includes the sender's asset holding identifier, the receiver's asset receiving identifier, the transaction quantity, and the transaction price.

4. The method for constructing a platform integrating digital asset issuance and trading according to claim 3, characterized in that, Step 3 includes: The system determines the initial holding identifier in the review result data of the request review data corresponding to each asset identifier in the platform identifier set and the asset holding identifier of the sender of each matching transaction order. If the initial holding identifier and the asset holding identifier are the same, the transaction tag of the sender of the matching transaction order of the asset identifier is determined to be a first-level transaction. If the initial holding identifier and the asset holding identifier are different, the transaction tag of the sender of the matching transaction order of the asset identifier is determined to be a second-level transaction. Based on each asset identifier in the platform identifier set, the asset type of the asset identifier, the asset holding identifier of the sender of each matching transaction order, and the transaction tag, the historical asset sending data of the sender of each matching transaction order for each asset identifier in the platform identifier set is obtained, and the sending tag of the sender of each matching transaction order for each asset identifier in the platform identifier set is determined. Based on each asset identifier in the platform identifier set, the asset type of the asset identifier, the asset receiving identifier of the recipient of each matched transaction order, and the transaction tag, the historical asset receiving data of the recipient of each matched transaction order for each asset identifier in the platform identifier set is obtained, and the receiving tag of the recipient of each matched transaction order for each asset identifier in the platform identifier set is determined.

5. The method for constructing a platform integrating digital asset issuance and trading according to claim 4, characterized in that, Step 3 also includes: Obtain the sender asset transaction set of each matching transaction order for each asset identifier in the platform identifier set, wherein the sender asset transaction set includes asset identifiers and asset types from multiple historical transactions; Determine whether the sender's asset transaction set of the matching transaction order for the asset identifier contains the asset identifier, and determine the first determination result of the recipient of the matching transaction order for the asset identifier; If the transaction tag of the sender of the matching transaction order of the asset identifier is a first-level transaction, and the first judgment result of the sender of the matching transaction order of the asset identifier is not included, and the historical asset sending data of the sender of the matching transaction order of the asset identifier is empty, then the sending tag of the sender of each matching transaction order of each asset identifier in the platform identifier set is determined to be not sent. If the transaction tag of the sender of the matching transaction order of the asset identifier is a first-level transaction, and the first judgment result of the sender of the matching transaction order of the asset identifier is inclusion, the historical asset sending data of the sender of the matching transaction order of the asset identifier includes the type identifier data of all asset identifiers corresponding to the asset type of the asset identifier, and the sending tag of the sender of each matching transaction order of each asset identifier in the platform identifier set is determined to be the first sending, wherein the type identifier data includes real-time holding quantity, change similarity value, first change time, and latest change time; If the transaction tag of the sender of the matching transaction order for an asset identifier is a secondary transaction, the sending asset transaction data of the sender of the matching transaction order for the asset identifier includes the sending identifier holding data of the asset identifier and the type identifier data of all asset identifiers other than the asset identifier corresponding to the asset type of the asset identifier. It is determined that the sending tag of the sender of each matching transaction order for each asset identifier in the platform identifier set is not the first sending. The sending identifier holding data includes the real-time holding quantity, holding change record, first change time, latest change time, and number of transactions. The holding change record includes the change quantity of multiple changes within a specified time period, historical counterparty identifier, historical change time, historical change unit price, and change tag. The change tag includes cross-chain transactions and non-cross-chain transactions.

6. The method for constructing a platform integrating digital asset issuance and trading according to claim 4, characterized in that, Step 3 also includes: Obtain the recipient asset transaction set for each matching transaction order for each asset identifier in the platform identifier set, wherein the recipient asset transaction set includes asset identifiers and asset types from multiple historical transactions; Determine whether the recipient's asset transaction set of the matching transaction order for the asset identifier contains the asset identifier, and determine the second determination result of the recipient of the matching transaction order for the asset identifier. At the same time, determine whether the recipient's asset transaction set contains the asset type of the asset identifier, and determine the third determination result of the recipient of the matching transaction order for the asset identifier. If the second judgment result of the recipient of the matching transaction order of the asset identifier is not included and the third judgment result is not included, the received asset transaction data of the recipient of the matching transaction order of the asset identifier is empty, and the receiving tag of the recipient of the matching transaction order of the asset identifier is determined to be not received. If the second judgment result of the recipient of the matching transaction order of the asset identifier is not included and the third judgment result is included, the received asset transaction data of the recipient of the matching transaction order of the asset identifier includes the type identifier data of all asset identifiers corresponding to the asset type, and the receiving tag of the recipient of the matching transaction order of the asset identifier is determined to be the first reception. If the second judgment result of the recipient of the matching transaction order of the asset identifier is inclusive and the third judgment result is inclusive, the received asset transaction data of the recipient of the matching transaction order of the asset identifier includes the receiving identifier holding data of the asset identifier and the type identifier data of all asset identifiers other than the asset identifier corresponding to the asset type. Among them, the receiving identifier holding data includes real-time holding quantity, holding change record, first change time, latest change time, number of transactions, number of purchases, and number of sales. It is determined that the receiving tag of the recipient of the matching transaction order of the asset identifier is not the first time receiving.

7. The method for constructing a platform integrating digital asset issuance and trading according to claim 4, characterized in that, Step 4 includes: Obtain the asset transaction data of each asset in the platform identifier set within a specified time period, extract features from the asset transaction data of each asset in the platform identifier set, and determine the asset transaction vector; For each asset identifier in the platform identifier set whose sending tag is a non-first-time sender, feature extraction is performed on the holding change records in the sending identifier holding data of the sending asset transaction data. This determines the change feature vector of each asset identifier in the platform identifier set whose sending tag is a non-first-time sender. For each asset identifier in the platform identifier set, the receiving label is a receiver who is not receiving for the first time. The holding change records in the receiving identifier holding data are extracted to determine the change feature vector of each asset identifier in the platform identifier set whose receiving label is a receiver who is not receiving for the first time. Based on the asset transaction vector of each asset identifier in the platform identifier set, the historical asset sending data of the sender of each matching transaction order, the sending tag, and the change feature vector of the sender whose sending tag is not the first sending, the sending adjustment factor of the sender of each matching transaction order for each asset identifier in the platform identifier set is calculated. Based on the asset transaction vector of each asset identifier in the platform identifier set, the historical asset receiving data of the recipient of each matching transaction order, the receiving tag, and the change feature vector of the recipient whose receiving tag is not the first time receiving, the receiving adjustment factor of the recipient of each matching transaction order of each asset identifier in the platform identifier set is calculated. Based on the initial lock time of each asset identifier in the platform identifier set and the sending adjustment factor of the sender and the receiving adjustment factor of each matching transaction order, the transaction lock time of each matching transaction order for each asset identifier in the platform identifier set is determined.

8. The method for constructing a platform integrating digital asset issuance and trading according to claim 1, characterized in that, Step 5 also includes: After the transaction lock time, for each matching transaction order of each asset identifier in the platform identifier set, the asset delivery and fund settlement are executed through smart contract. The result tag of each matching transaction order of each asset identifier in the platform identifier set is determined, and the transaction results of matching transaction orders with the result tag of completion are recorded on the blockchain. The result tag includes completion and incomplete. Based on all result tags of all asset identifiers in the platform identifier set that are incomplete matching transaction orders, the transaction data of both parties for each asset identifier in the platform identifier set are adjusted; Based on the order matching engine, the transaction data of each asset identifier in the adjusted platform identifier set is matched to determine multiple matching adjustment orders for each asset identifier in the platform identifier set. The matching adjustment order includes the sender's asset holding identifier, the receiver's asset receiving identifier, the transaction quantity, and the transaction price. Based on each matching adjustment order for each asset identifier in the platform's identifier set, asset delivery and fund settlement are executed through smart contracts, transferring asset ownership from the sender to the receiver, and recording the transaction results on the blockchain to complete the platform asset transaction.