CN115660665A - NFT transaction method, system, device, equipment and storage medium - Google Patents
NFT transaction method, system, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115660665A CN115660665A CN202211406669.1A CN202211406669A CN115660665A CN 115660665 A CN115660665 A CN 115660665A CN 202211406669 A CN202211406669 A CN 202211406669A CN 115660665 A CN115660665 A CN 115660665A
- Authority
- CN
- China
- Prior art keywords
- nft
- digital asset
- ticket
- asset
- transaction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The application discloses a NFT transaction method, a system, a device, equipment and a storage medium, wherein the method comprises the following steps: receiving a transaction request sent by an asset buyer, wherein the transaction request comprises identification information of a digital asset and a first fee; generating a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, wherein the first NFT ticket characterizes a transaction fee record for the digital asset; generating a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset; transferring ownership of the first NFT ticket to the asset buyer over the federation chain, and transferring ownership of the second NFT ticket to the asset buyer over the public chain. The method and the system avoid the intermediary information carried in the NFT ticket of the digital asset, and reduce the transaction cost of the NFT.
Description
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a NFT transaction method, system, apparatus, device, and storage medium.
Background
Currently, when trading digital assets, an asset seller submits a digital asset to an exchange and casts a NFT (Non-homogeneous Token) ticket in the public chain, and when an asset buyer purchases a digital asset, the exchange transfers the NFT ticket from the public chain to the asset buyer, thereby completing the NFT transaction. Specifically, referring to fig. 1, step 1: the asset seller A submits the digital asset to a trading exchange and casts an NFT ticket, namely a Token ID, on the public chain; step 2: exchange B publishes the digital asset, i.e., presents the digital asset to potential asset buyers D1-Dn; and step 3: submitting purchase funds to an exchange B by an asset buyer willing to purchase; and 4, step 4: paying the remaining funds to the asset seller A after the exchange deducts a commission; and 5: the asset seller a transfers ownership of the NFT ticket to the asset buyer on the public chain.
For the NFT transaction process, there are corresponding transaction fee records, and these transaction fee records are written into the NFT ticket on the public chain together with the digital asset information of the digital asset, especially when there are several intermediary transactions before the digital asset is purchased by the asset buyer, the transaction fee record at each intermediary transaction is written into the NFT ticket on the public chain, so that there is a lot of intermediary information in the NFT ticket, and in addition, the casting cost of the asset seller a casting the NFT ticket on the public chain is high, and if the digital asset cannot be sold, the asset seller a loses the casting cost.
Disclosure of Invention
In view of this, embodiments of the present application provide a method, a system, an apparatus, a device, and a storage medium for NFT transaction, which aim to avoid carrying intermediary information in an NFT ticket of a digital asset and reduce NFT transaction cost.
To achieve the above object, the present application provides a NFT transaction method, including:
receiving a transaction request sent by an asset buyer, wherein the transaction request comprises identification information of a digital asset and a first fee;
generating a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, wherein the first NFT ticket characterizes a transaction fee record for the digital asset;
generating a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset;
transferring ownership of the first NFT ticket to the asset buyer on the federation chain, and transferring ownership of the second NFT ticket to the asset buyer on the public chain.
Illustratively, before generating the first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, the method includes:
in response to an upload request of an asset seller to upload a digital asset, generating a third NFT ticket on a alliance chain based on digital asset information included in the upload request; the third NFT ticket is an upload proof of the digital asset.
Illustratively, after generating a third NFT ticket on the federation chain based on digital asset information included in the upload request in response to an upload request of an asset seller to upload a digital asset, the method includes:
distributing the digital asset over the alliance chain to other exchanges for the other exchanges to present the digital asset;
determining an asset buyer for the digital asset based on the other exchanges.
Illustratively, the generating a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset comprises:
acquiring ownership of the third NFT ticket over the federation chain;
acquiring digital asset information of the digital asset based on ownership of the third NFT ticket;
generating a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset.
Illustratively, the generating a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset comprises:
deducting a second fee used for purchasing the first NFT ticket in the first fee to obtain a third fee;
paying the third fee to the asset seller;
upon detecting that the asset seller receives the third fee, generating a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset.
In addition, to achieve the above object, the present application also discloses an NFT transaction system, which includes an exchange:
the exchange receives a transaction request sent by an asset buyer, wherein the transaction request comprises identification information of the digital asset and a first fee;
generating, by the exchange, a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, wherein the first NFT ticket characterizes a transaction fee record for the digital asset;
generating, by the exchange, a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset;
the exchange transfers ownership of the first NFT ticket to the asset buyer over the federation chain and transfers ownership of the second NFT ticket to the asset buyer over the public chain.
Illustratively, the exchanges include at least a primary exchange and a plurality of secondary exchanges;
the primary exchange is for distributing the digital assets to respective secondary exchanges;
the plurality of secondary exchanges is for presenting the digital assets.
In addition, to achieve the above object, the present application also provides an NFT transaction apparatus, including:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a transaction request sent by an asset buyer, and the transaction request comprises identification information and a first fee of a digital asset;
a first generating module, configured to generate a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, wherein the first NFT ticket characterizes a transaction fee record for the digital asset;
a second generation module to generate a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset;
a transfer module to transfer ownership of the first NFT ticket to the asset buyer on the federation chain and to transfer ownership of the second NFT ticket to the asset buyer on the corporate chain.
In addition, to achieve the above object, the present application also provides an NFT transaction apparatus, which includes a memory, a processor, and an NFT transaction program stored on the memory and operable on the processor, and when executed by the processor, the NFT transaction program implements the steps of the NFT transaction method as described above.
Further, to achieve the above object, the present application also provides a computer readable storage medium having stored thereon an NFT transaction program, which when executed by a processor, implements the steps of the NFT transaction method as described above.
Compared with the prior art that a great deal of intermediary information is written into the NFT ticket on the public chain in the process of the digital asset from the asset seller to the asset buyer, and the cost of casting the NFT ticket is lost when the digital asset cannot be sold by the asset seller, the method has the advantages that the transaction request sent by the asset buyer is received, wherein the transaction request comprises the identification information of the digital asset and the first fee; generating a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, wherein the first NFT ticket characterizes a transaction fee record for the digital asset; generating a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset; transferring ownership of the first NFT ticket to the asset buyer on the federation chain, and transferring ownership of the second NFT ticket to the asset buyer on the public chain. According to the method and the system, the first NFT ticket of the transaction expense record is generated on the alliance chain, the second NFT ticket of the digital asset is generated on the public chain instead of directly generating the NFT ticket containing the transaction expense record and the digital asset on the public chain, the splitting of the NFT ticket is realized, the second NFT ticket cannot contain the transaction expense record, namely, the NFT ticket of the digital asset is prevented from carrying intermediary information, in addition, the second NFT ticket is cast after receiving a transaction request sent by an asset buyer, the NFT ticket of the digital asset is cast on the public chain under the condition that the transaction is formally carried out, the problem that when the digital asset cannot be sold, an asset seller can net lose the cost of casting the NFT ticket is avoided, and the NFT transaction cost is reduced.
Drawings
Fig. 1 is a schematic flow chart of an NFT transaction related to the background art of the NFT transaction method of the present application;
FIG. 2 is a schematic flow chart diagram of a first embodiment of the NFT transaction method of the present application;
fig. 3 is a schematic view of a scenario of a transaction process in a first embodiment of the NFT transaction method of the present application;
fig. 4 is another schematic view of a transaction process in the first embodiment of the NFT transaction method of the present application;
fig. 5 is a schematic view of another scenario of a transaction process in the first embodiment of the NFT transaction method of the present application;
fig. 6 is a schematic structural diagram of a hardware operating environment according to an embodiment of the present application.
The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Referring to fig. 2, fig. 2 is a schematic flowchart of a first embodiment of the NFT transaction method of the present application.
While the embodiments of the present application provide an embodiment of a NFT transaction method, it should be noted that although a logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in an order different than that shown or described herein. The NFT transaction method may be applied to a server where the exchange is located.
Where the exchange is a business service that allows the client to trade NFT with other assets, including legal currency or other cryptocurrency. The exchange can be a market dealer (intermediary) that uses the trade price difference as a trade commission for the service, or can be a pairing platform that simply collects the commission.
For convenience of description, the execution subject is omitted below to describe various steps of the NFT transaction method. The NFT transaction method comprises the following steps:
step S110, receiving a transaction request sent by an asset buyer, wherein the transaction request includes identification information of a digital asset and a first fee.
The asset buyer is a user of the exchange and purchases the digital asset through the exchange; the transaction request is for requesting a purchase of the digital asset. Wherein the identification information includes a name of the digital asset, production information, and the like.
The first fee includes a commission drawn by the transaction and a transaction cost. The commission refers to a part of fee deducted from the total transaction amount of the exchange which matches and completes the transaction in the NFT transaction activity, namely service fee. The transaction cost refers to that NFT transactions occur on the blockchain, and because the blockchain activities (such as casting, transferring, and the like) need to consume computing resources, the computing resources are consumed for each NFT transaction, and the part of the cost is borne by both transaction parties and is paid to a blockchain computing power provider (commonly called a miner).
Step S120, generating a first NFT ticket of the digital asset on a federation chain based on the identification information and the first fee, wherein the first NFT ticket represents a transaction fee record of the digital asset.
A federation chain is a private block chain built and commonly managed by multiple enterprises (exchanges). Each enterprise manages one or more nodes, and data in the nodes is only allowed to be read, written and transmitted by different enterprises in the alliance chain. Compared with the public link, the alliance link has the advantages of high transaction speed, high safety and good privacy guarantee. In addition, the transaction cost is greatly reduced because only a few generally recognized high-computation-force nodes are needed to confirm the transaction process. For example, the federation chain is built by 20 nodes, and 5 core nodes (high-computation-power nodes) confirm the federation chain in the transaction process, and then the 5 core nodes distribute the confirmation result to the rest 15 nodes in the federation chain.
The NFT is a unit of data on a digital book called a blockchain, and each NFT may represent a unique digital document as an electronic certificate or certificate of ownership of a virtual good. Because of their non-interchangeable nature, NFTs may represent digital assets such as paintings, artwork, sounds, videos, in-game items, or other forms of creative works. Although the work itself is infinitely reproducible, the NFT representing the work can be completely tracked across its underlying blockchain, thus providing proof of ownership of the digital asset to the asset buyer. NFT may also represent other digital content such as transaction fee records.
It is understood that the transaction fee record is used to record a first fee for the digital asset.
Step S130, a second NFT ticket of the digital asset is generated on the public chain based on the digital asset information of the digital asset.
The digital asset information includes designer information or author information, production information, the work itself, and the like, which can characterize the digital asset.
The public chain is also called a public chain, and is a consensus block chain which is open to all people. On the public link, each node can freely join and leave. Anyone can read data and initiate transactions at will, and each transaction can be effectively confirmed, so that the method has the characteristics of anonymity, low access threshold, complete decentralization, no influence of developers, transparent data disclosure, no tampering and the like. For example, bitcoin (BTC) employs a public chain technique. Compared with the alliance chain, the alliance chain needs more node confirmation in the transaction process, and therefore the transaction cost is high. For example, an etherhouse includes 10w nodes, of which 5w are required for validation.
After payment by the asset buyer, a first NFT ticket is generated on the federation chain, i.e., cast on the federation chain, and when sold (transferred) to the next level, the sale fee is a commission and a fee for casting the NFT, i.e., the first fee. It should be noted that the NFT ticket casted by the asset seller on the public chain in the prior art not only serves as the proof of ownership of the digital asset, but also includes the transaction fee record, and it can be understood that the first NFT ticket in this embodiment is equivalent to splitting the NFT ticket casted by the asset seller on the public chain in the prior art. This prevents the second NFT ticket from containing transaction fee records, thus avoiding the occurrence of a large amount of noise in the second NFT ticket even if the digital asset undergoes multiple transactions, making the digital asset more pure in collection. That is, the transaction fee record exists only in the private chain (alliance chain) and not in the public chain, and the asset buyer cannot acquire the transaction fee record from the public chain. For example, the exchange (broker) purchases the digital asset from the asset seller for value-added purposes, then sells the digital asset, and after at least one round of broker transaction, the digital asset is finally purchased by the asset buyer (e.g., for collection purposes, not sold), at which time the ownership of the second NFT ticket is transferred to the asset buyer, and the transaction fee record is written into the first NFT ticket.
Thus, after the transaction fee record and the digital asset are split (the splitting of the NFT ticket is actually embodied as the splitting of the information recorded therein), the exchange can also return to the original responsibility, i.e., trade the second NFT ticket characterizing the digital asset; moreover, because the first NFT ticket is cast in the transaction chain (alliance chain), the transaction fee record is completely embodied in the transaction chain, which is also constructed by a plurality of exchanges, when the transaction fee record needs to be queried in detail in the transaction, the query can be directly performed in the transaction chain without separately developing the program interface record and querying the transaction fee record for each exchange, which is beneficial to the integrity, traceability and simplicity of the transaction, and each exchange can access the transaction scheme in the embodiment by directly using the original NFT transaction interface without developing a new interface, thereby greatly reducing the access threshold of each exchange and saving the development cost.
Step S140, transferring ownership of the first NFT ticket to the asset buyer on the federation chain, and transferring ownership of the second NFT ticket to the asset buyer on the public chain.
Referring to fig. 3, fig. 3 is a schematic view of a transaction process in the first embodiment of the NFT transaction method of the present application. In fig. 3, 301 is a first NFT ticket, 302 is a transferred first NFT ticket, 303 is a second NFT ticket, and 304 is a transferred second NFT ticket. The transfer of the first NFT ticket to the asset buyer is automatically performed on the basis of a smart contract by charging the asset buyer for the purchase of the digital asset and then paying the asset seller for the purchase. After the asset seller charges a fee, a second NFT ticket is generated and ownership of the second NFT ticket is transferred to the asset buyer.
Compared with the prior art that a great deal of intermediary information is written into the NFT ticket on the public chain in the process of the digital asset from the asset seller to the asset buyer, and the cost of casting the NFT ticket is lost when the digital asset cannot be sold by the asset seller, the method has the advantages that the transaction request sent by the asset buyer is received, wherein the transaction request comprises the identification information of the digital asset and the first fee; generating a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, wherein the first NFT ticket characterizes a transaction fee record for the digital asset; generating a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset; transferring ownership of the first NFT ticket to the asset buyer on the federation chain, and transferring ownership of the second NFT ticket to the asset buyer on the public chain. According to the method and the device, the first NFT ticket of the transaction expense record is generated on the alliance chain, the second NFT ticket of the digital asset is generated on the public chain instead of directly generating the NFT ticket containing the transaction expense record and the digital asset on the public chain, the splitting of the NFT ticket is realized, the second NFT ticket cannot contain the transaction expense record, namely, the NFT ticket of the digital asset is prevented from carrying intermediary information, in addition, the second NFT ticket is cast after receiving a transaction request sent by an asset buyer, the NFT ticket of the digital asset is cast on the public chain under the condition that the transaction is formally carried out, the problem that when the digital asset cannot be sold, an asset seller can net lose the cost of casting the NFT ticket is avoided, and the NFT transaction cost is reduced.
Illustratively, before generating the first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, the method includes:
step a, responding to an uploading request of an asset seller for uploading digital assets, and generating a third NFT ticket on a alliance chain based on digital asset information included in the uploading request; the third NFT ticket is an upload proof of the digital asset.
In the prior art, after the asset seller uploads the digital asset, the NFT ticket of the digital asset is generally required to be cast on the public chain immediately, but the cost of casting the NFT ticket on the public chain is high, and if the digital asset is not sold finally, the cost of casting the NFT ticket is lost, for example, casting a picture as NFT costs $ 30, and if the picture is not sold finally, the asset seller loses $ 30. Based on this, part of the exchange launches a delayed casting service, i.e., the NFT ticket for a digital asset is cast when the asset buyer buys the digital asset. However, since the NFT ticket for the digital asset is not cast on the public chain after the digital asset is uploaded by the asset seller, the exchange may not acknowledge that it sold the digital asset in the case that the digital asset has already been sold, but since the asset seller does not have the NFT ticket, i.e., has no proof of ownership of the digital asset, the asset seller has no way to sell the funds for the digital asset, i.e., there is a risk that the exchange is tied back. Thus, the asset seller is at risk of losing the casting fee of the NFT ticket for the digital asset, or of being tied up by the exchange.
The present embodiment proposes a two-fold solution, i.e., when the seller of the asset uploads the digital asset, the NFT ticket is not immediately cast on the public chain, but a third NFT ticket is cast, which is cast on the federation chain, whereas according to the above-described embodiments related to the federation chain, the transaction cost on the federation chain is lower than the transaction cost on the public chain, where the transaction cost includes the casting cost of casting the NFT ticket, i.e., the casting cost of casting the NFT ticket on the federation chain is also lower than the casting cost of casting the NFT ticket on the public chain. Accordingly, while the loss risk of the casting cost is avoided, the exchange cannot be reimbursed due to the fact that the third NFT right is the uploading proof of the digital assets, namely the risk of reimbursement by the exchange is avoided.
Referring to fig. 4, fig. 4 is another schematic view of a transaction process in the first embodiment of the NFT transaction method of the present application. Wherein 401 is a first NFT ticket, 402 is a transferred first NFT ticket, 403 is a second NFT ticket, 404 is a transferred second NFT ticket, 405 is a third NFT ticket, and 406 is a transferred third NFT ticket. After payment by the asset buyer, a third NFT ticket is generated (i.e., cast) on the federation chain where the transaction is located.
It can be appreciated that after the asset seller uploads the digital asset, the asset seller does not need to cast NFT on the public chain by itself, i.e., the seller and buyer do not perceive the commission of the transaction in the transaction process as being drawn because the transaction fee record does not appear on the public chain, thereby facilitating the business development of NFT transaction.
Illustratively, after generating a third NFT ticket on the federation chain based on digital asset information included in the upload request in response to an upload request of an asset seller to upload a digital asset, the method includes:
step b, distributing the digital assets to other exchange stations on the alliance chain so that the digital assets can be displayed by the other exchange stations;
currently, there is only one exchange directly interfacing with an asset buyer and an asset seller, but for one exchange, the customer resources are limited, especially due to the specificity of NFT, the asset buyer and the asset seller only transact at their own trusted exchange, it can be understood that if the exchange at which the asset seller uploads a digital asset is not trusted by the potential buyer, the NFT corresponding to the digital asset may not be successfully sold. To solve the above-mentioned problem, the present embodiment proposes a multi-level exchange scheme, that is, a multi-level exchange may exist between an asset seller and an asset buyer. For example, an asset seller uploads a digital asset to its trusted exchange, defined as a primary exchange, which distributes the digital asset to other exchanges, including one or more, among which there is an exchange trusted by the asset buyer, defined as a secondary exchange; as another example, an asset seller uploads a digital asset to its trusted exchange, which is defined as a primary exchange that distributes the digital asset to other exchanges, which include one or more secondary exchanges, that define the other exchanges that directly interface with the primary exchange.
Illustratively, the other exchanges include a plurality of secondary exchanges, and the first-to-order potential buyer is determined from the plurality of potential buyers as the asset buyer of the digital asset when simultaneously receiving purchase requests of the plurality of potential buyers returned by the plurality of secondary exchanges. That is, if there are multiple potential buyers in other exchanges and there are multiple potential buyers, and the multiple potential buyers initiate multiple purchase requests within a certain time (which may be set as required), it can be understood that only one NFT corresponding to the digital asset is provided and the multiple purchase requests cannot be simultaneously satisfied, then a target purchase request needs to be selected from the multiple purchase requests, and the potential buyer initiating the target purchase request is determined as the asset buyer of the digital asset.
Referring to fig. 5, fig. 5 is a schematic view of another scenario of a transaction process in the first embodiment of the NFT transaction method of the present application. Wherein 501 is a first NFT ticket, 502 is a transferred first NFT ticket, 503 is a second NFT ticket, 504 is a transferred second NFT ticket, 505 is a third NFT ticket, 506 is a transferred third NFT ticket, 507 is a fourth NFT ticket, and 508 is a transferred fourth NFT ticket. Wherein the fourth NFT ticket is similar to the first NFT ticket, and wherein after payment by the asset buyer, the first NFT ticket is created (i.e., casted) on the federation chain for the primary transaction and the fourth NFT ticket is created (i.e., casted) on the federation chain for the secondary transaction. It will be appreciated that the asset buyer of the digital asset is the asset buyer 1, the purchase request submitted by the asset buyer 1 is uploaded to the secondary exchange 1 and uploaded by the secondary exchange 1 to the primary exchange, upon payment of a fee by the asset buyer to the secondary exchange 1, the primary exchange generates 501, the secondary exchange 1 generates 507, with a concomitant flow of fees by the asset buyer 1 in the direction of the secondary exchange 1, the primary exchange and the asset seller, 505, 501 and 507 transfer in the direction of the asset seller, the primary exchange, the secondary exchange 1 and the asset buyer 1 simultaneously, and upon collection by the asset seller, the primary exchange transfers 503 to the secondary exchange 1 and ultimately to the asset buyer 1 by the secondary exchange 1.
In addition, the secondary exchange may continue to distribute digital assets to the tertiary exchange, the tertiary exchange may continue to distribute digital assets to the quaternary exchange, and so on. It will be appreciated that by providing a multi-tier exchange between an asset seller and a potential buyer, the exposure of a digital asset to potential buyers can be increased, i.e., the coverage of potential buyers can be increased, thereby increasing the transaction success rate of the digital asset. Correspondingly, the other exchanges also have transaction costs, and the NFT ticket of the transaction fee record can also be generated on the federation chain, and the specific implementation of the NFT ticket generated by the other exchanges in transaction is substantially the same as that of the first NFT ticket exchanged by the primary exchange, and is not described herein again.
Step c, determining an asset buyer for the digital asset based on the other exchanges.
Illustratively, the generating a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset comprises:
and d, acquiring the ownership of the third NFT ticket on the alliance chain.
Ownership of the third NFT ticket is not able to operate on the digital asset at the seller of the asset, i.e., except for the seller of the asset, and thus ownership of the third NFT ticket needs to be acquired first.
Step e, acquiring digital asset information of the digital asset based on ownership of the third NFT ticket;
and f, generating a second NFT ticket of the digital asset on the public chain based on the digital asset information of the digital asset.
After acquiring digital asset information of the digital asset through ownership of the third NFT ticket, a second NFT ticket characterizing the digital asset information is generated (i.e., cast) on the public chain. It can be appreciated that there is a mapping relationship between the third NFT ticket and the digital asset information, and the digital asset information can be obtained by the third NFT ticket through the mapping relationship.
Illustratively, the generating a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset comprises:
step g, deducting a second fee for purchasing the first NFT ticket from the first fee to obtain a third fee;
step h, paying the third fee to the asset seller;
and i, under the condition that the asset seller is detected to receive the third fee, generating a second NFT ticket of the digital asset on a public chain based on the digital asset information of the digital asset.
Referring to FIG. 4, the first fee is the fee the asset buyer pays to the exchange, the third fee is the fee the exchange pays to the asset seller, and the second fee is the fee spent purchasing the first NFT ticket. Accordingly, a fee for the purchase of the digital asset by the asset buyer is charged, similar to while the first NFT ticket is transferred to the asset buyer; the transfer of the third NFT ticket to the exchange while the third fee is paid to the asset seller is also automatically performed based on the smart contract.
Wherein the second fee includes at least a commission, a transaction cost of the first NFT ticket, and a transaction cost of the second NFT ticket. It can be appreciated that the embodiment does not need to additionally calculate and deduct commission, transaction cost, but directly pass through the first NFT ticket for transaction, thereby improving the efficiency of the transaction process.
In addition, the present application also provides an NFT transaction system, the system including an exchange:
the exchange receives a transaction request sent by an asset buyer, wherein the transaction request comprises identification information of the digital asset and a first fee;
generating, by the exchange, a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, wherein the first NFT ticket characterizes a transaction fee record for the digital asset;
generating, by the exchange, a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset;
the exchange transfers ownership of the first NFT ticket to the asset buyer over the federation chain and transfers ownership of the second NFT ticket to the asset buyer over the public chain.
Illustratively, the exchanges include at least a primary exchange and a plurality of secondary exchanges;
the primary exchange is for distributing the digital assets to respective secondary exchanges;
the plurality of secondary exchanges is for presenting the digital assets.
The specific implementation of the NFT transaction system of the present application is substantially the same as the embodiments of the NFT transaction method described above, and is not described herein again.
In addition, the present application also provides an NFT transaction apparatus, including:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a transaction request sent by an asset buyer, and the transaction request comprises identification information and a first fee of a digital asset;
a first generation module, configured to generate a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, where the first NFT ticket characterizes a transaction fee record of the digital asset;
a second generation module to generate a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset;
a transfer module to transfer ownership of the first NFT ticket to the asset buyer on the federation chain and to transfer ownership of the second NFT ticket to the asset buyer on the corporate chain.
Illustratively, the NFT transaction apparatus further comprises:
a third generation module, configured to generate, in response to an upload request of an asset seller to upload a digital asset, a third NFT ticket on a federation chain based on digital asset information included in the upload request; the third NFT ticket is an upload proof of the digital asset.
Illustratively, the NFT transaction apparatus further comprises:
a distribution module, configured to distribute the digital asset to other exchanges over the alliance chain so that the digital asset is displayed by the other exchanges;
a determination module to determine an asset buyer for the digital asset based on the other exchanges.
Illustratively, the other exchanges include a plurality of exchanges, and the determining module is specifically configured to:
receiving a plurality of purchase requests of a plurality of potential buyers returned by a plurality of other transactions;
determining, from among the plurality of potential buyers, a first-to-order potential buyer as an asset buyer for the digital asset based on the plurality of purchase requests.
Illustratively, the second generating module is specifically configured to:
acquiring ownership of the third NFT ticket over the federation chain;
acquiring digital asset information of the digital asset based on ownership of the third NFT ticket;
generating a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset.
Illustratively, the first generating module is specifically configured to:
deducting a second fee used for purchasing the first NFT ticket in the first fee to obtain a third fee;
paying the third fee to the asset seller;
upon detecting that the asset seller receives the third fee, generating a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset.
The detailed implementation of the NFT transaction apparatus of the present application is substantially the same as that of the above NFT transaction method, and is not described herein again.
In addition, the application also provides NFT transaction equipment. As shown in fig. 6, fig. 6 is a schematic structural diagram of a hardware operating environment according to an embodiment of the present application.
In one possible implementation, fig. 6 is a schematic structural diagram of a hardware operating environment of the NFT transaction apparatus.
As shown in fig. 6, the NFT transaction apparatus may include a processor 601, a communication interface 602, a memory 603 and a communication bus 604, wherein the processor 601, the communication interface 602 and the memory 603 complete communication with each other through the communication bus 604, and the memory 603 is used for storing computer programs; the processor 601 is configured to implement the steps of the NFT transaction method when executing the program stored in the memory 603.
The communication bus 604 mentioned in the NFT transaction apparatus may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 604 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface 602 is used for communication between the NFT transaction device and other devices.
The Memory 603 may include a Random Access Memory (RMD) and may also include a Non-Volatile Memory (NM), such as at least one disk Memory. Optionally, the memory 603 may also be at least one storage device located remotely from the processor 601.
The Processor 601 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
The specific implementation of the NFT transaction apparatus of the present application is substantially the same as the embodiments of the NFT transaction method described above, and is not described herein again.
Furthermore, an embodiment of the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores thereon an NFT transaction program, and the NFT transaction program, when executed by a processor, implements the steps of the NFT transaction method as described above.
The specific implementation of the computer-readable storage medium of the present application is substantially the same as the embodiments of the NFT transaction method described above, and is not described herein again.
In addition, to achieve the above object, the present application also provides a computer program product comprising: a computer program which, when executed by a processor, implements the steps of the NFT transaction method as described above.
The specific implementation of the computer program product of the present application is substantially the same as the embodiments of the NFT transaction method described above, and will not be described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes: the instructions are used to enable a terminal device (which may be a mobile phone, a computer, a server, a device, or a network device) to perform the method described in the embodiments of the present application.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.
Claims (10)
1. A NFT transaction method, the method comprising:
receiving a transaction request sent by an asset buyer, wherein the transaction request comprises identification information of a digital asset and a first fee;
generating a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, wherein the first NFT ticket characterizes a transaction fee record for the digital asset;
generating a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset;
transferring ownership of the first NFT ticket to the asset buyer on the federation chain, and transferring ownership of the second NFT ticket to the asset buyer on the public chain.
2. The method of claim 1, wherein the generating the first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, comprises, prior to:
in response to an upload request of an asset seller to upload a digital asset, generating a third NFT ticket on a alliance chain based on digital asset information included in the upload request; the third NFT ticket is an upload proof of the digital asset.
3. The method as recited in claim 2, wherein, in response to an upload request by an asset seller to upload a digital asset, after generating a third NFT ticket over a federation chain based on digital asset information included in the upload request, comprising:
distributing the digital asset over the alliance chain to other exchanges for the other exchanges to present the digital asset;
determining an asset buyer for the digital asset based on the other exchanges.
4. The method of claim 2, wherein the generating a second NFT ticket for the digital asset over a public chain based on digital asset information of the digital asset comprises:
acquiring ownership of the third NFT ticket over the federation chain;
acquiring digital asset information of the digital asset based on ownership of the third NFT ticket;
generating a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset.
5. The method of claim 1 or 4, wherein the generating a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset comprises:
deducting a second fee used for purchasing the first NFT ticket in the first fee to obtain a third fee;
paying the third fee to the asset seller;
upon detecting that the asset seller receives the third fee, generating a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset.
6. A NFT transaction system, the system comprising an exchange:
the exchange receives a transaction request sent by an asset buyer, wherein the transaction request comprises identification information of the digital asset and a first fee;
generating, by the exchange, a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, wherein the first NFT ticket characterizes a transaction fee record for the digital asset;
generating, by the exchange, a second NFT ticket for the digital asset over a public chain based on digital asset information for the digital asset;
the exchange transfers ownership of the first NFT ticket to the asset buyer over the federation chain and transfers ownership of the second NFT ticket to the asset buyer over the public chain.
7. The system of claim 6, wherein the exchanges include at least a primary exchange and a plurality of secondary exchanges;
the primary exchange is for distributing the digital assets to respective secondary exchanges;
the plurality of secondary exchanges is for presenting the digital assets.
8. An NFT transaction apparatus, the apparatus comprising:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a transaction request sent by an asset buyer, and the transaction request comprises identification information and a first fee of a digital asset;
a first generation module, configured to generate a first NFT ticket for the digital asset over a federation chain based on the identification information and the first fee, where the first NFT ticket characterizes a transaction fee record of the digital asset;
a second generation module to generate a second NFT ticket for the digital asset on a public chain based on digital asset information for the digital asset;
a transfer module to transfer ownership of the first NFT ticket to the asset buyer on the federation chain and to transfer ownership of the second NFT ticket to the asset buyer on the corporate chain.
9. An NFT transaction device, comprising a memory, a processor, and an NFT transaction program stored on the memory and executable on the processor, the NFT transaction program when executed by the processor implementing the steps of the NFT transaction method as recited in any of claims 1 to 5.
10. A computer-readable storage medium having stored thereon an NFT transaction program that, when executed by a processor, performs the steps of the NFT transaction method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211406669.1A CN115660665A (en) | 2022-11-10 | 2022-11-10 | NFT transaction method, system, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211406669.1A CN115660665A (en) | 2022-11-10 | 2022-11-10 | NFT transaction method, system, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115660665A true CN115660665A (en) | 2023-01-31 |
Family
ID=85021766
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211406669.1A Pending CN115660665A (en) | 2022-11-10 | 2022-11-10 | NFT transaction method, system, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115660665A (en) |
-
2022
- 2022-11-10 CN CN202211406669.1A patent/CN115660665A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220198447A1 (en) | Target object management method, smart contract, and management device | |
| JP7385706B2 (en) | Method of distributing digital assets registered on blockchain and autonomous computing agent | |
| KR102573433B1 (en) | Platform for trading energy using block chain and method thereof | |
| CN110599182B (en) | Resource management method and device | |
| JP2021520010A (en) | Blockchain loan transaction system and method | |
| WO2019227449A1 (en) | Second-hand car trading method, and server | |
| US20220164791A1 (en) | Method for distributing collectables ownership based on blockchain networks and online transaction server using the same | |
| KR102343615B1 (en) | Block chain system for transacting art work and managing information of art work and control method thereof | |
| EP3937110A1 (en) | Intellectual property right trade system using blockchain, and operating method therefor | |
| KR20190120474A (en) | Transaction processing method and apparatus thereof | |
| CN110648204A (en) | Method and apparatus for arbitration | |
| US8055583B2 (en) | Shared online auction provisioning | |
| KR102136976B1 (en) | Service method for tokenization mobile gift card and service provider thereof | |
| JP2003337892A (en) | System and method for selling and buying intellectual property right, program thereof, and recording medium | |
| CN114742654A (en) | Digital asset circulation method, system, electronic device and medium based on alliance chain | |
| KR20200000595A (en) | Blockchain based certificate management method and device, server and system thereof | |
| JPWO2018092443A1 (en) | Digital content transaction management apparatus, digital content transaction management method and program | |
| KR20220009791A (en) | Real estate direct transaction system and method using artificial intelligence | |
| CN108876339B (en) | E-pet transaction method and device based on certificate | |
| CN110633966A (en) | Block chain-based contract securitization method and device | |
| CN115880062A (en) | Product exchange method, device, equipment and system based on digital collections in block chain | |
| CN115660665A (en) | NFT transaction method, system, device, equipment and storage medium | |
| WO2018092443A1 (en) | Digital content commerce management device, digital content commerce management method, and program | |
| CN115131034A (en) | Block chain-based rights and interests digital collection verification method and equipment | |
| KR20230011197A (en) | Method for providing the real art trading using of non fungible token |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |