Real-name NFT transaction methods, devices, equipment and storage media

Abstract

This application discloses a method, apparatus, device, and storage medium for real-name NFT transactions. The method includes the following steps: generating a shadow transaction of a transaction information NFT corresponding to a transaction request on an identity blockchain; the transaction information NFT includes at least a real-name wallet associated with the anonymous wallets of both parties in the NFT transaction; detecting the completion of the shadow transaction, and generating a real transaction of the asset NFT corresponding to the transaction request on a public blockchain based on a smart contract. This application, based on a smart contract, generates a real transaction on a public blockchain through an anonymous wallet associated with the real-name wallet. This allows for indirect oversight of real transactions even if direct oversight of real transactions conducted by anonymous wallets on the public blockchain is not possible, as oversight can be achieved through shadow transactions conducted by real-name wallets associated with anonymous wallets. This improves the convenience of overseeing NFT transactions.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a method, apparatus, device and storage medium for real-name NFT transactions. Background Technology

[0002] Reference Figure 1 In existing technology, the asset seller owns wallets A, B, and C, while the asset buyer owns wallets D and E. When the asset seller conducts an NFT (Non-Fungible Token) transaction with the asset buyer on the asset blockchain (public blockchain) through wallet A, the asset buyer receives the NFT through wallets D and E. Wallets A, B, C, D, and E are all anonymous wallets, meaning the NFT transaction is conducted anonymously, making it difficult to regulate the NFT transaction. Summary of the Invention

[0003] In view of this, embodiments of this application provide a method, apparatus, device, and storage medium for real-name NFT transactions, aiming to improve the convenience of supervising NFT transactions.

[0004] To achieve the above objectives, this application provides a method for real-name NFT transactions, the method comprising:

[0005] On the identity chain, a shadow transaction of the transaction information NFT corresponding to the transaction request is generated; the transaction information NFT includes at least real-name wallets associated with the anonymous wallets of both parties to the NFT transaction;

[0006] Upon detection of the completion of the shadow transaction, a real transaction of the asset NFT corresponding to the transaction request is generated on the public blockchain based on the smart contract.

[0007] For example, before generating the shadow transaction of the NFT corresponding to the transaction request on the identity chain, the process includes:

[0008] Receive transaction requests from asset sellers for NFT assets on the asset chain they hold;

[0009] Submit the transaction request to the identity chain;

[0010] Receive the risk assessment results transmitted back from the identity chain;

[0011] If the risk assessment result indicates that the transaction request passes the risk assessment, then the shadow transaction step of generating the transaction information NFT corresponding to the transaction request on the identity chain is executed.

[0012] Furthermore, to achieve the above objectives, this application also provides a method for real-name NFT transactions, the method being applied to member devices of an identity chain, the method comprising:

[0013] Generate a real-name wallet associated with an anonymous wallet in the asset chain; the real-name wallet includes the seller's real-name wallet and the buyer's real-name wallet in the transaction request;

[0014] Ownership of the transaction information NFT corresponding to the transaction request is transferred to the asset buyer; the transaction information NFT includes at least the seller's real-name wallet and the buyer's real-name wallet.

[0015] For example, before generating the real-name wallet associated with the anonymous wallet in the asset chain, the process includes:

[0016] Receive the real-name authentication information of NFT traders, and perform real-name authentication on the NFT traders based on the real-name authentication information;

[0017] If the real-name authentication is successful, then the step of generating a real-name wallet associated with the anonymous wallet in the asset chain is executed.

[0018] For example, generating a real-name wallet associated with an anonymous wallet in the asset chain includes:

[0019] Based on the real-name authentication information, a real-name wallet for the NFT trader is generated;

[0020] Receive the anonymous wallet information submitted by the NFT trader, and associate the real-name wallet with the anonymous wallet information.

[0021] For example, the method further includes:

[0022] Receive query requests from transaction monitoring equipment;

[0023] The transaction information NFT is sent to the transaction monitoring device so that the transaction monitoring device can monitor the transactions on the identity chain.

[0024] For example, before transferring ownership of the transaction information NFT corresponding to the transaction request to the asset buyer, the process includes:

[0025] Receive transaction requests submitted by the transaction management device;

[0026] A risk assessment is performed on the transaction request to obtain the risk assessment results;

[0027] The risk assessment results are sent back to the transaction management device.

[0028] Furthermore, to achieve the above objectives, this application also provides a real-name NFT transaction device, the device comprising:

[0029] The first generation module is used to generate a shadow transaction of the transaction information NFT corresponding to the transaction request on the identity chain; the transaction information NFT includes at least real-name wallets associated with the anonymous wallets of both parties to the NFT transaction;

[0030] The second generation module is used to detect the completion of the shadow transaction and, based on the smart contract, generate the real transaction of the asset NFT corresponding to the transaction request on the public chain.

[0031] Furthermore, to achieve the above objectives, this application also provides a real-name NFT transaction device, the device comprising:

[0032] The generation module is used to generate real-name wallets associated with anonymous wallets in the asset chain; the real-name wallets include the seller's real-name wallet and the buyer's real-name wallet in the transaction request.

[0033] The transfer module is used to transfer ownership of the transaction information NFT corresponding to the transaction request to the asset buyer; the transaction information NFT includes at least the seller's real-name wallet and the buyer's real-name wallet.

[0034] In addition, to achieve the above objectives, this application also provides a transaction management device, which includes a memory, a processor, and a real-name NFT transaction program stored in the memory and executable on the processor. When the real-name NFT transaction program is executed by the processor, it implements the steps of the real-name NFT transaction method as described above.

[0035] In addition, to achieve the above objectives, this application also provides a member device, which includes a memory, a processor, and a real-name NFT transaction program stored in the memory and executable on the processor. When the real-name NFT transaction program is executed by the processor, it implements the steps of the real-name NFT transaction method as described above.

[0036] In addition, to achieve the above objectives, this application also provides a computer-readable storage medium storing a real-name NFT transaction program, which, when executed by a processor, implements the steps of the real-name NFT transaction method as described above.

[0037] Compared to existing technologies where NFT transactions between asset buyers and sellers are conducted through anonymous wallets, making it difficult to regulate these transactions, this application generates a shadow transaction of the NFT transaction information corresponding to the transaction request on the identity chain. This transaction information NFT includes at least a real-name wallet associated with the anonymous wallets of both parties involved in the NFT transaction. Upon detection of the shadow transaction's completion, a real transaction of the asset NFT corresponding to the transaction request is generated on the public chain based on a smart contract. Before the real transaction of the asset NFT, this application also conducts a shadow transaction on the identity chain. During the shadow transaction, the NFT trading parties use the transaction information NFT including both parties' real-name wallets. After the shadow transaction is completed, a real transaction is generated on the public chain through the anonymous wallet associated with the real-name wallet, based on a smart contract. This allows for indirect regulation of the real transaction, even if the real transaction conducted by the anonymous wallet on the public chain cannot be directly regulated, but the shadow transaction conducted through the real-name wallet associated with the anonymous wallet can be regulated, thereby improving the convenience of regulating NFT transactions. Attached Figure Description

[0038] Figure 1 This is a schematic diagram illustrating a scenario where NFT traders conduct transactions through anonymous wallets, as covered in the background technology of this application.

[0039] Figure 2 This is a flowchart illustrating the first embodiment of the real-name NFT transaction method of this application;

[0040] Figure 3 This is a schematic diagram of a scenario of NFT transaction in the first embodiment of the real-name NFT transaction method of this application;

[0041] Figure 4 This is another schematic diagram of an NFT transaction scenario in the first embodiment of the real-name NFT transaction method of this application;

[0042] Figure 5 This is another schematic diagram of an NFT transaction scenario in the first embodiment of the real-name NFT transaction method of this application;

[0043] Figure 6 This is a flowchart illustrating the second embodiment of the real-name NFT transaction method of this application;

[0044] Figure 7 This is a schematic diagram illustrating a scenario in the second embodiment of the real-name NFT transaction method of this application, showing the association between a real-name wallet and an anonymous wallet;

[0045] Figure 8 This is a schematic diagram illustrating a scenario in which a transaction monitoring device monitors NFT transactions, as described in the second embodiment of the real-name NFT transaction method of this application.

[0046] Figure 9This is a schematic diagram of the hardware operating environment involved in the first embodiment of this application;

[0047] Figure 10 This is a schematic diagram of the hardware operating environment involved in the second embodiment of this application.

[0048] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0049] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0050] This application provides a method for real-name NFT transactions, referring to... Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the real-name NFT transaction method of this application.

[0051] This application provides an embodiment of a real-name NFT transaction method. It should be noted that although the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here. The real-name NFT transaction method can be applied to a transaction management device, which can be a terminal or a server.

