Corresponding digital assets and physical objects

Abstract

A method performed on a computer to associate a digital asset with a physical object. The method includes selecting a record to associate with the digital asset. The method includes receiving a unique identifier associated with the physical object. A method performed on a computer to grant access. The method includes receiving an identifier that identifies the physical object from the computing device. The method includes sending the wallet's unencrypted public key and identifier to the application used to grant access, once it is determined that the conditions are met. Access is granted depending on whether the wallet owns the digital asset linked to the physical object. A method performed on a computer to claim the digital asset linked to the physical object. The method includes determining whether the wallet identifier associated with the wallet owning the digital asset matches the initial wallet identifier. The initial wallet identifier is associated with the minting of the digital asset.

Description

Technical Field

[0001] This application claims priority to U.S. Provisional Application 63 / 430,975, filed Dec. 7, 2022. The entire contents of the above application are hereby incorporated by reference herein.

[0002] This disclosure relates to embodiments of a method and apparatus for associating digital assets, physical assets, and associating digital assets with physical assets, claiming digital assets, and permitting access based on digital assets and physical assets. More specifically, the present disclosure relates to a method and apparatus executable on a computer that associates a digital asset, such as a non-fungible token (“NFT”), with a near-field communication (“NFC”) chip, claims the digital asset linked to the NFC chip, and permits access based on the digital asset and / or the NFC chip.

Background Art

[0003] A new type of entrepreneur has emerged. Creators of all genres, such as entertainers, athletes, artists, gamers, etc., have audiences who desire authentic interaction and engagement with the creators they admire. Historically, these creators have had limited options for engaging with their fan bases and generating revenue, and fans have also had limited options for supporting the creators and demonstrating their connection.

[0004] To bridge this gap, digital assets such as cryptocurrency tokens ("Crypto") and non-fungible tokens ("NFTs") have emerged. Crypto assets help align the incentives of creators and fans, as they allow creators to sell digital assets directly to their fans. For example, professional athletes may release a collection of digital assets capturing the best moments of their careers. Another way creators interact with fans is by selling physical merchandise related to their image. For example, the same athlete might release a sneaker line in collaboration with a sportswear brand. Fans of the athlete can purchase both the digital assets and the sneakers to express their support. [Overview of the project]

[0005] NFTs represent a groundbreaking evolution in asset ownership in the digital environment. Fans can own unique digital assets from their favorite creators. However, current approaches limit the potential of NFTs to the digital world. Because each NFT is unique and verifiable on the blockchain, it has the potential to exercise its rights in the physical world as well. Therefore, new technologies are needed to effectively link and leverage NFTs with physical objects.

[0006] In some embodiments disclosed herein, a user can associate a digital asset with a Near Field Communication (NFC) chip. The NFC chip may be embedded in a physical object. The NFC chip provides a means for linking the digital asset to the physical object. In an exemplary embodiment, a user can receive a pre-encoded Uniform Resource Locator (URL) by scanning the NFC chip with a computing device. The user can select a digital asset and associate it with the NFC chip using the pre-encoded URL.

[0007] Several embodiments disclosed herein enable a user to claim a digital asset linked to an NFC chip. A computing device can receive a request to claim a digital asset in response to a user scanning an NFC chip with a user device such as a mobile phone. The computing device may identify whether a digital asset is available by comparing the current owner of the digital asset with the original entity that minted the digital asset. If the two are the same, the digital asset is available for the user to claim.

[0008] Some embodiments disclosed herein grant access based on ownership of digital assets and / or NFC chips. In exemplary embodiments, a user may be granted access to an event if they can demonstrate ownership of a digital asset and / or physical object (i.e., a physical asset) with an NFC chip that is part of a particular collection. To demonstrate ownership, the user may connect a crypto wallet and / or scan the NFC chip.

[0009] The advantage of the embodiments disclosed herein is to provide a way to efficiently leverage the benefits of digital assets in the real world. By associating digital assets with physical objects, users can easily verify the authenticity of the physical objects. Counterfeit products can be easily identified and eliminated because they do not have an NFC chip linked to the correct digital asset.

[0010] Another advantage of the embodiments disclosed herein is a reliable method of gatekeeping access. Since ownership of a physical object linked to a digital asset cannot be forged, ownership of an object and / or a digital asset can be an efficient way to grant access, for example, to an event or exclusive content. A user deciding whether to grant access can ensure that only persons on a list of those who own the digital asset and / or a physical object with an NFC chip are granted access.

[0011] According to a first aspect, a method is provided for a computer to perform on associating a digital asset with a physical object. The method includes selecting a record to be associated with the digital asset. The method includes receiving a unique identifier associated with the physical object. The unique identifier is obtained by scanning the physical object. The method includes sending a request message. The request message includes the unique identifier and data to be associated with the digital asset.

[0012] In some embodiments, the unique identifier is a pre-encoded uniform resource locator (URL).

[0013] In some embodiments, the physical object includes a Near Field Communication (NFC) chip, and a unique identifier is obtained by scanning the NFC chip of the physical object.

[0014] In some embodiments, record selection includes selecting a record from a list displayed on a graphical display.

[0015] In some embodiments, digital assets are not associated with any physical objects.

[0016] In some embodiments, the request message includes instructions to associate a digital asset with a physical object.

[0017] In some embodiments, the record describes a physical object.

[0018] In some embodiments, the digital asset includes cryptocurrency tokens.

[0019] In some embodiments, the cryptographic token is a non-fungible token (NFT).

[0020] In some embodiments, the physical object is one or more of the following: footwear, clothing, artwork, fixtures, event tickets, and functional assets.

[0021] According to a second aspect, a computing device is provided. The computing device comprises a processing circuit and a memory containing instructions executable by the processing circuit for associating digital assets with physical objects. The computing device operates to select a record associated with a digital asset. The computing device operates to receive a unique identifier associated with a physical object. The unique identifier is obtained by scanning the physical object. The computing device operates to send a request message. The request message includes a unique identifier and data associated with a digital asset.

[0022] According to a third aspect, a method is provided for a computer to perform a claim for a digital asset linked to a physical object. The method includes receiving an identifier from a computing device that identifies the physical object. The identifier is obtained by the computing device scanning the physical object. The method includes identifying the digital asset associated with the physical object. The method includes determining whether a wallet identifier associated with a wallet that owns the digital asset matches an initial wallet identifier. The initial wallet identifier is associated with the minting of the digital asset.

[0023] In some embodiments, the physical object includes a Near Field Communication (NFC) chip, and the identifier is obtained by a computing device scanning the NFC chip of the physical object.

[0024] In some embodiments, the method includes guiding a user of a computing device to a verification web page when it is determined that a wallet identifier associated with a digital asset does not match an initial wallet identifier, receiving the user's wallet identifier, and determining whether the user's wallet identifier matches a wallet identifier associated with a wallet that owns the digital asset.

[0025] In some embodiments, the method includes obtaining an encrypted token and transmitting the encrypted token to a computing device when it is determined that a wallet identifier associated with a digital asset matches an initial wallet identifier.

[0026] In some embodiments, the encrypted token includes one or more of a digital asset identifier associated with the digital asset, a group identifier associated with the digital asset, and a time identifier.

[0027] In some embodiments, the encrypted token includes a successful uniform resource locator (URL) redirect associated with a physical object and / or a NFC chip serial number.

[0028] In some embodiments, the method includes receiving a claim message. The claim message includes a key associated with the wallet and an encrypted token.

[0029] In some embodiments, the method includes determining that the time identifier is not expired and transferring the digital asset to the user's wallet.

[0030] In some embodiments, the method includes receiving a payment identifier associated with a physical object.

