Digital blind box processing method and system

Abstract

The invention provides a digital blind box processing method and system. The system comprises front-end equipment, a back-end server and an Ethereum platform, a front-end browser and a front-end verification plug-in are deployed on the front-end equipment; the method comprises the steps that a front-end browser receives a blind box creation instruction input by a blind box seller, responds to the blind box creation instruction, and obtains a block chain identifier through a front-end verification plug-in; the front-end browser receives blind box creation data input by a blind box seller and sends a blind box creation request to the rear-end server; the back-end server creates a smart contract according to the blind box creation request, and sends an unsigned transaction containing the smart contract to the front-end browser; and the front-end browser signs the smart contract through the front-end verification plug-in to obtain a signature transaction containing the smart contract, deploys the smart contract to the Ethereum platform according to the signature transaction, obtains the address of the smart contract in the Ethereum platform through the front-end verification plug-in, and outputs the address of the smart contract, thereby improving the blind box processing efficiency and security.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and specifically, to a digital blind box processing method and system. Background Art

[0002] In the blockchain field, the new generation of blockchain systems based on smart contracts and virtual machines, represented by Ethereum, has brought new application scenarios to the digital economy. Among them, non-fungible tokens (NFTs) as a new type of digital economic application scenario provide a new blind box system based on digital assets NFTs. The new blind box system combines traditional blind boxes with blockchain technology.

[0003] At present, the virtual blind box trading platform based on NFT is deployed and developed based on private blockchain or alliance blockchain. Private blockchain or alliance blockchain often relies on a few nodes or servers, which has the risk of over-centralization and cannot guarantee the authenticity of virtual blind boxes and the rarity of hidden items. In addition, the Ethereum Request for Comments (ERC) contract used by the current virtual blind box trading platform is an ERC721 contract. Each ERC721 contract can only issue one NFT asset. In the application scenario of virtual blind box trading, there are disadvantages of high transaction fees and low operating efficiency.

[0004] Therefore, there are certain limitations in the existing technology of virtual blind box transactions based on NFT. Summary of the invention

[0005] The purpose of this application is to provide a digital blind box processing method and system to address the deficiencies in the above-mentioned prior art and to solve the practical problems in the prior art.

[0006] To achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:

[0007] In the first aspect, the embodiment of the present application provides a digital blind box processing method, which is applied to a digital blind box processing system, wherein the digital blind box processing system includes: a front-end device, a back-end server, and an Ethereum platform; a front-end browser and a front-end verification plug-in are deployed on the front-end device; the method includes:

[0008] The front-end browser receives the blind box creation instruction input by the blind box seller, responds to the blind box creation instruction, and obtains the blockchain identifier through the front-end verification plug-in;

[0009] The front-end browser receives the blind box creation data input by the blind box seller, and sends a blind box creation request to the back-end server;

[0010] The backend server creates a smart contract according to the blind box creation request, and sends an unsigned transaction containing the smart contract to the front-end browser;

[0011] The front-end browser signs the smart contract through the front-end verification plug-in to obtain a signed transaction containing the smart contract, deploys the smart contract to the Ethereum platform according to the signed transaction, obtains the address of the smart contract in the Ethereum platform through the front-end verification plug-in, and outputs the address of the smart contract.

[0012] As an optional implementation method, obtaining the blockchain identifier through the front-end verification plug-in includes:

[0013] The front-end browser calls the request function in the front-end verification plug-in;

[0014] The front-end browser receives the confirmation login instruction from the blind box seller, and sends the confirmation login instruction to the front-end verification plug-in;

[0015] The front-end browser obtains the seller's public key from the front-end verification plug-in, and sends a request to obtain the blockchain identifier to the front-end verification plug-in to obtain the blockchain identifier through the front-end verification plug-in, wherein the seller's public key is used to identify the blind box seller.

[0016] As an optional implementation, the blind box creation request includes: the seller's public key, the blockchain identifier, and the blind box creation data;

[0017] The backend server creates a smart contract according to the blind box creation request, including:

[0018] The back-end server calls the contract creation related functions in the back-end server in sequence according to the blind box creation request to create the smart contract, wherein the contract creation related functions include: open function, create function, compile function and constructor.

[0019] As an optional implementation method, the front-end browser signs the smart contract through the front-end verification plug-in to obtain a signed transaction containing the smart contract, deploys the smart contract to the Ethereum platform according to the signed transaction, and obtains the address of the smart contract in the Ethereum platform through the front-end verification plug-in, including:

[0020] The front-end browser sends a seller signature transaction request to the front-end verification plug-in, receives the confirmation deployment instruction input by the blind box seller, responds to the signature operation of the blind box seller, obtains the signature transaction containing the smart contract and sends it to the front-end verification plug-in;

[0021] The front-end verification plug-in sends the signed transaction to the Ethereum platform, deploys the smart contract on the Ethereum platform according to the signed transaction, obtains the first hash value and sends it to the front-end browser;

[0022] The front-end browser sends a first receipt request to the front-end verification plug-in according to the first hash value, so as to obtain the address of the smart contract in the Ethereum platform through the front-end verification plug-in.

[0023] As an optional implementation, the method further includes:

[0024] The front-end browser receives a blind box purchase instruction input by a blind box buyer, responds to the blind box purchase instruction, and obtains the blockchain identifier through the front-end verification plug-in;

[0025] The front-end browser receives the blind box purchase data input by the blind box buyer, and sends a blind box purchase request to the back-end server;

[0026] The backend server accesses the smart contract according to the blind box purchase request, and sends an unsigned purchase transaction including the blind box price to the front-end browser;

[0027] The front-end browser signs the unsigned purchase transaction through the front-end verification plug-in to obtain a signed purchase transaction including the blind box price, and outputs the blind box purchase result based on the signed purchase transaction and the smart contract deployed on the Ethereum platform.

[0028] As an optional implementation method, the blind box purchase request includes: a buyer's public key, the blockchain identifier, and the blind box purchase data, wherein the buyer's public key is used to identify the blind box buyer;

[0029] The backend server accesses the smart contract according to the blind box purchase request, and sends an unsigned purchase transaction containing the blind box price to the front-end browser, including:

[0030] The backend server determines the address of the smart contract corresponding to the blind box according to the blind box purchase request;

[0031] The backend server accesses the smart contract according to the address of the smart contract to obtain the blind box price through the smart contract;

[0032] The back-end server creates the unsigned purchase transaction including the blind box price according to the blind box price and the blind box purchase request and sends it to the front-end browser.

[0033] As an optional implementation, the outputting of the blind box purchase result according to the signed purchase transaction and the smart contract deployed on the Ethereum platform includes:

[0034] The front-end verification plug-in calls the blind box purchase function of the smart contract deployed on the Ethereum platform according to the signed purchase transaction, obtains the second hash value and the purchase receipt, and sends them to the front-end browser;

[0035] The front-end browser outputs the blind box purchase result to the blind box buyer based on the second hash value and the purchase receipt.

[0036] As an optional implementation, the digital blind box processing system further includes: a large model, and the method further includes:

[0037] The front-end browser receives the blind box opening instruction input by the blind box buyer, responds to the blind box opening instruction, and obtains the blockchain identifier through the front-end verification plug-in;

