Digital asset transaction method and system based on distributed account book

Abstract

The invention belongs to the technical field of digital asset transaction, and particularly discloses a digital asset transaction method and system based on a distributed account book, which realizes the availability and invisibility of information before transaction through a mechanism of'off-chain security processing 'plus'on-chain verifiable execution', ensures the high security and privacy of the whole transaction process, especially the link before accounting, and improves the transaction efficiency. In combination with zero knowledge proof, an end-to-end security guarantee is provided; by combining high-load order matching with efficient under-chain execution and lightweight on-chain verification, high-throughput and low-delay transaction experience is realized, transaction efficiency comparable to that of a centralized platform is realized, and absolute transparency and fairness of transaction matching and clearing are guaranteed; the key operation result is sent to the smart contract for verification processing, and the core elements of the transaction are subjected to distributed account book evidence storage, so that the process is ensured to be open and transparent; a necessary audit tracking path is provided for a supervision mechanism through a transaction identifier and an authorized access mechanism.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of digital asset transaction, and particularly relates to a digital asset transaction method and system based on a distributed ledger. BACKGROUND

[0002] With the in-depth development of digital economy, the transaction demand of digital assets (including digital property rights, network data and information assets, tokenized real-world assets RWA, etc.) is growing. The traditional centralized transaction platform has problems such as single point of failure, insufficient transparency, and user asset custody risk. Therefore, the decentralized transaction platform based on distributed ledger technology emerges as the times require. It automatically executes transactions through smart contracts, returns the asset control right to the user, and greatly enhances the system's resistance to censorship and trust foundation. However, the existing decentralized transaction scheme still faces multiple challenges, mainly including: 1. Balance between transparency and privacy: Although the blockchain itself has the characteristics of public and traceable transaction data, completely publishing all transaction details (such as uncompleted orders, complete user identity association information) on the chain may expose user transaction strategies and privacy. Some current schemes choose to only chain the final transaction result, but this sacrifices the verifiability of the transaction process.

[0003] 2. Transaction efficiency bottleneck: In a high-concurrency transaction scenario, especially for derivative transactions, the matching and clearing of each order are completed on the chain, which is limited by the performance of the underlying blockchain, resulting in high latency and high cost.

[0004] 3. Pre-transaction information security: There is a risk of privacy information leakage in the process of submitting transaction information to the distributed network for consensus and recording. The security protection measures of the existing schemes for this link are usually insufficient.

[0005] Therefore, there is an urgent need for a complete solution that can systematically implement dynamic encryption protection before transaction information enters the distributed recording process, and organically integrate high-performance matching and on-chain verifiability. SUMMARY

[0006] The purpose of the present application is to provide a digital asset transaction method and system based on a distributed ledger, which solves the above-mentioned problems existing in the prior art.

[0007] In order to achieve the above-mentioned purpose, the present application adopts the following technical solutions: In a first aspect, a digital asset transaction method based on a distributed ledger is provided, comprising: obtaining an original transaction request initiated by a buyer transaction node, and parsing the original transaction request to extract key privacy data and publicly verifiable data from the original transaction request; Key privacy data is dynamically encrypted to obtain privacy-encrypted data; A transaction identifier is generated using publicly verifiable data and privacy-encrypted data, and the publicly verifiable data and the transaction identifier are packaged together to generate a lightweight transaction request; Lightweight transaction requests are queued into a transaction queue, and the transaction queue is processed into a transaction block proposal to obtain a transaction block proposal containing the lightweight transaction requests. The blockchain verifiable engine matches transaction block proposals and generates a lightweight transaction request matching result and corresponding zero-knowledge proof when a transaction is completed. Publicly verifiable data, transaction identifiers, matching results, and zero-knowledge proofs are all submitted to the distributed ledger. The validity of zero-knowledge proofs is verified by smart contracts deployed on a distributed ledger. After the validity verification is passed, digital asset delivery is executed according to the matching results, and publicly verifiable data and transaction identifiers are associated and written into the distributed ledger.

[0008] In one possible design, the method further includes: After associating the privacy-encrypted data with the corresponding transaction identifier, it is stored in the privacy storage area specified by the buyer's transaction node; Obtain the audit authorization key and transaction identifier sent by the data compliance audit node; The audit authorization key is verified, and after the key verification is successful, the privacy-encrypted data is retrieved from the privacy storage area based on the transaction identifier; Privacy-encrypted data is sent to the data compliance audit node, which then uses the privacy-encrypted data and publicly verifiable data to generate a verification transaction identifier. The verification transaction identifier is then compared with the transaction identifier to obtain the corresponding data compliance audit result. Both the publicly verifiable data and the transaction identifier are obtained by the data compliance audit node from the distributed ledger.