[0031] In some embodiments, the digital asset is transferred after receiving the payment identifier.

[0032] In some embodiments, the digital asset includes cryptocurrency tokens.

[0033] In some embodiments, the cryptographic token is a non-fungible token (NFT).

[0034] According to a fourth aspect, a computing device is provided. The computing device comprises a processing circuit and a memory containing instructions executable by the processing circuit for claiming a digital asset linked to a physical object. The computing device operates to receive an identifier from the computing device that identifies the physical object. The identifier is obtained by the computing device scanning the physical object. The computing device operates to identify the digital asset associated with the physical object. The computing device operates to determine whether a wallet identifier associated with a wallet owning the digital asset matches an initial wallet identifier associated with the minting of the digital asset.

[0035] According to a fifth aspect, a method is provided to be performed on a computer that is to be granted access. The method includes receiving an identifier from a computing device that identifies a physical object. The identifier is obtained by the computing device scanning the physical object, which is linked to a digital asset. The method includes receiving an encrypted message, which includes an encrypted token. The method includes determining whether the encrypted token satisfies certain conditions. If the method determines that the conditions are met, it includes sending the application the unencrypted public key and identifier of a wallet to be used to grant access. Access is granted depending on whether the wallet owns the digital asset linked to the physical object.

[0036] In some embodiments, the physical object includes a Near Field Communication (NFC) chip, and the identifier is obtained by a computing device scanning the NFC chip of the physical object.

[0037] In some embodiments, determining whether an encrypted token satisfies a condition includes determining whether the encrypted token is decryptable, or determining whether the time identifier associated with the encrypted token has not expired.

[0038] In some embodiments, the method includes receiving a key message containing a public key, encrypting the public key into an encrypted token, wherein the encrypted token includes a time identifier and a unique identifier key, and storing an initialization vector of the encrypted token in a memory cache.

[0039] In some embodiments, the method includes sending an encrypted token to a browser, which is then displayed to the user as a QR code.

[0040] In some embodiments, encrypted messages are received when the user scans a QR code.

[0041] In some embodiments, access is granted according to ownership of the physical object.

[0042] According to the sixth aspect, a computing device is provided. The computing device comprises a processing circuit and a memory containing instructions that can be executed by the processing circuit to grant access. The computing device operates to receive an identifier from the computing device that identifies a physical object. The identifier is obtained by the computing device scanning the physical object, which is linked to a digital asset. The computing device operates to receive an encrypted message. The encrypted message contains an encrypted token. The computing device operates to determine if the encrypted token satisfies a condition. If the computing device determines that the condition is met, it operates to send the wallet's unencrypted public key and identifier to an application used to grant access. Access is granted depending on whether the wallet owns the digital asset linked to the physical object.

[0043] According to the seventh aspect, a computer program product is provided which includes a non-temporary computer-readable medium storing a computer program that, when executed by a processing circuit, causes the processing circuit to execute a method of any one embodiment of the first, third, and fifth aspects.

[0044] According to the eighth aspect, an apparatus is provided, comprising a memory and a processing circuit coupled to the memory, wherein the apparatus performs a method of any one embodiment of the first, third, and fifth aspects.

[0045] The accompanying drawings, incorporated herein and constituting part of this specification, illustrate various embodiments. [Brief explanation of the drawing]

[0046] [Figure 1] Figure 1 is a block diagram showing architectures according to several embodiments. [Figure 2]Figure 2 is a block diagram showing the manufacturing process of an unencoded NFC chip according to several embodiments. [Figure 3] Figure 3 is a block diagram showing an in-app encoding process for linking physical and digital products according to several embodiments. [Figure 4] Figure 4 is a block diagram showing the manufacturing process of a pre-encoded NFC chip according to several embodiments. [Figure 5] Figure 5 is a block diagram showing the in-app association process for linking physical and digital products according to several embodiments. [Figure 6] Figure 6 is a block diagram showing the process of linking physical assets and digital assets according to several embodiments. [Figure 7] Figure 7 is a sequence diagram illustrating a method for associating an NFC chip with a digital asset according to several embodiments. [Figure 8] Figure 8 is a flowchart showing the process according to several embodiments. [Figure 9] Figure 9 is a block diagram showing the process of claiming a digital asset linked to an NFC chip according to several embodiments. [Figure 10] Figure 10 is a sequence diagram illustrating a method for claiming a digital asset linked to an NFC chip according to several embodiments. [Figure 11A] Figures 11A and 11B show graphical representations of digital assets according to several embodiments. [Figure 11B] Figures 11A and 11B show graphical representations of digital assets according to several embodiments. [Figure 12] Figure 12 shows a graphical representation of claiming digital assets according to several embodiments. [Figure 13] Figure 13 shows a graphical representation of claiming digital assets according to several embodiments. [Figure 14] Figure 14 is a flowchart showing the process according to several embodiments. [Figure 15] Figure 15 is a sequence diagram illustrating how to grant access according to several embodiments. [Figure 16] Figure 16 is a sequence diagram illustrating how to grant access according to several embodiments. [Figure 17] Figure 17 is a flowchart showing the process according to several embodiments. [Figure 18] Figure 18 is a block diagram of a device according to several embodiments. [Modes for carrying out the invention]

[0047] Figure 1 is a block diagram showing architectures according to several embodiments. A physical object 102 (e.g., footwear such as sneakers, apparel, artwork, fixtures, event tickets, or functional assets) may include an NFC chip. The NFC chip may be embedded in the physical object 102 or attached to the physical object 102. The NFC chip may be embodied as a silicon component or integrated circuit and communicate with a computing device 104. The computing device 104 may include an antenna that communicates with the NFC chip of the physical object 102.

[0048] A physical object 102, more specifically an NFC chip, may be linked to a digital asset on blockchain 108. The digital asset may be embodied as a cryptographic token such as an NFT. In some embodiments, a computing device 104 may be used to establish a link between the NFC chip and the digital asset. The computing device 104 may establish a link by communicating with an application programming interface ("API") 106 using a network 110 (e.g., the internet). The API 106 sends a list of available digital assets to the computing device 104. The computing device 104 responds to the API 106 with a digital asset selected from the list and an encoded uniform resource locator ("URL") obtained from the NFC chip. The API 106 then sends the linked association between the NFC chip and the digital asset to blockchain 108 using the network 110.

[0049] In some embodiments, the computing device 104 may claim digital assets on behalf of the user. For example, the user purchases a physical object 102, and this purchase includes a linked digital asset. To acquire the digital asset, the user can request API 106 to transfer ownership of the digital asset on blockchain 108 to their crypto wallet. A crypto wallet is a self-managed digital wallet used to store and manage digital assets such as cryptocurrencies and NFTs. The user is first required to prove ownership of the physical object 102 by scanning the NFC chip with the computing device 104.

[0050] In some embodiments, a user may be granted access by proving ownership of the physical object 102 and / or the digital assets linked thereto. To prove ownership of the digital assets, the user can connect their wallet containing the digital assets to API 106. API 106 can compare the wallet address with the address listed as the owner of the digital assets on blockchain 108. If the two addresses match, the user's proof of ownership of the digital assets is successful. The user can prove ownership of the physical object 102 by scanning the NFC chip with a computing device 104.

[0051] Linking NFC chips to digital assets

[0052] Physical goods (i.e., assets or objects) are increasingly accompanied by corresponding digital versions (digital versions of goods, digital certificates, etc.). To link physical goods with their digital versions (and vice versa), a unique identifier can be assigned to the physical goods. Often, this is a scannable chip (e.g., an NFC chip) programmed to be linked to the corresponding digital asset (e.g., an NFT). In some embodiments, there can be a one-to-one relationship between the physical goods, their corresponding chips, and the digital assets.