[0038] The front-end browser receives the blind box opening data input by the blind box buyer, and sends a blind box opening request to the back-end server;

[0039] The back-end server calls the construction function in the back-end server according to the blind box opening request to construct an unsigned opening transaction containing the number of blind boxes, and sends the unsigned opening transaction containing the number of blind boxes to the front-end browser;

[0040] The front-end browser signs the unsigned opening transaction through the front-end verification plug-in to obtain a signed opening transaction containing the number of blind boxes, and calls the blind box opening function in the smart contract deployed on the Ethereum platform according to the signed opening transaction to obtain a third hash value;

[0041] The front-end browser sends the third hash value to the back-end server, and the back-end server calls the large model according to the third hash value to generate the digital assets corresponding to the blind box through the large model;

[0042] The back-end server sends the digital assets corresponding to the blind box to the front-end browser, and the front-end browser outputs the blind box opening result according to the digital assets corresponding to the blind box.

[0043] As an optional implementation method, the generating of the digital assets corresponding to the blind box through the large model includes:

[0044] The large model obtains the third hash value and the blind box prompt word pre-entered by the blind box seller;

[0045] The big model integrates the third hash value and the blind box prompt word into the prompt word of the big model to generate and output the digital assets corresponding to the blind box according to the prompt word of the big model.

[0046] In a second aspect, an embodiment of the present application provides a digital blind box processing system, the digital blind box processing system comprising: a front-end device, a back-end server and an Ethereum platform; a front-end browser and a front-end verification plug-in are deployed on the front-end device;

[0047] The digital blind box processing system is used to execute the steps of the digital blind box processing method described in the first aspect above.

[0048] The beneficial effects of this application are:

[0049] The present application provides a digital blind box processing method and system. In the process of creating a new digital blind box, the front-end browser receives and responds to the blind box creation instruction input by the blind box seller, and obtains the blockchain identifier that identifies the blockchain operating environment through the front-end verification plug-in. The front-end browser also receives the blind box creation data input by the blind box seller, generates a blind box creation request based on the blind box creation data and the blockchain identifier, and sends it to the back-end server. The back-end server creates a smart contract that can issue multiple blind boxes according to the blind box creation request, and creates an unsigned transaction containing the smart contract and sends it to the front-end browser. The front-end browser interacts with the front-end verification plug-in according to the unsigned transaction containing the smart contract, obtains the signed transaction containing the smart contract through the front-end verification plug-in, and deploys the smart contract created by the back-end processor on the public blockchain of the Ethereum platform through the front-end verification plug-in, obtains the smart contract address and sends it to the front-end browser. The front-end browser displays the blind box creation result to the blind box seller based on the address of the smart contract. The blockchain identifier can improve the legitimacy and security of deploying smart contracts on the public blockchain of the Ethereum platform; sending the data in the message body of the blind box creation request improves the security of data transmission and the amount of data transmitted. The smart contracts created by the back-end processor can reduce the cost of creating large quantities of blind boxes and improve the efficiency of creating large quantities of blind boxes. Since the smart contracts are deployed on the public blockchain of the Ethereum platform, based on the decentralized nature of the Ethereum public chain and the diversity of multiple digital assets that can be issued by a single smart contract, the authenticity of the digital blind boxes and the rarity of hidden models are guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0051] Figure 1 A schematic diagram of the architecture of a digital blind box processing system provided in an embodiment of the present application;

[0052] Figure 2 A flowchart of a digital blind box processing method provided in an embodiment of the present application;

[0053] Figure 3 A schematic diagram of the process of obtaining a blockchain identifier for a digital blind box processing method provided in an embodiment of the present application;

[0054] Figure 4 A schematic diagram of the process of obtaining the address of a smart contract in the Ethereum platform for the digital blind box processing method provided in an embodiment of the present application;

[0055] Figure 5 Another schematic diagram of the process of processing a digital blind box provided in an embodiment of the present application;

[0056] Figure 6 A flowchart of the digital blind box processing method provided in an embodiment of the present application for accessing a smart contract and sending an unsigned purchase transaction including the blind box price to a front-end browser;

[0057] Figure 7 A schematic diagram of the process of outputting blind box purchase results of the digital blind box processing method provided in an embodiment of the present application;

[0058] Figure 8 Another schematic diagram of the architecture of the digital blind box processing system provided in an embodiment of the present application;

[0059] Fig. 9 Another schematic diagram of the architecture of the digital blind box processing system provided in the embodiment of the present application

[0060] Fig.10 Another flowchart of the digital blind box processing method provided in the embodiment of the present application;

[0061] Fig.11 A schematic diagram of the process of generating digital assets corresponding to a blind box according to the digital blind box processing method provided in an embodiment of the present application;

[0062] Fig.12 Schematic diagram of the interactive process for generating digital assets corresponding to blind boxes based on a large model provided in an embodiment of the present application. DETAILED DESCRIPTION

[0063] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.

[0064] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0065] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0066] At present, the virtual blind box trading platform based on NFT is deployed and developed based on private blockchain or alliance blockchain, which has the risk of over-centralization and cannot guarantee the authenticity of virtual blind boxes and the rarity of hidden items. Moreover, the ERC721 contract used by the current virtual blind box trading platform has the disadvantages of high transaction fees and low operating efficiency in the application scenario of virtual blind box trading. In addition, the current virtual blind box trading platform only converts the contents of the blind box from physical items to virtual items, which makes it difficult to provide a good user experience.

[0067] Based on the above problems, the embodiment of the present application proposes a method for processing digital blind boxes. A front-end verification plug-in is introduced on the basis of the browser / server architecture, and an integrated decentralized Internet architecture including a front-end browser, a front-end verification plug-in and a back-end server is designed. Through the interaction of the front-end browser, the front-end verification plug-in and the back-end server, it is convenient for users to access the decentralized Internet conveniently, and sellers can create blind boxes, buyers can buy blind boxes, open blind boxes and merge blind boxes efficiently, thereby improving the security guarantee during blind box transactions. By deploying the ERC1155 smart contract to the Ethereum platform, based on the decentralized characteristics of the Ethereum public chain and the diversity of a single ERC1155 contract that can issue a variety of digital assets, the authenticity of the blind box and the rarity of the hidden items are guaranteed, and the efficiency of blind box transactions is improved. By introducing large model technology when opening the blind box, digital assets can be generated intelligently, and a new way of playing with blind box fusion is provided, which enriches the types of blind boxes and increases the fun and playability of blind boxes.

[0068] Figure 1 A schematic diagram of the architecture of the digital blind box processing system provided in the embodiment of the present application is shown in FIG. Figure 1 As shown, the digital blind box processing system includes a front-end device, a back-end server and an Ethereum platform. Among them, the front-end device includes a front-end browser and a front-end verification plug-in. The front-end browser can provide a human-computer interaction interface for a personal computer browser terminal or a human-computer interaction interface for a mobile browser terminal. The front-end verification plug-in is a front-end MetaMask plug-in. Blind box sellers or blind box buyers can interact with the Ethereum platform with the help of the front-end browser and the front-end MetaMask plug-in. The front-end MetaMask plug-in is used to create users, verify users and access WEB3 services, such as sending transactions and obtaining transaction receipts. The back-end server can create ERC1155 smart contracts and unsigned transactions containing ERC1155 smart contracts. Continue to refer to Figure 1 , the backend server can interact with the front-end browser, the front-end MetaMask plug-in, and the smart contracts deployed in the Ethereum platform.