[0009] In one possible design, the method further includes: The privacy-encrypted data is segmented to obtain several privacy-encrypted data blocks. Each piece of privacy-encrypted data is associated with its corresponding transaction identifier and then stored in the authorized nodes specified by the buyer's transaction node. Obtain the audit authorization key and transaction identifier sent by the data compliance audit node; The audit authorization key is verified, and after the key verification is successful, privacy encrypted data blocks are retrieved from each authorized node according to the transaction identifier, and privacy encrypted data is composed of each privacy encrypted data block. The privacy encryption data is sent to the data compliance audit node, so that the data compliance audit node generates a check transaction identifier by using the privacy encryption data and the publicly verifiable data, and performs check comparison by using the check transaction identifier and the transaction identifier to obtain a corresponding data compliance audit result, wherein the publicly verifiable data and the transaction identifier are obtained by the data compliance audit node from the distributed ledger.

[0010] In a possible design, the key privacy data includes buyer identity information and a buyer transaction node IP address, and the publicly verifiable data includes a timestamp, a digital asset type, a transaction quantity, a transaction price, and a buyer fund pool identifier.

[0011] In a possible design, the matching result includes a buyer-seller matching relationship, a traded digital asset type, and a traded digital asset quantity, and the buyer-seller matching relationship includes a matching relationship between a buyer fund pool identifier and a seller fund pool identifier, and the execution of the digital asset delivery according to the matching result includes: According to the matching relationship between the buyer fund pool identifier and the seller fund pool identifier, the digital asset transfer of the corresponding traded digital asset type and traded digital asset quantity between the seller fund pool and the buyer fund pool is completed.

[0012] In a possible design, the dynamic encryption of the key privacy data to obtain the privacy encryption data includes: The key privacy data is combined with a timestamp to obtain dynamic combination data. The dynamic combination data is encrypted by using a national encryption SM2 algorithm to obtain the privacy encryption data.

[0013] In a possible design, the generation of the transaction identifier by using the publicly verifiable data and the privacy encryption data includes: The publicly verifiable data and the privacy encryption data are respectively subjected to hash calculation to obtain a first hash value and a second hash value. The first hash value and the second hash value are combined to obtain the transaction identifier.

[0014] In a possible design, the zero-knowledge proof adopts a zk-SNARKs zero-knowledge proof.

[0015] In a second aspect, a digital asset transaction system based on a distributed ledger is provided, including a request acquisition unit, a privacy encryption unit, a transaction generation unit, a transaction arrangement unit, a transaction matching unit, a data submission unit, and a delivery and accounting unit, wherein: The request acquisition unit is configured to acquire an original transaction request initiated by a buyer transaction node, and parse the original transaction request to extract key privacy data and publicly verifiable data from the original transaction request. A privacy encryption unit is configured to encrypt critical privacy data dynamically to obtain privacy encrypted data; A transaction generation unit is configured to generate a transaction identifier by using the publicly verifiable data and the privacy encrypted data, and to pack the publicly verifiable data and the transaction identifier to generate a lightweight transaction request; A transaction arrangement unit is configured to arrange the lightweight transaction request into a transaction queue, and to perform transaction block proposal processing on the transaction queue to obtain a transaction block proposal containing the lightweight transaction request; A transaction matching unit is configured to perform transaction matching on the transaction block proposal based on a blockchain verifiable engine, and to generate a matching result of the lightweight transaction request and a corresponding zero-knowledge proof when the transaction is reached; A data submission unit is configured to jointly submit the publicly verifiable data, the transaction identifier, the matching result, and the zero-knowledge proof to a distributed ledger; A delivery and accounting unit is configured to perform validity verification on the zero-knowledge proof based on a smart contract deployed on the distributed ledger, and to execute digital asset delivery according to the matching result and write the publicly verifiable data and the transaction identifier into the distributed ledger after the validity verification is passed.

[0016] In a third aspect, a digital asset transaction system based on a distributed ledger is provided, including a plurality of service nodes, each service node including: A memory is configured to store instructions; A processor is configured to read the instructions stored in the memory and participate in executing the digital asset transaction method based on the distributed ledger according to the instructions.

