US-12626244-B2 - Location-based non-fungible token distribution and verification

US12626244B2US 12626244 B2US12626244 B2US 12626244B2US-12626244-B2

Abstract

Aspects of the present disclosure are directed to providing location-based non-fungible tokens (NFTs) using request verification. Digital collectibles can be any suitable unit of data affiliated with person(s), organization(s), or any other entities. A digital collectible can comprise a display component that supports display of the digital collectible data. Some digital collectibles and/or NFTs can be generated as a set, such as digital collectibles linked to the same event (e.g., sporting events, concert, or other social event). Implementations support a set of location-based NFTs that correspond to digital collectibles linked to a predefined location, and in some examples a particular period of time (e.g., particular event) at the predefined location. For example, a claim manager can enforce a claim policy for the set of location-based NFTs, where user requests are validated against the claim policy before they are granted access to the set of location-based NFTs.

Inventors

Nicholas Lemieux

Assignees

DAPPER LABS, INC.

Dates

Publication Date: 20260512
Application Date: 20230413

Claims (16)

1 . A method for providing location-based non-fungible tokens (NFTs) using request verification, the method comprising: minting at least a first portion of a set of location-based NFTs, wherein the set of location-based NFTs are associated with an active time period, and wherein the at least the first portion of the set of location-based NFTs are minted prior to the active time period; receiving, from a client application, a request for one or more NFTs from the set of location-based NFTs; verifying the request originated from a predefined physical location that corresponds to the set of location-based NFTs by: comparing one or more network address identifiers from the request to a set of known network address identifiers affiliated with the predefined physical location, wherein, the set of known network address identifiers are compiled, at least in part, using historical requests for another set of location-based NFTs similar to the set of location-based NFTs, and one or more historical network address identifiers are added to the set of known network address identifiers when a threshold number of the historical requests include the one or more historical network address identifiers; and verifying the request when the one or more network address identifiers are included in the set of known network address identifiers; minting at least a second portion of the set of location-based NFTs on-demand during the active time period in response to received client application requests or verification that client application requests originated from the predefined physical location; permitting, in response to the verifying that the request originated from the predefined physical location and the request is performed within the active time period, the client application access to claim a predefined quantity of the set of location-based NFTs; and executing, in response to a claim action of a user via the client application, one or more smart contracts that select the predefined quantity of NFTs from among the set of locations based NFTs and transfer the selected NFTs to a token wallet affiliated with the user.
2 . The method of claim 1 , wherein: one or more of the set of location-based NFTs are unclaimed after the active time period, and the one or more unclaimed location-based NFTs are automatically destroyed.
3 . The method of claim 1 , wherein the one or more network address identifiers comprise an internet protocol (IP) address and/or a media access control (MAC) address.
4 . The method of claim 1 , wherein the set of known network address identifiers is compiled, at least in part, using network identifiers included in an initial set of client application requests for NFTs from the set of location-based NFTs.
5 . The method of claim 4 , wherein: the initial set of client application requests for NFTs from the set of location-based NFTs are received proximate to a starting time of the active time period for the set of location-based NFTs.
6 . The method of claim 1 , further comprising: compiling at least a portion of the set of known network address identifiers by processing, using one or more machine learning models, an initial set of client application requests for NFTs from the set of location-based NFTs, wherein: the initial set of client application requests for NFTs from the set of location-based NFTs are received proximate to a starting time of the active time period for the set of location-based NFTs.
7 . The method of claim 1 , wherein the set of known network address identifiers are affiliated with the predefined physical location.
8 . A computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform a process for providing location-based non-fungible tokens (NFTs) using request verification, the process comprising: minting at least a first portion of a set of location-based NFTs, wherein the set of location-based NFTs are associated with an active time period, and wherein the at least the first portion of the set of location-based NFTs are minted prior to the active time period; receiving, from a client application, a request for one or more NFTs from the set of location-based NFTs; verifying the request originated from a predefined physical location that corresponds to the set of location-based NFTs by: comparing one or more network address identifiers from the request to a set of known network address identifiers affiliated with the predefined physical location, wherein, the set of known network address identifiers are compiled, at least in part, using historical requests for another set of location-based NFTs similar to the set of location-based NFTs, and one or more historical network address identifiers are added to the set of known network address identifiers when a threshold number of the historical requests include the one or more historical network address identifiers; and verifying the request when the one or more network address identifiers are included in the set of known network address identifiers; minting at least a second portion of the set of location-based NFTs on-demand during the active time period in response to received client application requests or verification that client application requests originated from the predefined physical location; permitting, in response to the verifying that the request originated from the predefined physical location and the request is performed within the active time period, the client application access to claim a predefined quantity of the set of location-based NFTs; and executing, in response to a claim action of a user via the client application, one or more smart contracts that select the predefined quantity of NFTs from among the set of locations based NFTs and transfer the selected NFTs to a token wallet affiliated with the user.
9 . The computer-readable storage medium of claim 8 , wherein: one or more of the set of location-based NFTs are unclaimed after the active time period, and the one or more unclaimed location-based NFTs are automatically destroyed.
10 . The computer-readable storage medium of claim 8 , wherein the one or more network address identifiers comprise an internet protocol (IP) address and/or a media access control (MAC) address.
11 . The computer-readable storage medium of claim 8 , wherein the set of known network address identifiers is compiled, at least in part, using network identifiers included in an initial set of client application requests for NFTs from the set of location-based NFTs.
12 . The computer-readable storage medium of claim 11 , wherein: the initial set of client application requests for NFTs from the set of location-based NFTs are received proximate to a starting time of the active time period for the set of location-based NFTs.
13 . The computer-readable storage medium of claim 8 , wherein the process further comprises: compiled, at least in part, the set of known network address identifiers by processing, using one or more machine learning models, an initial set of client application requests for NFTs from the set of location-based NFTs, wherein: the initial set of client application requests for NFTs from the set of location-based NFTs are received proximate to a starting time of the active time period for the set of location-based NFTs.
14 . A computing system for providing location-based non-fungible tokens (NFTs) using request verification, the computing system comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the computing system to perform a process comprising: minting at least a first portion of a set of location-based NFTs, wherein the set of location-based NFTs are associated with an active time period, and wherein the at least the first portion of the set of location-based NFTs are minted prior to the active time period; receiving, from a client application, a request for one or more NFTs from the set of location-based NFTs; verifying the request originated from a predefined physical location that corresponds to the set of location-based NFTs by: comparing one or more network address identifiers from the request to a set of known network address identifiers affiliated with the predefined physical location, wherein, the set of known network address identifiers are compiled, at least in part, using historical requests for another set of location-based NFTs similar to the set of location-based NFTs, and one or more historical network address identifiers are added to the set of known network address identifiers when a threshold number of the historical requests include the one or more historical network address identifiers; and verifying the request when the one or more network address identifiers are included in the set of known network address identifiers; minting at least a second portion of the set of location-based NFTs on-demand during the active time period in response to received client application requests or verification that client application requests originated from the predefined physical location; permitting, in response to the verifying that the request originated from the predefined physical location and the request is performed within the active time period, the client application access to claim a predefined quantity of the set of location-based NFTs; and executing, in response to a claim action of a user via the client application, one or more smart contracts that select the predefined quantity of NFTs from among the set of locations based NFTs and transfer the selected NFTs to a token wallet affiliated with the user.
15 . The method of claim 1 , wherein the one or more smart contracts are automatically executed, at least in part, in response to the claim, from the client application, for the predefined quantity of the set of location-based NFTs.
16 . The method of claim 1 , wherein the one or more network address identifiers from the request comprise a plurality of network identifiers for multiple Wi-Fi networks that cover a user system that originates the request with respect to a time at which the request was originated.