[0069] Figure 2 A flowchart of a digital blind box processing method provided in an embodiment of the present application, the execution subject of the method is Figure 1 The digital blind box processing system shown in FIG. Figure 2 As shown, the method includes:

[0070] S201. The front-end browser receives the blind box creation instruction input by the blind box seller, responds to the blind box creation instruction, and obtains the blockchain identifier through the front-end verification plug-in.

[0071] Optionally, the front-end browser provides a human-computer interaction interface of a browser terminal to the blind box seller, and a blind box creation control is provided on the human-computer interaction interface. When the blind box seller wants to create a new digital blind box product, he can perform a first touch operation on the blind box creation control on the human-computer interaction interface, thereby inputting a blind box creation instruction to the front-end browser. Among them, the first touch operation on the blind box creation control can be a single click, double click or long press operation of the blind box creation control by the blind box seller, and the operation type of the first touch operation is not specifically limited here.

[0072] The front-end browser responds to the blind box creation instructions input by the blind box seller, verifies the blind box seller's login information through the front-end MetaMask plug-in, and obtains the blockchain identifier. Among them, the blockchain identifier is used to identify the operating environment of the blockchain, so as to deploy smart contracts on the public blockchain of the Ethereum platform based on the blockchain identifier, thereby ensuring the legality and security of the smart contract deployment.

[0073] S202. The front-end browser receives the blind box creation data input by the blind box seller and sends a blind box creation request to the back-end server.

[0074] Optionally, the blind box seller can enter the attributes of the blind box to be created on the human-computer interaction interface of the front-end browser, for example, the number, type and price of the blind box to be created. The front-end browser performs Base64 encoding on the attributes of the blind box to be created, encodes the binary data into a string, and generates blind box creation data in Base64 format. The front-end browser generates a blind box creation request based on the blind box creation data in Base64 format and the blockchain identifier and sends it to the back-end server. Among them, the blind box creation request is a send (POST) request in the Hypertext Transfer Protocol (HTTP), that is, a POST HTTP request. The POST HTTP request sends the data in the message body of the request. The front-end browser sends the POST HTTP request for blind box creation to the back-end server, which improves the security of data transmission and the amount of data transmitted.

[0075] S203. The back-end server creates a smart contract based on the blind box creation request and sends an unsigned transaction containing the smart contract to the front-end browser.

[0076] Optionally, the backend server creates an ERC1155 smart contract based on the POST HTTP request created by the blind box. Any type of NFT assets can be issued in a single ERC1155 smart contract, that is, a single ERC1155 smart contract supports the creation and issuance of digital blind boxes of different styles and types, without the need to create a separate smart contract for each blind box.

[0077] The backend server creates an unsigned transaction containing the ERC1155 smart contract based on the created ERC1155 smart contract, and sends the unsigned transaction containing the ERC1155 smart contract to the front-end browser.

[0078] S204. The front-end browser signs the smart contract through the front-end verification plug-in to obtain a signed transaction containing the smart contract, deploys the smart contract to the Ethereum platform according to the signed transaction, obtains the address of the smart contract in the Ethereum platform through the front-end verification plug-in, and outputs the address of the smart contract.

[0079] Optionally, the front-end browser interacts with the MetaMask plug-in on the front end based on the unsigned transaction containing the ERC1155 smart contract sent by the back-end processor, and responds to the blind box seller's confirmation and signing operation on the unsigned transaction containing the ERC1155 smart contract through the front-end MetaMask plug-in to obtain a signed transaction containing the ERC1155 smart contract.

[0080] The front-end MetaMask plug-in deploys the ERC1155 smart contract created by the back-end processor on the public blockchain of the Ethereum platform according to the signed transaction containing the ERC1155 smart contract, obtains the address of the ERC1155 smart contract on the public blockchain of the Ethereum platform, and sends the address of the ERC1155 smart contract to the front-end browser by interacting with the front-end browser. The human-computer interaction interface of the front-end browser displays the blind box creation results to the blind box seller based on the address of the ERC1155 smart contract.

[0081] In this embodiment, in the process of creating a new digital blind box, the front-end browser receives and responds to the blind box creation instruction input by the blind box seller, and obtains the blockchain identifier that identifies the blockchain operating environment through the front-end verification plug-in. The front-end browser also receives the blind box creation data input by the blind box seller, generates a blind box creation request based on the blind box creation data and the blockchain identifier, and sends it to the back-end server. The back-end server creates a smart contract that can issue multiple blind boxes according to the blind box creation request, and creates an unsigned transaction containing the smart contract and sends it to the front-end browser. The front-end browser interacts with the front-end verification plug-in based on the unsigned transaction containing the smart contract, obtains the signed transaction containing the smart contract through the front-end verification plug-in, and deploys the smart contract created by the back-end processor on the public blockchain of the Ethereum platform through the front-end verification plug-in, obtains the smart contract address and sends it to the front-end browser. The front-end browser displays the blind box creation result to the blind box seller based on the address of the smart contract. The blockchain identifier can improve the legitimacy and security of deploying smart contracts on the public blockchain of the Ethereum platform; sending data in the message body of the blind box creation request improves the security of data transmission and the amount of data transmitted. The smart contracts created by the back-end processor can reduce the cost of creating large quantities of blind boxes and improve the efficiency of creating large quantities of blind boxes. Since the smart contracts are deployed on the public blockchain of the Ethereum platform, based on the decentralized nature of the Ethereum public chain and the diversity of multiple digital assets that can be issued by a single smart contract, the authenticity of the digital blind boxes and the rarity of hidden models are guaranteed.

[0082] The following is a detailed description of the process of obtaining a blockchain identifier through a front-end verification plug-in.

[0083] Figure 3 A flowchart of a method for processing a digital blind box provided in an embodiment of the present application for obtaining a blockchain identifier is shown in FIG. Figure 3 As shown, the step of obtaining the blockchain identifier through the front-end verification plug-in in the above step S201 includes:

[0084] S301, the front-end browser calls the request function in the front-end verification plug-in.

[0085] Optionally, a request function is pre-set in the front-end MetaMask plug-in, and the request function is used to obtain the public key and blockchain identifier of the blind box user. Among them, the blind box user can be a blind box seller or a blind box buyer. In the process of creating a blind box, the blind box user is the blind box seller. The front-end browser responds to the blind box creation instruction input by the blind box seller and calls the request function in the front-end MetaMask plug-in.

[0086] S302. The front-end browser receives the confirmation login instruction from the blind box seller and sends the confirmation login instruction to the front-end verification plug-in.

[0087] Optionally, the front-end browser pops up a confirmation login page to the blind box seller through the human-computer interaction interface according to the request function, responds to the blind box seller's confirmation login operation on the confirmation login page, receives the blind box seller's confirmation login instruction, and sends the confirmation login instruction to the front-end MetaMask plug-in, so that the front-end MetaMask plug-in can verify the login information of the blind box seller.