[0052] For ease of description, the following omits the individual steps of the real-name NFT transaction method. The real-name NFT transaction method includes:

[0053] Step S210: On the identity chain, generate a shadow transaction of the transaction information NFT corresponding to the transaction request; the transaction information NFT includes at least real-name wallets associated with the anonymous wallets of both parties to the NFT transaction.

[0054] After an asset seller initiates a transaction request, the system queries the real-name wallet corresponding to the seller's anonymous wallet on the asset chain (public chain), and also queries the real-name wallet corresponding to the anonymous wallet of the asset buyer to whom the transaction request is directed on the asset chain. The real-name wallet is located on the identity chain (a private chain used to implement real-name registration for NFT transactions). The anonymous wallet is not bound to real-name information, while the real-name wallet is bound to real-name information.

[0055] NFTs are data units on a blockchain digital ledger. Each NFT can represent a unique digital document, serving as an electronic certificate or proof of ownership of virtual goods. Due to their non-fungible nature, NFTs can represent digital assets such as paintings, artworks, audio, video, game items, or other forms of creative works. While the artwork itself can be infinitely copied, the NFT representing the artwork can be fully traced on its underlying blockchain, thus providing buyers with proof of ownership of the digital asset.

[0056] A private blockchain is a dedicated blockchain jointly managed by multiple institutions. Each institution manages one or more nodes, and data within the private blockchain can only be read, written, and sent between different institutions within the same private blockchain. Compared to public blockchains, private blockchains offer faster transaction speeds, higher security, and better privacy protection. Furthermore, since only a few widely recognized high-computing-power nodes are needed for confirmation during the transaction process, transaction costs are significantly reduced. For example, a private blockchain composed of 20 nodes can have transactions confirmed by 5 core nodes (high-computing-power nodes), and then these 5 core nodes can distribute the confirmation results to the remaining 15 nodes within the private blockchain.

[0057] Regarding transaction costs, since NFT transactions occur on the blockchain, and blockchain activities (such as minting and transferring) require computing resources, each NFT transaction consumes computing resources. This cost is borne by both parties to the transaction and is paid to the blockchain computing power provider (commonly known as a miner).

[0058] A public blockchain, also known as a "public blockchain," is a consensus-based blockchain open to everyone. On a public blockchain, nodes can freely join and leave. Anyone can freely read data, initiate transactions, and every transaction is effectively confirmed. It features anonymity, low barriers to entry, complete decentralization, immunity to developer influence, and transparent and tamper-proof data. For example, Bitcoin (BTC) uses public blockchain technology. Compared to private blockchains, public blockchains require more nodes to confirm transactions, resulting in higher transaction costs. For instance, Ethereum has 100,000 nodes, requiring 50,000 of them for confirmation.

[0059] For example, a transaction request may include the transaction amount, the anonymous wallets (wallet addresses) of both parties in the NFT transaction, etc.

[0060] For example, shadow trading does not involve trading asset NFTs. Because real-name information is involved, shadow trading is conducted on a private blockchain to ensure information security. The purpose is to record relevant information of the real transaction through the traded transaction information NFT.

[0061] For example, relevant information for a real transaction includes the real-name information of both parties in the NFT transaction, the real-name wallets on the identity chain, and the original NFT (i.e., asset NFT) information.

[0062] For example, an individual can only have one real-name wallet, but can have multiple anonymous wallets. These multiple anonymous wallets can be on one or more public blockchains. For real-name wallets associated with anonymous wallets, the real-name wallet is associated with all of the individual's anonymous wallets on all public blockchains. Thus, it is possible to query all of an individual's anonymous wallets through a real-name wallet. In other words, the real-name wallet enables the supervision of NFT transactions made by the individual through any of their anonymous wallets.

[0063] It should be noted that "association" means that after a real-name wallet and an anonymous wallet are associated, the real-name wallet can find the associated anonymous wallet, or vice versa.

[0064] For example, refer to Figure 3 , Figure 3 This is a schematic diagram of an NFT transaction scenario. Before the shadow transaction of the NFT corresponding to the transaction request is generated on the identity chain, the process includes:

[0065] Step a: Receive transaction requests from asset sellers for NFT assets on the asset chain they hold;

[0066] Reference Figure 4 , Figure 4 This is another illustration of an NFT transaction scenario. Based on a smart contract, when a transaction request is detected from an asset seller regarding an NFT held on the asset chain, the transaction request is intercepted, i.e., the transaction request is accepted.