Description

TECHNICAL FIELD The present disclosure is directed to providing location-based non-fungible tokens (NFTs) using request verification. BACKGROUND A blockchain is a list of records, each called a block, which can be linked through cryptography. Each block includes a timestamp, a hash of the previous block, and transaction data. The timestamp proves that the transaction data was included when the block was added in order to get its hash. Because each block specifies the block previous to it, the set of blocks make a chain, with each new block reinforcing the set of blocks before it in the chain. Therefore, blockchains are very difficult to modify because data, once added to the blockchain, cannot be altered without altering all subsequent blocks. Non-Fungible Tokens (NFTs), are blockchain-backed identifiers specifying a unique (digital or real-world) item. Through a distributed ledger, the ownership of these tokens can be tracked and verified. Such tokens can link to a representation of the unique item, e.g., via a traditional URL or a distributed file system such as IPFS. While a variety of blockchain systems support NFTs, common platforms that supports NFT exchange allow for the creation of unique and indivisible NFT tokens. Traditionally, NFTs represent a way of being able to define ownership for practically anything that is digital. In other words, any material that can be digitized or which is already in a digital format can be the subject of an NFT. Some examples of NFT content can include digital photographs, video frames, social media interactions, and virtually all items that can be converted for receipt and processing by a computer (e.g., a scanned autograph). Asset ownership via digital items, such as NFTs, has grown in popularity. NFTs can include identifying information that identifies the asset tied to the NFT, such as unique identifying information, a web link, or other suitable identifying information. NFTs can be managed on a blockchain, thus providing transparency and reliability to the asset ownership. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram illustrating an overview of devices on which some implementations can operate. FIG. 2 is a block diagram illustrating an overview of an environment in which some implementations can operate. FIG. 3 is a block diagram illustrating components which, in some implementations, can be used in a system employing the disclosed technology. FIG. 4A is conceptual diagram illustrating system components for providing location-based non-fungible tokens (NFTs) using request verification. FIG. 4B is conceptual diagram illustrating user systems requesting location-based NFTs from different locations. FIG. 5 is a conceptual diagram of a digital collectible affiliated with an NFT. FIG. 6 is a conceptual diagram of a user workflow for requesting a location-based NFT. FIG. 7 is a flow diagram illustrating a process used in some implementations for providing location-based non-fungible tokens (NFTs) using request verification. FIG. 8 is a flow diagram illustrating a process used in some implementations for verifying a user is located in a predefined location affiliated with a set of location-based NFTs. The techniques introduced here may be better understood by referring to the following Detailed Description in conjunction with the accompanying drawings, in which like reference numerals indicate identical or functionally similar elements. DETAILED DESCRIPTION Aspects of the present disclosure are directed to providing location-based non-fungible tokens (NFTs) using request verification. NFTs are blockchain-backed identifiers specifying an item, such as a digital item. In some implementations, NFTs are linked to digital collectibles. Digital collectibles can be any suitable unit of data (e.g., data structure) affiliated with person(s), organization(s), or any other suitable entities. A digital collectible can comprise a display component that supports display of the digital collectible data. For example, digital collectible data can include an affiliated person (e.g., a sports player), an affiliated team (e.g., a sports team), a digital media file (e.g., video clip, image, etc.), or any other suitable digital collectible data. Some digital collectibles and/or NFTs can be generated as a set, such as digital collectibles linked to the same event (e.g., sporting events, concert, or other social event). Implementations support a set of location-based NFTs that correspond to digital collectibles linked to a predefined location, and in some examples a particular period of time (e.g., particular event) at the predefined location. For example, a claim manager can enforce a claim policy for the set of location-based NFTs, where user requests are validated against the claim policy before they are granted access to the set of location-based NFTs. The claim policy can define that granted user requests should originate from the predefined location affiliated with the se