[0088] S303. The front-end browser obtains the seller’s public key from the front-end verification plug-in, and sends a request to obtain the blockchain identifier to the front-end verification plug-in to obtain the blockchain identifier through the front-end verification plug-in, where the seller’s public key is used to identify the blind box seller.

[0089] Optionally, the front-end MetaMask plug-in verifies the login information of the blind box seller according to the confirmation login instruction and the request function called by the front-end browser, and then obtains the seller's public key and sends it to the front-end browser. Among them, whether it is a blind box seller or a blind box buyer, each blind box user has a unique public key to distinguish different blind box user identities. The seller's public key is used to identify the blind box seller, verify the blind box seller's identity and track transactions. Through the seller's public key, the blind box seller can receive payment and deliver the blind box, ensuring the legitimacy and security of the blind box creation.

[0090] After the front-end browser receives the seller's public key sent by the front-end MetaMask plug-in, it generates a request to obtain the blockchain identifier and sends it to the front-end MetaMask plug-in. The front-end MetaMask plug-in obtains the blockchain identifier used to identify the blockchain operating environment based on the blockchain identifier acquisition request and sends it to the front-end browser.

[0091] In this embodiment, in the front-end device, the front-end browser responds to the blind box creation instruction input by the blind box seller, calls the request function in the front-end verification plug-in, and receives and responds to the confirmation login instruction of the blind box seller according to the request function, and sends the confirmation login instruction to the front-end verification plug-in. The front-end verification plug-in verifies the login information of the blind box seller according to the confirmation login instruction and the request function, obtains the seller's public key and sends it to the front-end browser. After the front-end browser receives the seller's public key, it generates a request to obtain the blockchain identifier and sends it to the front-end verification plug-in, so that the front-end verification plug-in obtains the blockchain identifier according to the request to obtain the blockchain identifier and sends it to the front-end browser. Through the interaction between the front-end browser and the front-end verification plug-in in the front-end device, the login information of the blind box seller is verified, and the seller's public key and blockchain identifier are obtained, thereby improving the security of blind box creation.

[0092] As an optional implementation, the blind box creation request includes: the seller's public key, the blockchain identifier, and the blind box creation data.

[0093] Optionally, the blind box creation request includes creation request parameters, which are the seller's public key, blockchain identifier, and blind box creation data in Base64 format, where the blind box creation data is used to characterize the quantity, type, and price of the blind boxes to be created input by the blind box seller. The blind box creation request is a POST HTTP request for blind box creation, and the creation request parameters can be sent in the message body of the request to improve the security and transmission volume of the creation request parameters.

[0094] As an optional implementation, the step of creating a smart contract by the backend server according to the blind box creation request in the above step S203 includes:

[0095] According to the blind box creation request, the back-end server calls the contract creation related functions in the back-end server in sequence to create a smart contract, where the contract creation related functions include: open function, create function, compile function and constructor.

[0096] Optionally, the back-end server is pre-set with contract creation related functions, including Open function, Create function, Compile function and Constructor function. According to the POST HTTP request for blind box creation sent by the front-end browser, the back-end server calls the Open function, Create function, Compile function and Constructor function in sequence based on the seller's public key, blockchain identifier and Base64 format blind box creation data in the POST HTTP request for blind box creation, and constructs an ERC1155 smart contract, so that the constructed single ERC1155 smart contract supports the creation and issuance of digital blind boxes of different styles and types.

[0097] In this embodiment, the back-end server calls the open function, creation function, compile function and constructor in the back-end server in sequence according to the seller's public key, blockchain identifier and blind box creation data in the blind box creation request, and builds a smart contract that supports the creation and issuance of digital blind boxes of different styles and types, avoiding the creation of a separate smart contract for each blind box, so as to improve the blind box processing efficiency and reduce the blind box processing cost.

[0098] The following is a detailed description of the process of signing a smart contract through a front-end verification plug-in by a front-end browser, obtaining a signed transaction containing the smart contract, deploying the smart contract to the Ethereum platform according to the signed transaction, and obtaining the address of the smart contract in the Ethereum platform through the front-end verification plug-in.

[0099] Figure 4 A flow chart of the method for processing a digital blind box provided in an embodiment of the present application for obtaining the address of a smart contract in the Ethereum platform is shown in FIG. Figure 4 As shown, in the above step S204, the front-end browser signs the smart contract through the front-end verification plug-in to obtain a signed transaction containing the smart contract, deploys the smart contract to the Ethereum platform according to the signed transaction, and obtains the address of the smart contract in the Ethereum platform through the front-end verification plug-in, including:

[0100] S401. The front-end browser sends a seller signature transaction request to the front-end verification plug-in, receives the confirmation deployment instructions entered by the blind box seller, and responds to the blind box seller's signature operation to obtain a signature transaction containing a smart contract and send it to the front-end verification plug-in.

[0101] Optionally, the front-end browser generates a seller signature transaction request based on the unsigned transaction containing the ERC1155 smart contract sent by the back-end processor and sends it to the front-end MetaMask plug-in, and pops up a confirmation deployment and signature page to the blind box seller through the human-computer interaction interface, responds to the blind box seller's confirmation deployment operation on the confirmation deployment and signature page, and receives the blind box seller's confirmation deployment instruction. The front-end browser also responds to the blind box seller's signature operation on the confirmation deployment and signature page, obtains the signed transaction containing the ERC1155 smart contract, and sends the signed transaction containing the ERC1155 smart contract to the front-end MetaMask plug-in.

[0102] S402, the front-end verification plug-in sends the signed transaction to the Ethereum platform, deploys the smart contract on the Ethereum platform according to the signed transaction, obtains the first hash value and sends it to the front-end browser.

[0103] Optionally, the front-end MetaMask plug-in sends the received signed transaction containing the ERC1155 smart contract to the Ethereum platform, and deploys the ERC1155 smart contract in the signed transaction containing the ERC1155 smart contract on the public blockchain corresponding to the blockchain identifier in the Ethereum platform according to the signed transaction containing the ERC1155 smart contract. After the front-end MetaMask plug-in deploys the ERC1155 smart contract, it obtains the first hash value, which is the transaction hash value for the blind box seller to create the blind box, and the front-end MetaMask plug-in sends the first hash value to the front-end browser.

[0104] S403. The front-end browser sends a first receipt request to the front-end verification plug-in according to the first hash value, so as to obtain the address of the smart contract in the Ethereum platform through the front-end verification plug-in.

[0105] Optionally, the front-end browser generates a first receipt request corresponding to the first hash value according to the received first hash value and sends it to the front-end MetaMask plug-in. The front-end MetaMask plug-in obtains the address of the ERC1155 smart contract on the public blockchain of the Ethereum platform according to the first receipt request corresponding to the received first hash value, and sends it to the front-end browser.