[0067] Step b: Submit the transaction request to the identity chain;

[0068] Step c: Receive the risk assessment results returned by the identity chain;

[0069] The transaction request is submitted to the identity chain. If the risk assessment result is that the transaction request fails the risk assessment, the transaction request is rejected. At this time, the transaction is terminated, and a notification message is sent to the transaction monitoring device. The notification message is used to inform the transaction monitoring device that a risky transaction request has occurred.

[0070] For example, transaction monitoring equipment is equipment of a regulatory agency.

[0071] Step d: If the risk assessment result is that the transaction request passes the risk assessment, then the shadow transaction step of generating the transaction information NFT corresponding to the transaction request on the identity chain is executed.

[0072] Step S220: Upon detecting the completion of the shadow transaction, a real transaction of the asset NFT corresponding to the transaction request is generated on the public blockchain based on the smart contract.

[0073] Reference Figure 5, Figure 5 This is another illustration of an NFT transaction scenario.

[0074] After the shadow transaction is completed, the transaction request is automatically released based on the smart contract, thereby completing the real transaction corresponding to the transaction request, that is, transferring the asset NFT from the asset seller's anonymous wallet to the asset buyer's anonymous wallet.

[0075] Compared to existing technologies where NFT transactions between asset buyers and sellers are conducted through anonymous wallets, making it difficult to regulate these transactions, this application generates a shadow transaction of the NFT transaction information corresponding to the transaction request on the identity chain. This transaction information NFT includes at least a real-name wallet associated with the anonymous wallets of both parties involved in the NFT transaction. Upon detection of the shadow transaction's completion, a real transaction of the asset NFT corresponding to the transaction request is generated on the public chain based on a smart contract. Before the real transaction of the asset NFT, this application also conducts a shadow transaction on the identity chain. During the shadow transaction, the NFT trading parties use the transaction information NFT including both parties' real-name wallets. After the shadow transaction is completed, a real transaction is generated on the public chain through the anonymous wallet associated with the real-name wallet, based on a smart contract. This allows for indirect regulation of the real transaction, even if the real transaction conducted by the anonymous wallet on the public chain cannot be directly regulated, but the shadow transaction conducted through the real-name wallet associated with the anonymous wallet can be regulated, thereby improving the convenience of regulating NFT transactions.

[0076] Furthermore, this application provides a method for real-name NFT transactions, referring to... Figure 6 , Figure 6 This is a flowchart illustrating the second embodiment of the real-name NFT transaction method of this application.

[0077] This application provides an embodiment of a real-name NFT transaction method. It should be noted that although the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order. The real-name NFT transaction method can be applied to member devices of an identity chain, where the member device can be a terminal or a server.

[0078] For ease of description, the following omits the individual steps of the real-name NFT transaction method. The real-name NFT transaction method includes:

[0079] Step S610: Generate a real-name wallet that is associated with the anonymous wallet in the asset chain; the real-name wallet includes the seller's real-name wallet and the buyer's real-name wallet in the transaction request.

[0080] For example, a transaction request may include the transaction amount, the anonymous wallets (wallet addresses) of both parties in the NFT transaction, etc. The anonymous wallets are not linked to real-name information, while the real-name wallets are linked to real-name information.

[0081] For example, a public blockchain (asset blockchain), also known as a "public chain," is a consensus-based blockchain open to everyone. On a public blockchain, nodes can freely join and leave. Anyone can freely read data, initiate transactions, and every transaction is effectively confirmed. It features anonymity, low barriers to entry, complete decentralization, immunity to developer influence, and transparent and tamper-proof data. Bitcoin (BTC), for instance, uses public blockchain technology. Compared to private blockchains, public blockchains require more nodes to confirm transactions, resulting in higher transaction costs. For example, Ethereum has 100,000 nodes, requiring 50,000 of them for confirmation.

[0082] Reference Figure 7 , Figure 7 This is a schematic diagram illustrating the association between real-name wallets and anonymous wallets. Real-name wallet Ⅰ is the seller's real-name wallet for the asset seller, and real-name wallet Ⅱ is the buyer's real-name wallet for the asset buyer. Wallets A, B, C, D, E, and R are anonymous wallets; wallets A, B, C, and R are the anonymous wallets for the asset sellers, and wallets D and E are the anonymous wallets for the asset buyers. The seller's real-name wallet is associated with wallet R on asset chain 2, and wallets A, B, and C on the asset chain, respectively. The buyer's real-name wallet is associated with wallets D and E on the asset chain.

[0083] It should be noted that "association" means that after a real-name wallet and an anonymous wallet are associated, the real-name wallet can find the associated anonymous wallet, or vice versa.

[0084] For example, before generating the real-name wallet associated with the anonymous wallet in the asset chain, the process includes:

[0085] Step e: Receive the real-name authentication information of the NFT trader, and perform real-name authentication on the NFT trader based on the real-name authentication information;

[0086] For example, the real-name authentication information of NFT traders can be ID card information, social security card information, and facial information. In this embodiment, both the asset buyer and the asset seller are NFT traders.

[0087] Step f: If the real-name authentication is successful, then the step of generating a real-name wallet associated with the anonymous wallet in the asset chain is executed.

[0088] If real-name authentication is not passed, the NFT trader will be reminded to confirm whether the real-name authentication information provided is correct, or the NFT trader will be reminded to resubmit the real-name authentication information.

[0089] For example, generating a real-name wallet associated with an anonymous wallet in the asset chain includes:

[0090] Step g: Based on the real-name authentication information, generate the real-name wallet of the NFT trader;

[0091] A real-name wallet is generated and bound to real-name authentication information, so that the real-name wallet carries the real-name authentication information. That is, the real-name wallet points to the natural person who provided the real-name authentication information.

[0092] Step h: Receive the anonymous wallet information submitted by the NFT trader, and associate the real-name wallet with the anonymous wallet information.

[0093] For example, anonymous wallet information includes the address where the anonymous wallet is located and the asset chain on which the anonymous wallet is located.

[0094] For example, an individual can only have one real-name wallet, but can have multiple anonymous wallets. These multiple anonymous wallets can be on one or more public blockchains. For real-name wallets associated with anonymous wallets, the real-name wallet is associated with all of the individual's anonymous wallets on all public blockchains. Thus, it is possible to query all of an individual's anonymous wallets through a real-name wallet. In other words, the real-name wallet enables the supervision of NFT transactions made by the individual through any of their anonymous wallets.

[0095] Step S620: Transfer ownership of the transaction information NFT corresponding to the transaction request to the asset buyer; the transaction information NFT includes at least the seller's real-name wallet and the buyer's real-name wallet.

[0096] For example, a transaction information NFT records the real-name information of both parties in the NFT transaction, their real-name wallets on the identity chain, and the original NFT (i.e., asset NFT) information. This transaction information NFT facilitates the supervision of NFT transactions by transaction monitoring devices.

[0097] The transaction of transaction information NFTs is a shadow transaction, which is completed based on a smart contract by transferring the transaction information NFT from the seller's real-name wallet to the buyer's real-name wallet.

[0098] For example, before transferring ownership of the transaction information NFT corresponding to the transaction request to the asset buyer, the process includes:

[0099] Step i: Receive transaction requests submitted by the transaction management device;

[0100] The transaction management device is the transaction management device in the first embodiment described above.

[0101] Step j: Perform a risk assessment on the transaction request and obtain the risk assessment result;

[0102] Risk assessment includes evaluating the creditworthiness of both parties, the transaction amount, and the frequency of transactions. The assessment logic is pre-defined by the regulatory agency.

[0103] For example, the assessment logic includes whether the creditworthiness of both parties meets the credit requirements, whether the transaction amount meets the amount requirements, and whether the transaction frequency meets the frequency requirements. It can be understood that when the creditworthiness of both parties meets the credit requirements, the transaction amount meets the amount requirements, and the transaction frequency meets the frequency requirements, the risk assessment result is that the transaction request passes the risk assessment; when the creditworthiness of both parties does not meet the credit requirements, the transaction amount does not meet the amount requirements, and the transaction frequency does not meet the frequency requirements, the risk assessment result is that the transaction request fails the risk assessment.

[0104] To determine whether the credit scores of both parties in a transaction meet the credit score requirements, if either party's credit score is lower than a preset credit score threshold, then both parties' credit scores are deemed not to meet the requirements. Conversely, if both parties' credit scores are greater than or equal to the preset credit score threshold, then both parties' credit scores are deemed to meet the requirements. For example, if the preset credit score threshold is 50, the asset buyer's credit score is 40, and the asset seller's credit score is 60, then both parties' credit scores are deemed not to meet the requirements. However, if the preset credit score threshold is 50, the asset buyer's credit score is 60, and the asset seller's credit score is 70, then both parties' credit scores are deemed to meet the requirements. It can be understood that the credit score requirement is that both parties' credit scores are higher than the preset credit score threshold.