[0017] Beneficial effects: The present application realizes the "availability and invisibility" of information before transaction by the "off-chain security processing" and "on-chain verifiable execution" mechanism, ensures the high security and privacy of the whole transaction process, especially the pre-accounting link, and provides end-to-end security protection in combination with zero-knowledge proof; By combining high-load order matching with efficient off-chain execution and lightweight on-chain verification, high throughput and low latency transaction experience is realized, transaction efficiency comparable to centralized platforms is realized, and absolute transparency and fairness of transaction matching and clearing are guaranteed; By submitting the key operation result to the smart contract for verification processing, the core elements of the transaction are stored on the distributed ledger to ensure the openness and transparency of the process; Through the transaction identifier and the authorized access mechanism, the necessary audit tracking path is provided for the regulatory authorities; It has important value for promoting decentralized finance and popularizing a wider digital asset ecosystem. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the accompanying drawings in the following description only constitute some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained from these drawings without creative labor.

[0019] Figure 1 A flowchart of the method in Embodiment 1 of the present application is shown. Figure 2 A schematic diagram of the system in Embodiment 2 of the present application is shown. DETAILED DESCRIPTION

[0020] It should be noted that the description of these embodiments is used to help understand the present application, but does not constitute a limitation of the present application. The specific structures and functional details disclosed herein are only used to describe the example embodiments of the present application. However, the present application can be embodied in many alternative forms, and should not be understood as limited in the embodiments set forth herein.

[0021] It should be understood that, unless otherwise explicitly specified and limited, the corresponding terms should be broadly understood, for example, "connection" can be fixed connection, or detachable connection, or integrally connected; can be directly connected, or indirectly connected through intermediate medium, or internal communication of two elements. For those skilled in the art, the specific meaning of the above terms in the embodiments can be understood according to the specific circumstances.

[0022] In the following description, specific details are provided to facilitate a full understanding of the example embodiments. However, those skilled in the art should understand that the example embodiments can be implemented without these specific details. For example, devices can be shown in block diagrams to avoid unnecessary details that make the examples unclear. In other embodiments, well-known processes, structures and techniques can not be shown in unnecessary details to avoid obscuring the embodiments.

[0023] Embodiment 1 The present embodiment provides a digital asset transaction method based on distributed ledger, which can be applied to a corresponding decentralized network system, such as Figure 1 As shown, the method comprises the following steps: S1. Obtain the original transaction request initiated by the buyer transaction node, and parse the original transaction request to extract key privacy data and publicly verifiable data from the original transaction request.

[0024] In specific implementation, the buyer transaction node can first initiate an original transaction request. After the system obtains the original transaction request initiated by the buyer transaction node, the original transaction request is parsed through a pre-transaction data preprocessing mechanism, and key privacy data and publicly verifiable data are extracted from the original transaction request. The key privacy data includes buyer identity information and buyer transaction node IP address, etc. The publicly verifiable data includes timestamp, digital asset type, transaction quantity, transaction price, and buyer fund pool identifier, etc.

[0025] S2. The key privacy data is dynamically encrypted to obtain privacy encrypted data.

[0026] In specific implementation, for the key privacy data, it can be combined with the timestamp to obtain dynamic combination data, and then the dynamic combination data is encrypted by using the SM2 encryption algorithm to obtain the privacy encrypted data.

[0027] S3. The publicly verifiable data and the privacy encrypted data are used to generate a transaction identifier, and the publicly verifiable data and the transaction identifier are packaged to generate a lightweight transaction request.

[0028] In specific implementation, the publicly verifiable data and the privacy encrypted data can be subjected to hash calculation respectively to obtain a first hash value and a second hash value, and then the first hash value and the second hash value are combined to obtain the transaction identifier. Then the publicly verifiable data and the transaction identifier are packaged to generate the lightweight transaction request.

[0029] Meanwhile, after obtaining the privacy encrypted data and the transaction identifier, the privacy encrypted data can be stored in the privacy storage area (such as the trusted execution environment TEE) specified by the buyer transaction node in association with the corresponding transaction identifier, or the privacy encrypted data can be subjected to data segmentation to obtain a plurality of privacy encrypted data blocks, and then each privacy encrypted data block is stored in the corresponding trusted node specified by the buyer transaction node in association with the corresponding transaction identifier.

[0030] S4. The lightweight transaction request is sorted into a transaction queue, and the transaction queue is subjected to transaction block proposal processing to obtain a transaction block proposal containing the lightweight transaction request.

[0031] In specific implementation, the generated lightweight transaction request can be sorted into a transaction queue by a sorting node, and the transaction queue is subjected to transaction block proposal processing to obtain a transaction block proposal containing the lightweight transaction request. The sorting node is responsible for receiving lightweight transaction requests from the entire network, and temporarily sorting and batch packaging the lightweight transaction requests according to their arrival order or specific rules (such as price-time priority) to form a transaction block proposal.

[0032] S5. The transaction block proposal is traded by the blockchain verifiable engine, and when the transaction is reached, the matching result of the lightweight transaction request and the corresponding zero-knowledge proof are generated.

[0033] In specific implementation, the transaction block proposal can be traded by the blockchain verifiable engine, which performs efficient order book management and matching logic off-chain. Once a transaction is reached, the blockchain verifiable engine generates a matching result and a corresponding zero-knowledge proof for this matching. Exemplarily, the matching result includes the matching relationship of the buyer and seller, the type of digital assets traded, the number of digital assets traded, and the price of digital assets traded, etc. The matching relationship of the buyer and seller includes the matching relationship of the buyer pool identifier and the seller pool identifier. The zero-knowledge proof can be a zk-SNARKs zero-knowledge proof, which can verify that: 1. The matching complies with the public rules (such as price priority); 2. The consistency of the input request and the output result; 3. No undisclosed information is used for manipulation.

[0034] S6. The publicly verifiable data, transaction identifier, matching result, and zero-knowledge proof are jointly submitted to the distributed ledger.

[0035] In specific implementation, the publicly verifiable data, transaction identifier, matching result, and zero-knowledge proof generated during the transaction process are jointly submitted to the distributed ledger for subsequent processing. The distributed ledger is a database shared, replicated, and synchronized among network members. The distributed ledger records transactions between network participants, such as the exchange of assets or data, which reduces the time and cost of resolving different ledgers. A specific form of the distributed ledger is the blockchain, which links data in the form of "blocks" in chronological order into a chain structure.

[0036] S7. The validity of the zero-knowledge proof is verified based on the smart contract deployed on the distributed ledger, and after the validity verification is passed, the digital asset delivery is executed according to the matching result, and the publicly verifiable data and transaction identifier are associated and written into the distributed ledger.

[0037] In specific implementation, the validity of the zero-knowledge proof is automatically verified by the smart contract deployed on the distributed ledger, and after the verification is passed, the digital asset delivery and settlement are executed according to the matching result, i.e., the digital asset transfer between the seller pool and the buyer pool corresponding to the type and number of digital assets traded is completed (including automatic liquidation based on the transaction price) according to the matching relationship of the buyer pool identifier and the seller pool identifier. At the same time, the publicly verifiable data and transaction identifier are associated and written into the distributed ledger, realizing the distributed ledger storage of the core elements of the transaction.

[0038] When the subsequent data compliance audit node performs transaction audit tracking, the public transaction identifier and the publicly verifiable data can be obtained from the distributed ledger, and then the audit request is performed by using the audit authorization key and the transaction identifier. The decentralized network system performs key verification based on the audit authorization key, and after the key verification is passed, the privacy encryption data is called from the privacy storage area according to the transaction identifier, or the privacy encryption data blocks are respectively called from each credit node according to the transaction identifier, and the privacy encryption data blocks are used to form the privacy encryption data. The privacy encryption data is sent to the data compliance audit node, and the data compliance audit node generates the check transaction identifier by using the privacy encryption data and the publicly verifiable data, and performs check comparison by using the check transaction identifier and the transaction identifier, to obtain the corresponding data compliance audit result.

[0039] The method realizes the "availability and invisibility" of the information before the transaction by the "off-chain security processing" and "on-chain verifiable execution" mechanism, ensures the high security and privacy of the whole transaction process, especially the pre-accounting link, and provides end-to-end security protection in combination with zero-knowledge proof; by combining the high-load order matching with the efficient off-chain execution and the lightweight on-chain verification, a high-throughput and low-latency transaction experience is realized, the transaction efficiency comparable to the centralized platform is realized, and the absolute transparency and fairness of transaction matching and clearing are ensured; by submitting the key operation result to the smart contract for verification processing, the core elements of the transaction are stored in the distributed ledger, ensuring the openness and transparency of the process; by using the transaction identifier and the authorized access mechanism, the necessary audit tracking path is provided for the regulatory authorities; it has important value for promoting decentralized finance and popularizing a wider digital asset ecosystem.