[0106] In this embodiment, the front-end browser generates a seller signature transaction request based on the untraded signature containing the smart contract and sends it to the front-end verification plug-in. The front-end browser receives the confirmation deployment instruction input by the blind box seller, responds to the signature operation of the blind box seller, obtains the signature transaction containing the smart contract and sends it to the front-end verification plug-in. The front-end verification plug-in sends the signature transaction to the Ethereum platform, deploys the smart contract on the public blockchain corresponding to the blockchain identifier in the Ethereum platform according to the signature transaction, and obtains the first hash value and sends it to the front-end browser. The front-end browser generates a first receipt request corresponding to the first hash value according to the first hash value, and sends it to the front-end verification plug-in. The front-end verification plug-in obtains the address of the smart contract on the public blockchain of the Ethereum platform according to the first receipt request corresponding to the first hash value, and sends it to the front-end browser so that the front-end browser displays the address of the smart contract to the blind box seller. Through the interaction between the front-end browser and the front-end verification plug-in in the front-end device, the deployment of the smart contract on the Ethereum platform is confirmed to the blind box seller, and the contract address is displayed to the blind box seller.

[0107] Figure 5 Another flowchart of the digital blind box processing method provided in the embodiment of the present application is as follows Figure 5 As shown, the method also includes:

[0108] S501. The front-end browser receives the blind box purchase instruction input by the blind box buyer, responds to the blind box purchase instruction, and obtains the blockchain identifier through the front-end verification plug-in.

[0109] Optionally, the front-end browser provides a human-computer interaction interface of a browser terminal to the blind box buyer, and a blind box purchase control is provided on the human-computer interaction interface. When the blind box buyer wants to purchase a digital blind box product, he can perform a second touch operation on the blind box purchase control on the human-computer interaction interface, thereby inputting a blind box purchase instruction to the front-end browser. Among them, the second touch operation on the blind box purchase control can be a single click, double click or long press operation of the blind box purchase control by the blind box buyer, and the operation type of the second touch operation is not specifically limited here.

[0110] The front-end browser responds to the blind box purchase instructions entered by the blind box buyer, verifies the blind box buyer's login information through the front-end MetaMask plug-in, and obtains the blockchain identifier. Among them, the blockchain identifier is used to identify the operating environment of the blockchain, so as to access and call the smart contract deployed on the public blockchain of the Ethereum platform based on the blockchain identifier, thereby ensuring the legitimacy and security of the smart contract access and call.

[0111] It is worth noting that the steps for obtaining the blockchain identifier can refer to the steps for obtaining the blockchain identifier in steps S301-S303, which will not be repeated here.

[0112] S502. The front-end browser receives the blind box purchase data entered by the blind box buyer and sends a blind box purchase request to the back-end server.

[0113] Optionally, the blind box buyer can enter the attributes of the blind box to be purchased on the human-computer interaction interface of the front-end browser, such as the quantity and type of the blind box to be purchased. The front-end browser performs Base64 encoding on the attributes of the blind box to be purchased, encodes the binary data into a string, and generates blind box purchase data in Base64 format. The front-end browser generates a blind box purchase request based on the blind box purchase data in Base64 format and the blockchain identifier and sends it to the back-end server. Among them, the blind box purchase request is a POST HTTP request for blind box purchase.

[0114] S503. The backend server accesses the smart contract based on the blind box purchase request and sends an unsigned purchase transaction containing the blind box price to the front-end browser.

[0115] Optionally, the back-end server accesses the ERC1155 smart contract deployed on the public blockchain of the Ethereum platform based on the POST HTTP request for the blind box purchase, to create an unsigned purchase transaction including the blind box price based on the ERC1155 smart contract, and sends the unsigned purchase transaction including the blind box price to the front-end browser.

[0116] S504. The front-end browser signs the unsigned purchase transaction through the front-end verification plug-in to obtain a signed purchase transaction including the blind box price, and outputs the blind box purchase result based on the signed purchase transaction and the smart contract deployed on the Ethereum platform.

[0117] Optionally, the front-end browser interacts with the MetaMask plug-in on the front end according to the unsigned purchase transaction containing the blind box price sent by the back-end processor, and responds to the blind box buyer's confirmation and signing operation of the unsigned purchase transaction containing the blind box price through the MetaMask plug-in on the front end, and obtains the signed purchase transaction containing the blind box price. Among them, the front-end browser signs the unsigned purchase transaction through the front-end verification plug-in, and the step of obtaining the signed purchase transaction containing the blind box price can refer to the step of obtaining the signed transaction containing the smart contract in step S401, which will not be repeated here.

[0118] The front-end MetaMask plug-in sends the blind box purchase information to the front-end browser according to the signed purchase transaction containing the blind box price and the ERC1155 smart contract pre-deployed on the public blockchain of the Ethereum platform, and the front-end browser displays the blind box purchase result to the blind box buyer according to the blind box purchase information. Among them, the blind box purchase information may include the second hash value and the receipt corresponding to the second hash value.

[0119] In this embodiment, during the purchase of a digital blind box, the front-end browser receives and responds to the blind box purchase instruction input by the blind box buyer, and obtains the blockchain identifier that identifies the blockchain operating environment through the front-end verification plug-in. The front-end browser also receives the blind box purchase data input by the blind box buyer, generates a blind box purchase request based on the blind box purchase data and the blockchain identifier, and sends it to the back-end server. According to the blind box purchase request, the back-end server accesses the smart contract deployed on the public blockchain of the Ethereum platform to create an unsigned purchase transaction containing the blind box price according to the smart contract and send it to the front-end browser. The front-end browser interacts with the front-end verification plug-in based on the unsigned purchase transaction containing the blind box price, obtains the signed purchase transaction containing the blind box price through the front-end verification plug-in, and outputs the blind box purchase result based on the signed purchase transaction and the smart contract deployed on the Ethereum platform. The blockchain identifier can improve the legitimacy and security of calling and accessing smart contracts; sending data in the message body of the blind box purchase request improves the security of data transmission and the amount of data transmitted. Smart contracts deployed on the public blockchain of the Ethereum platform can reduce the cost and improve the efficiency of purchasing blind boxes in large quantities, and ensure the authenticity of digital blind boxes and the rarity of hidden models.

[0120] As an optional implementation, the blind box purchase request includes: a buyer's public key, a blockchain identifier, and blind box purchase data, wherein the buyer's public key is used to identify the blind box buyer.

[0121] Optionally, the blind box purchase request includes purchase request parameters, which are the buyer's public key, blockchain identifier, and blind box purchase data in Base64 format. The buyer's public key is used to identify the blind box buyer, verify the blind box buyer's identity, and track transactions. Through the buyer's public key, the blind box buyer can purchase a blind box, open a blind box, or merge a blind box, ensuring the legality and security of the blind box purchase, opening, and fusion. The blind box purchase data is used to characterize the quantity and type of blind boxes to be purchased entered by the blind box buyer. The blind box purchase request is a POST HTTP request for blind box purchase. The purchase request parameters can be sent in the message body of the request to improve the security and transmission volume of the purchase request parameters.

[0122] The following is a detailed description of the process in which the backend server accesses the smart contract based on the blind box purchase request and sends an unsigned purchase transaction containing the blind box price to the front-end browser.

[0123] Figure 6 A flowchart of the digital blind box processing method provided in the embodiment of the present application for accessing the smart contract and sending an unsigned purchase transaction containing the blind box price to the front-end browser, such as Figure 6 As shown, in the above step S503, the backend server accesses the smart contract according to the blind box purchase request, and sends an unsigned purchase transaction containing the blind box price to the front-end browser, including:

[0124] S601. The backend server determines the address of the smart contract corresponding to the blind box based on the blind box purchase request.

[0125] Optionally, the back-end server queries the address of the ERC1155 smart contract corresponding to the blind box based on the buyer's public key, blockchain identifier and blind box purchase data in Base64 format in the POST HTTP request for blind box purchase sent by the front-end browser.

[0126] S602. The backend server accesses the smart contract according to the address of the smart contract to obtain the blind box price through the smart contract.

[0127] Optionally, the back-end server accesses the ERC1155 smart contract deployed on the public blockchain of the Ethereum platform according to the address of the ERC1155 smart contract corresponding to the blind box, so as to query the price of each blind box pre-set by the blind box seller according to the ERC1155 smart contract.

[0128] S603. The backend server creates an unsigned purchase transaction including the blind box price according to the blind box price and the blind box purchase request and sends it to the front-end browser.

[0129] Optionally, the backend server determines the total blind box price based on the price of each blind box and the number of blind boxes to be purchased entered by the blind box buyer contained in the blind box purchase data in Base64 format in the POST HTTP request for the blind box purchase. The backend server creates an unsigned purchase transaction containing the blind box price based on the total blind box price, and sends the unsigned purchase transaction containing the blind box price to the front-end browser.

[0130] In this embodiment, the back-end server queries the address of the smart contract corresponding to the blind box according to the buyer's public key, blockchain identifier and blind box purchase data in the blind box purchase request, and accesses the smart contract deployed on the public blockchain of the Ethereum platform according to the address of the smart contract corresponding to the blind box, so as to query the price of each blind box according to the smart contract. The back-end server determines the total blind box price according to the price of each blind box and the number of blind boxes to be purchased contained in the blind box purchase data in the blind box purchase request, and creates an unsigned purchase transaction containing the blind box price according to the total blind box price and sends it to the front-end browser, thereby improving the security of blind box purchase.

[0131] Below, the process of outputting the blind box purchase results based on the signed purchase transaction and the smart contract deployed on the Ethereum platform is described in detail.

[0132] Figure 7 A flowchart of the output blind box purchase result of the digital blind box processing method provided in the embodiment of the present application is as follows: Figure 7 As shown, the step of outputting the blind box purchase result according to the signed purchase transaction and the smart contract deployed on the Ethereum platform in the above step S504 includes:

[0133] S701. The front-end verification plug-in calls the blind box purchase function of the smart contract deployed on the Ethereum platform based on the signed purchase transaction, obtains the second hash value and the purchase receipt, and sends them to the front-end browser.

[0134] Optionally, the ERC1155 smart contract deployed on the public blockchain of the Ethereum platform includes a blind box purchase function. The front-end MetaMask plug-in calls the blind box purchase function in the ERC1155 smart contract deployed on the public blockchain of the Ethereum platform according to the received unsigned purchase transaction containing the blind box price. The front-end MetaMask plug-in obtains the second hash value and the purchase receipt corresponding to the second hash value through the blind box purchase function, and sends them to the front-end browser. Among them, the second hash value is the transaction hash value of the blind box buyer purchasing the blind box.

[0135] Specifically, the blind box purchase function in the ERC1155 smart contract sends the NFT of the blind box to be purchased to the MetaMask plug-in on the front end, and generates a transaction hash value of the blind box buyer's purchase of the blind box and the corresponding purchase receipt, which are sent to the MetaMask plug-in on the front end. The ERC1155 smart contract recalculates the number of digital blind boxes available for sale.

[0136] S702. The front-end browser outputs the blind box purchase result to the blind box buyer based on the second hash value and the purchase receipt.

[0137] Optionally, the front-end browser displays the blind box purchase result to the blind box buyer based on the received second hash value and the purchase receipt corresponding to the second hash value. If the ERC1155 smart contract determines that the number of blind boxes to be sold is insufficient or the balance in the blind box seller's wallet address is insufficient, the blind box purchase transaction will be rejected, and the front-end browser displays the blind box purchase result to the blind box buyer as a failed purchase.

[0138] In this embodiment, the front-end verification plug-in calls the blind box purchase function of the smart contract deployed on the Ethereum platform according to the unsigned purchase transaction containing the blind box price, obtains the second hash value and the purchase receipt corresponding to the second hash value through the blind box purchase function, and sends them to the front-end browser. The front-end browser displays the blind box purchase result to the blind box buyer according to the second hash value and the purchase receipt corresponding to the second hash value, so that the blind box buyer can understand the blind box purchase situation.

[0139] Figure 8 Another schematic diagram of the architecture of the digital blind box processing system provided in the embodiment of the present application is as follows Figure 8 As shown, the digital blind box processing system also includes: a large model. Among them, the large model is an artificial intelligence generated content (AIGC) large model, which is used to intelligently generate digital assets corresponding to the blind box. The AIGC large model interacts with the back-end server and the ERC1155 smart contract deployed on the public blockchain of the Ethereum platform, wherein the back-end server can perform a series of processing operations such as creating, purchasing, opening or merging the digital blind box.

[0140] Fig. 9 Another schematic diagram of the architecture of the digital blind box processing system provided in the embodiment of the present application is as follows Fig. 9As shown, the front-end browser includes a personal computer browser and a mobile browser, and the front-end MetaMask plug-in includes the functions of signing and sending transactions, creating users, verifying users, accessing Web3 verification, and obtaining transaction credentials. The back-end server may include a blind box creation interface, a blind box purchase interface, a blind box opening interface, and a blind box fusion interface. The back-end server directly communicates with the ERC1155 smart contract and the AIGC large model deployed on the public blockchain of the Ethereum platform through each blind box interface to realize the operations of creating blind boxes, purchasing blind boxes, opening blind boxes, and fusion blind boxes.

[0141] Fig.10 Another flowchart of the digital blind box processing method provided in the embodiment of the present application is as follows Fig.10 As shown, the method also includes:

[0142] S1001. The front-end browser receives the blind box opening instruction input by the blind box buyer, responds to the blind box opening instruction, and obtains the blockchain identifier through the front-end verification plug-in.

[0143] Optionally, the front-end browser provides a human-computer interaction interface of a browser terminal to the blind box buyer, and a blind box purchase control is provided on the human-computer interaction interface. When the blind box buyer wants to open the previously purchased digital blind box product, he can perform a third touch operation on the blind box opening control on the human-computer interaction interface, thereby inputting a blind box opening instruction to the front-end browser. Among them, the third touch operation on the blind box opening control can be a single click, double click or long press operation of the blind box opening control by the blind box buyer, and the operation type of the third touch operation is not specifically limited here.

[0144] The front-end browser responds to the blind box opening instructions input by the blind box buyer, verifies the blind box buyer's login information through the front-end MetaMask plug-in, and obtains the blockchain identifier.

[0145] S1002. The front-end browser receives the blind box opening data entered by the blind box buyer and sends a blind box opening request to the back-end server.