[0105] To determine if a transaction amount meets the requirements, if the transaction amount is greater than or equal to a preset transaction amount threshold, it is determined that the transaction amount does not meet the requirements; if the transaction amount is less than the preset transaction amount threshold, it is determined that the transaction amount meets the requirements. For example, if the preset transaction amount threshold is 500,000 and the transaction amount is 600,000, then the transaction amount does not meet the requirements; conversely, if the preset transaction amount threshold is 500,000 and the transaction amount is 400,000, then the transaction amount meets the requirements. It can be understood that the requirement is that the transaction amount is less than the preset transaction amount threshold.

[0106] To determine whether a trading frequency meets the requirements, if the trading frequency is greater than or equal to a preset trading frequency threshold, it is determined that the trading frequency does not meet the requirements; if the trading frequency is less than the preset trading frequency threshold, it is determined that the trading frequency meets the requirements. For example, if the preset trading frequency threshold is 1 time / week and the trading frequency is 1 time / day, then the trading frequency does not meet the requirements; conversely, if the preset trading frequency threshold is 1 time / week and the trading frequency is 1 time / month, then the trading frequency meets the requirements. It can be understood that the frequency requirement is that the trading frequency is less than the preset trading frequency threshold.

[0107] It should be noted that the preset credit rating threshold, preset transaction amount threshold, and preset transaction frequency threshold can all be set as needed, and this embodiment does not impose any specific limitations.

[0108] Step k: The risk assessment results are sent back to the transaction management device.

[0109] For example, refer to Figure 8 , Figure 8 This is a schematic diagram illustrating a scenario where a transaction monitoring device monitors NFT transactions. The method also includes:

[0110] Step 1: Receive query requests from transaction monitoring devices;

[0111] The query requests include requests to query real-name wallets based on real-name information and requests to query real-name wallets based on anonymous wallets. That is, the transaction monitoring device can directly query NFT transaction information in a real-name wallet, and it can also query NFT transaction information in a real-name wallet from an anonymous wallet. It can be understood that the transaction monitoring device queries real-name wallets, which involve identity information. Only authorized, transaction management, or transaction monitoring devices can view this information; other people or devices have no right to view it to protect the privacy of NFT traders.

[0112] Step m: Send the transaction information NFT to the transaction monitoring device so that the transaction monitoring device can monitor the transactions on the identity chain.

[0113] It is understandable that transaction information NFTs can meet the query needs of transaction monitoring devices for natural persons' transaction records.

[0114] This embodiment generates a real-name wallet associated with an anonymous wallet in the asset chain. The real-name wallet includes the seller's real-name wallet (for the asset seller in the transaction request) and the buyer's real-name wallet (for the asset buyer). Ownership of the transaction information NFT corresponding to the transaction request is transferred to the asset buyer. The transaction information NFT includes at least the seller's real-name wallet and the buyer's real-name wallet. This embodiment transfers the transaction information NFT within the identity chain, protecting the real information of NFT traders in the public chain while simultaneously storing this real information within the identity chain. This facilitates regulatory oversight of transaction information and prevents NFT traders from engaging in illegal activities.

[0115] In addition, this application also provides a real-name NFT transaction device, the device comprising:

[0116] The first generation module is used to generate a shadow transaction of the transaction information NFT corresponding to the transaction request on the identity chain; the transaction information NFT includes at least real-name wallets associated with the anonymous wallets of both parties to the NFT transaction;

[0117] The second generation module is used to detect the completion of the shadow transaction and, based on the smart contract, generate the real transaction of the asset NFT corresponding to the transaction request on the public chain.

[0118] For example, the real-name NFT transaction device further includes:

[0119] The first receiving module is used to receive transaction requests initiated by asset sellers for the NFT assets they hold on the asset chain.

[0120] The submission module is used to submit the transaction request to the identity chain;

[0121] The second receiving module is used to receive the risk assessment result returned by the identity chain; if the risk assessment result is that the transaction request passes the risk assessment, then the shadow transaction step of generating the transaction information NFT corresponding to the transaction request on the identity chain is executed.