[0040] Embodiment 2 The embodiment provides a digital asset transaction system based on a distributed ledger, as shown in Figure 2 The transaction generation unit, the transaction arrangement unit, the transaction matching unit, the data submission unit and the delivery and accounting unit are used to perform the following steps: The request acquisition unit is used to acquire the original transaction request initiated by the buyer transaction node, and to parse the original transaction request to extract the key privacy data and the publicly verifiable data from the original transaction request; The privacy encryption unit is used to dynamically encrypt the key privacy data to obtain the privacy encryption data; The transaction generation unit is used to generate a transaction identifier by using the publicly verifiable data and the privacy encryption data, and to pack the publicly verifiable data and the transaction identifier to generate a lightweight transaction request; The transaction arrangement unit is used to arrange the lightweight transaction request into a transaction queue, and to perform transaction block proposal processing on the transaction queue to obtain a transaction block proposal containing the lightweight transaction request; The transaction matching unit is configured to match the transaction block proposal based on the blockchain verifiable engine, and generate a matching result of the lightweight transaction request and a corresponding zero-knowledge proof when the transaction is reached. The data submission unit is configured to jointly submit the publicly verifiable data, the transaction identifier, the matching result and the zero-knowledge proof to the distributed ledger. The delivery and accounting unit is configured to verify the validity of the zero-knowledge proof based on the smart contract deployed on the distributed ledger, and execute the delivery of the digital asset according to the matching result after the validity verification is passed, and write the publicly verifiable data and the transaction identifier to the distributed ledger.

[0041] Embodiment 3 The embodiment provides a distributed ledger-based digital asset transaction system, which is used to execute the distributed ledger-based digital asset transaction method in Embodiment 1. The system includes a plurality of server nodes, and each server node includes a data interface, a memory and a processor at the hardware level. Optionally, each server node further includes an internal bus, and the processor, the memory and the data interface are connected to each other through the internal bus. The internal bus can be a Peripheral Component Interconnect Eexpress (PCIe) bus, and the bus can be divided into an address bus, a data bus, a control bus and the like. The memory can include, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Flash Memory, a First Input First Output (FIFO) memory and / or a First In Last Out (FILO) memory and the like. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP) and the like; and can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0042] Finally, it should be noted that the above description is only the preferred embodiment of the present application, and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A digital asset transaction method based on distributed ledger, characterized in that, include: Obtain the original transaction request initiated by the buyer's transaction node, parse the original transaction request, and extract key privacy data and publicly verifiable data from the original transaction request; Key privacy data is dynamically encrypted to obtain privacy-encrypted data; A transaction identifier is generated using publicly verifiable data and privacy-encrypted data. The publicly verifiable data and the transaction identifier are then packaged to generate a lightweight transaction request. The lightweight transaction request is queued into a transaction queue, and the transaction queue is processed into a transaction block proposal to obtain a transaction block proposal containing the lightweight transaction request. The blockchain verifiable engine matches transaction block proposals and generates a lightweight transaction request matching result and corresponding zero-knowledge proof when a transaction is completed. The publicly verifiable data, transaction identifier, matching result and zero-knowledge proof are jointly submitted to the distributed ledger. The validity of zero-knowledge proofs is verified by smart contracts deployed on a distributed ledger. After the validity verification is passed, digital asset delivery is executed according to the matching results, and publicly verifiable data and transaction identifiers are associated and written into the distributed ledger.

2. The digital asset transaction method based on distributed ledger according to claim 1, characterized in that, The method further includes: associating the privacy-encrypted data with the corresponding transaction identifier and storing it in the privacy storage area designated by the buyer's transaction node; obtaining the audit authorization key and transaction identifier sent by the data compliance audit node; performing key verification on the audit authorization key, and retrieving the privacy-encrypted data from the privacy storage area based on the transaction identifier after the key verification is successful; sending the privacy-encrypted data to the data compliance audit node, enabling the data compliance audit node to generate a verification transaction identifier using the privacy-encrypted data and publicly verifiable data, and performing a verification comparison between the verification transaction identifier and the transaction identifier to obtain the corresponding data compliance audit result, wherein the publicly verifiable data and the transaction identifier are both obtained by the data compliance audit node from the distributed ledger.