[0146] Optionally, the blind box buyer can enter the attributes of the blind box to be opened on the human-computer interaction interface of the front-end browser, such as the number and type of blind boxes to be opened. The front-end browser performs Base64 encoding on the attributes of the blind box to be opened, encodes the binary data into a string, and generates blind box opening data in Base64 format. The front-end browser generates a blind box opening request based on the blind box opening data in Base64 format and the blockchain identifier and sends it to the back-end server.

[0147] S1003. The back-end server calls the construction function in the back-end server according to the blind box opening request to construct an unsigned opening transaction containing the number of blind boxes, and sends the unsigned opening transaction containing the number of blind boxes to the front-end browser.

[0148] Optionally, the blind box opening request includes opening request parameters, which are the buyer's public key, blockchain identifier, and blind box opening data in Base64 format, where the blind box opening data is used to characterize the number and type of blind boxes to be opened input by the blind box buyer. The blind box opening request is a POST HTTP request for blind box opening, and the opening request parameters can be sent in the message body of the request to improve the security and transmission volume of the transmission opening request parameters.

[0149] The back-end server calls the Constructor function in the back-end server according to the number of blind boxes to be opened in the blind box opening data of the POST HTTP request for blind box opening, builds an unsigned opening transaction containing the number of blind boxes and sends it to the front-end browser.

[0150] S1004. The front-end browser signs the unsigned open transaction through the front-end verification plug-in, obtains the signed open transaction containing the number of blind boxes, and opens the transaction according to the signature, calls the blind box open function in the smart contract deployed on the Ethereum platform, and obtains the third hash value.

[0151] Optionally, the front-end browser interacts with the MetaMask plug-in at the front end according to the unsigned open transaction containing the number of blind boxes sent by the back-end processor, and responds to the determination and signature operation of the blind box buyer on the unsigned open transaction containing the number of blind boxes through the MetaMask plug-in at the front end, and obtains the signed open transaction containing the number of blind boxes. Among them, the front-end browser signs the unsigned open transaction through the front-end verification plug-in, and the step of obtaining the signed open transaction containing the number of blind boxes can refer to the step of obtaining the signed transaction containing the smart contract in step S401, which will not be repeated here.

[0152] The ERC1155 smart contract deployed on the public blockchain of the Ethereum platform also includes a blind box opening function. The front-end MetaMask plug-in opens the transaction according to the received signature containing the number of blind boxes, calls the blind box opening function in the ERC1155 smart contract deployed on the public blockchain of the Ethereum platform, and the front-end MetaMask plug-in obtains the third hash value and the opening receipt corresponding to the third hash value through the blind box opening function, and sends them to the front-end browser. Among them, the third hash value is the transaction hash value of the blind box buyer opening the blind box.

[0153] S1005. The front-end browser sends the third hash value to the back-end server, and the back-end server calls the big model according to the third hash value to generate the digital assets corresponding to the blind box through the big model.

[0154] Optionally, the front-end browser sends the received third hash value to the back-end server, and the back-end server calls the AIGC big model according to the third hash value. The AIGC big model generates the digital assets corresponding to the blind box and outputs them to the back-end server.

[0155] S1006. The back-end server sends the digital assets corresponding to the blind box to the front-end browser, and the front-end browser outputs the blind box opening result based on the digital assets corresponding to the blind box.

[0156] Optionally, the back-end browser sends the digital assets corresponding to the blind box generated by the AIGC large model to the front-end browser, and the front-end browser displays the blind box opening result to the blind box buyer based on the digital assets corresponding to the blind box, so that the blind box buyer can understand the blind box opening situation.

[0157] In this embodiment, in the process of opening the digital blind box, the front-end browser receives and responds to the blind box opening instruction input by the blind box buyer, and obtains the blockchain identifier through the front-end verification plug-in. The front-end browser also receives the blind box opening data input by the blind box buyer, generates a blind box opening request based on the blind box opening data and the blockchain identifier, and sends it to the back-end server. The back-end server calls the construction function in the back-end server according to the blind box opening request, builds an unsigned open transaction containing the number of blind boxes and sends it to the front-end browser. The front-end browser interacts with the front-end verification plug-in according to the unsigned open transaction containing the number of blind boxes, obtains the signature open transaction containing the number of blind boxes through the front-end verification plug-in, and calls the blind box opening function in the smart contract deployed on the Ethereum platform according to the signature open transaction containing the number of blind boxes, obtains the third hash value and sends it to the back-end server. The back-end server calls the large model according to the third hash value, generates the digital assets corresponding to the blind box by the large model and outputs it to the back-end server, and the back-end browser sends the digital assets corresponding to the blind box to the front-end browser, and the front-end browser displays the blind box opening result to the blind box buyer according to the digital assets corresponding to the blind box, so that the blind box buyer can understand the blind box opening situation. Blockchain identification can improve the legitimacy and security of accessing and calling smart contracts; sending data in the message body of the blind box opening request improves the security of data transmission and the amount of data transmitted. Smart contracts deployed on the public blockchain of the Ethereum platform can reduce the cost of opening blind boxes in large quantities, improve the efficiency of opening blind boxes in large quantities, and ensure the authenticity of digital blind boxes and the rarity of hidden models. By introducing large model technology when opening blind boxes, the intelligence level of generating digital assets is improved.

[0158] Fig.11A flowchart of a digital blind box processing method for generating digital assets corresponding to a blind box provided in an embodiment of the present application is shown in FIG. Fig.11 As shown, the step of generating the digital assets corresponding to the blind box through the large model in the above step S1005 includes:

[0159] S1101. The large model obtains the third hash value and the blind box prompt word pre-entered by the blind box seller.

[0160] Optionally, Fig.12 A schematic diagram of the interactive process of generating digital assets corresponding to a blind box based on a large model provided in an embodiment of the present application, referring to Fig.12 The AIGC big model receives the third hash value sent by the back-end browser and obtains the blind box prompt word pre-entered by the blind box seller. The blind box prompt word is used to indicate the type of blind box created by the blind box seller.

[0161] S1102. The big model integrates the third hash value and the blind box prompt word into the prompt word of the big model to generate and output the digital assets corresponding to the blind box according to the prompt word of the big model.

[0162] Optionally, the AIGC big model integrates the third hash value sent by the back-end browser and the blind box prompt word pre-entered by the blind box seller to obtain the prompt word (Prompt) of the AIGC big model, and inputs the prompt word from the prompt word input end of the AIGC big model into the AIGC big model. The prompt word of the AIGC big model is used to guide the AIGC big model to intelligently generate the digital assets corresponding to the blind box and output them to the back-end server.

[0163] In this embodiment, the big model receives the third hash value and obtains the blind box prompt word pre-entered by the blind box seller, integrates the third hash value and the blind box prompt word into the prompt word of the big model, and guides the big model through the prompt word of the big model to intelligently generate and output the digital assets corresponding to the blind box, so as to display the blind box opening result to the blind box buyer according to the digital assets corresponding to the blind box.