[0122] The specific implementation method of the real-name NFT transaction device in this application is basically the same as the first embodiment of the real-name NFT transaction method described above, and will not be repeated here.

[0123] In addition, this application also provides a real-name NFT transaction device, the device comprising:

[0124] The generation module is used to generate real-name wallets associated with anonymous wallets in the asset chain; the real-name wallets include the seller's real-name wallet and the buyer's real-name wallet in the transaction request.

[0125] The transfer module is used to transfer ownership of the transaction information NFT corresponding to the transaction request to the asset buyer; the transaction information NFT includes at least the seller's real-name wallet and the buyer's real-name wallet.

[0126] For example, the real-name NFT transaction device further includes:

[0127] The first receiving module is used to receive the real-name authentication information of NFT traders, and to perform real-name authentication on the NFT traders based on the real-name authentication information; if the real-name authentication is successful, the step of generating a real-name wallet associated with the anonymous wallet in the asset chain is executed.

[0128] For example, the generation module is specifically used for:

[0129] Based on the real-name authentication information, a real-name wallet for the NFT trader is generated;

[0130] Receive the anonymous wallet information submitted by the NFT trader, and associate the real-name wallet with the anonymous wallet information.

[0131] For example, the real-name NFT transaction device further includes:

[0132] The second receiving module is used to receive query requests from the transaction monitoring equipment;

[0133] The sending module is used to send the transaction information NFT to the transaction monitoring device so that the transaction monitoring device can monitor the transactions on the identity chain.

[0134] For example, the real-name NFT transaction device further includes:

[0135] The third receiving module is used to receive transaction requests submitted by the transaction management device;

[0136] The assessment module is used to assess the risk of the transaction request and obtain the risk assessment result;

[0137] The feedback module is used to send the risk assessment results back to the transaction management device.

[0138] The specific implementation method of the real-name NFT transaction device in this application is basically the same as the second embodiment of the real-name NFT transaction method described above, and will not be repeated here.

[0139] Furthermore, this application also provides a transaction management device. In one possible implementation, Figure 9 This can be a schematic diagram of the hardware operating environment of the transaction management device.

[0140] like Figure 9 As shown, the transaction management device may include a processor 901, a communication interface 902, a memory 903, and a communication bus 904. The processor 901, the communication interface 902, and the memory 903 communicate with each other through the communication bus 904. The memory 903 is used to store computer programs. When the processor 901 executes the program stored in the memory 903, it implements the steps of the real-name NFT transaction method.

[0141] The communication bus 904 mentioned in the aforementioned transaction management device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus 904 can be divided into an address bus, a data bus, and a control bus, etc. For ease of illustration, it is represented by only one thick line in the figure, but this does not indicate that there is only one bus or one type of bus.

[0142] Communication interface 902 is used for communication between the above-mentioned transaction management device and other devices.

[0143] The memory 903 may include random access memory (RMD) or non-volatile memory (NM), such as at least one disk storage device. Optionally, the memory 903 may also be at least one storage device located remotely from the aforementioned processor 901.

[0144] The processor 901 mentioned above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it 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, or discrete hardware components.

[0145] The specific implementation method of the transaction management device in this application is basically the same as the first embodiment of the real-name NFT transaction method described above, and will not be repeated here.

[0146] Furthermore, this application also provides a member device. In one possible implementation, Figure 10 This can be a structural diagram of the hardware operating environment of member devices.

[0147] like Figure 10 As shown, the member device may include a processor 1001, a communication interface 1002, a memory 1003, and a communication bus 1004. The processor 1001, the communication interface 1002, and the memory 1003 communicate with each other through the communication bus 1004. The memory 1003 is used to store computer programs. When the processor 1001 executes the program stored in the memory 1003, it implements the steps of the real-name NFT transaction method.

[0148] The communication bus 1004 mentioned in the above-mentioned member devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus 1004 can be divided into an address bus, a data bus, and a control bus, etc. For ease of illustration, it is represented by only one thick line in the figure, but this does not indicate that there is only one bus or one type of bus.

[0149] Communication interface 1002 is used for communication between the aforementioned member devices and other devices.

[0150] The memory 1003 may include random access memory (RMD) or non-volatile memory (NM), such as at least one disk storage device. Optionally, the memory 1003 may also be at least one storage device located remotely from the aforementioned processor 1001.

[0151] The processor 1001 mentioned above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it 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, or discrete hardware components.

