A token transaction control system, method, apparatus, device, product and medium
Patent Information
- Application Number
- CN202610741068.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-05-27
- Publication Date
- 2026-08-28
AI Technical Summary
[0006]本申请的目的在于提供一种通证交易控制系统、方法、装置、设备、产品及介质,以解决现有RWA交易平台存在信任机制不健全和决策机制僵化的问题
本申请实施例的通证交易控制系统,首先,通过第一智能体引入N个签名主体的双管道签名验证机制,相较于传统的中心化单点授权,能够实现数据要素的分布式确权与防篡改存证,完善了信任机制,解决了现有RWA平台验证效率低的问题,从源头保障了资产上链的真实性;其次,通过第二智能体与智能合约协同,实现了先认证、后发行的机制,仅在多重签名验证通过后执行通证铸造,有效杜绝了非法或权属不清资产流入市场,提升了RWA资产发行的合规性;最后,通过第三智能体实现了RWA通证的合规验证与挂单数量的动态管理,在确保交易合法性的前提下,通过实时监控买卖数量比(市场情绪指标),自适应第调节订单簿挂单量,这种机制能够根据市场深度动态收窄买卖价差,解决了决策机制僵化的问题。
Smart Images

Figure CN122656757A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of blockchain technology, specifically to a token transaction control system, method, apparatus, equipment, product, and medium. Background Technology
[0002] Real-world assets (RWA) tokens are a financial innovation model that has emerged in recent years. They use blockchain technology to transform physical assets into on-chain digital rights, giving data elements the ability to be tokenized, traded, split, and circulated. RWAs differ fundamentally from stablecoins: the former are certificates of asset ownership, while the latter are vehicles for stable value.
[0003] Artificial intelligence (AI) agents are intelligent entities that can perceive the environment, make autonomous decisions, and execute actions to achieve specific goals. They possess core characteristics such as autonomy, responsiveness, goal orientation, and learning ability. They are typically composed of four parts: a large language model (LLM), a memory module, planning ability, and tool use, forming a collaborative system of "brain + hands and feet + tools".
[0004] Currently, there is an RWA trading platform with a built-in strict compliance framework that supports dynamic liquidity pools and off-chain asset custody, ensuring compliance and security. This RWA trading platform can use blockchain technology to transform physical assets such as real estate, bonds, and artworks into tradable digital tokens, significantly improving asset liquidity and lowering the investment threshold.
[0005] However, the existing RWA trading platform suffers from an inadequate trust mechanism and a rigid decision-making process. Summary of the Invention
[0006] The purpose of this application is to provide a token trading control system, method, device, equipment, product and medium to solve the problems of unsound trust mechanism and rigid decision-making mechanism in the existing RWA trading platform.
[0007] One embodiment of this application provides a token transaction control system, including: The first intelligent agent is used to verify the validity of the dual-channel signatures of N signature subjects of the data element, and write the data element into the blockchain if each dual-channel signature is successfully verified. The dual-channel signature corresponds one-to-one with the signature subject. The dual-channel signature is a digital signature with dual parameters generated by the signature subject for the data element, where N is an integer greater than 2. A second intelligent agent is used to mint the real-world asset RWA token of the data elements through smart contracts; A third intelligent agent is used to invoke the smart contract to perform compliance verification on the RWA token. If the RWA token verification is successful, the agent dynamically adjusts the number of orders placed for the RWA token based on the buy-sell ratio. The buy-sell ratio includes the ratio of buy orders to sell orders, or the ratio of sell orders to buy orders.
[0008] One embodiment of this application provides a token transaction control method applied to a terminal, including: Perform dual-pipe signature on the data element to obtain the dual-pipe signature of the signature body of the data element, wherein the dual-pipe signature corresponds one-to-one with the signature body, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature body corresponding to the dual-pipe signature for the data element; Send the data element on-chain request information to the first intelligent agent. The on-chain request information includes the dual-pipe signatures of N signature subjects of the data element, where N is an integer greater than 2.
[0009] Optionally, the step of performing dual-pipe signing on the data elements to obtain the dual-pipe signature of the signing body of the data elements includes: Perform a hash operation on the data elements to obtain a first hash value; Perform a modulo operation on the first hash value to obtain the second value; The first parameter value is determined based on the first private key of the signing subject and the first preset elliptic curve; Get random numbers; The second parameter value is determined based on the first private key, the second value, the first parameter value, and the random number; The first parameter value and the second parameter value are determined as the signature of the data element in a dual-pipe signature.
[0010] Optionally, the method further includes: Based on the second private key of the signing subject, an authorization signature for the project release information of the data element is generated. The second private key is a randomly generated integer, and the authorization signature is used to represent the authorization of the signing subject for the project release information.
[0011] One embodiment of this application provides a token transaction control method, applied to a first intelligent agent, comprising: Receive the on-chain request information for data elements sent by the receiving terminal; Based on the on-chain request information, obtain the dual-pipe signatures of N signature subjects of the data element, wherein the dual-pipe signature corresponds one-to-one with the signature subject, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature subject for the data element, where N is an integer greater than 2; Validate the validity of each of the dual-pipe signatures. If each of the aforementioned dual-channel signatures is successfully verified, the data element is written into the blockchain; Send data element compliance information to the second intelligent agent, the data element compliance information being used to indicate that the data element is compliant.
[0012] Optionally, the validity verification of each of the dual-pipe signatures includes: Obtain the first public key of the signing subject corresponding to the dual-pipe signature; Perform a hash operation on the data elements to obtain a second hash value; Perform a modulo operation on the second hash value to obtain the first value; The first coefficient and the second coefficient are determined based on the first value and the first and second parameter values of the dual-pipe signature; The X coordinate of the target point is determined based on the first coefficient, the first preset elliptic curve, the second coefficient, and the first public key. If the X coordinate of the target point is the same as the first parameter value, the dual-pipe signature verification is deemed successful.
[0013] One embodiment of this application provides a token transaction control method, applied to a second intelligent agent, comprising: Receive data element compliance information sent by a first intelligent agent, wherein the data element compliance information is used to indicate that the data element is compliant; Obtain N authorized signatures of the project issuance information of the data element, wherein each authorized signature corresponds one-to-one with the signature subject of the data element, and the authorized signature is: a digital signature generated by the signature subject for the project issuance information, where N is an integer greater than 2; Generate a joint signature based on the N authorized signatures; Through a smart contract, based on the project issuance information, the joint signature, and the second public keys of N signing entities, an RWA token for the data element is minted. The second public key is generated based on the second private key of the signing entity and a second preset elliptic curve. The second private key is a randomly generated integer. Send token issuance information to a third-party intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token.
[0014] One embodiment of this application provides a token transaction control method applied to a third-party intelligent agent, comprising: Receive token issuance information sent by a second intelligent agent, wherein the token issuance information is used to indicate that the RWA token of the data element has been minted, and the token issuance information includes the identity identifier of the RWA token; Based on the identity identifier of the RWA token, the smart contract is invoked to perform compliance verification on the RWA token; If the RWA token is successfully verified, the number of orders for the RWA token is dynamically adjusted according to the buy-sell ratio of the RWA token. The buy-sell ratio includes the ratio of the number of buy orders to the number of sell orders, or the ratio of the number of sell orders to the number of buy orders.
[0015] Optionally, dynamically adjusting the order quantity of the RWA token based on the buy-sell ratio of the RWA token includes at least one of the following: If the ratio of the number of buy orders to the number of sell orders is greater than or equal to a first threshold, a first number of sell orders are added every preset time interval until the ratio of the number of buy orders to the number of sell orders is less than the first threshold, wherein the first number is the product of the difference between the number of buy orders and the number of sell orders and a first preset ratio. If the ratio of the number of sell orders to the number of buy orders is greater than or equal to a second threshold, a second number of sell orders are added every preset time interval until the ratio of the number of sell orders to the number of buy orders is less than the second threshold. The second number is the product of the difference between the number of sell orders and the number of buy orders and a second preset ratio.
[0016] One embodiment of this application also provides a token transaction control device applied to a terminal, the device comprising: The first signature module is used to perform dual-pipe signature on data elements to obtain the dual-pipe signature of the signature body of the data elements, wherein the dual-pipe signature corresponds one-to-one with the signature body, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature body corresponding to the dual-pipe signature for the data elements. The first sending module is used to send the on-chain request information of the data element to the first intelligent agent. The on-chain request information includes the dual-pipe signature of N signature subjects of the data element, where N is an integer greater than 2.
[0017] One embodiment of this application also provides a token transaction control device, applied to a first intelligent agent, the device comprising: The first receiving module is used to receive the data element uplink request information sent by the terminal; The first acquisition module is used to acquire the dual-pipe signatures of N signature subjects of the data element according to the on-chain request information, wherein the dual-pipe signature corresponds one-to-one with the signature subject, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature subject for the data element, where N is an integer greater than 2; The first verification module is used to verify the validity of each of the dual-pipe signatures. The first processing module is used to write the data element into the blockchain if each of the dual-pipe signatures is successfully verified. The second sending module is used to send data element compliance information to the second intelligent agent, wherein the data element compliance information is used to indicate that the data element is compliant.
[0018] One embodiment of this application also provides a token transaction control device applied to a second intelligent agent, the device comprising: The second receiving module is used to receive data element compliance information sent by the first intelligent agent, wherein the data element compliance information is used to indicate that the data element is compliant. The second acquisition module is used to acquire N authorized signatures of the project issuance information of the data element, wherein the authorized signature corresponds one-to-one with the signature subject of the data element, and the authorized signature is: a digital signature generated by the signature subject for the project issuance information, where N is an integer greater than 2; The second signature module is used to generate a joint signature based on the N authorized signatures; The token minting module is used to mint RWA tokens of the data elements through smart contracts, based on the project issuance information, the joint signature, and the second public keys of N signing entities. The second public key is generated based on the second private key of the signing entity and a second preset elliptic curve. The second private key is a randomly generated integer. The token issuance module is used to send token issuance information to a third-party intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token.
[0019] One embodiment of this application also provides a token transaction control device applied to a third intelligent agent, the device comprising: The third receiving module is used to receive token issuance information sent by the second intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token. The second verification module is used to call a smart contract based on the identity identifier of the RWA token to perform compliance verification on the RWA token. The order book adjustment module is used to dynamically adjust the number of orders for the RWA token based on the buy-sell ratio when the RWA token is successfully verified. The buy-sell ratio includes the ratio of buy orders to sell orders, or the ratio of sell orders to buy orders.
[0020] One embodiment of this application also provides a device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the token transaction control method applied to a terminal as described above, or implements the token transaction control method applied to a first intelligent agent as described above, or implements the token transaction control method applied to a second intelligent agent as described above, or implements the token transaction control method applied to a third intelligent agent as described above.
[0021] One embodiment of this application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the steps of the token transaction control method applied to a terminal as described above, or implement the steps of the token transaction control method applied to a first intelligent agent as described above, or implement the steps of the token transaction control method applied to a second intelligent agent as described above, or implement the steps of the token transaction control method applied to a third intelligent agent as described above.
[0022] One embodiment of this application also provides a readable storage medium, wherein a program is stored on the readable storage medium, and when the program is executed by a processor, it implements the steps in the token transaction control method applied to a terminal as described above, or implements the steps in the token transaction control method applied to a first intelligent agent as described above, or implements the steps in the token transaction control method applied to a second intelligent agent as described above, or implements the steps in the token transaction control method applied to a third intelligent agent as described above.
[0023] At least one of the above-mentioned technical solutions of this application has the following beneficial effects: The token trading control system of this application firstly introduces a dual-channel signature verification mechanism with N signing entities through a first intelligent agent. Compared with the traditional centralized single-point authorization, this mechanism enables distributed ownership confirmation and tamper-proof evidence storage of data elements, improves the trust mechanism, and solves the problem of low verification efficiency in existing RWA platforms, ensuring the authenticity of assets on the chain from the source. Secondly, through the collaboration of a second intelligent agent and smart contracts, a mechanism of authentication before issuance is implemented. Token minting is only executed after multi-signature verification is passed, effectively preventing illegal or unclear assets from entering the market and improving the compliance of RWA asset issuance. Finally, through a third intelligent agent, the compliance verification of RWA tokens and the dynamic management of order book quantity are realized. Under the premise of ensuring the legality of transactions, the order book quantity is adaptively adjusted by monitoring the buy-sell ratio (market sentiment indicator) in real time. This mechanism can dynamically narrow the buy-sell price difference according to market depth, solving the problem of rigid decision-making mechanisms. Attached Figure Description
[0024] Figure 1 This is a technical schematic diagram of a token trading control system according to one embodiment of this application; Figure 2 This is a flowchart illustrating the token transaction control method applied to a terminal according to an embodiment of this application; Figure 3 This is a schematic diagram of a data element on-chain algorithm according to one embodiment of this application; Figure 4 This is a flowchart illustrating the token transaction control method applied to the first intelligent agent according to an embodiment of this application; Figure 5 This is a flowchart illustrating the token transaction control method applied to a second intelligent agent according to an embodiment of this application; Figure 6 This is a flowchart illustrating the token transaction control method applied to a third-party intelligent agent according to an embodiment of this application; Figure 7 This is a schematic diagram of the token transaction control device applied to a terminal according to an embodiment of this application; Figure 8 This is a schematic diagram of the token transaction control device applied to the first intelligent agent according to an embodiment of this application; Figure 9 This is a schematic diagram of the token transaction control device applied to the second intelligent agent according to an embodiment of this application; Figure 10 This is a schematic diagram of the token transaction control device applied to a third-party intelligent agent according to an embodiment of this application. Detailed Implementation
[0025] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, and the number of objects is not limited; for example, the first object can be one or more.
[0026] In various embodiments of the present invention, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
[0027] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.
[0028] It should be understood that "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.
[0029] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.
[0030] In addition, the terms "system" and "network" are often used interchangeably in this article.
[0031] Relevant technical specifications: In existing technologies, RWA trading platforms with built-in strict compliance frameworks mainly suffer from the following drawbacks: (1) The RWA trading platform only targets real asset tokens and does not support data asset tokenization (DAT) with data resource ownership attributes. As the core pillar of the digital economy, data elements are difficult to tokenize through the RWA trading platform.
[0032] (2) When dealing with complex and adaptive decisions, the RWA trading platform with its built-in strict compliance framework requires human meetings for decision-making, which is complex, rigid, and requires multiple layers of approval, resulting in low efficiency.
[0033] (3) The trust mechanism is not sound. RWA projects on the RWA trading platform still rely on centralized institutions to manage assets or cash flow, and have failed to truly achieve the transparency of "code is law", which leads to investors having doubts about the correspondence between on-chain tokens and physical assets.
[0034] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0035] This application addresses the problems of an unsound trust mechanism and a rigid decision-making mechanism in existing RWA trading platforms by providing a token trading control system, method, device, equipment, product, and medium.
[0036] like Figure 1 As shown, one embodiment of this application provides a token transaction control system, which can specifically be a data element token system based on a multi-agent collaborative architecture.
[0037] For example, the system includes: a data exchange, industry ecosystem partners, a multi-agent collaboration module, and a blockchain system. The data exchange is responsible for establishing and registering the RWA (Real-Time Analysis and Transaction) system, handling transaction affairs, and disclosing relevant information. Industry ecosystem partners include: auditors, investors, data element holders, and brokers. The multi-agent collaboration module includes multiple agents: a first agent (compliance audit agent), a second agent (issuance agent), a third agent (market making agent), and a fourth agent (risk control agent). User requests first enter the multi-agent collaboration module, and then the agents write the transaction to the blockchain, with multiple agents coordinating their work. The blockchain system maintains the blockchain and performs functions such as data on-chaining, revenue on-chaining, and asset on-chaining.
[0038] In some embodiments, a first intelligent agent (compliance audit agent) is used to verify the validity of the dual-pipe signatures of N signing entities for a data element, and write the data element into the blockchain if each dual-pipe signature is successfully verified. The dual-pipe signature corresponds one-to-one with the signing entity, and the dual-pipe signature is a digital signature containing dual parameters generated by the signing entity for the data element, where N is an integer greater than 2.
[0039] It's important to note that the Compliance Audit Agent, acting as the system's "gatekeeper," can integrate with external Boneh-Lynn-Schacham (BLS) verification application programming interfaces (APIs) to perform functions such as document recognition, facial recognition, and sanctions list checks. The Compliance Audit Agent is responsible for executing Know Your Customer (KYC) and Anti-Money Laundering (AML) processes in real time, uploading data elements to the blockchain through data element on-chain algorithms. KYC is a common compliance requirement in the financial industry and various business sectors, designed to prevent fraud, money laundering, and other illicit activities; AML refers to the use of legal, technological, and regulatory means to prevent and combat the disguise of illicit funds as legitimate income.
[0040] When a new user registers or conducts a large transaction, the compliance audit agent automatically verifies their identity and compliance, significantly accelerating the traditional account opening process that takes several days. After verifying the user's compliance, the compliance audit agent can call the blockchain system's data element on-chain module to complete the data element on-chain verification, thus confirming data element compliance. Subsequently, the compliance audit agent can notify the issuing agent, market-making agent, and risk control agent that the data element is compliant.
[0041] It should be noted that the auditor, investor, data element holder, broker, and data exchange all need to perform a dual-channel signature calculation on data element D. The compliance audit agent is responsible for verifying the dual-channel signatures of all parties. After confirming that the signatures are correct, the data element D is written into the blockchain, thus completing the on-chain data element process.
[0042] The second smart agent (issuing agent) is used to mint the real-world asset RWA token (i.e., data element token) of the data element through smart contracts.
[0043] It should be noted that in this system, the Issuance Agent acts as a "bridge," responsible for mapping between physical assets and RWA tokens. For example, the Issuance Agent can use a joint minting algorithm that supports compliance verification to issue RWA tokens.
[0044] The third smart agent (market maker) is used to invoke the smart contract to verify the compliance of the RWA token. If the verification of the RWA token is successful, the agent dynamically adjusts the number of orders for the RWA token based on the buy-sell ratio. The buy-sell ratio includes the ratio of buy orders to sell orders, or the ratio of sell orders to buy orders.
[0045] It should be noted that the market maker agent can act as a "lubricant" for the market, continuously and dynamically adjusting the buy and sell orders posted on the order book (for example, by using the BS sentiment balancing algorithm to dynamically adjust), thus providing liquidity for the RWA token.
[0046] The fourth intelligent agent (risk control agent) is used to monitor transaction data in real time, identify anomalies (such as systemic risks or illegal transactions) based on the transaction data, and suspend transactions or freeze assets when anomalies are detected, so as to ensure the security of the entire chain of data element tokenization transactions.
[0047] It's important to note that the Risk Control Agent acts as the system's "sentinel." It doesn't directly handle user requests but continuously monitors the overall state, including price data (e.g., data element price data at any given time), inventory reports (e.g., each user's data element token holdings), and large account holdings (e.g., the top 20 accounts by data element token holdings). Price data, inventory reports, and large account holdings are transaction data, which are real-time, off-chain data. Upon detecting anomalies, such as drastic price fluctuations (e.g., price increases or decreases exceeding 50% within one hour) or inventory mismatches (e.g., data element token holdings not equal to issuance quantities), the Risk Control Agent has the right to suspend trading by calling the `pause_Transtate` function of the RWA token smart contract to prevent the spread of systemic risk. The `pause_Transtate` function is a smart contract security control function that forcibly resets the transaction state variable `Transtate` to `false`, immediately freezing trading permissions and interrupting the RWA token circulation chain.
[0048] For example, the specific risk control scheme of this risk control agent may include: real-time monitoring of data element price data at any point in time; calculating the data element token holdings of each user and generating an inventory report; ranking data element token holdings and classifying the top 20 accounts as large-scale holdings; monitoring data element token prices, and when the price increase or decrease exceeds 50% within one hour, calling the pause_Transtate function of the RWA token smart contract to stop trading; and real-time calculation of whether the holdings and issuance of data element tokens are equal. If they are found to be unequal, it indicates an inventory mismatch, and the pause_Transtate function of the RWA token smart contract can be called to stop trading. It is understood that after stopping trading, the risk control agent can also notify all other agents that the data element will no longer be tradable.
[0049] In this embodiment, the risk control agent can call the `pause_Transtate` function of the RWA token smart contract to stop the transaction when a risk is detected, setting the transaction status (Transtate) of the RWA token contract to false, thus preventing the data element from being traded. The risk control agent can also notify all other agents that the data element cannot be traded.
[0050] It should be noted that the token trading control system in the above embodiments of this application is an AI-driven multi-agent system. It transforms data elements into on-chain digital rights through blockchain technology, achieving not only a seamless conversion from data elements to data element tokens (i.e., RWA tokens for data elements), but also constructing a trading ecosystem that balances efficiency and security, supporting data element tokens with data resource ownership attributes. Specifically, this system integrates the flexibility and automated decision-making capabilities of AI agents with the transparency, immutability, and determinism of the blockchain by deploying four specialized AI agents off-chain and key security logic on-chain. The most critical security constraints are directly encoded into immutable smart contracts, ensuring the enforced execution of the system's core invariants. Off-chain agents handle complex, adaptive decisions (such as compliance judgments and market-making strategies), while on-chain smart contracts act like a "constitution," enforcing a few crucial core rules (such as proof-of-reserve and circuit breaker mechanisms). Multi-party joint signatures ensure the trustworthiness of on-chain assets, resolving the impossible trinity of RWA compliance, liquidity, and risk control.
[0051] The token trading control system described in this application firstly introduces a dual-channel signature verification mechanism with N signing entities through a first intelligent agent. Compared to traditional centralized single-point authorization, this mechanism enables distributed ownership confirmation and tamper-proof evidence storage of data elements, improves the trust mechanism, and solves the problem of low verification efficiency in existing RWA platforms, ensuring the authenticity of assets on the blockchain from the source. Secondly, through collaboration between a second intelligent agent and smart contracts, a mechanism of authentication before issuance is implemented. Token minting is only executed after multi-signature verification is passed, effectively preventing illegal or unclearly owned assets from entering the market and improving the compliance of RWA asset issuance. Finally, a third intelligent agent realizes the compliance verification of RWA tokens and the dynamic management of order book quantity. Under the premise of ensuring the legality of transactions, the order book quantity is adaptively adjusted by real-time monitoring of the buy-sell ratio (market sentiment indicator). This mechanism can dynamically narrow the buy-sell price difference according to market depth, solving the problem of rigid decision-making mechanisms.
[0052] For a detailed description of the system described in this application, please refer to the following detailed description of the token transaction control method when applied to a terminal, a first intelligent agent, a second intelligent agent, and a third intelligent agent. It will not be repeated here.
[0053] like Figure 2 As shown, another embodiment of this application also provides a token transaction control method, applied to a terminal, including: Step 201: Perform dual-pipe signature on the data element to obtain the dual-pipe signature of the signature subject of the data element, wherein the dual-pipe signature corresponds one-to-one with the signature subject, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature subject corresponding to the dual-pipe signature for the data element.
[0054] It should be noted that the terminal here refers to the terminal used by the signing entity. The signing entity (i.e., the multiple independent participants associated with the data element) includes: the auditor, the investor, the data holder, the broker, and the data exchange. Step 202: Send the on-chain request information of the data element to the first intelligent agent. The on-chain request information includes the dual-pipe signature of N signature subjects of the data element, where N is an integer greater than 2.
[0055] In this embodiment, by performing dual-pipe signing on the terminal side, a highly secure digital certificate (i.e., dual-pipe signing) is generated using dual parameters, effectively preventing data tampering or forgery and ensuring clear ownership from the source. The distributed signature mechanism employing multiple signing entities breaks through the limitations of traditional centralized single-point verification, achieving joint ownership confirmation and collective consensus among multiple parties. By preprocessing the terminal and carrying multiple signature packet requests, standardized input is provided for the efficient parallel verification of the first intelligent agent, ensuring the transparency of data asset circulation and overall processing efficiency.
[0056] like Figure 3 As shown, in some embodiments, performing dual-pipe signing on data elements to obtain a dual-pipe signature of the signature body of the data elements includes: Step 2011: Perform a hash operation on the data elements to obtain a first hash value.
[0057] Here, the first hash value h can be expressed as: h = HASH(data element D), where HASH() represents hash operation (hash function).
[0058] Step 2012: Perform a modulo operation on the first hash value to obtain the second value.
[0059] Here, the second value h' can be expressed as: h' = h mod n, where n represents a preset value, which is a large integer.
[0060] Step 2013: Determine the first parameter value based on the first private key of the signing subject and the first preset elliptic curve.
[0061] Here, we assume that the first public key and first private key of each signing entity (e.g., the auditor, the investor, the data holder, the broker, and the data exchange) are pki and ski, respectively, where i = 1, 2, 3, 4, and 5. For example, pk1 and sk1 are the first public key and first private key of the auditor, respectively, and pk3 and sk3 are the first public key and first private key of the data holder, respectively.
[0062] In step 2013, Ri = ski·G can be calculated, and the X coordinate of Ri can be taken as the first parameter value ri. Here, G represents the first preset elliptic curve.
[0063] Step 2014: Obtain a random number, that is, generate a random number ki.
[0064] For example, a random number ki can be requested from a public endpoint of a Distributed Randomness Beacon (DRAND) network. The DRAND network is a distributed random beacon protocol network designed to provide public, verifiable, unbiased, and unpredictable random number services.
[0065] Step 2015: Determine the second parameter value based on the first private key, the second value, the first parameter value, and the random number.
[0066] Here, the second parameter value si can be expressed as: si = ski- 1 (h'+ri·ki) mod n.
[0067] Step 2016: Determine the first parameter value ri and the second parameter value si as the dual-pipe signature of the signature body of the data element. For example, the dual-pipe signature of the i-th party for data element D can be represented as (ri, si).
[0068] In this embodiment, the terminals of N signing entities can each perform dual-pipe signature calculation on the hash value (i.e., the first hash value) of the data element to form the dual-pipe signature (ri, si) of the signing entity, thus ensuring the authenticity of the asset on the chain from the source.
[0069] In some embodiments, the method further includes: generating an authorization signature for the project release information of the data element based on a second private key of the signing subject, wherein the second private key is a randomly generated integer, and the authorization signature is used to represent the authorization of the signing subject for the project release information.
[0070] It should be noted that all parties involved in the project (i.e., the auditors, investors, data holders, brokers, and data traders) are required to sign the project issuance information. The second public keys of each party are {AuPK1, AuPK2, ..., AuPKN}, and the second private keys are {AuSK1, AuSK2, ..., AuSKN}.
[0071] For example, the inputs to this signing process are: project release information ProInfo, the second public keys {AuPK1, AuPK2, ..., AuPKN} and the second private keys {AuSK1, AuSK2, ..., AuSKN} of the parties involved in the project. The output is: the authorized signatures of N project release information ProInfos are {Mq1, Mq2, ..., MqN}.
[0072] In bilinear curves (such as BLS12-381), and This represents two distinct elliptic curve groups and is typically used in bilinear pairing operations. The group is a subgroup on an elliptic curve whose elements are in additive group form and whose order is a large prime number; The group is another subgroup on an elliptic curve, and... They are of the same order but have higher embedding density, used to support efficient bilinear mapping computation.
[0073] For the i-th signer among the N signers (i.e., the signing entities) related to the project, its second public key is AuPKi, and its second private key is AuSKi. The second private key AuSKi is a randomly selected integer, and the second public key AuPKi = ... ·AuSKi.
[0074] It should be noted that for message (m) (which needs to be hashed first) The process of generating signature σ using the private key (sk) in the group is as follows: signature σ = e(SHA256(m),sk) =sk·SHA256(m), where SHA256 is a widely used cryptographic hash function belonging to the SHA-2 family.
[0075] For a message (m), the process of verifying the signature σ using the public key (pk) is as follows: Determine e(σ, ) = ·Whether σ is equal to e(SHA256(m),pk) =pk·SHA256(m); if they are equal, the signature is valid; otherwise, the signature is invalid.
[0076] For example, in this embodiment of the application, the algorithm for authorizing the signing of the project release information ProInfo is: Authorization signature Mqi = e(SHA256(ProInfo), AuSKi), where the authorization signature Mqi is in the group superior.
[0077] Given the project release information ProInfo, the authorized signature Mqi, and the second public key AuPKi, the authorized signature Mqi can be verified using the following verification algorithm: determine whether e(SHA256(ProInfo), AuPKi) is equal to e(Mqi, If the values are equal, the authorized signature is valid; otherwise, the authorized signature is invalid.
[0078] It should be noted that the principle of this verification algorithm can be expressed as follows: e(Mqi, ) = e( SHA256(ProInfo) AuSKi , = e(SHA256(ProInfo), ) AuSKi =e( SHA256(ProInfo), AuSKi ) =e( SHA256(ProInfo) ,AuPKi ).
[0079] The token transaction control method described in this application establishes a dual-parameter verification mechanism from the source by constructing a dual-pipe signature using hash, modulo, and elliptic curve algorithms on the terminal. This significantly enhances data anti-tampering and anti-forgery capabilities and improves data integrity. Furthermore, the terminal side employs a separate signature mechanism: data signature (i.e., dual-pipe signature) and authorization signature. This achieves independent control over data ownership confirmation and project issuance authorization, strengthens access control, and meets the business needs of multi-role collaboration while ensuring system security.
[0080] For specific implementation details of the method described in this application applied to a first intelligent agent, please refer to the detailed descriptions of the specific implementation details of the system and method applied to a first intelligent agent, a second intelligent agent, and a third intelligent agent, which will not be repeated here.
[0081] like Figure 4As shown, another embodiment of this application also provides a token transaction control method, applied to a first intelligent agent, including: Step 401: Receive the data element uplink request information sent by the terminal.
[0082] Step 402: Based on the on-chain request information, obtain the dual-pipe signatures of N signature subjects for the data element, wherein the dual-pipe signature corresponds one-to-one with the signature subject, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature subject for the data element, where N is an integer greater than 2.
[0083] Step 403: Verify the validity of each of the dual-pipe signatures.
[0084] Step 404: If each of the dual-channel signatures is successfully verified, the data element is written into the blockchain. Step 405: Send data element compliance information to the second intelligent agent, the data element compliance information being used to indicate that the data element is compliant.
[0085] Understandably, the first intelligent agent (compliance audit agent) can also send data element compliance information to other intelligent agents (such as market making agent and risk control agent).
[0086] Here, once the dual-channel signatures of all parties for data element D (for example, the dual-channel signatures of the N signing entities are (r1,s1), (r2,s2), (r3,s3), (r4,s4), (r5,s5)) are successfully verified, the compliance audit agent can write the data element, the N dual-channel signatures, and the public keys of each signing entity into the blockchain to complete the on-chaining of data element D.
[0087] In this embodiment, by using a first intelligent agent to verify the validity of dual-channel signatures of N signing entities, distributed ownership confirmation and tamper-proof evidence storage of data elements can be achieved, the trust mechanism can be improved, the problem of low verification efficiency of existing RWA platforms can be solved, and the authenticity of assets on the chain can be guaranteed from the source.
[0088] like Figure 3 As shown, in some embodiments, the validity verification of each of the dual-pipe signatures includes: Step 4031: Obtain the first public key (pki) of the signing subject corresponding to the dual-pipe signature. Where i = 1, 2, 3, 4, 5, pki represents the first public key of the i-th signing subject. For example, the first public keys of N signing subjects are pk1, pk2, ..., pkN.
[0089] Step 4032: Perform a hash operation on the data element to obtain a second hash value Hash(D), where D represents the data element.
[0090] Step 4033: Perform a modulo operation on the second hash value to obtain the first value.
[0091] Here, the first value h' can be calculated using the formula h' = Hash(D) mod n, where n represents a large integer. This step 4033 restricts h' to a certain interval.
[0092] Step 4034: Determine the first coefficient and the second coefficient based on the first value and the first and second parameter values of the dual-pipe signature.
[0093] For example, the first coefficient According to the formula = h' / si calculation, second coefficient According to the formula =ri / si calculation.
[0094] Step 4035: Determine the X coordinate of the target point based on the first coefficient, the first preset elliptic curve, the second coefficient, and the first public key.
[0095] Step 4036: If the X coordinate of the target point is the same as the first parameter value, the dual-pipe signature verification is confirmed to be successful.
[0096] Specifically, it can be calculated using the formula Ri'= G + • pki determines the coordinates of the target point Ri', and then verifies whether the X coordinate of the target point Ri' on the elliptic curve ecc is equal to the first parameter value ri. If it is equal, then the double-pipe signature (ri, si) is successfully verified.
[0097] In this embodiment, a central verifier (such as a compliance audit agent) verifies all collected signature pairs (i.e., N dual-channel signatures, such as (r1,s1), (r2,s2), (r3,s3), (r4,s4), (r5,s5)) one by one. Only after all participants (i.e., the N signing entities) have passed the dual-channel signature verification is {data element D, (r1,s1,pk1), (r2,s2,pk2), (r3,s3,pk3), (r4,s4,pk4), (r5,s5,pk5)} written into the blockchain, thereby completing the multi-party authorization on-chain based on cryptographic checks and balances.
[0098] The token transaction control method described in this application introduces a dual-pipe signature verification mechanism involving N signing entities through a first intelligent agent. Utilizing dual-parameter characteristics, it strengthens data anti-counterfeiting and integrity verification from the source, effectively overcoming the trust limitations of traditional centralized single-point verification and achieving distributed multi-node collaborative rights confirmation. Simultaneously, through rigorous verification steps such as hash operations, modulo operations, and comparison of the X-coordinate of the elliptic curve target point, it achieves precise compliance testing of data elements before they are added to the blockchain, ensuring that only fully authorized data can be written to the blockchain, effectively enhancing the authority and security of the ledger data. Furthermore, after successful verification, compliance information is automatically sent to other intelligent agents, significantly improving the overall efficiency and compliance level of data token circulation.
[0099] For specific implementation details of the method described in this application applied to a first intelligent agent, please refer to the detailed descriptions of the specific implementation details of the system and method applied to a terminal, a second intelligent agent, and a third intelligent agent, which will not be repeated here.
[0100] like Figure 5 As shown, another embodiment of this application also provides a token transaction control method, applied to a second intelligent agent, including: Step 501: Receive data element compliance information sent by the first intelligent agent, the data element compliance information being used to indicate data element compliance.
[0101] Here, after receiving the data element compliance information from the first intelligent agent (compliance audit agent), the second intelligent agent (issuance agent) begins the RWA token issuance process. For example, the issuance process is as follows: Step 502: Obtain N authorized signatures of the project issuance information of the data element, wherein each authorized signature corresponds one-to-one with the signature subject of the data element, and the authorized signature is: a digital signature generated by the signature subject for the project issuance information, where N is an integer greater than 2.
[0102] It should be noted that the data element holder in the signing entity can apply for project registration with the data exchange in the system to form project issuance information ProInfo. The issuance agent can require the terminals of N signing entities related to the project (such as the auditor, capital party, data element holder, broker, and data exchange) to use the signature calculation in the joint minting algorithm that supports compliance verification in order to obtain N authorized signatures.
[0103] Step 503: Generate a joint signature based on the N authorized signatures.
[0104] In this step, the issuing agent aggregates N authorized signatures into a single joint signature algorithm-ProInfo.
[0105] For example, a joint signature algorithm-ProInfo can be generated based on the public keys {AuPK1, AuPK2, ..., AuPKN} and private keys {AuSK1, AuSK2, ..., AuSKN} of N project stakeholders (i.e., N signing entities), the authorized signatures {Mq1, Mq2, ..., MqN} of N project release information ProInfo, and the project release information ProInfo.
[0106] It should be noted that the joint signature algorithm-ProInfo is a signature that supports compliance verification. The verification method is given below as an example: For the i-th signer (i.e., the signing subject) and the j-th signer, suppose their authorized signatures are Mqi and Mqj respectively, where Mqi = ,Mqj = .
[0107] Then the following equations hold true: e(Mqi·Mqj , ) = e( · , = e((SHA256(ProInfo)) AuSKi+AuSKj , = e(SHA256(ProInfo), ) AuSKi+AuSKj = e( SHA256(ProInfo), ) AuSKi ·e( SHA256(ProInfo) , ) AuSKj = e(Mqi , )·e(Mqj , ) =e( SHA256(ProInfo),AuPKi ) · e( SHA256(ProInfo),AuPKj ).
[0108] In other words, e(Mqi·Mqj, =e( SHA256(ProInfo),AuPKi )· e( SHA256(ProInfo),AuPKj ). Therefore, Mqi·Mqj can be used to verify whether the i-th signer and the j-th signer have jointly signed the project release information ProInfo.
[0109] And so on, e( Mq1·Mq2……·MqN , =e( SHA256(ProInfo) , AuPK1 )· e( SHA256(ProInfo) , AuPK2 )……· e( SHA256(ProInfo) ,AuPKN ), therefore, if the above equation holds, it means that N signing entities have jointly signed the project release information ProInfo.
[0110] Therefore, if we let the joint signature algorithm-ProInfo = Mq1·Mq2 ……·MqN, we can use Mq·Mq1·Mq2 ……·MqN, SHA256(ProInfo), AuPK1, AuPK2, ……, AuPKN to verify whether algorithm-ProInfo is generated by the joint signature of all N signing entities.
[0111] Step 504: Through a smart contract, based on the project issuance information, the joint signature, and the second public keys (AuPKi, for example, the second public keys of the N signature subjects are: AuPK1, AuPK2, ..., AuPKN), mint the RWA token of the data element. The second public key is generated based on the second private key of the signature subject and a second preset elliptic curve. The second private key is a randomly generated integer.
[0112] Here, the issuing agent can run the minting smart contract to issue RWA tokens (or mint RWA tokens).
[0113] For example, the RWA token smart contract for the project information ProInfo includes the following functions: set_ProInfo_Auth, valid_ProInfo_Auth, valid_Transtate, and pause_Transtate. The set_ProInfo_Auth function writes the project information ProInfo, the joint signature algorithm-ProInfo, AuPK1, AuPK2, ..., AuPKN, and the transaction state (Transtate) as contract parameters to the blockchain, and then calls the valid_Transtate function of the RWA token smart contract to activate the transaction. The valid_Transtate function sets the transaction state of the RWA token smart contract to true, indicating that the transaction can proceed; the pause_Transtate function sets the transaction state of the RWA token smart contract to false, indicating that the transaction can be stopped.
[0114] Step 505: Send token issuance information to the third intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token.
[0115] Here, after the issuing agent successfully issues the RWA token, it can notify the compliance audit agent, market making agent, and risk control agent that the RWA token has been successfully issued.
[0116] In the above embodiments of this application, the issuing agent employs a joint minting algorithm that supports compliance verification. Therefore, after the issuing agent completes the minting of RWA tokens, any party (e.g., the auditor or investor) can verify the compliance of the RWA tokens through information on the blockchain. For example, the verification algorithm is as follows: This can be verified by e(algorithm-ProInfo, The validity of the RWA token is determined by checking if it equals e(SHA256(ProInfo), AuPK1)·e(SHA256(ProInfo), AuPK2)……·e(SHA256(ProInfo), AuPKN). If they are equal, the verification is successful, the federated signature algorithm-ProInfo is valid, and the RWA token is compliant.
[0117] For example, the `valid_ProInfo_Auth` function can be used to implement compliance verification. The `valid_ProInfo_Auth` function takes the project information `ProInfo`, the joint signature `algorithm-ProInfo`, and the public keys `AuPK1`, `AuPK2`, ..., `AuPKN` of the parties involved in the project as contract parameters, and verifies `e(algorithmProInfo, ...`. Does it equal e(SHA256(ProInfo), AuPK1)·e(SHA256(ProInfo), AuPK2)……·e(SHA256(ProInfo), AuPKN)? If they are equal, the verification is successful and algorithm-InfoMK is valid.
[0118] For example, during the issuance of RWA by the issuing agent calling the minting contract, the valid_ProInfo_Auth function can be called to verify the compliance of the project. Capital providers (funds, banks, accredited investors) can also call the valid_ProInfo_Auth function to determine the compliance of the RWA token.
[0119] The token transaction control method described in this application requires the second intelligent agent (issuing agent) to generate BLS signatures Mqi (i.e., authorization signatures) for all designated project participants using their respective private keys AuSKi to hash the project issuance information ProInfo before minting the tokens. Then, the second intelligent agent (issuing agent) aggregates these dispersed authorization signatures into a single joint signature algorithm-ProInfo. Subsequently, during on-chain verification, the smart contract verifies the equation e(algorithm-ProInfo) by performing a bilinear pairing operation. The equation ) = ∏e(SHA256(ProInfo),AuPKi) is valid. The validity of this equation is a necessary condition for the token smart contract to allow the minting or to determine the compliance of the token, thereby ensuring the automated verification and immutability of the issuance authorization.
[0120] For specific implementations of the method described in this application applied to a second intelligent agent, please refer to the detailed descriptions of the specific implementations of the system and method applied to a terminal, a first intelligent agent, and a third intelligent agent, which will not be repeated here.
[0121] like Figure 6 As shown, another embodiment of this application also provides a token transaction control method, applied to a third intelligent agent, including: Step 601: Receive token issuance information sent by the second intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token.
[0122] Step 602: Based on the identity identifier of the RWA token, invoke the smart contract to perform compliance verification on the RWA token.
[0123] Here, after receiving the token issuance information from the second smart agent (issuing agent), the third smart agent (market maker) can obtain the RWA token based on its identity identifier (for example, the RWA token has been written into the smart contract). It can also call the smart contract's `valid_ProInfo_Auth` function to verify the compliance of the RWA token, ensuring that the issuance of the RWA token is legitimate. The `valid_ProInfo_Auth` function is the compliance verification mechanism within the smart contract, used to verify the compliance of the project issuance information and the compliance status of the RWA token.
[0124] In step 602, compliance verification of the RWA token may include verification of federated signatures.
[0125] Step 603: If the RWA token is successfully verified, the number of orders for the RWA token is dynamically adjusted according to the buy-sell ratio of the RWA token. The buy-sell ratio includes the ratio of the number of buy orders to the number of sell orders, or the ratio of the number of sell orders to the number of buy orders.
[0126] In other words, once it is confirmed that there are no problems with the issuance of the RWA token, the market maker agent can dynamically adjust the number of orders for the RWA token (for example, by using the BS sentiment balancing algorithm) to ensure smooth trading.
[0127] Here, the market-making agent dynamically adjusts its quotes with the goal of maintaining a narrow bid-ask spread. For example, the market-making agent can employ a rule-based strategy to provide a data interface to a reinforcement learning (RL)-based market-making model. The data accessed through this interface includes information such as order book depth, bid-ask prices, bid-ask prices, and customer returns, allowing the market-making model to adaptively optimize the spread under varying market volatility.
[0128] In some embodiments, dynamically adjusting the order quantity of the RWA token based on the buy-sell ratio of the RWA token includes at least one of the following: (1) When the ratio of the number of buy orders to the number of sell orders is greater than or equal to a first threshold, a first number of sell orders are added every preset time interval until the ratio of the number of buy orders to the number of sell orders is less than the first threshold, wherein the first number is the product of the difference between the number of buy orders and the number of sell orders and a first preset ratio.
[0129] (2) When the ratio of the number of sell orders to the number of buy orders is greater than or equal to the second threshold, the number of sell orders is increased by a second number every preset time interval until the ratio of the number of sell orders to the number of buy orders is less than the second threshold, wherein the second number is the product of the difference between the number of sell orders and the number of buy orders and the second preset ratio.
[0130] Here, the first preset ratio and the second preset ratio can be equal or different; for example, it can be 30%.
[0131] For example, suppose the current order quantity is The current number of sell orders is The market-making agent can activate the BS sentiment balancing algorithm to adjust the number of pending orders in the following two situations: Case (1): When the ratio of buy orders to sell orders is ( / When the value is greater than or equal to the first threshold (e.g., 1.3), the market is in an optimistic state, and the market-making agent increases the first quantity (e.g., ( - (30%) sell orders, each with a price that is the third preset percentage of the current price (e.g., 112%). This loop repeats every preset duration (e.g., M seconds, where M is a positive integer) until... / Stop the loop when the value is less than the first threshold.
[0132] Case (2): When the ratio of sell orders to buy orders is ( / When the threshold is greater than or equal to the second threshold (e.g., 1.2), the market is in a pessimistic state, and the market-making agent increases the second quantity (e.g., (…)). - (30%) sell orders, each with a price that is the fourth preset percentage of the current price (e.g., 112%). This loop repeats every preset duration (e.g., M seconds, where M is a positive integer) until... / Stop the loop when the value is less than the second threshold.
[0133] The token trading control method described in this application continuously monitors the number of buy and sell orders in the order book through a market-making agent, and automatically determines the market sentiment state based on preset sentiment ratio thresholds (such as a first threshold and a second threshold). This triggers the BS sentiment balancing algorithm, which dynamically calculates and places new orders with quantities calculated using a specific formula that are opposite to market sentiment. The algorithm actively adjusts the buy and sell pressure and price spread in a cyclical manner, thereby providing and maintaining endogenous liquidity for token trading.
[0134] For specific implementations of the method described in this application when applied to a third intelligent agent, please refer to the detailed descriptions of the specific implementations of the system and method when applied to a terminal, a first intelligent agent, and a second intelligent agent, which will not be repeated here.
[0135] like Figure 7 As shown, one embodiment of this application also provides a token transaction control device applied to a terminal, the device comprising: The first signature module 710 is used to perform dual-pipe signature on data elements to obtain the dual-pipe signature of the signature body of the data elements, wherein the dual-pipe signature corresponds one-to-one with the signature body, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature body corresponding to the dual-pipe signature for the data elements. The first sending module 720 is used to send the on-chain request information of the data element to the first intelligent agent. The on-chain request information includes the dual-pipe signature of N signature subjects of the data element, where N is an integer greater than 2.
[0136] In this embodiment, by performing dual-pipe signing on the terminal side, a highly secure digital certificate (i.e., dual-pipe signing) is generated using dual parameters, effectively preventing data tampering or forgery and ensuring clear ownership from the source. The distributed signature mechanism employing multiple signing entities breaks through the limitations of traditional centralized single-point verification, achieving joint ownership confirmation and collective consensus among multiple parties. By preprocessing the terminal and carrying multiple signature packet requests, standardized input is provided for the efficient parallel verification of the first intelligent agent, ensuring the transparency of data asset circulation and overall processing efficiency.
[0137] Optionally, the first signature module 710 includes: The first processing unit is used to perform a hash operation on the data elements to obtain a first hash value; The second processing unit is used to perform a modulo operation on the first hash value to obtain a second value; The third processing unit is used to determine the first parameter value based on the first private key of the signing subject and the first preset elliptic curve. The first acquisition unit is used to acquire random numbers; The fourth processing unit is used to determine the second parameter value based on the first private key, the second value, the first parameter value, and the random number; The fifth processing unit is used to determine the first parameter value and the second parameter value as the signature body of the data element in a dual-pipe signature.
[0138] Optionally, the device further includes: The third signature module is used to generate an authorization signature for the project release information of the data element based on the second private key of the signing subject. The second private key is a randomly generated integer, and the authorization signature is used to represent the authorization of the signing subject for the project release information.
[0139] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0140] like Figure 8 As shown, one embodiment of this application also provides a token transaction control device, applied to a first intelligent agent, the device comprising: The first receiving module 810 is used to receive the data element uplink request information sent by the terminal; The first acquisition module 820 is used to acquire the dual-pipe signatures of N signature subjects of the data element according to the on-chain request information, wherein the dual-pipe signature corresponds one-to-one with the signature subject, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature subject for the data element, where N is an integer greater than 2; The first verification module 830 is used to verify the validity of each of the dual-pipe signatures. The first processing module 840 is used to write the data element into the blockchain if each of the dual-pipe signatures is successfully verified. The second sending module 850 is used to send data element compliance information to the second intelligent agent, wherein the data element compliance information is used to indicate that the data element is compliant.
[0141] In this embodiment, by using a first intelligent agent to verify the validity of dual-channel signatures of N signing entities, distributed ownership confirmation and tamper-proof evidence storage of data elements can be achieved, the trust mechanism can be improved, the problem of low verification efficiency of existing RWA platforms can be solved, and the authenticity of assets on the chain can be guaranteed from the source.
[0142] Optionally, the first verification module 830 includes: The second acquisition unit is used to acquire the first public key of the signature subject corresponding to the dual-pipe signature; The sixth processing unit is used to perform a hash operation on the data elements to obtain a second hash value; The seventh processing unit is used to perform a modulo operation on the second hash value to obtain the first value; The eighth processing unit is configured to determine the first coefficient and the second coefficient based on the first value and the first and second parameter values of the dual-pipe signature. The ninth processing unit is used to determine the X coordinate of the target point based on the first coefficient, the first preset elliptic curve, the second coefficient, and the first public key; The tenth processing unit is used to determine that the dual-pipe signature verification is successful if the X coordinate of the target point is the same as the first parameter value.
[0143] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0144] like Figure 9 As shown, one embodiment of this application also provides a token transaction control device, applied to a second intelligent agent, the device comprising: The second receiving module 910 is used to receive data element compliance information sent by the first intelligent agent, wherein the data element compliance information is used to indicate that the data element is compliant. The second acquisition module 920 is used to acquire N authorized signatures of the project issuance information of the data element, wherein the authorized signature corresponds one-to-one with the signature body of the data element, and the authorized signature is: a digital signature generated by the signature body for the project issuance information, where N is an integer greater than 2; The second signature module 930 is used to generate a joint signature based on the N authorized signatures; The token minting module 940 is used to mint the RWA token of the data element through a smart contract, based on the project issuance information, the joint signature and the second public keys of N signature subjects. The second public key is generated based on the second private key of the signature subject and a second preset elliptic curve. The second private key is a randomly generated integer. The token issuance module 950 is used to send token issuance information to a third intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token.
[0145] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0146] like Figure 10 As shown, one embodiment of this application also provides a token transaction control device applied to a third intelligent agent, the device comprising: The third receiving module 1010 is used to receive token issuance information sent by the second intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token. The second verification module 1020 is used to call a smart contract based on the identity identifier of the RWA token to perform compliance verification on the RWA token. The order adjustment module 1030 is used to dynamically adjust the number of orders for the RWA token based on the buy-sell ratio of the RWA token when the RWA token is successfully verified. The buy-sell ratio includes the ratio of the number of buy orders to the number of sell orders, or the ratio of the number of sell orders to the number of buy orders.
[0147] Optionally, the order adjustment module 1030 includes: The eleventh processing unit is used to add a first number of sell orders every preset time interval when the ratio of the number of buy orders to the number of sell orders is greater than or equal to a first threshold, until the ratio of the number of buy orders to the number of sell orders is less than the first threshold, wherein the first number is the product of the difference between the number of buy orders and the number of sell orders and a first preset ratio. The twelfth processing unit is used to add a second number of sell orders every preset time interval when the ratio of the number of sell orders to the number of buy orders is greater than or equal to a second threshold, until the ratio of the number of sell orders to the number of buy orders is less than the second threshold, wherein the second number is the product of the difference between the number of sell orders and the number of buy orders and a second preset ratio.
[0148] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0149] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.
[0150] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0151] One embodiment of this application also provides an apparatus, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the above-described token transaction control method.
[0152] It should be noted that the device provided in this embodiment of the invention can implement all the method steps implemented in the above-mentioned token transaction control method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.
[0153] In addition, specific embodiments of this application also provide a readable storage medium storing a program. When executed by a processor, this program implements the various processes of the above-described token transaction control method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here. The readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).
[0154] This application also provides a computer program product, including computer instructions. When executed by a processor, the computer instructions implement the various processes of the above-described token transaction control method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0155] Optionally, embodiments of this application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0156] The computer program product described in this application includes computer instructions that, when executed by a processor, implement the various processes of the method embodiments shown above and achieve the same technical effects. To avoid repetition, these will not be repeated here.
[0157] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0158] It should be noted that many of the functional components described in this specification are referred to as modules / submodules in order to more specifically emphasize the independence of their implementation.
[0159] In this application embodiment, the module / submodule can be implemented in software so that it can be executed by various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of computer instructions, which may be constructed as objects, procedures, or functions. Nevertheless, the executable code of the identified module does not need to be physically located together, but may include different instructions stored in different bits, which, when logically combined, constitute the module and achieve the module's intended purpose.
[0160] In practice, an executable code module can be a single instruction or many instructions, and can even be distributed across multiple different code segments, different programs, and across multiple memory devices. Similarly, operational data can be identified within the module and can be implemented in any suitable form and organized within any suitable data structure. This operational data can be collected as a single dataset or distributed across different locations (including different storage devices), and can exist, at least in part, solely as electronic signals within the system or network.
[0161] When a module can be implemented using software, considering the current level of hardware technology, modules that can be implemented in software can be implemented using hardware circuits by those skilled in the art to achieve the corresponding functions, without considering cost. These hardware circuits include conventional very-large-scale integrated circuits (VLSI) or gate arrays, as well as existing semiconductors such as logic chips and transistors, or other discrete components. Modules can also be implemented using programmable hardware devices, such as field-programmable gate arrays, programmable array logic, and programmable logic devices.
[0162] The above describes the preferred embodiments of this application. It should be noted that those skilled in the art can make several improvements and modifications without departing from the principles described in this application, and these improvements and modifications should also be considered within the scope of protection of this application.
Claims
1. A token trading control system, characterized in that, include: The first intelligent agent is used to verify the validity of the dual-channel signatures of N signature subjects of the data element, and write the data element into the blockchain if each dual-channel signature is successfully verified. The dual-channel signature corresponds one-to-one with the signature subject. The dual-channel signature is a digital signature with dual parameters generated by the signature subject for the data element, where N is an integer greater than 2. A second intelligent agent is used to mint the real-world asset RWA token of the data elements through smart contracts; A third intelligent agent is used to invoke the smart contract to perform compliance verification on the RWA token. If the RWA token verification is successful, the agent dynamically adjusts the number of orders placed for the RWA token based on the buy-sell ratio. The buy-sell ratio includes the ratio of buy orders to sell orders, or the ratio of sell orders to buy orders.
2. A token transaction control method, characterized in that, Applied to terminals, including: Perform dual-pipe signature on the data element to obtain the dual-pipe signature of the signature body of the data element, wherein the dual-pipe signature corresponds one-to-one with the signature body, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature body corresponding to the dual-pipe signature for the data element; Send the data element on-chain request information to the first intelligent agent. The on-chain request information includes the dual-pipe signatures of N signature subjects of the data element, where N is an integer greater than 2.
3. The token transaction control method according to claim 2, characterized in that, The process of performing dual-pipe signing on data elements to obtain the dual-pipe signature of the signature body of the data elements includes: Perform a hash operation on the data elements to obtain a first hash value; Perform a modulo operation on the first hash value to obtain the second value; The first parameter value is determined based on the first private key of the signing subject and the first preset elliptic curve; Get random numbers; The second parameter value is determined based on the first private key, the second value, the first parameter value, and the random number; The first parameter value and the second parameter value are determined as the signature of the data element in a dual-pipe signature.
4. The token transaction control method according to claim 2, characterized in that, The method further includes: Based on the second private key of the signing subject, an authorization signature for the project release information of the data element is generated. The second private key is a randomly generated integer, and the authorization signature is used to represent the authorization of the signing subject for the project release information.
5. A token transaction control method, characterized in that, Applied to the first intelligent agent, including: Receive the on-chain request information for data elements sent by the receiving terminal; Based on the on-chain request information, obtain the dual-pipe signatures of N signature subjects of the data element, wherein the dual-pipe signature corresponds one-to-one with the signature subject, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature subject for the data element, where N is an integer greater than 2; Validate the validity of each of the dual-pipe signatures. If each of the aforementioned dual-channel signatures is successfully verified, the data element is written into the blockchain; Send data element compliance information to the second intelligent agent, the data element compliance information being used to indicate that the data element is compliant.
6. The token transaction control method according to claim 5, characterized in that, The validity verification of each of the dual-pipe signatures includes: Obtain the first public key of the signing subject corresponding to the dual-pipe signature; Perform a hash operation on the data elements to obtain a second hash value; Perform a modulo operation on the second hash value to obtain the first value; The first coefficient and the second coefficient are determined based on the first value and the first and second parameter values of the dual-pipe signature; The X coordinate of the target point is determined based on the first coefficient, the first preset elliptic curve, the second coefficient, and the first public key. If the X coordinate of the target point is the same as the first parameter value, the dual-pipe signature verification is deemed successful.
7. A token transaction control method, characterized in that, Applied to second intelligent agents, including: Receive data element compliance information sent by a first intelligent agent, wherein the data element compliance information is used to indicate that the data element is compliant; Obtain N authorized signatures of the project issuance information of the data element, wherein each authorized signature corresponds one-to-one with the signature subject of the data element, and the authorized signature is: a digital signature generated by the signature subject for the project issuance information, where N is an integer greater than 2; Generate a joint signature based on the N authorized signatures; Through a smart contract, based on the project issuance information, the joint signature, and the second public keys of N signing entities, an RWA token for the data element is minted. The second public key is generated based on the second private key of the signing entity and a second preset elliptic curve. The second private key is a randomly generated integer. Send token issuance information to a third-party intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token.
8. A token transaction control method, characterized in that, Applied to third-party intelligent agents, including: Receive token issuance information sent by a second intelligent agent, wherein the token issuance information is used to indicate that the RWA token of the data element has been minted, and the token issuance information includes the identity identifier of the RWA token; Based on the identity identifier of the RWA token, the smart contract is invoked to perform compliance verification on the RWA token; If the RWA token is successfully verified, the number of orders for the RWA token is dynamically adjusted according to the buy-sell ratio of the RWA token. The buy-sell ratio includes the ratio of the number of buy orders to the number of sell orders, or the ratio of the number of sell orders to the number of buy orders.
9. The token transaction control method according to claim 8, characterized in that, The step of dynamically adjusting the order quantity of RWA tokens based on the buy-sell ratio of RWA tokens includes at least one of the following: If the ratio of the number of buy orders to the number of sell orders is greater than or equal to a first threshold, a first number of sell orders are added every preset time interval until the ratio of the number of buy orders to the number of sell orders is less than the first threshold, wherein the first number is the product of the difference between the number of buy orders and the number of sell orders and a first preset ratio. If the ratio of the number of sell orders to the number of buy orders is greater than or equal to a second threshold, a second number of sell orders are added every preset time interval until the ratio of the number of sell orders to the number of buy orders is less than the second threshold. The second number is the product of the difference between the number of sell orders and the number of buy orders and a second preset ratio.
10. A token transaction control device, characterized in that, Applied to a terminal, the device includes: The first signature module is used to perform dual-pipe signature on data elements to obtain the dual-pipe signature of the signature body of the data elements, wherein the dual-pipe signature corresponds one-to-one with the signature body, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature body corresponding to the dual-pipe signature for the data elements. The first sending module is used to send the on-chain request information of the data element to the first intelligent agent. The on-chain request information includes the dual-pipe signature of N signature subjects of the data element, where N is an integer greater than 2.
11. A token transaction control device, characterized in that, Applied to a first intelligent agent, the device includes: The first receiving module is used to receive the data element uplink request information sent by the terminal; The first acquisition module is used to acquire the dual-pipe signatures of N signature subjects of the data element according to the on-chain request information, wherein the dual-pipe signature corresponds one-to-one with the signature subject, and the dual-pipe signature is: a digital signature containing dual parameters generated by the signature subject for the data element, where N is an integer greater than 2; The first verification module is used to verify the validity of each of the dual-pipe signatures. The first processing module is used to write the data element into the blockchain if each of the dual-pipe signatures is successfully verified. The second sending module is used to send data element compliance information to the second intelligent agent, wherein the data element compliance information is used to indicate that the data element is compliant.
12. A token transaction control device, characterized in that, Applied to a second intelligent agent, the device includes: The second receiving module is used to receive data element compliance information sent by the first intelligent agent, wherein the data element compliance information is used to indicate that the data element is compliant. The second acquisition module is used to acquire N authorized signatures of the project issuance information of the data element, wherein the authorized signature corresponds one-to-one with the signature subject of the data element, and the authorized signature is: a digital signature generated by the signature subject for the project issuance information, where N is an integer greater than 2; The second signature module is used to generate a joint signature based on the N authorized signatures; The token minting module is used to mint RWA tokens of the data elements through smart contracts, based on the project issuance information, the joint signature, and the second public keys of N signing entities. The second public key is generated based on the second private key of the signing entity and a second preset elliptic curve. The second private key is a randomly generated integer. The token issuance module is used to send token issuance information to a third-party intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token.
13. A token transaction control device, characterized in that, Applied to a third intelligent agent, the device includes: The third receiving module is used to receive token issuance information sent by the second intelligent agent. The token issuance information is used to indicate that the RWA token of the data element has been minted. The token issuance information includes the identity identifier of the RWA token. The second verification module is used to call a smart contract based on the identity identifier of the RWA token to perform compliance verification on the RWA token. The order book adjustment module is used to dynamically adjust the number of orders for the RWA token based on the buy-sell ratio when the RWA token is successfully verified. The buy-sell ratio includes the ratio of buy orders to sell orders, or the ratio of sell orders to buy orders.
14. A device, characterized in that, The device includes a processor, a memory, and a program stored in the memory and executable on the processor. When executed by the processor, the program implements the token transaction control method as described in any one of claims 2 to 4, or implements the token transaction control method as described in claim 5 or 6, or implements the token transaction control method as described in claim 7, or implements the token transaction control method as described in claim 8 or 9.
15. A computer program product, characterized in that, The method includes computer instructions that, when executed by a processor, implement the steps of the token transaction control method as described in any one of claims 2 to 4, or implement the steps of the token transaction control method as described in claim 5 or 6, or implement the steps of the token transaction control method as described in claim 7, or implement the steps of the token transaction control method as described in claim 8 or 9.
16. A readable storage medium, characterized in that, The readable storage medium stores a program that, when executed by a processor, implements the steps of the token transaction control method as described in any one of claims 2 to 4, or implements the steps of the token transaction control method as described in claim 5 or 6, or implements the steps of the token transaction control method as described in claim 7, or implements the steps of the token transaction control method as described in claim 8 or 9.