3. The digital asset transaction method based on distributed ledger according to claim 1, characterized in that, The method further includes: performing data segmentation on the privacy-encrypted data to obtain several privacy-encrypted data blocks; associating each privacy-encrypted data block with a corresponding transaction identifier and storing them respectively to each authorized node designated by the buyer's transaction node; obtaining the audit authorization key and transaction identifier sent by the data compliance audit node; performing key verification on the audit authorization key, and after the key verification is successful, retrieving the privacy-encrypted data blocks from each authorized node according to the transaction identifier, and using each privacy-encrypted data block to assemble privacy-encrypted data; sending the privacy-encrypted data to the data compliance audit node, enabling the data compliance audit node to generate a verification transaction identifier using the privacy-encrypted data and publicly verifiable data, and performing verification comparison using the verification transaction identifier and the transaction identifier to obtain the corresponding data compliance audit result, wherein the publicly verifiable data and the transaction identifier are both obtained by the data compliance audit node from the distributed ledger.

4. The digital asset transaction method based on distributed ledger according to claim 1, characterized in that, The key privacy data includes the buyer's identity information and the buyer's transaction node IP address. The publicly verifiable data includes timestamps, digital asset types, transaction quantities, transaction prices, and the buyer's fund pool identifier.

5. A digital asset transaction method based on distributed ledger according to claim 4, characterized in that, The matching result includes the buyer-seller matching relationship, the type of digital asset traded, and the quantity of digital assets traded. The buyer-seller matching relationship includes the matching relationship between the buyer's fund pool identifier and the seller's fund pool identifier. The step of executing digital asset delivery based on the matching result includes: completing the transfer of digital assets between the seller's fund pool and the buyer's fund pool based on the matching relationship between the buyer's fund pool identifier and the seller's fund pool identifier, specifying the type and quantity of digital assets traded.

6. A digital asset transaction method based on distributed ledger according to claim 4, characterized in that, The process of dynamically encrypting key privacy data to obtain privacy-encrypted data includes: combining key privacy data with a timestamp to obtain dynamically combined data; and encrypting the dynamically combined data using the national cryptographic SM2 encryption algorithm to obtain privacy-encrypted data.

7. The digital asset transaction method based on distributed ledger according to claim 1, characterized in that, The step of generating a transaction identifier using publicly verifiable data and private encrypted data includes: performing hash calculations on the publicly verifiable data and the private encrypted data respectively to obtain a first hash value and a second hash value; and combining the first hash value and the second hash value to obtain the transaction identifier.

8. The digital asset transaction method based on distributed ledger according to claim 1, characterized in that, The zero-knowledge proof uses zk-SNARKs zero-knowledge proof.

9. A digital asset trading system based on distributed ledger, characterized in that, The system comprises a request acquisition unit, a privacy encryption unit, a transaction generation unit, a transaction orchestration unit, a transaction matching unit, a data submission unit, and a settlement and accounting unit. Specifically: the request acquisition unit acquires the original transaction request initiated by the buyer's trading node, parses the original transaction request, and extracts key privacy data and publicly verifiable data from it; the privacy encryption unit dynamically encrypts the key privacy data to obtain privacy-encrypted data; the transaction generation unit generates a transaction identifier using the publicly verifiable data and the privacy-encrypted data, and packages the publicly verifiable data and the transaction identifier to generate a lightweight transaction request; the transaction orchestration unit queues the lightweight transaction request into a transaction queue. The system processes transaction block proposals in the transaction queue to obtain transaction block proposals containing lightweight transaction requests. A transaction matching unit matches transaction block proposals based on the blockchain's verifiable engine, generating a matching result for the lightweight transaction request and the corresponding zero-knowledge proof upon transaction completion. A data submission unit submits publicly verifiable data, transaction identifiers, matching results, and zero-knowledge proofs to the distributed ledger. A settlement and accounting unit verifies the validity of the zero-knowledge proofs based on smart contracts deployed on the distributed ledger, and, upon successful verification, executes digital asset settlement based on the matching result, associating publicly verifiable data and transaction identifiers with the distributed ledger.

10. A digital asset trading system based on distributed ledger, characterized in that, It includes several service nodes, each service node comprising: a memory for storing instructions; and a processor for reading the instructions stored in the memory and participating in the execution of the digital asset transaction method based on a distributed ledger as described in any one of claims 1-8 according to the instructions.

Images