[0152] The specific implementation method of the transaction management device in this application is basically the same as the second embodiment of the real-name NFT transaction method described above, and will not be repeated here.

[0153] Furthermore, embodiments of this application also propose a computer-readable storage medium storing a real-name NFT transaction program, wherein the real-name NFT transaction program, when executed by a processor, implements the steps of the real-name NFT transaction method as described above.

[0154] The specific implementation of the computer-readable storage medium in this application is basically the same as the embodiments of the above-described real-name NFT transaction method, and will not be repeated here.

[0155] In addition, to achieve the above objectives, this application also provides a computer program product, comprising: a computer program, which, when executed by a processor, implements the steps of the real-name NFT transaction method as described above.

[0156] The specific implementation method of the computer program product in this application is basically the same as the various embodiments of the real-name NFT transaction method described above, and 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] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0159] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes: several instructions to cause a terminal device (which may be a mobile phone, computer, server, device, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0160] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for real-name NFT transactions, characterized in that, The method is applied to a transaction management device, and the method includes: On the identity chain, a shadow transaction of the transaction information NFT corresponding to the transaction request is generated; the transaction information NFT includes at least a real-name wallet associated with the anonymous wallets of both parties to the NFT transaction; wherein, the shadow transaction does not trade the asset NFT, but is conducted on the private chain; Upon detection of the completion of the shadow transaction, a real transaction of the asset NFT corresponding to the transaction request is generated on the public blockchain based on the smart contract.

2. The method as described in claim 1, characterized in that, Before generating the shadow transaction of the NFT corresponding to the transaction request on the identity chain, the process includes: Receive transaction requests from asset sellers for NFT assets on the asset chain they hold; Submit the transaction request to the identity chain; Receive the risk assessment results transmitted back from the identity chain; If the risk assessment result indicates that the transaction request passes the risk assessment, then the shadow transaction step of generating the transaction information NFT corresponding to the transaction request on the identity chain is executed.

3. A method for real-name NFT transactions, characterized in that, The method is applied to member devices of the identity chain, and the method includes: Generate a real-name wallet associated with an anonymous wallet in the asset chain; the real-name wallet includes the seller's real-name wallet and the buyer's real-name wallet in the transaction request; Ownership of the transaction information NFT corresponding to the transaction request is transferred to the asset buyer; the transaction information NFT includes at least the seller's real-name wallet and the buyer's real-name wallet.

4. The method as described in claim 3, characterized in that, Before generating the real-name wallet associated with the anonymous wallet in the asset chain, the following steps are included: Receive the real-name authentication information of NFT traders, and perform real-name authentication on the NFT traders based on the real-name authentication information; If the real-name authentication is successful, then the step of generating a real-name wallet associated with the anonymous wallet in the asset chain is executed.

5. The method as described in claim 4, characterized in that, The generation of a real-name wallet associated with an anonymous wallet in the asset chain includes: Based on the real-name authentication information, a real-name wallet for the NFT trader is generated; Receive the anonymous wallet information submitted by the NFT trader, and associate the real-name wallet with the anonymous wallet information.

6. The method as described in claim 3, characterized in that, The method further includes: Receive query requests from transaction monitoring equipment; The transaction information NFT is sent to the transaction monitoring device so that the transaction monitoring device can monitor the transactions on the identity chain.

7. The method as described in claim 3, characterized in that, Before transferring ownership of the transaction information NFT corresponding to the transaction request to the asset buyer, the process includes: Receive transaction requests submitted by the transaction management device; A risk assessment is performed on the transaction request to obtain the risk assessment results; The risk assessment results are transmitted back to the transaction management device.

8. A real-name NFT trading device, characterized in that, The device includes: The first generation module is used to generate a shadow transaction of the transaction information NFT corresponding to the transaction request on the identity chain; the transaction information NFT includes at least real-name wallets associated with the anonymous wallets of both parties to the NFT transaction; The second generation module is used to detect the completion of the shadow transaction and, based on the smart contract, generate the real transaction of the asset NFT corresponding to the transaction request on the public chain.

9. A transaction management device, characterized in that, The transaction management device includes a memory, a processor, and a real-name NFT transaction program stored in the memory and executable on the processor. When the real-name NFT transaction program is executed by the processor, it implements the steps of the real-name NFT transaction method as described in any one of claims 1 to 2.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a real-name NFT transaction program, which, when executed by a processor, implements the steps of the real-name NFT transaction method as described in any one of claims 1 to 2, 3-7.

Images