[0164] It is worth noting that the ERC1155 smart contract deployed on the public blockchain of the Ethereum platform in the embodiment of the present application also includes a casting function _mint() and a smelting function _burn(), which supports batch casting of blind box NFTs and batch smelting of NFTs to reduce the cost of batch casting of blind box NFTs and batch smelting of NFTs. Based on the ERC1155 smart contract deployed on the public blockchain of the Ethereum platform and the AIGC large model, multiple unopened blind boxes owned by blind box buyers can be fused to obtain a brand new blind box and open it, and it is possible to obtain the ultimate hidden blind box, which improves the playability and fun of the blind box. Among them, the more unopened blind boxes that are fused, the greater the probability of opening the ultimate hidden blind box.

[0165] An embodiment of the present application also proposes a digital blind box processing system, which includes: a front-end device, a back-end server and an Ethereum platform; a front-end browser and a front-end verification plug-in are deployed on the front-end device.

[0166] The digital blind box processing system is used to execute the steps of the digital blind box processing method described in the aforementioned embodiment.

[0167] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the method embodiment, and will not be repeated in this application. In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0168] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, RandomAccess Memory), disk or optical disk and other media that can store program code.

[0169] The above are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be covered by the protection scope of the present application.

Claims

1. A digital blind box processing method, characterized in that: Applied to a digital blind box processing system, the digital blind box processing system includes: a front-end device, a back-end server and an Ethereum platform; a front-end browser and a front-end verification plug-in are deployed on the front-end device; the method includes: The front-end browser receives the blind box creation instruction input by the blind box seller, responds to the blind box creation instruction, and obtains the blockchain identifier through the front-end verification plug-in; The front-end browser receives the blind box creation data input by the blind box seller, and sends a blind box creation request to the back-end server; The backend server creates a smart contract according to the blind box creation request, and sends an unsigned transaction containing the smart contract to the front-end browser; The front-end browser signs the smart contract through the front-end verification plug-in to obtain a signed transaction containing the smart contract, deploys the smart contract to the Ethereum platform according to the signed transaction, obtains the address of the smart contract in the Ethereum platform through the front-end verification plug-in, and outputs the address of the smart contract.

2. The method according to claim 1, characterized in that The obtaining of the blockchain identifier through the front-end verification plug-in includes: The front-end browser calls the request function in the front-end verification plug-in; The front-end browser receives the confirmation login instruction from the blind box seller, and sends the confirmation login instruction to the front-end verification plug-in; The front-end browser obtains the seller's public key from the front-end verification plug-in, and sends a request to obtain the blockchain identifier to the front-end verification plug-in to obtain the blockchain identifier through the front-end verification plug-in, wherein the seller's public key is used to identify the blind box seller.

3. The method according to claim 1, characterized in that The blind box creation request includes: the seller's public key, the blockchain identifier, and the blind box creation data; The backend server creates a smart contract according to the blind box creation request, including: The back-end server calls the contract creation related functions in the back-end server in sequence according to the blind box creation request to create the smart contract, wherein the contract creation related functions include: open function, create function, compile function and constructor.

4. The method according to claim 1, characterized in that: The front-end browser signs the smart contract through the front-end verification plug-in to obtain a signed transaction containing the smart contract, deploys the smart contract to the Ethereum platform according to the signed transaction, and obtains the address of the smart contract in the Ethereum platform through the front-end verification plug-in, including: The front-end browser sends a seller signature transaction request to the front-end verification plug-in, receives the confirmation deployment instruction input by the blind box seller, responds to the signature operation of the blind box seller, obtains the signature transaction containing the smart contract and sends it to the front-end verification plug-in; The front-end verification plug-in sends the signed transaction to the Ethereum platform, deploys the smart contract on the Ethereum platform according to the signed transaction, obtains the first hash value and sends it to the front-end browser; The front-end browser sends a first receipt request to the front-end verification plug-in according to the first hash value, so as to obtain the address of the smart contract in the Ethereum platform through the front-end verification plug-in.

5. The method according to claim 1, characterized in that The method further comprises: The front-end browser receives a blind box purchase instruction input by a blind box buyer, responds to the blind box purchase instruction, and obtains the blockchain identifier through the front-end verification plug-in; The front-end browser receives the blind box purchase data input by the blind box buyer, and sends a blind box purchase request to the back-end server; The backend server accesses the smart contract according to the blind box purchase request, and sends an unsigned purchase transaction including the blind box price to the front-end browser; The front-end browser signs the unsigned purchase transaction through the front-end verification plug-in to obtain a signed purchase transaction including the blind box price, and outputs the blind box purchase result based on the signed purchase transaction and the smart contract deployed on the Ethereum platform.

6. The method according to claim 5, characterized in that The blind box purchase request includes: a buyer's public key, the blockchain identifier, and the blind box purchase data, wherein the buyer's public key is used to identify the blind box buyer; The backend server accesses the smart contract according to the blind box purchase request, and sends an unsigned purchase transaction containing the blind box price to the front-end browser, including: The backend server determines the address of the smart contract corresponding to the blind box according to the blind box purchase request; The backend server accesses the smart contract according to the address of the smart contract to obtain the blind box price through the smart contract; The back-end server creates the unsigned purchase transaction including the blind box price according to the blind box price and the blind box purchase request and sends it to the front-end browser.

7. The method according to claim 5, characterized in that The outputting of the blind box purchase result according to the signed purchase transaction and the smart contract deployed on the Ethereum platform includes: The front-end verification plug-in calls the blind box purchase function of the smart contract deployed on the Ethereum platform according to the signed purchase transaction, obtains the second hash value and the purchase receipt, and sends them to the front-end browser; The front-end browser outputs the blind box purchase result to the blind box buyer based on the second hash value and the purchase receipt.

8. The method according to claim 1, characterized in that The digital blind box processing system further includes: a large model, and the method further includes: The front-end browser receives the blind box opening instruction input by the blind box buyer, responds to the blind box opening instruction, and obtains the blockchain identifier through the front-end verification plug-in; The front-end browser receives the blind box opening data input by the blind box buyer, and sends a blind box opening request to the back-end server; The back-end server calls the construction function in the back-end server according to the blind box opening request to construct an unsigned opening transaction containing the number of blind boxes, and sends the unsigned opening transaction containing the number of blind boxes to the front-end browser; The front-end browser signs the unsigned opening transaction through the front-end verification plug-in to obtain a signed opening transaction containing the number of blind boxes, and calls the blind box opening function in the smart contract deployed on the Ethereum platform according to the signed opening transaction to obtain a third hash value; The front-end browser sends the third hash value to the back-end server, and the back-end server calls the large model according to the third hash value to generate the digital assets corresponding to the blind box through the large model; The back-end server sends the digital assets corresponding to the blind box to the front-end browser, and the front-end browser outputs the blind box opening result according to the digital assets corresponding to the blind box.

9. The method according to claim 8, characterized in that The generating of the digital assets corresponding to the blind box through the large model includes: The large model obtains the third hash value and the blind box prompt word pre-entered by the blind box seller; The big model integrates the third hash value and the blind box prompt word into the prompt word of the big model to generate and output the digital assets corresponding to the blind box according to the prompt word of the big model.

10. A digital blind box processing system, characterized in that: The digital blind box processing system includes: a front-end device, a back-end server and an Ethereum platform; a front-end browser and a front-end verification plug-in are deployed on the front-end device; The digital blind box processing system is used to execute the steps of the digital blind box processing method as described in any one of claims 1 to 9.

Images