[0053] In some embodiments, the NFC chip, which is a scannable chip, may not be pre-encoded and may support data writing. In this case, the user can use an application that has the ability to write data to the NFC chip. When an order is made, such as a purchase on an e-commerce website or the exchange of a digital asset for a physical product, a unique URL is generated and can be used to encode it onto a blank NFC chip. This URL links the physical product to the digital asset. The digital asset is linked to the order and the URL, and the URL is encoded onto the physical product.

[0054] Users can also lock the NFC chip. Locking the NFC chip prevents tampering with or rewriting of the data on the chip.

[0055] Figure 2 is a block diagram showing the manufacturing process of an unencoded NFC chip according to several embodiments. Process 200 may begin from step 202.

[0056] In step 202, the NFC chip is procured from the manufacturer, who may not provide any pre-encoding instructions. In step 204, the manufacturer or assembler of the final product receives the NFC chip and may attach or embed it in a physical object. In step 206, the finished product with the embedded NFC chip, i.e., the physical object, is sent to a fulfillment warehouse where the NFC chip is encoded.

[0057] Figure 3 is a block diagram illustrating an in-app encoding process for linking physical and digital products according to several embodiments. Process 300 begins with step 302.

[0058] In 302, the app user can select an order to fulfill from a list within the application. Each order may include a description of a physical object and a digital asset. In some embodiments, the computing device may be an Android® or Apple® smartphone.

[0059] In 304, the user can select a physical object from the selected order that matches the description of the physical object. For example, the user can select a physical object that is the same size and color as the description of the physical object.

[0060] In 306, the user can scan the NFC chip in the product to encode the URL associated with the NFC chip into a digital asset. In some embodiments, this creates a one-to-one link between the NFC chip and the digital asset on the blockchain. In 308, the user can lock the NFC chip to make the data immutable. At this point, an association is established between the URL encoded in the NFC chip and the digital asset.

[0061] Figure 4 is a block diagram showing the manufacturing process of a pre-encoded NFC chip according to one of several embodiments. Process 400 can begin from step 402.

[0062] In 402, the manufacturer can encode a unique URL for the NFC chip according to the provided criteria. In 404, the manufacturer can complete the manufacturing and encoding process and ship the NFC chips to the final product manufacturer or assembler. In 406, the NFC chips are randomly selected by the final product manufacturer. The final product manufacturer can attach the NFC chips to a physical object or embed the NFC chips into a physical object. In 408, the finished products are sent to a fulfillment warehouse for association and shipment to the customer.

[0063] Figure 5 is a block diagram showing an in-app association process for linking physical and digital products according to several embodiments. Process 500 can begin from step 502.

[0064] In 502, the user can select an order to fulfill from a list within the application. Each order may include a description of a physical object and a digital asset. In 504, the user can select a physical object that matches the description of the physical object. For example, the user can select a physical object from the list that is the same size and color as the physical object.

[0065] In 506, the user can scan the NFC chip on a physical object to identify the encoded URL. In 508, the user can press the association button to create a new database record that associates the digital asset with an NFC-specific identifier (e.g., a URL).

[0066] Figure 6 is a block diagram illustrating the process of linking physical and digital assets according to several embodiments. Process 600 can begin from step 602. In 602, the user can identify the order to be fulfilled and retrieve the appropriate products. In 604, the user searches for the order in an application. In some embodiments, the user can search for the order on a computing device such as an Android or Apple smartphone.

[0067] Before goods are delivered to customers, users / fulfillment personnel can use the application to search for orders in the order management system via the marketplace API. When the application is opened, an order list containing order IDs and corresponding verification URLs is retrieved from the marketplace API and stored locally on the device. Orders are presented in list format, identified by order number, and matched one-to-one with the corresponding verification URLs for the customer's digital assets (e.g., information about assets corresponding to physical items). In some embodiments, this information is retrieved from the marketplace API and takes the form of verification URLs. When a user taps an order from the list, they can be taken to a new page displaying the order information and verification URL, and which has a button to read an NFC chip and associate it with the order.

[0068] With version 606, the user can scan the product to encode a verification URL into the chip and obtain the serial number. The user can then press the "Read" button and bring the NFC chip close to the device that will scan the product to be fulfilled. This reads the data on the NFC tag and obtains the serial ID of the NFC tag attached to (or associated with) the physical product.

[0069] In step 608, the user can verify the order is correct and update the verification URL database record with the serial number of the NFC tag. When the user presses the "Set Serial Number" button, the serial ID is uploaded to the marketplace server and the ID is stored in the database along with the verification URL encoded on the chip. Next, the user can press the "Associate" button and scan the product again to associate the URL encoded on the NFC chip with the digital asset of the specified order.

[0070] In 610, the user can rescan the product to lock the NFC tag. In some embodiments, the NFC tag is not pre-encoded and needs to be encoded when the order is fulfilled. In this case, the user needs to encode the URL associated with the order to be fulfilled into the NFC tag. The user can press the "Encode" button to write the URL to the chip. The user then visually verifies that the encoded data is correct and locks the NFC tag. The size of the ordered product must match the size of the actual product, and the order name must match the NFT owner name. The user presses the "Lock" button and rescans the NFC tag to lock it.

[0071] With step 612, the user can proceed with fulfilling the order. Once the NFC tag is properly associated, the order is ready for fulfillment.

[0072] Figure 7 is a sequence diagram showing how to associate an NFC chip with a digital asset according to several embodiments. To associate a digital asset with a physical item, a pre-encoded NFC chip must be associated with a database record that references the digital asset on the blockchain. Method 700 begins with step 702.

[0073] In 702, API 705 may provide the computing device 701 with a list of object descriptions. The list of object descriptions includes a description of the object (e.g., size, color, pattern) and the associated digital assets. In some embodiments, the digital assets are pre-created and stored on the blockchain. In some embodiments, the computing device may be embodied as an Android or Apple smartphone.

[0074] An application on computing device 701 may have the ability to read order data from API 705 and store it in local persistent memory. Downloading this order data in advance before fulfillment begins reduces the risk of work stoppages due to network latency or data unavailability. Orders are presented in a list by drop and accessed when the user taps a drop button on the main screen. A drop is a group of physical objects and digital assets. In some embodiments, an order represents an e-commerce order placed through a web store or individual items within a bulk-ordered product. An order may or may not show product size or other details. An order may also be linked one-to-one with a digital asset.

[0075] If the order data has not been downloaded, the user must first tap the refresh icon for the drop they wish to order on the main screen to download the order data. Once the data is downloaded, the user can tap the drop to proceed to the order screen.

[0076] In 704, the user of computing device 701 can select an object description from a list. The user can select an object description using the graphical display provided by computing device 701. By selecting an object description, the user is also selecting a digital asset. The user can select an object description based on a description that matches the physical object 703.

[0077] When the user presses "Associate," they can move to the "Associate" screen. Here, the user can scan the target NFC chip using computing device 701. This reads the chip, and a pre-encoded URL is stored in local memory. In 706, the user can scan the NFC chip of physical object 703 using computing device 701. The NFC chip of physical object 703 can respond with the URL encoded in 708.

[0078] In 710, the computing device 701 can send an association message to API 705 to associate the NFC chip with a digital asset. In some embodiments, pressing the association button sends a network request to API 705 containing the digital asset data to be associated with the scanned URL. In 712, the API can associate the NFC chip with a digital asset on blockchain 707. API 705 can receive the scanned URL, decode it, and receive the chip's UID. This UID, along with the digital asset data, is inserted into a database such as blockchain 709 to create an association between the NFC chip and the digital asset. Finally, the user can press the "Done" button to flag the digital asset as associated, preventing duplicate associations.

[0079] Figure 8 is a flowchart showing the process according to several embodiments.

[0080] Process 800 is a method performed by a computer to associate digital assets with physical objects. Referring to Figure 8, process 800 can begin from step s802.

[0081] Step s802 involves selecting the record associated with the digital asset.

[0082] Step s804 involves receiving a unique identifier associated with the physical object. The unique identifier is obtained by scanning the physical object.

[0083] Step s806 includes sending a request message. The request message includes a unique identifier and data associated with the digital asset.

[0084] In some embodiments, the unique identifier is a pre-encoded uniform resource locator (URL). In some embodiments, the physical object includes a Near Field Communication (NFC) chip, and the unique identifier is obtained by scanning the NFC chip of the physical object. In some embodiments, record selection includes selecting a record from a list displayed on a graphical display. In some embodiments, the digital asset is not associated with any physical object. In some embodiments, the request message includes instructions to associate the digital asset with a physical object. In some embodiments, the record describes a physical object. In some embodiments, the digital asset includes a cryptographic token. In some embodiments, the cryptographic token is a non-fungible token (NFT). In some embodiments, the physical object is one or more of the following: footwear, clothing, artwork, fixtures, event tickets, and functional assets.

[0085] In-person NFT billing

[0086] In some embodiments, a pre-encoded NFC chip embedded or attached to a physical product may function as a link to a corresponding digital asset. The digital asset may be pre-created, and the NFC chip may be programmed to link to one of a set of digital assets. A user can claim the corresponding digital asset for a physical product by scanning the NFC chip contained within that product. By owning the physical product, the owner can acquire the right to own the digital component, which is made possible by scanning the embedded or attached NFC chip with an NFC-readable device such as an Android or Apple device.

[0087] An NFC chip can be implemented as a thin integrated circuit that enables bidirectional communication between two devices (one circuit and the other a device capable of transmitting radio waves). Radio waves power the circuit and allow data to be read from and written to the circuit. In some embodiments, the NFC chip may be embedded in a physical object, such as a tag on the tongue of a sneaker or a silicone label heat-pressed onto a T-shirt, sweatshirt, bag, etc.

[0088] Most consumer mobile phones have NFC functionality. The back or top of the phone may have a wireless antenna that can automatically detect and read NFC chips when they are very close (for example, within 4 cm).

[0089] When a user purchases a physical product associated with a digital asset, the user can claim the corresponding digital asset after owning the physical product.

[0090] Figure 9 is a block diagram showing the process of claiming a digital asset linked to an NFC chip according to one embodiment. The process 900 begins with step 902.

[0091] In step 902, the user initiates the process of claiming a digital asset linked to an NFC chip. In step 904, the user scans the NFC chip within a physical object, such as a pair of sneakers. The user performs the scan using a computing device.

[0092] In some embodiments, a user can identify a physical object by scanning the item, optically identifying the item or its components, or by any other form of scanning or identifying the item, using a mobile device such as an Android or Apple phone. Scanning can be performed using any technology, including NFC, Quick Response ("QR"), Radio Frequency Identification ("RFID"), and optical scanning. Upon successful identification, a verification website or application opens, displaying the linked digital asset corresponding to the physical item.

[0093] In step 906, the API receives a claim request for a digital asset and determines whether the digital asset has already been claimed. The digital asset may be embodied as an NFT. The website or application determines whether the digital asset corresponding to the physical object has been claimed. To do this, it sends a network request to the backend service. The backend service finds the owner of the digital asset by calling a function in the blockchain smart contract called "ownerOf" using the token ID of the digital asset. ownerOf is a smart contract function defined in the ERC 721 smart contract that searches for the owner of a given token ID.

[0094] Next, we compare this address to a known custody wallet address that was initially used to mint the digital asset. If the two addresses are the same, the digital asset has not yet been claimed.

[0095] If the digital asset has already been claimed, process 900 can proceed to step 908. In step 908, the API can redirect the user to a verification page. If the digital asset has already been claimed, i.e., the owner of the digital asset does not match the address in the custody wallet, the site or application can redirect the user to a verification page. On the verification page, the user can verify ownership of the digital asset by connecting their wallet and confirming that the connected wallet owns the digital asset.

[0096] In step 910, the user can connect their crypto wallet to the verification page to verify ownership of the NFT. Verification is the process by which the owner of a physical object with an embedded NFC chip scans the chip and verifies the details of the digital asset associated with the NFC chip. Here, the user can connect their crypto wallet to prove that they own the digital asset associated with the physical object.

[0097] In some embodiments, verification may involve a user scanning an NFC chip on a physical object using a mobile device. The URL on the chip is opened in a web browser. This URL may be a unique small URL. This small URL is processed by a backend service and can redirect the web browser to a website containing a token that includes information about the digital asset connected to the physical item. The web page provides the user with details and also allows the user to connect to a wallet to prove ownership of the digital asset.

[0098] Figures 11A and 11B show graphical representations of digital assets according to several embodiments. Web page 1100 shows a verification page. Web page 1100 may include a visual representation 1102 of the digital asset. Web page 1100 may also include the status 1104 of the digital asset, the name 1106 of the digital asset, a description 1008 of the associated physical object (e.g., size), the owner 1110 of the digital asset, a link to the blockchain 1112, and a button 1114 to disconnect the user's wallet. In this embodiment, the connected wallet does not own the digital asset.

[0099] Referring to Figure 9, if the digital asset has not been claimed, step 900 can proceed to step 912. In 912, the API can redirect the user to a claim page that includes token claiming. If the digital asset has not yet been claimed, the verification service can redirect the user to a webpage with the steps and functions to claim the digital asset. This redirect request may include an encrypted token containing information about the token ID of the digital asset to be claimed, the collection to which the digital asset is associated, and its expiration date. The expiration date prevents malicious scanning by requiring the user to complete the claim within a certain time frame. In some embodiments, this expiration date is 10 minutes from the token's creation. The claiming flow is a specific feature of the site or application that guides the user through the process of connecting or creating a crypto wallet. The user then verifies that the wallet is correct and begins the process of transferring the digital asset from the custody wallet to the user's own wallet.

[0100] Figure 12 shows a graphical representation of a digital asset claim according to several embodiments. A user can claim a digital asset using the graphical representation 1200. The graphical representation 1200 includes a description of the digital asset 1202, a link 1204 to create a crypto wallet, and a link to connect to a crypto wallet. After the user creates a wallet or connects to a wallet, the user can proceed to the graphical representation 1300.

[0101] Figure 13 shows a graphical representation of a digital asset claim according to several embodiments. The graphical representation 1300 includes a description of the digital asset 1302, the address of the connected wallet 1304, the terms and conditions 1306, and a button 1308 to claim the digital asset.

[0102] If a digital asset is not claimed, the user is directed to a claim flow that includes an encrypted web token for the digital asset they wish to claim. This web token may contain information about the specific digital asset, the collection to which the digital asset belongs, the time limit the user must complete the claim flow before the token expires, and where the user will be redirected if they successfully claim the digital asset.

[0103] The contents of this encrypted web token may include the following: • Digital Asset Token ID • Digital asset name or drop name • Token expiration date • Successful URL redirection

[0104] This URL is a verification URL generated using the digital asset ID and drop data. For claimed digital assets, the scan is typically sent to this URL. The purpose here is to provide a place where the user can verify the digital asset after a successful claim.

[0105] In some embodiments, the encrypted web token may include the serial number of the NFC chip.

[0106] In some embodiments, a user cannot claim a digital asset unless they have confirmed that they have purchased the corresponding product. Sales verification can be performed by integrating with a point-of-sale (POS) system or an e-commerce system.

[0107] In 914, users can connect their crypto wallets to the claim page. Once the crypto wallet is connected, users can confirm that this is an irrevocable transaction by agreeing to the terms of service before proceeding by pressing the claim button. On the claim flow page, users can provide a blockchain-based public key wallet address to which digital assets can be transferred. This can be done by connecting to a wallet via a web browser plugin such as MetaMask or MyEtherWallet (MEW), or by authenticating with a third-party wallet provider such as Magic.Link.

[0108] In 916, the API can request that the connected wallet be billed for digital assets. After the wallet is connected, to process the transfer of digital assets, the site or application sends a request to the backend API using the encrypted web token and the connected wallet address. The digital assets are billed to this address.

[0109] In step 918, step 900 determines whether the claim token is valid. In some embodiments, the web token has a limited validity period. If the user takes longer to complete the transaction than the web token's validity period, the claim flow times out, and the user must re-identify (i.e., rescan) the physical object to obtain a new encrypted web token and start the process again from the beginning. In the backend, the claim token is decrypted and its expiration date is checked.

[0110] If the claim token is valid, step 900 proceeds to step 920. In step 920, the digital asset is transferred to the provided wallet address. If the token is authenticated, the claim request is processed using information about the digital asset. This information may include the digital asset token ID and drop name to prevent malicious users from inserting a different token ID when submitting a claim along with the wallet address.

[0111] Blockchain transactions may be created and sent to the blockchain. These transactions may include calls to the claimTo or transferFrom function, which change ownership of a digital wallet from a custody wallet to a specified wallet address.

[0112] `transferFrom` is a smart contract function defined in ERC 721 smart contracts that transfers an NFT from one address to another.

[0113] claimsTo is a smart contract function that enables secure transfers from a pre-specified custody wallet to a target wallet address.

[0114] The following is the `claimTo` function, a smart contract that enables the claiming of digital assets. This function is called by the API, signs the transaction using the private key of the deployer address, and sends it to the blockchain. The function's parameters are `userWallet` and `tokenId`, which are the destination wallet address and the digital asset token ID being claimed, respectively. This function is a wrapper for `safeTransferFrom`, which uses the custody wallet address as the source. This prevents the transfer of digital assets that have already been claimed. functionclaimTo( address _userWallet, uint256 _tokenId ) public { safeTransferFrom(CustodialWalletAddress, _userWallet, _tokenId); }

[0115] A TypeScript function that calls `claimTo` in a program.

[0116] This function is a TypeScript implementation that calls the smart contract's claimTo function using the provided information. It is provided with the smart contract, the digital asset token ID, the recipient wallet address, the URL of the blockchain to which the transaction will be sent (which determines whether the transaction will be sent to Ethereum, Polygon, or a staging environment on either chain), and finally, the private key of the signer's wallet (usually a custody wallet). Once sent to the blockchain, a transaction hash is returned, allowing the frontend to periodically check the transaction status. const claimNFT = async ( contract: any, tokenId: number, toWalletAddress: string, rpcUrl: string, signerPk: string ) => { const claimToTxn = contract.contract.methods.claimTo( toWalletAddress, PIN ID ); const result = await ethTransactionSend({ nftContractAddress: contract.address, transaction: claimToTxn, signerPk, rpcUrl, }); return result.transactionHash; };

[0117] In step 922, the user is shown that the transfer is complete and is prompted to go to the verification page. Once the transaction is sent to the blockchain, the transaction hash is returned to the frontend webpage or application, allowing the transaction status to be checked at set intervals. The webpage uses the transaction hash to request the transaction status on the blockchain. Once the blockchain confirms that the transaction write was completed successfully, the user is shown a success message and given the option to view the requested NFT.

[0118] If the billing token is invalid, process 900 can proceed to step 924. In step 924, the API can inform the user that the token is invalid and prompt the user to scan the shoes again.

[0119] Figure 10 is a sequence diagram showing a method for claiming a digital asset linked to an NFC chip according to one embodiment. Method 100 can begin from step 1002.

[0120] In step 1002, user 1003 can scan the NFC chip of the physical product 1001. Scanning the NFC chip opens a URL on user 1003's device. The URL opens and connects directly to API 1007 to check the status of the digital asset linked to the NFC chip.

[0121] In 1006, API 1007 compares the owner of a digital asset with a custody wallet using Web 31011, which is a blockchain. A blockchain is a system that records transactions on a peer-to-peer digital ledger. In some embodiments, a blockchain may include the Ethereum Virtual Machine or EVM, which is the underlying technology that drives multiple different blockchains and enables functions such as state management and smart contracts.

[0122] In 1008, API 1007 may create a unique claim token to authenticate the claim action. API 1007 may store the token in cache 1009 for later verification. Cache 1009 is a web service running in the cloud in parallel with the API and may be used to store temporary or non-persistent values. API 1007 may then redirect user 1003 to web page 1005, which displays the claim page containing the claim token. Web page 1005 is displayed on user 1003's computing device. In 1012, user 1012 can connect their crypto wallet to Web 31011 and receive the claim digital assets.

[0123] At 1014, user 1003 checks their wallet and presses the "Claim" button on webpage 1005. Webpage 1005 then sends the public key and claim token to API 1007, initiating the claim process at 1016. At 1018, API 1007 verifies the authenticity of the received claim token by decrypting it using the version stored in cache 1009. API 1007 successfully decrypts the token and verifies the authenticity of the claim at 1020. At this point, the user's wallet can receive the digital assets.

[0124] In 1022, API 1007 sends a function to Web 31011 that transfers ownership of the digital asset to user 1003's wallet. In some embodiments, API 1007 calls claimTo or safeTransferFrom on the smart contract to claim the digital asset to the provided wallet and returns the transaction hash when the transaction is sent to the blockchain.

[0125] At step 1024, API 1007 responds to web page 1005 with the UI and transaction hash. At step 1026, web page 1005 uses Web 31011 to check the transaction status using the transaction hash. Web 31011 responds when the transaction has been successfully written, the billing process is complete, and at step 1028, the user now owns the NFT. At step 1030, web page 1005 displays the billed digital asset to user 1003.

[0126] Figure 14 is a flowchart showing the process according to several embodiments.

[0127] Step 1400 is a method performed on a computer to bill for digital assets linked to physical objects. Referring to Figure 14, step 1400 can begin from step s1402.

[0128] Step s1402 includes receiving an identifier that identifies a physical object from the computing device, the identifier being obtained by the computing device scanning the physical object.

[0129] Step s1404 includes identifying the digital assets associated with the physical object.

[0130] Step s1406 includes determining whether the wallet identifier associated with the wallet that owns the digital asset matches the initial wallet identifier associated with the minting of the digital asset.

[0131] In some embodiments, the physical object includes a Near Field Communication (NFC) chip, and the identifier is obtained by a computing device scanning the NFC chip of the physical object.

[0132] In some embodiments, the method includes determining that the wallet identifier associated with a digital asset does not match the initial wallet identifier, directing the user of the computing device to a verification webpage, receiving the user wallet identifier, and determining whether the user wallet identifier matches the wallet identifier associated with the wallet that owns the digital asset.

[0133] In some embodiments, the method includes determining that a wallet identifier associated with a digital asset matches an initial wallet identifier, obtaining an encrypted token, and sending the encrypted token to a computing device.

[0134] In some embodiments, the encrypted token includes one or more of the following: a digital asset identifier associated with the digital asset, a group identifier associated with the digital asset, and a time identifier.

[0135] In some embodiments, the encrypted token includes a successful uniform resource locator (URL) redirect and / or a serial number on an NFC chip associated with a physical object.

[0136] In some embodiments, the method includes receiving a billing message, which includes a key and an encrypted token associated with a wallet.

[0137] In some embodiments, the method includes determining whether a time identifier has expired and transferring the digital asset to the user's wallet.

[0138] In some embodiments, the method includes receiving a payment identifier associated with a physical object.

[0139] In some embodiments, the digital asset is transferred after the payment identifier is received.

[0140] In some embodiments, the digital asset includes cryptocurrency tokens.

[0141] In some embodiments, the cryptographic token is a non-fungible token (NFT).

[0142] Permission to access

[0143] In some embodiments, users may be granted access to online and in-person benefits if they can prove they own the digital assets and / or corresponding physical items belonging to a particular drop. A drop may refer to a collection of individual products, which may be produced in limited quantities and typically offered only for a short period. Users may be required to prove they own the physical goods or the digital assets. In some embodiments, users may be required to prove they own both the physical goods and the corresponding digital assets.

[0144] To prove ownership of genuine digital assets, users may need to connect their digital wallet or hardware wallet to a verification webpage or mobile application that contains the associated digital assets.

[0145] For web pages with cryptocurrency wallet functionality, users can connect their wallet to a cryptocurrency wallet browser extension, allowing the web page to access the user's wallet's public key. This public key may be matched against the owner of the associated digital asset. If the two wallet addresses match, the user proves ownership of the digital asset, and ownership is verified.

[0146] For users of the mobile application, or users using a webpage without a cryptocurrency wallet function, a secure one-to-one connection can be established between the mobile application and a desktop computer-based browser with a connected cryptocurrency wallet.

[0147] Figure 15 is a sequence diagram illustrating access permission methods according to several embodiments. The user first scans the NFC chip to obtain information associated with the connected digital asset. This reads the digital asset number and DropID from the blockchain and displays them to the user. Method 1500 can begin from step 1502.

[0148] In step 1502, user 1501 requests to connect their wallet to wallet provider 1505. User 1501 may be a person who owns both digital NFTs and physical products and is seeking to verify ownership.

[0149] In step 1504, the wallet provider 1505 may expose the wallet's public key to the frontend webpage 1503. The frontend webpage 1503 may send the public key to API 1507. The frontend webpage 1503 may have encryption capabilities. Once connected, the webpage 1503 may use the wallet's public key to generate a unique QR code in which the wallet's public key is encoded as an image.

[0150] In step 1508, API 1507 encrypts the public key and stores the initialization vector of that encryption in cache 1509. Cache 1509 is a data store, such as Redis, that can store data as key-value pairs with expiration dates. The API encrypts the public key into a token with an expiration date and a unique identification key. The initialization vector of the encrypted token is inserted into cache 1509 along with the same expiration date and the corresponding wallet public key. Once the expiration date has passed, the initialization vector is deleted and the encrypted token becomes unusable.

[0151] In step 1510, API 1507 returns the encrypted values ​​of the public key, expiration date, and cache key to the frontend webpage 1503. The frontend webpage 1503 displays the encrypted values ​​to user 1501 as a QR code. The QR code is read by the camera on the mobile device.

[0152] Figure 16 is a sequence diagram showing a method for granting access according to several embodiments. Method 600 can begin from step 1602.

[0153] In step 1602, user 1601 scans the NFC chip using a computing device and connects to the digital asset using mobile application 1603. In step 1604, mobile application 1603 switches to a web browser to generate a QR code. In step 1606, user 1601 scans the QR code using the device's camera. In response, the mobile application reads the encrypted token in step 1608 and sends the encrypted token to API 1607 in step 1610.

[0154] At step 1612, API 1607 accesses the token initialization vector from cache 1609, and cache 1609 returns the initialization vector to API 1607 at step 1614. At step 1616, API 1607 decrypts the token and responds to the mobile application using the public key.

[0155] API 1607 decrypts the token to obtain the public key, expiration date, and unique cache key. In some embodiments, the request is rejected if decryption of the token fails because the token is in an invalid format or is invalid. The request is rejected if the token is decrypted but has expired. The request is rejected if the unique key does not exist in the in-memory cache 1609 due to a reset or expiration. If all checks are successful, API 1607 returns the unencrypted public key to the mobile app. Once the app obtains the unencrypted public key, it can verify ownership of the scanned digital asset by comparing the connected public key with the wallet address of the owner of the scanned digital asset.

[0156] In step 1618, the mobile application 1603 verifies the public key of the digital asset scanned on Web 31605. Since ownership of the digital item is authenticated, the user is granted access to the token gate space or event (physical or digital).

[0157] In some embodiments, to verify ownership of a genuine physical item, a user can scan an embedded or mounted NFC chip with an NFC-enabled device, such as an Android or Apple smartphone. For products with encrypted NFC chips, the manufacturing process of these chips is protected and cannot be duplicated, potentially allowing authentication to be verified simply by opening a webpage. For unencrypted NFC chips, the user may need to connect to the digital component to prove ownership and thus verify true ownership.

[0158] When a physical item is scanned, the user may be directed to a verification page or mobile application for the associated digital asset. On this page, the user can connect the wallet that owns the associated digital asset by connecting their own wallet or by signing in to a third-party wallet provider to prove ownership of the digital asset.

[0159] By identifying physical items and connecting them to digital or hardware wallets, a unified digital / physical identity is created, allowing users to participate in authenticated, user-specific online digital experiences and in-person physical experiences.

[0160] Figure 17 is a flowchart showing the process according to several embodiments.

[0161] Step 1700 is the method to be performed on the computer that is granted access. Referring to Figure 17, step 1700 can begin from step s1702.

[0162] Step s1702 includes receiving an identifier from the computing device that identifies a physical object. The identifier is obtained by the computing device scanning the physical object, which is linked to a digital asset.

[0163] Step s1704 involves receiving an encrypted message, the encrypted message containing an encrypted token.

[0164] Step s1706 includes determining whether the encrypted token meets the requirements. Step s1708, if the requirements are determined to be met, includes sending the wallet's unencrypted public key and identifier to the application used to grant access, which is granted depending on whether the wallet possesses digital assets linked to physical objects.

[0165] In some embodiments, the physical object includes a Near Field Communication (NFC) chip, and the identifier is obtained by a computing device scanning the NFC chip of the physical object.

[0166] In some embodiments, determining whether an encrypted token satisfies a condition includes determining whether the encrypted token is decryptable, or whether the time identifier associated with the encrypted token has not expired.

[0167] In some embodiments, the method includes receiving a key message containing a public key, encrypting the public key into an encrypted token, ensuring that the encrypted token includes a time identifier and a unique identifier key, and storing an initialization vector of the encrypted token in a memory cache.

[0168] In some embodiments, the method includes sending an encrypted token to a browser and displaying the encrypted token to the user as a QR code.

[0169] In some embodiments, encrypted messages are received by the user by scanning a QR code.

[0170] In some embodiments, access is granted according to ownership of the physical object.

[0171] Figure 18 is a block diagram of the apparatus 1800 according to several embodiments. As shown in Figure 18, the apparatus comprises a processing circuit (PC) 1802 including one or more processors (P) 1855 (e.g., general-purpose microprocessors and / or one or more other processors, e.g., application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc.), a network interface 1848 including a transmitter (Tx) 1845 and a receiver (Rx) 1847 that enable the transmission and reception of data to and from other computing devices connected to a network 1810 (e.g., an Internet Protocol (IP) network) to which the network interface 1848 is connected, and a local storage device (also known as a “data storage system”) 1808 including one or more non-volatile storage devices and / or one or more volatile storage devices. In embodiments in which the PC 1802 includes a programmable processor, a computer program product (CPP) 1841 may be provided. The CPP 1841 includes a computer-readable medium (CRM) 1842 that stores a CP including computer-readable instructions (CRI) 1844. CRM1842 may be a non-temporary computer-readable medium such as a magnetic medium (e.g., a hard disk), an optical medium, or a memory device (e.g., random access memory, flash memory).

[0172] In some embodiments, the device 1800 may have and / or perform any of the computing devices, APIs, and objects described in Figures 1-12. In some embodiments, the CRI 1844 of the computer program 1843, when executed by the PC 1802, causes the device 1800 to perform the steps / functions described herein (for example, steps / functions described herein with reference to Figures 2-17). In other embodiments, the device 1800 may perform the steps / functions described herein without requiring code. That is, for example, the PC 1802 may consist of only one or more ASICs. Thus, the features of the embodiments described herein may be implemented in hardware and / or software.

[0173] While various embodiments of the Disclosure are described herein, it should be understood that these are presented for illustrative purposes only and are not limiting. Therefore, the scope and extent of the Disclosure should not be limited by any of the above-described exemplary embodiments. Furthermore, unless otherwise described herein or otherwise clearly contradicted by the context, all possible combinations of the above elements are incorporated herein.

[0174] Furthermore, although the process described above and shown in the diagrams is presented as a series of steps, this is done solely for illustrative purposes. Therefore, it is conceivable that some steps may be added, some may be omitted, the order of the steps may be changed, or some steps may be performed in parallel.

Claims

1. A computer-based method (800) for associating a digital asset with a physical object (102), Selecting a record associated with the aforementioned digital asset (s802), Receiving a unique identifier associated with the physical object (s804), wherein the unique identifier is obtained by scanning the physical object, Sending a request message (s806), wherein the request message includes the unique identifier and the data associated with the digital asset. A method that includes running on a computer.

2. The aforementioned unique identifier is a pre-encoded uniform resource locator (URL). The method to be executed on a computer as described in claim 1.

3. The physical object includes a Near Field Communication (NFC) chip, The aforementioned unique identifier is obtained by scanning the NFC chip of the physical object. A method to be performed on a computer according to claim 1 or claim 2.

4. Selecting the record includes selecting the record from a list displayed on a graphical display. A method to be performed on a computer according to any one of claims 1, 2, or 3.

5. The aforementioned digital assets are not associated with any physical objects. A method performed on a computer according to any one of claims 1, 2, 3, or 4.

6. The request message includes instructions to associate the digital asset with the physical object. A method performed on a computer according to any one of claims 1, 2, 3, 4, or 5.

7. The record describes the physical object. A method to be performed on a computer according to any one of claims 1, 2, 3, 4, 5, or 6.

8. The aforementioned digital assets include crypto tokens. A method to be performed on a computer according to any one of claims 1, 2, 3, 4, 5, 6, and 7.

9. The aforementioned cryptographic token is a non-fungible token (NFT). The method to be executed on a computer according to claim 8.

10. The aforementioned physical object is one or more of the following: footwear, clothing, artwork, fixtures, event tickets, and functional assets. A method to be performed on a computer according to any one of claims 1, 2, 3, 4, 5, 6, 7, 8, and 9.

11. A computer program product (1841) comprising a non-temporary computer-readable medium (1842) that stores a computer program (1843) which, when executed by a processing circuit (1802), causes the processing circuit to perform the method described in claim 1.

12. A computing device (1800), Processing circuit (1802), The system includes a memory (1342) containing instructions executable by the processing circuit for associating digital assets with physical objects (102), The computing device is Selecting a record associated with the aforementioned digital asset (S802), Receiving a unique identifier associated with the physical object (S804), wherein the unique identifier is obtained by scanning the physical object, Sending a request message (S806), wherein the request message includes the unique identifier and the data associated with the digital asset. To make it work, Computing device.

13. The aforementioned unique identifier is a pre-encoded uniform resource locator (URL). The computing device according to claim 12.

14. The physical object includes a Near Field Communication (NFC) chip, The aforementioned unique identifier is obtained by scanning the NFC chip of the physical object. The computing device according to claim 12 or claim 13.

15. Selecting the record includes selecting the record from a list displayed on a graphical display. A computing device according to any one of claims 12, 13, or 14.

16. The aforementioned digital assets are not associated with any physical objects. A computing device according to any one of claims 12, 13, 14, or 15.

17. The request message includes instructions to associate the digital asset with the physical object. A computing device according to any one of claims 12, 13, 14, 15, or 16.

18. The record describes the physical object. A computing device according to any one of claims 12, 13, 14, 15, 16, or 17.

19. The aforementioned digital assets include crypto tokens. A computing device according to any one of claims 12, 13, 14, 15, 16, 17, or 18.

20. The aforementioned cryptographic token is a non-fungible token (NFT). The computing device according to claim 19.

21. The aforementioned physical object is one or more of the following: footwear, clothing, artwork, fixtures, event tickets, and functional assets. A computing device according to any one of claims 12, 13, 14, 15, 16, 17, 18, 19, or 20.

22. A device (1800) for associating digital assets with physical objects (102), Memory (1302) and, The system comprises a processing circuit (1342) connected to the memory, The aforementioned device is Selecting a record associated with the aforementioned digital asset (s802), Receiving a unique identifier associated with the physical object (s804), wherein the unique identifier is obtained by scanning the physical object, Sending a request message (s806), wherein the request message includes the unique identifier and data associated with the digital asset. A device that performs this task.

23. A method (1400) to be performed on a computer that is permitted to access, Receiving an identifier from a computing device that identifies a physical object (102) (s1402), wherein the identifier is obtained by the computing device scanning the physical object, and the physical object is linked to a digital asset. Receiving an encrypted message (s1404), wherein the encrypted message includes an encrypted token, Determining whether the encrypted token satisfies the conditions (s1406), When it is determined that the above conditions are met, the unencrypted public key of the wallet and the identifier are transmitted to the application used to grant access (s1408), wherein the access is granted depending on whether the wallet owns the digital assets linked to the physical object. A method that includes running on a computer.

24. The physical object includes a Near Field Communication (NFC) chip, The identifier is obtained by the computing device scanning the NFC chip of the physical object. The method to be performed on a computer according to claim 23.

25. Determining whether the encrypted token satisfies the conditions is: Determining whether the encrypted token is decryptable, or This includes determining whether the time identifier associated with the encrypted token has not expired. The method performed on a computer according to claim 23 or 24.

26. Receiving a key message, wherein the key message includes the public key, The process of encrypting the public key into the encrypted token, wherein the encrypted token includes a time identifier and a unique identifier key. The initialization vector of the encrypted token is stored in a memory cache, Includes A method performed on a computer according to any one of claims 23, 24, or 25.

27. Sending the encrypted token to the browser, wherein the encrypted token is displayed to the user as a QR code. Includes The method to be performed on a computer according to claim 26.

28. The encrypted message is received when the user scans the QR code. The method to be performed on a computer according to claim 27.

29. The aforementioned access is permitted according to ownership of the physical object. A method performed on a computer according to any one of claims 23, 24, 25, 26, 27, or 28.

30. A computer program product comprising a non-temporary computer-readable medium storing a computer program that, when executed by a processing circuit, includes instructions causing the processing circuit to perform the method according to claim 23.

31. A computing device (1800), Processing circuit (1802), The system includes a memory (1842) that stores instructions executable by the processing circuit in order to grant access, The computing device is Receiving an identifier from the computing device that identifies a physical object (102) (s1402), wherein the identifier is obtained by the computing device scanning the physical object, and the physical object is linked to a digital asset. Receiving an encrypted message (s1404), wherein the encrypted message includes the encrypted token, Determining whether the encrypted token satisfies the conditions (s1406), When it is determined that the above conditions are met, the unencrypted public key of the wallet and the identifier are transmitted to the application used to grant access (s1408), wherein the access is granted depending on whether the wallet owns the digital assets linked to the physical object. Execute Computing device.

32. The physical object includes a Near Field Communication (NFC) chip, The identifier is obtained by the computing device scanning the NFC chip of the physical object. The computing device according to claim 31.

33. Determining whether the encrypted token satisfies the above conditions is: Determining whether the encrypted token is decryptable, or This includes determining whether the time identifier associated with the encrypted token has not expired. The computing device according to claim 31 or 32.

34. Receiving a key message, wherein the key message includes the public key, The process of encrypting the public key into the encrypted token, wherein the encrypted token includes a time identifier and a unique identifier key. The initialization vector of the encrypted token is stored in a memory cache, Execute A computing device according to any one of claims 31, 32, or 33.

35. Sending an encrypted token to a browser, wherein the encrypted token is displayed to the user as a QR code. Execute The computing device according to claim 34.

36. The encrypted message is received when the user scans the QR code. The computing device according to claim 35.

37. The aforementioned access is permitted according to ownership of the physical object. A computing device according to any one of claims 31, 32, 33, 34, 35, or 36.

38. A device (1800) that permits access, Memory (1802), The system comprises a processing circuit (1842) connected to the memory, The aforementioned device is Receiving an identifier from a computing device that identifies a physical object (102) (s1402), wherein the identifier is obtained by the computing device scanning the physical object, and the physical object is linked to a digital asset. Receiving an encrypted message (s1404), wherein the encrypted message includes the encrypted token, Determining whether the encrypted token satisfies the conditions (s1406), When it is determined that the above conditions are met, the unencrypted public key of the wallet and the identifier are transmitted to the application used to grant access (s1408), wherein the access is granted depending on whether the wallet owns the digital assets linked to the physical object. Execute Device.

39. A method (1700) performed on a computer to claim a digital asset linked to a physical object (102), Receiving an identifier from a computing device that identifies the physical object (s1702), wherein the identifier is obtained by the computing device scanning the physical object, and receiving Identifying the digital asset associated with the physical object (s1704), (s1706) Determining whether the wallet identifier associated with the wallet owning the digital asset matches the initial wallet identifier, wherein the initial wallet identifier is associated with the minting of the digital asset. including How it is executed on a computer.

40. The aforementioned physical object includes a Near Field Communication (NFC) chip. The identifier is obtained by the computing device scanning the NFC chip of the physical object. The method to be performed on a computer according to claim 39.

41. If it is determined that the wallet identifier associated with the digital asset does not match the initial wallet identifier, the user of the computing device is directed to a verification webpage. Receiving the user wallet identifier, Determining whether the user wallet identifier matches the wallet identifier associated with the wallet that owns the digital asset, Includes The method performed on a computer according to claim 39 or 40.

42. When it is determined that the wallet identifier associated with the digital asset matches the initial wallet identifier, the encrypted token is obtained. The encrypted token is sent to the computing device, Includes A method performed on a computer according to any one of claims 39, 40, or 41.

43. The method executed on a computer according to claim 42, wherein the encrypted token includes one or more of the following: a digital asset identifier associated with the digital asset, a group identifier associated with the digital asset, and a time identifier.

44. The encrypted token includes a successful uniform resource locator (URL) redirect and / or the serial number of the NFC chip associated with the physical object. The method to be performed on a computer as described in claim 43.

45. This further includes receiving billing messages, The aforementioned invoice message includes the wallet and the key associated with the encrypted token. The method to be performed on a computer as described in claim 43.

46. The time identifier is used to determine if it has not expired, Transferring the aforementioned digital assets to the user's wallet, Includes The method to be performed on a computer according to claim 45.

47. Further includes receiving a payment identifier associated with the aforementioned physical object. The method to be performed on a computer as described in claim 46.

48. The digital asset is transferred after the payment identifier is received. The method to be performed on a computer according to claim 47.

49. The aforementioned digital assets include crypto tokens. A method for performing on a computer according to any one of claims 39, 40, 41, 42, 43, 44, 45, 46, 47, or 48.

50. The aforementioned cryptographic token is a non-fungible token (NFT). The method to be performed on a computer according to claim 49.

51. A computer program product (1841) including a non-temporary computer-readable medium (1842), The aforementioned non-temporary computer-readable medium is When executed by the processing circuit (1802), it stores a computer program (1843) which includes instructions to cause the processing circuit to perform the method according to claim 39. Computer program products.

52. A computing device (1800), Processing circuit (1802), A memory (1842) containing instructions executable by the processing circuit for claiming a digital asset linked to a physical object (102), The computing device is Receiving an identifier that identifies the physical object from the computing device (s1702), wherein the identifier is obtained by the computing device scanning the physical object, and receiving Identifying the digital asset associated with the physical object (s1704), (s1706) Determining whether the wallet identifier associated with the wallet owning the digital asset matches the initial wallet identifier, wherein the initial wallet identifier is associated with the minting of the digital asset. Execute Computing device.

53. The physical object includes a Near Field Communication (NFC) chip, The identifier is obtained by the computing device scanning the NFC chip of the physical object. The computing device according to claim 52.

54. If it is determined that the wallet identifier associated with the digital asset does not match the initial wallet identifier, the user of the computing device is directed to a verification webpage. Receiving the user wallet identifier, The process involves determining whether the user wallet identifier matches the wallet identifier associated with the wallet that owns the digital asset, Execute The computing device according to claim 52 or 53.

55. When it is determined that the wallet identifier associated with the digital asset matches the initial wallet identifier, the encrypted token is obtained. The encrypted token is transmitted to the computing device, Execute A computing device according to any one of claims 52, 53, or 54.

56. The encrypted token includes one or more of the following: a digital asset identifier associated with the digital asset, a group identifier associated with the digital asset, and a time identifier. The computing device according to claim 55.

57. The encrypted token includes a successful uniform resource locator (URL) redirect and / or an NFC chip serial number associated with the physical object. The computing device according to claim 56.

58. Perform the action of receiving the billing message. The aforementioned invoice message includes the wallet and the key associated with the encrypted token. The computing device according to claim 56.

59. A computing device according to claim 58, which determines that the time identifier has not expired and operates to transfer the digital asset to the user's wallet.

60. Perform the action of receiving a payment identifier associated with the aforementioned physical object. The computing device according to claim 59.

61. The digital asset is transferred after the payment identifier is received. The computing device according to claim 60.

62. The aforementioned digital assets include crypto tokens. A computing device according to any one of claims 52, 53, 54, 55, 56, 57, 58, 59, 60, or 61.

63. The aforementioned cryptographic token is a non-fungible token (NFT). The computing device according to claim 62.

64. A device (1800) for claiming digital assets linked to a physical object (102), wherein the device is Memory (1802), The processing circuit (1842) connected to the memory is included, The aforementioned processing circuit is Receiving an identifier from a computing device that identifies the physical object (s1702), wherein the identifier is obtained by the computing device scanning the physical object, and receiving Identifying the digital asset associated with the physical object (s1704), (s1706) Determining whether the wallet identifier associated with the wallet owning the digital asset matches the initial wallet identifier, wherein the initial wallet identifier is associated with the minting of the digital asset. Execute Device.

Images