WO2025049217A2

WO2025049217A2 - Device and user interface for digital assets

Info

Publication number: WO2025049217A2
Application number: PCT/US2024/043330
Authority: WO
Inventors: Michael Jones; Jordan TATE
Original assignee: University of Cincinnati
Current assignee: University of Cincinnati
Priority date: 2023-08-25
Filing date: 2024-08-22
Publication date: 2025-03-06
Anticipated expiration: 2026-02-25
Also published as: WO2025049217A3

Abstract

Systems, methods, and computer program products for minting non-fungible tokens (52). The system includes a computing device (18, 24) that receives a dynamic uniform resource identifier (URI) (64) including a unique identifier and a hostname that identifies a host system (12). In response to receiving the dynamic URI (64), the computing device (18, 24) transmits data to the host system (12) identified by the hostname. The data includes the unique identifier and at least one of a time the computing device (18, 24) received the URI (64) and a physical location of the computing device (18, 24) when the URI (64) was received. In response to receiving the data from the computing device (18, 24), the host system (12) mints a non-fungible token (52) on a blockchain (30) that documents at least one of the time the computing device (18, 24) received the URI (64) and the physical location of the computing device (18, 24) when the URI (64) was received.

Description

DEVICE AND USER INTERFACE FOR DIGITAL ASSETS CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims the filing benefit of co-pending U.S. Provisional Application Serial Nos. 63/534,593, filed August 25, 2023, and 63/638,472 filed on April 25, 2024, the disclosures of which are each incorporated by reference in their entireties.

BACKGROUND

[0002] This section is intended to introduce the reader to various aspects of the art that may be related to various aspects of the present invention, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of various aspects of the present invention. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

[0003] A non-fungible token (NFT) is a digital asset that represents ownership of a unique physical or digital object. Non-fungible tokens have gained prominence in recent years as a means of authenticating, preserving, and exchanging assets in a secure and decentralized manner. Built on blockchain technology, non-fungible tokens allow for the transparent and verifiable tracking of digital asset ownership, providing a robust solution to challenges posed by the digital nature of these assets, such as replication and copyright infringement. Unlike cryptocurrencies such as Bitcoin or Ethereum, which are relatively fungible and can be exchanged on a one-to-one basis, non-fungible tokens are non-fungible, meaning each token is unique and cannot be exchanged on an equal basis with another non- fungible token. This characteristic makes non-fungible tokens particularly well-suited for representing digital works of art, certificates of competition, or proof of membership in a collective.

[0004] Conventional systems and methods for generating and managing non-fungible tokens provide a poor user experience. Typically, users of non-fungible tokens must interact with private keys, wallets, blind signing, and other potentially complex concepts. This results in a confusing and frustrating experience for both consumers and businesses. Therefore, a need exists for methods, systems, and computer program products that are user-friendly and facilitate management of non-fungible tokens and similar technologies.

SUMMARY

[0005] In one aspect of the disclosure, an improved method of generating non-fungible tokens is disclosed. The method includes receiving a first dynamic uniform resource identifier at a first computing device, transmitting first data from the first computing device to a host system, and minting a non-fungible token on a blockchain. The first dynamic uniform resource identifier includes a unique identifier and a hostname that identifies the host system. The first data transmitted to the host system includes the unique identifier, and at least one of a time the first computing device received the first dynamic uniform resource identifier and a physical location of the first computing device when the first dynamic uniform resource identifier was received. The non-fungible token documents at least one of the time the first computing device received the first dynamic uniform resource identifier and the physical location of the first computing device when the first dynamic uniform resource identifier was received.

[0006] In one embodiment of the disclosed method, the first computing device may be a user device, and the first dynamic uniform resource identifier may be received from a nearfield communication card associated with one of an event or an individual.

[0007] In another embodiment of the disclosed method, the unique identifier may include a card number, and the card number may be used to identify the event or the individual with which the near- field communication card is associated.

100081 In another embodiment of the disclosed method, the first computing device may be a card reader associated with an event, and the first dynamic uniform resource identifier may be received from a near- field communication card associated with an individual.

[0009] In another embodiment of the disclosed method, the method may further include the first computing device receiving a second dynamic uniform resource identifier that includes a second unique identifier and the hostname identifying the host system, and transmitting second data from the first computing device to the host system identified by the hostname. The second data may include the second unique identifier, and at least one of the time the first computing device received the second dynamic uniform resource identifier and the physical location of the first computing device when the second dynamic uniform resource identifier was received. In this embodiment, the non-fungible token may further document at least one of the time the first computing device received the second dynamic uniform resource identifier and the physical location of the first computing device when the second dynamic uniform resource identifier was received.

[0010] In another embodiment of the disclosed method, the first computing device may be a user device, the first dynamic uniform resource identifier may be received from a nearfield communication card associated with a first individual or an event, and the second dynamic uniform resource identifier may be received from a near-field communication card associated with a second individual. [0011] In another embodiment of the disclosed method, the method may further include generating a signature based on the first data, and minting the non- fungible token may include storing the signature on the blockchain.

[0012] In another embodiment of the disclosed method, the method may further include generating digital content, transmitting the digital content to a content storage system, and receiving a static uniform resource locator from the content storage system identifying a network location where the digital content is stored. In this embodiment, minting the non- fungible token may include storing the static uniform resource locator on the blockchain. [0013] In another embodiment of the disclosed method, the method may further include generating a hash of the digital content. In this embodiment, minting the non-fungible token may include storing the hash of the digital content on the blockchain.

[0014] In another embodiment of the disclosed method, the method may further include generating a signature based on the hash of the digital content. In this embodiment, minting the non-fungible token may include storing the signature on the blockchain.

[0015] In another aspect of the disclosure, an improved system for generating non- fungible tokens is disclosed. The system includes one or more processors, and memory in communication with the one or more processors. The memory includes program code that, when executed by the one or more processors, causes the system to receive the first dynamic uniform resource identifier at the first computing device, transmit the first data from the first computing device to the host system identified by the hostname, and mint the non-fungible token on the blockchain. The first dynamic uniform resource identifier includes the unique identifier and the hostname that identifies the host system, the first data includes the unique identifier and at least one of the time the first computing device received the first dynamic uniform resource identifier and the physical location of the first computing device when the first dynamic uniform resource identifier was received, and the non-fungible token documents at least one of the time the first computing device received the first dynamic uniform resource identifier and the physical location of the first computing device when the first dynamic uniform resource identifier was received.

[0016] In one embodiment of the disclosed system, the first computing device may be the user device, and the first dynamic uniform resource identifier may be received from the nearfield communication card associated with the event or the individual.

[0017] In another embodiment of the disclosed system, the unique identifier may include the card number, and the card number may be used to identify the event or the individual with which the near-field communication card is associated. [0018] In another embodiment of the disclosed system, the first computing device may be the card reader associated with the event, and the first dynamic uniform resource identifier may be received from the near- field communication card associated with the individual. [0019] In another embodiment of the disclosed system, the program code may further cause the first computing device to receive a second dynamic uniform resource identifier that includes the second unique identifier and the hostname identifying the host system, and transmit the second data from the first computing device to the host system identified by the hostname, the second data including the second unique identifier, and at least one of the time the first computing device received the second dynamic uniform resource identifier and the physical location of the first computing device when the second dynamic uniform resource identifier was received. In this embodiment, the non-fungible token may further document at least one of the time the first computing device received the second dynamic uniform resource identifier and the physical location of the first computing device when the second dynamic uniform resource identifier was received.

[0020] In another embodiment of the disclosed system, the first computing device may be the user device, the first dynamic uniform resource identifier may be received from the nearfield communication card associated with the first individual or the event, and the second dynamic uniform resource identifier may be received from the near- field communication card associated with the second individual.

[0021] In another embodiment of the disclosed system, the program code may further cause the system to generate the signature based on the first data. In this embodiment, minting the non-fungible token may include storing the signature on the blockchain.

[0022] In another embodiment of the disclosed system, the program code may further cause the system to generate digital content, transmit the digital content to the content storage system, and receive the static uniform resource locator from the content storage system identifying the network location where the digital content is stored. In this embodiment, minting the non-fungible token may include storing the static uniform resource locator on the blockchain.

[0023] In another embodiment of the disclosed system, the program code may further cause the system to generate the hash of the digital content. In this embodiment, minting the non-fungible token may include storing the hash of the digital content on the blockchain.

[0024] In another embodiment of the disclosed system, the program code may further cause the system to generate the signature based on the hash of the digital content. In this embodiment, minting the non-fungible token may include storing the signature on the blockchain.

[0025] In another aspect of the disclosure, an improved computer program product for generating non-fungible tokens is disclosed. The computer program produce includes a non- transitory computer-readable storage medium, and program code stored on the non-transitory computer-readable storage medium. The program code is configure so that, when the program code is executed by one or more processors, the program code causes the one or more processors to receive the first dynamic uniform resource identifier at the first computing device, transmit the first data from the first computing device to the host system identified by the hostname, and mint the non-fungible token on the blockchain. The first dynamic uniform resource identifier includes the unique identifier and the hostname that identifies the host system, the first data includes the unique identifier and at least one of the time the first computing device received the first dynamic uniform resource identifier and the physical location of the first computing device when the first dynamic uniform resource identifier was received, and the non-fungible token documents at least one of the time the first computing device received the first dynamic uniform resource identifier and the physical location of the first computing device when the first dynamic uniform resource identifier was received.

BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The objects and advantages of the present invention will be further appreciated in light of the following detailed descriptions and drawings in which:

[0027] FIG. 1 is a diagrammatic view of an exemplary operating environment including a badge system, a blockchain system, a content storage system, a user device, an NFC-card, one or more digital wallets, and a card reader.

[0028] FIG. 2 is a diagrammatic view of an exemplary blockchain that may be maintained by the blockchain system of FIG. 1.

[0029] FIG. 3 is a diagrammatic view of an exemplary non-fungible token minting process that may be implemented in the operating environment of FIG. 1.

[0030] FIG. 4 is a diagrammatic view of a user engaging the NFC-card and user device of FIG. 1.

[0031] FIGS. 5 and 6 are diagrammatic views of an exemplary user interface of the user device of FIG. 1.

[0032] FIG. 7 is a diagrammatic view of an exemplary NFC-card of FIG. 1.

[0033] FIGS. 8-13 are diagrammatic views of exemplary processes for minting a non- fungible token in the operating environment of FIG. 1. [0034] FIG. 14 is a diagrammatic view of an exemplary computer that may be used to implement one or more of the systems and processes depicted by FIGS. 1-13.

DETAILED DESCRIPTION OF THE INVENTION

[0035] FIG. 1 depicts an exemplary operating environment 10 in accordance with an embodiment of the present invention. The operating environment 10 includes a badge system 12, a blockchain system 14, a content storage system 16, a user device 18, a near-field communication (NFC) card 20, one or more digital wallets 22, a card reader 24, and a data network 26 through which one or more of the badge system 12, blockchain system 14, content storage system 16, user device 18, and card reader 24 communicate. The data network 26 may include one or more private and/or public networks (e.g., the Internet) that enable the exchange of data.

[0036] The badge system 12 may be associated with a validating organization, and may include one or more computers (e.g., web servers, proxy servers, application servers, database servers, domain name system (DNS) servers, etc.) that facilitate the generation of non- fungible tokens documenting activities engaged in by one or more users of the system.

100371 The blockchain system 14 may include a distributed peer-to-peer (P2P) network of nodes (e.g., computer systems) each communicating with one or more other nodes over a data network to maintain one or more copies of a blockchain. Each node of blockchain system 14 may participate by replicating, validating, synchronizing, and saving a copy of the blockchain. Although different blockchain systems may have varying architectural and security characteristics, blockchain systems are typically configured to provide a shared and distributed digital ledger. In operation, the blockchain system 14 may receive a transaction request (e.g., a request to mint a non-fungible token) from a subscribing computer system. In response to receiving the transaction request, the receiving node may broadcast the request to one or more additional nodes in the blockchain system 14. The nodes may then attempt to cryptographically validate the transaction using a consensus mechanism, e.g., proof of work, proof of stake, proof of contribution, proof of authority, etc. If validation is successful, the transaction may be encoded, time-stamped, signed, and added to the currently active block as a new transaction that is a permanent part of the blockchain. Blockchains may thereby provide a distributed and tamper-resistant ledger of validated transactions.

[0038] The content storage system 16 may provide media management functions that enable the badge system 12, blockchain system 14, user device 18, or other computing system to upload digital content. The content storage system 16 may include or be associated with one or more media hosts (not shown) that provide a website or other service which enables users to access digital content online. To this end, the content storage system 16 may store and retrieve data associated with uploaded digital content, such as usage rights, ownership, licensing, or other suitable types of data. The content storage system 16 may store this data in various databases or suitable network locations, e.g., database that maintains a public ledger, such as the blockchain system 14. The content storage system 16 may also store or otherwise manage data associated with the aforementioned digital content, such as data describing the digital content, data representing the digital content (e.g., hash values), metadata associated with the digital content, etc.

[0039] The user device 18 may include any suitable computing device, such as a smart phone, that communicates with one or more of the badge system 12, blockchain system 14, content storage system 16, NFC-card 20, and digital wallet 22, either directly or via the data network 26. This communication may use a suitable wireless protocol, such as Bluetooth®, a protocol based on IEEE 802.11 (i.e., “Wi-Fi”), and what are commonly known as near-field communication protocols. Near-field communication refers to communication between two electronic devices over a relatively short distance (e.g., up to 40 mm), and typically involves inductive coupling at a suitable frequency (e.g., 13.56 MHz) in the industrial, scientific, and medical (ISM) band.

[0040] The NFC-card 20 may include circuits configured to store and process data, and may communicate with the user device 18 or card reader 24 using near-field communication. The NFC-card 20 may have dimensions similar to that of a credit card (e.g., about 86 x 54 x 0.75 mm) in order to facilitate carrying of the NFC-card 20 by the user. In an alternative embodiment, the NFC-card 20 may be part of a larger device or system that enables users to check in by engaging the NFC-card 20 with their user device 18 upon arrival at an event. [0041] The NFC-card 20 may be configured to generate a unique distinguishable uniform resource locator (URL), referred to herein as a “dynamic URL”, each time it engages a user device 18, e.g., in response to being scanned by, physically touched by (e.g., tapped by), or otherwise engaged with the user device 18. A URL is a specific type of uniform resource identifier (URI) that may be used to identify resources on the Internet. URLs are sometimes referred to as web addresses, and typically identify a communication protocol (e.g., hypertext transfer protocol, file transfer protocol, email, Java database connectivity, etc.), a host system, and a file name. Each dynamic URL generated by the NFC-card may include one or more static portions and one or more dynamic portions. The static portions may include a hostname, such as a domain name or server address linked to the badge system 12. The dynamic portions may include a card number that uniquely identifies the card (typically assigned by the manufacturer), a scan count that indicates how many times the NFC-card 20 has generated a dynamic URL, and a cryptographic signature generated from the unique card number and scan count. The scan count may be incremented each time the NFC-card 20 issues a dynamic URL so that no two URLs are the same, and the cryptographic signature may be configured to prevent alteration of the URL once it has been generated. Thus, the dynamic portion of the URL may provide each URL with a unique identifier (UID) that enables the host system to distinguish each URL generated from all other URLs generated by the NFC-card 20 in question or by any other NFC-card 20.

[0042] The digital wallet 22 may be used to manage digital assets, such as non- fungible tokens, other digital tokens, crypto currency, and the like. The digital wallet 22 may be hardware-based (e.g., a dedicated function-specific device), software-based (e.g., an application running on user device 18), or a combination thereof. The digital wallet 22 may include a processor, one or more transceivers, an input/output module, and a memory. The memory may store an authentication module and a digital management module. The authentication module may include an authentication key and configuration data, and the digital asset management module may include an asset key and asset management data. Non- fungible tokens managed by the digital wallet 22 may be stored in one or more of the memory of digital wallet 22 or on a blockchain.

[0043] The card reader 24 may be configured to receive data from and transmit data to NFC-cards 20 using near-field communication radio frequencies. The card reader 24 may also be configured to communicate with NFC-cards 20 in other ways, such as through direct electrical contact (e.g., by inserting the card into the reader), or magnetically (e.g., by swiping the card through the reader).

[0044] One example of a commercially available blockchain technology is the ETHEREUM blockchain. ETHEREUM is a decentralized blockchain with smart contract functionality that is managed by a foundation having a headquarters in Zug, Switzerland. The ETHEREUM blockchain is configured to enable the creation of non-fungible tokens. Since non-fungible tokens are unique, they may be used to represent digital content such as, but not limited to digital art, collectibles, sports memorabilia, virtual real estate, and items within games. Although embodiments of the present invention may be described using references to ETHEREUM, it should be understood that other blockchains may also be used to generate non-fungible tokens, and that embodiments of the present invention are not limited to any particular type of blockchain or blockchain system. [0045] A blockchain is a data structure that strings blocks of data together into a chain to provide a distributed and constantly growing ledger of transactions. A blockchain is typically maintained by a blockchain system including a plurality of nodes each storing a copy of the blockchain. Blockchains can be used to provide a distributed database that is shared across a plurality of computer network nodes. Blockchains are often used to maintain a secure and decentralized record of events, such as the minting or transference of a non-fungible token. By way of example, the ERC-721 or ERC-1155 standards may be used to maintain records related to the minting of non-fungible tokens on the ETHEREUM blockchain.

[0046] FIG. 2 depicts an exemplary blockchain 30 as is a data structure including a chain of cryptographically linked blocks 32. Each block 32 may include a plurality of transactions 34 as well as metadata, e.g., a time stamp 36 and one or more hashes 38. The first block 32 (e.g., the N=0 block) may be referred to as a “genesis block”. The genesis block 32 may only include its own hash 38. Each subsequent block 32 may include a hash 38 of itself as well as the hash 38 of the previous block 32. The hash of the previous block 32 may define a link 40 to the previous block 32. Accordingly, each block 32 may be considered as a link of the blockchain 30.

[0047] Hashes may be generated by a cryptographic algorithm known as a hash function. Hash functions are mathematical algorithms that turn any input data (e.g., a block 32 of blockchain 30, an image file, password, etc.) into a fixed size output called a hash. Hash functions are generally configured to be relatively easy to compute and to generate output values that change unpredictably in response to small changes in the input data. Because any change in the underlying data (e.g., a block 32 or transaction 34) would result in a different hash, tampering can be detected by comparing a hash of current data with the previously generated and stored hash of the data. The hashes 38 of blocks 32 may thereby prevent alterations to previous blocks 32 by providing unique digital fingerprints that enable blocks 32 of the blockchain 30 to be identified and linked together in a verifiable manner. The hashes 38 generally require the blockchain 30 to be append only, meaning that new blocks 32 and transactions 34 can be added to the blockchain 30, but previously added blocks 32 and transactions 34 cannot be deleted or modified.

[0048] Each block 32 may have a certain storage capacity. When an active block 32 reaches its capacity, the active block 32 may be linked to a previously filled block by generating a hash 38 of the previously filled block 32 and storing the hash 38 in the active block 32. The active block 32 may then be closed, and a new active block 32 created. Newly received data may then be compiled into the newly active block 32, which may be added to the blockchain 30. When implemented in a decentralized manner, blockchains 30 have an inherently irreversible data timeline. When a block 32 is filled, it becomes a part of this timeline of blocks 32. Each block 32 of blockchain 30 may be populated with a timestamp 32 at the time it is created. A root hash 38 may provide proof that the respective block 32 contains all events recorded in the proper order, and may thereby prove the integrity of recorded transactions without having to store each event. A blockchain 30 may be viewed as a distributed database that includes and maintains an ever-growing list of data records. Because blockchains 30 are distributed and each block 32 in the chain includes a hash 38 from the previous block, blockchains 30 are essentially tamper proof. Blockchains 30 have many applications, one of which is as a public ledger for documenting the creation and trading of non-fungible tokens.

[0049] A non-fungible token is a unique digital asset that may be used to represent ownership of digital content, such as an image, video, audio clip, etc. A non-fungible token typically includes information that identifies both the digital content and the rights associated with the digital content represented by the non-fungible token. Non-fungible tokens are indivisible and unique digital assets, and ownership of each non-fungible token can be authenticated through decentralized blockchain ledgers. Although non-fungible tokens are typically associated with digital assets, they can also be linked to physical assets through a process known as tokenization.

[0050] Non-fungible tokens may include a “smart contract”. A smart contract includes program code that is stored as a transaction 34 in a block 32 of blockchain 30. The program code of a smart contract defines a set of conditions and corresponding actions that are to be taken if the conditions are met. The nodes of the blockchain system 14 may carry out the actions defined by a smart contract, for example, in response to receiving a transaction request indicating the conditions defined by the smart contract have been met. This is commonly referred to as “self-execution” of the smart contract. Smart contracts that only reference data stored on the blockchain 30 are referred to as “on-chain” smart contracts.

Smart contracts that reference data outside the blockchain 30 are referred to as “off-chain” smart contracts. Off-chain smart contracts typically rely on data feeds provided by third- party service providers known as “oracles”. A smart contract may be configured to tokenize a physical or digital asset. Tokenization refers to a process of converting the asset into a token stored on the blockchain 30.

[0051] Minting an NFT typically involves creating a unique cryptographic key pair including a public key and a private key. The public key is stored on the blockchain, and the private key held by the creator. Embodiments of the present invention use non-fungible tokens to establish ownership of any combination of one or more assets, physical locations, and events (collectively referred to herein as “experiences”) to establish ownership of an experience by the holder of the electronic device on which the non-fungible token is stored. The process of minting a non-fungible token involves creating a digital file, creating or obtaining digital data that defines the experience, setting up a text file with code, uploading the file to a non-fungible token contract on the blockchain, and storing the non-fungible token. Storing a non-fungible token on the hlockchain provides a secure and tamper-proof record of the experience.

[0052] FIG. 3 depicts an exemplary process 50 for generating a non-fungible token 52. Digital content 54 that is to be associated with the non-fungible token 52 may be provided as input to a hashing function 56. The hashing function 56 may map the data defining the digital content to a fixed-size datum referred to as a hash 58. Thus, the digital content provided to the hashing function 56 does not need to be limited to a specific size or type of data. The hash 58 may be provided to one or more of the digital wallet 22 and the blockchain system 14. The digital wallet 22 may encrypt the hash 58 using the private key of a private key/public key pair to generate a signature 60. The digital wallet 22 may also issue the public key 62 of the private key/public key pair for use in generating the non-fungible token 52. The digital content 54 may also be provided to the content storage system 16. The content storage system 16 may store the digital content 54 in a publicly accessible network location identified by a URI 64. The URI 64 may be a static URI in that it may be maintained over time such that the digital content 54 can be accessed based on the URI 64 as stored on the blockchain 30.

[0053] The hash 58, signature 60, public key 62, and URI 64 may be stored in a block 32 of blockchain 30 by the blockchain system 14 to generate the non-fungible token 52. The digital content 54 may be validated at a later time by applying the same hashing function 56 to the digital content 54 using the public key 62, and comparing the newly generated hash 58 to the hash 58 stored on the blockchain 30. If the new hash 38 matches the stored hash, the digital content 56 may be considered as validated. The process 50 may be used to generate or validate a non-fungible token 52, which is a cryptographic asset that has a unique identification code and metadata that uniquely identifies the non-fungible token 52.

[0054] In an exemplary embodiment, the digital content 54 may comprise digital media (e.g., one or more of text-based content, image-based content, audio-based content, etc.) that is to be hashed as part of the process of minting a non-fungible token 52. In another embodiment, the digital content 54 may be associated with an existing non-fungible token 52. The ownership of a non-fungible token 52 may be recorded on the blockchain 30, in which case it can be transferred to another owner by adding another transaction to the blockchain 30 indicating the change in ownership. Non-fungible tokens 52 are uniquely identifiable assets that may contain the digital content or a reference to the digital content with which they are associated. Non-fungible tokens may function like cryptographic tokens. However, unlike cryptocurrencies such as Bitcoin or ETHEREUM™, non-fungible tokens 52 are typically not mutually interchangeable due to their uniqueness.

[0055] Although the non-fungible token 52 is depicted as being stored in a blockchain 30, it should be understood that the data which fully defines the non-fungible token 52 may be stored across one or more systems, e.g., the blockchain system 14, content storage system 16, user device 18, digital wallet 22, or any other suitable system. In addition, it should be further understood that although the digital content is depicted by FIG. 3 as being stored “off- chain” (e.g., by the content storage system 16), in other embodiments, the digital content may be stored “on-chain” (e.g., in a block 32 of blockchain 30.) For example, in cases where the digital content 54 requires a relatively small amount of storage space, it may be advantageous to store the digital content on the blockchain 30, e.g., to avoid “link rot”. In this case, the steps of storing the digital content 54 externally and generating the URI 64 may be omitted. [0056] Based on the concept that humans may be more comfortable with physical possession representing ownership, an embodiment of the present invention may include an NFC-card 20 having an embedded digital wallet 22 that stores private keys, records showing ownership of non-fungible tokens, and other digital assets for the card holder. The NFC-card 20 may include one or more of a near-field communication chip and a quick-response (QR) code. The private keys for the digital wallet 22 associated with the NFC-card 20 may be known by the card issuer.

[0057] FIG. 4 depicts an embodiment of the present invention in which two-party verification is used document an experience. By way of example, a user 66 may possess an NFC-card 20 which has been issued to them by a validating organization, such as a nonprofit entity. The user 66 may engage their NFC-card 20 with a user device 18 (e.g., a smartphone) or card reader 24 (not shown) owned by the validating organization while at a specific physical location. In an alternative embodiment, users 66 may check-in using their user device 18, for example, by engaging an NFC-card 20 owned by the validating organization. The user’s presence may be validated based on one or more of their physical location as determined by the user device 18 (e.g., using global positioning system (GPS)), a dynamic URL received from the NFC-card 20, or by scanning a QR-code 68 on-site as a form of selfreported verification. In response to the user 66 checking in, the badge system 12 may issue a digital asset, e.g., a digital certificate associated with a non- fungible token 52. When used for checking in, the NFC-card 20 may serve as a physical security key for two factor authentication.

[0058] The artificial intelligence economy may be credited with a surge of fake content and fake users. Blockchains 30 may help to address this issue, since they are decentralized digital provenances of value. However, blockchain technology can also be difficult for users and organizations to manage due to features like blind signing, hardware wallets, and signatures. Embodiments of the present invention provide a solution to this problem by verifying physical presence before data is sent to a blockchain 30. After a user checks-in at the physical location, digital assets (e.g., data showing one or more of ownership of a non- fungible token 52 and a copy of the non-fungible token 52) may be stored in a digital wallet 22 associated with the NFC-card 20 of the user 66, i.e., a carbon copy. Since blockchain data is tamper-resistant or “immutable” once it is recorded, the present invention provides assurance of authentic data by recording a proof of physical presence on a blockchain 30. [0059] In some embodiments of the present invention, a privacy-preserving component may be incorporated into a digital asset viewer on the NFC-card 20. The NFC-card 20 may include embedded functionality that enables selective disclosure or privacy-preserving identification. For example, NFC technology may be incorporated into the NFC-cards 20 to enable cardholders to be in complete control over how much information they reveal about their identity and physical location. By using zero knowledge proofs to produce verified credentials, a verifier may only have access to the level of detail specified by the cardholder. [0060] Embodiments of the present invention may include a mobile application that runs on the user device 18. FIGS. 5 and 6 depicts exemplary screens 70 that may be displayed by a user interface of the mobile application. The screens 70 may display information regarding numbers and types of “badges” 72 and “reward points” 76 that have been earned by the user 66 for performing activities, such as activities that build their personal brand. Users 66 may compete with each other to earn badges 72. Badges 72 may be awarded in response to the generation of a non-fungible token 52, and may be exchanged for monetary and nonmonetary rewards, such as challenge coins or business cards. The mobile application may provide a “single pane of glass” that saves time and increases transparency between the university and student, simplifies compliance with state laws and athletic regulations, generates data and insights on unique online and offline experiences, and increases student and university brand value.

[0061] FIG. 7 depicts an exemplary NFC-card 20 including a QR-code 68 and an image 74 of the user 66 associated with the NFC-card 20, e.g., a student-athlete. This type of NFC- card 20 may be distributed as a business card or collector card, for example. A cardholder may confirm their presence at an event (e.g., an athletic event) by engaging the NCF-card 20 with a card reader 24 located at the event. The NFC-card 20 may enable multiple features. Examples of such features may include digital certificates of training completion, collective memberships for athletics, digital art collectibles, and loyalty cards. Embodiments of the present invention may also be used for visitor collectibles, certifications, fan engagement, and as an athlete’s name, image, and likeness (NIL) business card.

[0062] By way of an example of how embodiments of the present invention may facilitate fan engagement, the badge system 12 may be configured so that engaging the NFC- card 20 with a specific card reader 24 (e.g., a card reader 24 located at a stadium) enters the cardholder into a raffle that entitles them to receive a prize, e.g., an autographed ball. As another example, engaging the NFC-card 20 with the cardholder’s user device 18 while located at an event may enable the cardholder to vote on something related to the event, e.g., a song to be played when the athlete pictured on the NFC-card 20 approaches the batter’s box in a baseball game. Engaging the NFC-card 20 with the user device 18 may also cause the user device 18 to display a webpage associated with the athlete’s social media account, the athletes real time statistics, an after game podcast, or a coupon for a product, e.g., a meal at a restaurant.

[0063] Consider the following exemplary scenario. A user 66 who is a stylist attends an event where they receive advanced training from a beauty products company. An NFC-card 20 may be linked to a digital wallet 22 belonging to the user 66 that is created by the beauty products company. After completing the training, the user 66 may receive a non-fungible token 52 that represents a completion of training. When the NFC-card 20 is engaged with a smartphone, the NFC-card 20 may redirect a browser application in the phone to a website that displays one or more non-fungible token-based training certificates completed by the user 66. In addition, the QR-code 68 may link to the user’s social media account, e.g., Instagram, which is a photo and video sharing social networking service owned by Meta Platforms of Menlo Park, California, United States. When the user 66 interacts with their customers, they can provide the NFC-card 20 so that the customer can easily verify the user’s work. The beauty products company may control the private keys to the digital wallet 22, and may transfer control of the digital wallet 22 to the user 66.

[0064] Student athletes may use the NFC-card 20 as a business card for fan engagement. The NFC-card 20 may link to a digital wallet 22 that contains NFTs of game clips, commentaries, and other files relevant to the card holder. The QR-code 68 may also link to the webpage of the student athlete’s individual statistics and team statistics so that the card holder can follow the athlete’s performance. The NFC-card 20 may enable the athlete to verify attendance at a particular physical location and time (such as a game), so that NFTs can be sent to the card holder’s digital wallet 22.

[0065] People often make pilgrimages to museums to see artworks, artifacts, or other objects of cultural significance. Their presence in front of the artwork (or more frequently, a selfie with the artwork) validates the visit and captures the work’s aura - that nearly indefinable quality with which an artwork or object is imbued by its authentic existence. In his seminal work, The Work of Art in the Age of Mechanical Reproduction, Walter Benjamin wrote “Even the most perfect reproduction of a work of art is lacking in one element: its presence in time and space, its unique existence at the place where it happens to be.” Without the elements of both space and time, the aura of an artwork is diminished. While current technology can create time-stamped certificates of an artwork’s provenance, a digital artwork’s aura is unrealized without a spatial dimension. Embodiments of the present invention may create unique digital representations that embed the time and physical location of when a museum visitor was physically present with a particular artwork.

[0066] In an embodiment of the present invention, museum visitors may be given their own NFC-card 20 that links to a digital wallet 22. The cardholder may scan a QR code next to a work of art in a museum, e.g., using their user device 18. The museum may then confirm the physical location and presence of the cardholder based on GPS coordinates provided by the cardholder’s user device 18. The museum may then provide a proof-of-visit non-fungible token 52 that is time-stamped, geo-stamped, and linked to a digital representation of the object that the visitor is viewing. Simultaneously, a high-quality reproduction of the original object may be archived on a blockchain 30. Because a blockchain 30 is a globally distributed, immutable database of unique digital objects, this may enhance public engagement with museums while also providing free and open access to the digital scan of the artwork along with its history and relevant research background.

[0067] Embodiments of the present invention may thereby increase public engagement and understanding of art and blockchain technology by providing high quality reproductions that are immutably tied to the original object through embedded data on a blockchain 30. Embodiments of the present invention may enhance an artwork’s aura by tying a digital version thereof to the physical original, while encouraging viewers to participate and engage with the piece itself. The creation of a proof-of- visit digital asset may not just unlock the potential of an art collection, it may also enhance the aura of the museum attendee’s visit. Regarding artwork, embodiments of the present invention may encourage engagement and participation at museums and art collections by providing a free, immutable, digital collectible embedded with the history and context of the original artwork. In addition, both high- and low-resolution scans of physical collections may be produced while simultaneously adding a layer of security and verifiable authenticity to each object in the collection.

[0068] A variety of stakeholders may benefit from embodiments of the present invention, including public audiences, museums, and scholars. For example, museums face growing challenges with viewer engagement and attendance. In a recent survey conducted by the International Council of Museums, almost 70 percent of museums lost more than half of their visitors in 2020. The creation of a unique digital representation of an attendee’s visit, along with the ability for the visitor to assemble their own digital archive of art works tied to their physical presence in the museum, may create a more engaging and interactive experience. In addition to possessing a permanent record of information about the artwork or artist, public audiences may develop a sense of accomplishment as they progress through the exhibits. This form of gamification may reward and challenge visitors to explore more of the museum and increase their time spent in the museum. Limiting the production of these digital assets to individuals who view the artwork in a physical location may also preserve their economic value by creating scarcity.

[0069] Valuable artwork is always at risk of theft, damage, or destruction. The creation of a unique digital object documenting the time and physical location of an attendee’s visit on an immutable database may facilitate the restoration of any stolen or damaged artwork by demonstrating proof of ownership. In the event of an object’s repatriation, the object’s legacy has been recorded for public and government scrutiny. Embodiments of the present invention may enable a museum to display a digital copy of a work that they returned as well as presenting the context in which it was acquired. This level of transparency along with the ability to continue to display an “authentic” copy of the work may encourage more museums to move towards repatriation.

[0070] The development of digital infrastructure to support immutable records of museum visits may promote research into public engagement with digital and physical art. The vast majority of objects in collections nationwide are inaccessible to researchers, and frequently unknown outside of their institutions. A publicly available but de-identified database of visitors’ timestamped movements through a museum may provide insights into the visitor museum experience and how it may be improved.

[0071] While these and other similar exhibits emphasize the commercial viability of non- fungible token projects for artists and museums, embodiments of the present invention may advance the field by enabling the visitor to become part of the creative process. The number and quality of the digital assets may be related to, but distinct from, those produced for the artist. Only an in-person visit by a unique individual can bring a new object into existence. Embodiments of the present invention may support efforts by museums like the Guggenheim in which “conservators are... exploring the possibility of uploading ownership records to the blockchain, which could help art historians researching the collection.”

[0072] It may be expensive for organizations and tedious for users to generate a publicly verifiable record of a user’s physical location. However, without this data, it may be difficult for organizations to measure impact, expand capacity, and create loyal communities.

Embodiments of the present invention may enable the manufacture of branded, loyalty cards that store digital assets based on a user’s physical location. Trainings and certifications can also be tied to the loyalty card wallet.

[0073] Embodiments of the present invention may enable nonprofits to measure the economic impact of their volunteers, identify and recruit volunteers from a publicly verifiable record of engagements, and motivate volunteers with unique digital assets of generative art. Volunteers may generate a publicly verifiable resume based on nonprofit activities. Funders may have access to real-time insights on nonprofit capacity and efforts. Corporations may reward volunteers by exchanging digital assets for products and measure their own employees’ volunteer efforts for environmental, social, and government (ESG) reporting.

[0074] Income may be generated by embodiments of the present invention in a variety of ways, including initialization fees, design fees for NFC-cards 20 and digital assets, hardware wallet and security setup, recurring revenue, additional cards and digital assets, user analytics subscription services, foundations and governments fund data collection, and employee volunteer measurement for annual reports and displays.

[0075] FIG. 8 depicts an exemplary process 80 for generating a non- fungible token 52 that may be used to document an experience (e.g., attendance of an event) in accordance with an embodiment of the present invention. The process 80 includes generating digital content 82 with the user device 18. This may include one or more of the user device 18 capturing an image, generating a video clip, determining its physical location, or performing some other activity that generates data. The user device 18 may transmit the digital content 84 from the user device 18 to a content storage system 16. The digital content transmitted to the content storage system 16 may include both content data (e.g., data defining an image) and metadata (data describing the image data). The content storage system 16 may store the content data 86 (e.g., on a web server) and generate an address 88 where the content data can be accessed. The address may include, for example, a URI that defines a link to the web server and a network location of the digital content on the web server. The content storage system 16 may then transmit the address 90 back to the user device 18.

[0076] The process 80 may further include transmitting a request for signature 92 from the user device 18 to a digital wallet 22. The request for signature 92 may include a hash of the digital content. The hash may be generated, for example, by an application running on the user device 18. In response to receiving the request for signature 92, the digital wallet 22 may generate the signature 94, e.g., by encrypting the hash using a private key. The digital wallet 22 may then transmit a response 96 including the signature and a public key to the user device 18.

[0077] In response to receiving the signature, the user device 18 may transmit a mint request 98 to the blockchain system 14 requesting the blockchain system 14 mint a non- fungible token. The mint request 98 may include the URI of the digital content, the hash of the digital content, the signature, and the public key. In response to receiving the mint request 98, the blockchain system 14 may mint the non-fungible token 100, and transmit a response 102 including the blockchain address of the non-fungible token 52. In an embodiment of the present invention, the user device 18 may include an application that prompts the user 66 to perform certain steps, such as capturing an image at an event. The application may then proceed to cause the user device 18 to generate the non-fungible token 52 by interacting with the blockchain system 14, content storage system 16, and digital wallet 22, thereby documenting the user 66 attended the event.

[0078] FIG. 9 depicts an exemplary process 110 for generating a non-fungible token 52 that documents a user experience in accordance with another embodiment of the present invention. The process 110 includes engaging 112 the user device 18 and user NFC-card 20. The NFC-card 20 may be a card issued to the user 66, a card associated with the event (e.g., a card that is engaged by the user device 18 of each user 66 entering the event), or a card issued to another person attending the event (e.g., a doner or university official). In response to engagement 112 with the user device 18, the NFC-card 20 may transmit a response 114 to the user device 18 including a URI, scan count, and signature. The URI may include a URL with a web address assigned to the badge system 12. The user device 18 may open the URL and transmit one or more of the card number, scan count, signature, time, and position data 116 to the badge system 12. The position may be determined by the user device 18 using an internal GPS receiver or other suitable positioning system, for example.

[0079] The badge system 12 may proceed to authenticate the signature and position data 118. The authentication process may include determining if the user 66 is listed as an invitee to an event, and if the user device 18 is in a position corresponding to the event. If any of the data does not match the expected values, the badge system 12 may log a failed attempt to document the experience, send a notification of the failure 119 to the user device 18, and the process 110 may terminate. If both the signature and position data do match the expected values, the badge system 12 may proceed to generate digital content 120. The digital content may include, for example, data defining the identity of the user 66 and the event being attended. The badge system 12 may then transmit a signature request 122 to a digital wallet 22 associated with (e.g., controlled by) the same validating organization as the badge system 12. The signature request 122 may include a hash of the digital content, which may be generated by badge system 12. In response to receiving the signature request 122, the digital wallet 22 may generate the signature 124, e.g., by encrypting the hash using a private key. The digital wallet 22 may then transmit a response 126 to the badge system 12 including the signature and a public key.

[0080] The badge system 12 may then transmit a mint request 128 to the blockchain system 14 requesting the blockchain system 14 mint a non-fungible token. The mint request 128 may include one or more of the digital content, the hash, the signature, and the public key. In response to receiving the mint request 128, the blockchain system 14 may mint the non-fungible token 130, and transmit a response 132 including the blockchain address of the non-fungible token 52 to the badge system 12. In response to receiving the blockchain address of the non-fungible token 52, the badge system 12 may forward a confirmation 134 to the user device 18 including the blockchain address of the non-fungible token 52, thereby indicating that the user’s experience has been documented.

[0081] FIG. 10 depicts an exemplary process 140 for generating a non-fungible token 52 that documents a user experience which includes meeting another individual (e.g., a donor) in accordance with another embodiment of the present invention. The process 140 includes engaging 142 the user device 18 and an NFC-card 20 (e.g., a user NFC-card 20). In response to engagement 142 with the user device 18, the NFC-card 20 may transmit a response 144 to the user device 18. The response may include a URI, a scan count, and a signature. The URI may include a URL with a web address assigned to the badge system 12. The user device 18 may open the URL and transmit the scan count, signature, and position data 146 to the badge system 12. The badge system 12 may authenticate the signature and position data 148 by, for example, determining if the user 66 is listed as an invitee to the event, and if the user device 18 is in a position corresponding to the event. If any of the data does not match the expected values, the badge system 12 may log a failed attempt to document the experience, send a notification of the failure 149 to the user device 18, and the process 1 10 may terminate. [0082] The process 140 may also include engaging 150 the user device 18 with another NFC-card 20, e.g., a donor NFC-card 20. In response to engagement 150 with the user device 18, the NFC-card 20 may transmit a response 152 to the user device 18 including a URI, a scan count, and a signature. The URI may include a URL with a web address assigned to the badge system 12. The user device 18 may open the URL and transmit the scan count, signature, and position data 154 to the badge system 12. The badge system 12 may authenticate the additional signature and position data 156 by, for example, determining if the user 66 is scheduled to meet with the donor in question. If any of the data does not match the expected values, the badge system 12 may log a failed attempt to document the experience, send a notification of the failure 157 to the user device 18, and the process 110 may terminate.

[0083] If both signatures and any additional qualifying data match expected values, the badge system 12 may generate digital content 158. The digital content may include, for example, data defining the identity of the user 66, the donor, and the event, time, and place where the user 66 and donor are meeting. The badge system 12 may then transmit a signature request 160 to a digital wallet 22 associated with the same validating organization as the badge system 12. The signature request 160 may include a hash of the digital content, which may be generated by the badge system 12. In response to receiving the signature request 160, the digital wallet 22 may generate the signature 162, e.g., by encrypting the hash using a private key. The digital wallet 22 may then transmit a response 164 to the badge system 12 including the signature and a public key.

[0084] The badge system 12 may then transmit a mint request 166 to the blockchain system 14 requesting the blockchain system 14 mint a non-fungible token. The mint request 166 may include the digital content, the signature, and the public key. In response to receiving the mint request 166, the blockchain system 14 may mint the non-fungible token 168, and transmit a response 170 including the blockchain address of the non-fungible token 52. In response to receiving the blockchain address of the non-fungible token 52, the badge system 12 may forward a confirmation 172 to the user device 18 including the blockchain address of the non-fungible token 52, thereby indicating that the user’s meeting with the donor has been documented.

[0085] FIG. 11 depicts an exemplary process 180 for generating a non-fungible token 52 that documents a user experience which includes capturing an image in accordance with another embodiment of the present invention. The process 180 includes engaging 182 the user device 18 and with an NFC-card 20, e.g., the user’s NFC-card 20. In response to the engagement 182, the NFC-card 20 may transmit a response 184 to the user device 18 including a URI, a scan count, and a signature. The URI may include a URL with a web address assigned to the badge system 12. Within a period of time proximate to engaging the NFC-card 20 (e.g., a period time from shortly before to shortly after engaging the NFC-card 20), the user device 18 may capture an image 186. The image may include a landmark, a work of art, a “selfie” that includes the user 66, a QR-code, or any other suitable person, place, or thing. Once the NFC-card data and image have been obtained, the user device 18 may open the URL and transmit one or more of the scan count, signature, position, and image data 188 to the badge system 12.

[0086] The badge system 12 may authenticate the signature and position data 190 by, for example, determining if the user 66 is listed as an invitee to an event, and if the user device 18 is in a position corresponding to the event. If any of the data does not match the expected values, the badge system 12 may log a failed attempt to document the experience, send a notification of the failure 191 to the user device 18, and the process 110 may terminate. [0087] If the signature and any additional qualifying data matches the expected values, the badge system 12 may transmit digital content 192 (e.g., the image data) to the content storage system 16. The content storage system 16 may store the digital content 194, and return a static URL 196 indicating where the digital content can be accessed. The badge system 12 may then transmit a signature request 198 to a digital wallet 22 associated with the same validating organization as the badge system 12. The signature request 198 may include a hash of the digital content, which may be generated by the badge system 12 or content storage system 16. In response to receiving the signature request 198, the digital wallet 22 may generate the signature 200, e.g., by encrypting the hash using a private key. The digital wallet 22 may then transmit a response 202 to the badge system 12 including the signature and a public key. [0088] The badge system 12 may then transmit a mint request 204 to the blockchain system 14 requesting the blockchain system 14 mint a non-fungible token. The mint request 204 may include the address where the digital content can be accessed, a hash of the digital content, the signature, and the public key. In response to receiving the mint request 204, the blockchain system 14 may mint the non-fungible token 206 and transmit a response 208 including the blockchain address of the non-fungible token 52. In response to receiving the blockchain address of the non-fungible token 52, the badge system 12 may forward a confirmation 210 to the user device 18 including the blockchain address of the non-fungible token 52, thereby indicating that the user’s experience has been documented.

[0089] FIG. 12 depicts an exemplary process 220 for generating a non-fungible token 52 that documents a user experience which includes receiving confirmation from a third party (e.g., from another person at the event) in accordance with another embodiment of the present invention. The process 220 includes engaging 222 the user device 18 and an NFC-card 20, e.g., the user’s NFC-card 20. In response to engagement 222 with the user device 18, the NFC-card 20 may transmit a response 224 to the user device 18 including a URI, a scan count, and a signature. The URI may include a URL with a web address assigned to the badge system 12. The user device 18 may open the URL and transmit one or more of the scan count, signature, and position 226 to the badge system 12.

[0090] The badge system 12 may authenticate the signature and position data 228 by, for example, determining if the user 66 is listed as an invitee to an event, and if the user device 18 is in a position corresponding to the event. If any of the data does not match the expected values, the badge system 12 may log a failed attempt to document the experience, send a notification of the failure 229 to the user device 18, and the process 220 may terminate.

[0091] If the signature and any additional qualifying data matches expected values, the badge system 12 may transmit a request 230 to a witness system 231. The request 230 may include, for example, an email asking for confirmation the user 66 attended the event, or that the user 66 satisfied some requirement, such as filling out a form, giving a presentation, etc. The witness system 231 may transmit a response 232 including information indicating whether the user 66 attended the event in question, or otherwise satisfied any requirements associated with the event. The response 232 may include, for example, an email from another person at the event that can confirm attendance by the user 66.

[0092] In an embodiment of the present invention, the witness system 231 may include or be in communication with the Ethereum Attestation Service (EAS) (not shown). EAS is a decentralized system that facilitates the creation, management, and verification of attestations available that is available from ETHEREUM. A schema for these attestations may be recorded on-chain as part of the minting process of the non-fungible token 52. Depending on gas costs, the badge system 12 may aggregate one or more attestations before issuing the non- fungible token 52 to the user’s digital wallet 22. For example, suppose that a user checks in five different days for a volunteer activity at an organization. In this scenario, the badge system 12 may record each one of these “check-ins” using a schema, and then once all five check-ins have been attested, the badge system 12 may send a “5x Volunteer” non-fungible token badge to the user’s digital wallet 22.

[0093] Advantageously, using attestations may enable a third party to attest to the activity using EAS before the badge system 12 issues a non-fungible token 52. For example, the Executive Director at the volunteer organization may be able to attest that the user’s volunteer activity was satisfactorily completed, e.g., that the volunteer stayed the required amount of time and completed the assigned tasks. The use of EAS to confirm completion of an experience may enable embodiments of the present invention to mint non-fungible tokens 52 with or without a third party approval.

100941 If the response 232 fails to confirm the user 66 satisfied the requirements of the experience, the badge system 12 may log a failed attempt to document the experience, send a notification of the failure 235 to the user device 18, and the process 220 may terminate. If the response 232 confirms the user 66 satisfied the requirements of the experience, the badge system 12 may proceed to generate digital content 234. The badge system 12 may then transmit a signature request 236 to a digital wallet 22 associated with the same validating organization as the badge system 12. The signature request 236 may include a hash of the digital content, which may be generated by badge system 12. In response to receiving the signature request 236, the digital wallet 22 may generate the signature 238, e.g., by encrypting the hash using a private key. The digital wallet 22 may then transmit a response 240 to the badge system 12 including the signature and a public key.

[0095] The badge system 12 may then transmit a mint request 242 to the blockchain system 14 requesting the blockchain system 14 mint a non-fungible token. The mint request 242 may include one or more of the digital content, the hash of the digital content, the signature, and the public key. In response to receiving the mint request 242, the blockchain system 14 may mint the non-fungible token 244, and transmit a response 246 including the blockchain address of the non-fungible token 52. In response to receiving the blockchain address of the non-fungible token 52, the badge system 12 may forward a confirmation 248 to the user device 18 including the blockchain address of the non-fungible token 52, thereby indicating that the user’s experience has been documented.

[0096] FIG. 13 depicts an exemplary process 250 for generating a non-fungible token 52 that documents a user experience in accordance with another embodiment of the present invention. The process 250 includes a user NFC-card 20 engaging 252 a card reader 24 at an event. In response to engagement 252 with the card reader 24, the NFC-card 20 may transmit a response 254 to the card reader 24 including a URI, a scan count, and a signature. The card reader 24 may open the URL and transmit one or more of the card number, scan count, signature, time, and position data 256 to the badge system 12. The position may set based on a known physical location of the card reader 24, or may be determine by the card reader 24 using a positioning system, such as GPS.

[0097] The badge system 12 may proceed to authenticate the signature and position data 258. If authentication fails, the badge system 12 may log a failed attempt to document the experience and send a notification 260 the card reader 24, which may in turn provide an indication to the user 66 that they should attempt another scan. If authentication is successful, the badge system 12 may proceed to generate digital content 262. The digital content may include, for example, data defining the identity of the user 66 and the event being attended. The badge system 12 may then transmit a signature request 264 to a digital wallet 22 associated with the same validating organization as the badge system 12. The signature request 264 may include a hash of the digital content. In response to receiving the signature request 264, the digital wallet 22 may generate the signature 266, e.g., by encrypting the hash using a private key. The digital wallet 22 may then transmit a response 268 to the badge system 12 including the signature and a public key.

[0098] The badge system 12 may then transmit a mint request 270 to the blockchain system 14 requesting the blockchain system 14 mint a non-fungible token. The mint request 270 may include the digital content, the signature, and the public key. In response to receiving the mint request 270, the blockchain system 14 may mint the non-fungible token 272, and transmit a response 274 including the blockchain address of the non-fungible token 52.

[0099] Scholarships represent a vital lifeline for students by offering crucial support for tuition, textbooks, and other essential expenses. However, many scholarships have specific renewal criteria that students must meet to continue receiving funding. Universities grapple with verifying the eligibility of students for scholarships year after year. Traditionally, students navigate a labyrinth of hurdles, from procuring letters of recommendation to verifying attendance at various events. Embodiments of the present invention may be able to help address this problem by verifying student participation at campus events, such as career fairs, student club meetings, volunteer opportunities, etc. Embodiments of the present invention may enable students to document activities associated with building job and life skills, such as financial and legal literacy, using blockchain technology. The use of blockchains may enable donors and employers to view a publicly verifiable, immutable list of achievements.

[0100] Blockchains are considered by some to be fundamental building blocks of the digital economy. Embodiments of the present invention may be configured so that students can tap their phones on an NFC-card or other similarly configured device at the entrance to an event, such as a career fair. In response, their time and physical location may be stamped and recorded on a blockchain. The physical presence of the student at an event may be necessary to activate this type of attestation, e.g., by requiring them to unlock their phone using a password or biomarker. Furthermore, because the evidence is stored on a blockchain, the university can trust a student’s claim of meeting scholarship-related activities since the technology makes it virtually impossible to back-date an activity or change values in a record. Thus, one benefit of the mobile applications disclosed herein is that they can ensure the uninterrupted flow of financial assistance, enabling students to devote their energies to academic pursuits. Removing the burdensome distraction of managing, tracking, and reporting requirements may also help students avoid missing deadlines or seeking alternative funding avenues.

[0101] Embodiments of the present invention may also be used to provide a reputation and personal brand management platform that can be particularly helpful for students involved in competitive athletics. In particular, embodiments of the present invention may be used to manage a student’s name, image, and likeness, thereby facilitating corporate marketing deals and matchmaking between companies and students.

[0102] Rapid advances in generative artificial intelligence have contributed to an erosion in confidence in information due their ability to generate “deep fakes” and other false information. By providing highly secure documentation of student activities, embodiments of the present invention may improve the ability of students to prove their reputation and marketability. Although most companies in the name, image, and likeness marketing space focus on collegiate athletes, embodiments of the present invention may provide a solution to all students on a university campus. For example, the best match for a company marketing campaign may be someone other than a university-level sports performer, e.g., a student club president or a high- achieving journalism student.

[0103] Embodiments of the present invention may be used to certify student academic endeavors and enable students to document their activities on and off campus. Developing a brand may help students open doors to employment opportunities and corporate collaborations. Embodiments of the present invention may also enable students to pair with brand partners while simplifying tax filings and contract management. Accumulating digital badges that demonstrate offline and online activities, such as social media reach, volunteer work, academic achievements, and university event attendance, may facilitate students growing their personal brand. The use of blockchain may streamline administrative processes and foster a culture of transparency and empowerment, and enable corporate brands to trust verified metrics of the student- athletes, which may include academic performance, community, and social reputation. Companies may be more inclined to partner with student-athletes having a good reputation that aligns with their brand. Artificial intelligence algorithms may be used to analyze an athlete’s social media engagement and brand preferences to craft personalized strategies. Artificial intelligence may also help the matching process between student-athletes and brands. By evaluating compatibility based on factors like audience demographics and marketing objectives, artificial intelligence may be able to identify partnerships that are likely to be mutually beneficial.

[0104] Referring now to FIG. 14, embodiments of the present invention described above, or portions thereof, may be implemented using one or more computing devices or systems, such as exemplary computer 300. The computer 300 may include a processor 302, a memory 304, an input/output (I/O) interface 306, and a Human Machine Interface (HMI) 308. The computer 300 may also be operatively coupled to one or more external resources 310 via the data network 26 or I/O interface 306. External resources may include, but are not limited to, servers, databases, mass storage devices, peripheral devices, cloud-based network services, or any other resource that may be used by the computer 300.

[0105] The processor 302 may include one or more devices selected from microprocessors, micro-controllers, digital signal processors, microcomputers, central processing units, field programmable gate arrays, programmable logic devices, state machines, logic circuits, analog circuits, digital circuits, or any other devices that manipulate signals (analog or digital) based on operational instructions stored in memory 304. Memory 304 may include a single memory device or a plurality of memory devices including, but not limited to, read-only memory (ROM), random access memory (RAM), volatile memory, non- volatile memory, static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, cache memory, or data storage devices such as a hard drive, optical drive, tape drive, volatile or non-volatile solid state device, or any other device capable of storing data.

[0106] The processor 302 may operate under the control of an operating system 314 that resides in memory 304. The operating system 314 may manage computer resources so that computer program code embodied as one or more computer software applications, such as an application 16 residing in memory 304, may have instructions executed by the processor 302. In an alternative embodiment, the processor 302 may execute the application 316 directly, in which case the operating system 314 may be omitted. One or more data structures 318 may also reside in memory 304, and may be used by the processor 302, operating system 314, or application 316 to store or manipulate data.

[0107] The I/O interface 306 may provide a machine interface that operatively couples the processor 302 to other devices and systems, such as the external resource 310 or the network 312. The application 316 may thereby work cooperatively with the external resource 310 or network 312 by communicating via the I/O interface 306 to provide the various features, functions, applications, processes, or modules comprising embodiments of the present invention. The application 316 may also have program code that is executed by one or more external resources 310, or otherwise rely on functions or signals provided by other system or network components external to the computer 300. Indeed, given the nearly endless hardware and software configurations possible, persons having ordinary skill in the art will understand that embodiments of the present invention may include applications that are located externally to the computer 300, distributed among multiple computers or other external resources 310, or provided by computing resources (hardware and software) that are provided as a service over the network 312, such as a cloud computing service.

[0108] The HMI 308 may be operatively coupled to the processor 302 of computer 300 to allow a patient to interact directly with the computer 300. The HMI 308 may include video or alphanumeric displays, a touch screen, a speaker, and any other suitable audio and visual indicators capable of providing data to the patient. The HMI 308 may also include input devices and controls such as an alphanumeric keyboard, a pointing device, keypads, pushbuttons, control knobs, microphones, etc., capable of accepting commands or input from the patient and transmitting the entered input to the processor 302.

[0109] A database 320 may reside in memory 304, and may be used to collect and organize data used by the various systems and modules described herein. The database 320 may include data and supporting data structures that store and organize the data. In particular, the database 320 may be arranged with any database organization or structure including, but not limited to, a relational database, a hierarchical database, a network database, or combinations thereof. A database management system in the form of a computer software application executing as instructions on the processor 302 may be used to access the information or data stored in records of the database 320 in response to a query, which may be dynamically determined and executed by the operating system 314, other applications 316, or one or more modules.

[0110] In general, the routines executed to implement the embodiments of the present invention, whether implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions, or a subset thereof, may be referred to herein as “computer program code,” or simply “program code.” Program code typically comprises computer-readable instructions that are resident at various times in various memory and storage devices in a computer and that, when read and executed by one or more processors in a computer, cause that computer to perform the operations necessary to execute operations or elements embodying the various aspects of the embodiments of the present invention. Computer-readable program instructions for carrying out operations of the embodiments of the present invention may be, for example, assembly language, source code, or object code written in any combination of one or more programming languages.

[0111] Various program code described herein may be identified based upon the application within which it is implemented in specific embodiments of the present invention. However, it should be appreciated that any particular program nomenclature which follows is used merely for convenience, and thus the present invention should not be limited to use solely in any specific application identified or implied by such nomenclature. Furthermore, given the generally endless number of manners in which computer programs may be organized into routines, procedures, methods, modules, objects, and the like, as well as the various manners in which program functionality may be allocated among various software layers that are resident within a typical computer (e.g., operating systems, libraries, API’s, applications, applets, etc.), it should be appreciated that the embodiments of the present invention are not limited to the specific organization and allocation of program functionality described herein.

[0112] The program code embodied in any of the applications/modules described herein is capable of being individually or collectively distributed as a computer program product in a variety of different forms. In particular, the program code may be distributed using a computer-readable storage medium having computer-readable program instructions thereon for causing a processor to carry out aspects of the embodiments of the present invention. [0113] Computer-readable storage media, which is inherently non-transitory, may include volatile and non-volatile, and removable and non-removable tangible media implemented in any method or technology for storage of data, such as computer-readable instructions, data structures, program modules, or other data. Computer-readable storage media may further include RAM, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other solid state memory technology, portable compact disc read-only memory (CD-ROM), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store data and which can be read by a computer. A computer-readable storage medium should not be construed as transitory signals per se (e.g., radio waves or other propagating electromagnetic waves, electromagnetic waves propagating through a transmission media such as a waveguide, or electrical signals transmitted through a wire). Computer-readable program instructions may be downloaded to a computer, another type of programmable data processing apparatus, or another device from a computer-readable storage medium or to an external computer or external storage device via a network.

[0114] Computer-readable program instructions stored in a computer-readable medium may be used to direct a computer, other types of programmable data processing apparatuses, or other devices to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions that implement the functions, acts, or operations specified in the flowcharts, sequence diagrams, or block diagrams. The computer program instructions may be provided to one or more processors of a general purpose computer, a special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the one or more processors, cause a series of computations to be performed to implement the functions, acts, or operations specified in the text of the specification, flowcharts, sequence diagrams, or block diagrams.

[0115] The flowcharts and block diagrams depicted in the figures illustrate the architecture, functionality, or operation of possible implementations of systems, methods, or computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function or functions.

[0116] In certain alternative embodiments, the functions, acts, or operations specified in the flowcharts, sequence diagrams, or block diagrams may be re-ordered, processed serially, or processed concurrently consistent with embodiments of the present invention. Moreover, any of the flowcharts, sequence diagrams, or block diagrams may include more or fewer blocks than those illustrated consistent with embodiments of the present invention. It should also be understood that each block of the block diagrams or flowcharts, or any combination of blocks in the block diagrams or flowcharts, may be implemented by a special purpose hardware-based system configured to perform the specified functions or acts, or carried out by a combination of special purpose hardware and computer instructions.

[0117] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the present invention. As used herein, the singular forms “a”, “an” and “the” are intended to include both the singular and plural forms, and the terms “and” and “or” are each intended to include both alternative and conjunctive combinations, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” or “comprising,” when used in this specification, specify the presence of stated features, integers, actions, steps, operations, elements, or components, but do not preclude the presence or addition of one or more other features, integers, actions, steps, operations, elements, components, or groups thereof.

Furthermore, to the extent that the terms “includes”, “having”, “has”, “with”, “comprised of, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising”.

[0118] While all the present invention has been illustrated by a description of various embodiments, and while these embodiments have been described in considerable detail, it is not the intention of the Applicant to restrict or in any way limit the scope of the appended claims to such detail. Additional advantages and modifications will readily appear to those skilled in the art. The present invention in its broader aspects is therefore not limited to the specific details, representative apparatus and method, and illustrative examples shown and described. Accordingly, departures may be made from such details without departing from the spirit or scope of the Applicant’s general inventive concept.

Claims

CLAIMS What is claimed is:

1. A method of generating non-fungible tokens, comprising: receiving a first dynamic uniform resource identifier at a first computing device, the first dynamic uniform resource identifier including a unique identifier and a hostname that identifies a host system; transmitting first data from the first computing device to the host system identified by the hostname, the first data including the unique identifier and at least one of a time the first computing device received the first dynamic uniform resource identifier and a physical location of the first computing device when the first dynamic uniform resource identifier was received; and minting a non-fungible token on a blockchain that documents at least one of the time the first computing device received the first dynamic uniform resource identifier and the physical location of the first computing device when the first dynamic uniform resource identifier was received.

2. The method of claim 1, wherein the first computing device is a user device, and the first dynamic uniform resource identifier is received from a near- field communication card associated with one of an event or an individual.

3. The method of claim 2, wherein the unique identifier includes a card number, and the card number is used to identify the event or the individual with which the near-field communication card is associated.

4. The method of claim 1 , wherein the first computing device is a card reader associated with an event, and the first dynamic uniform resource identifier is received from a near-field communication card associated with an individual.

5. The method of claim 1, further comprising: receiving, by the first computing device, a second dynamic uniform resource identifier that includes a second unique identifier and the hostname identifying the host system; and transmitting second data from the first computing device to the host system identified by the hostname, the second data including the second unique identifier and at least one of the time the first computing device received the second dynamic uniform resource identifier and the physical location of the first computing device when the second dynamic uniform resource identifier was received, wherein the non-fungible token further documents at least one of the time the first computing device received the second dynamic uniform resource identifier and the physical location of the first computing device when the second dynamic uniform resource identifier was received.

6. The method of claim 5, wherein the first computing device is a user device, the first dynamic uniform resource identifier is received from a near- field communication card associated with a first individual or an event, and the second dynamic uniform resource identifier is received from a near-field communication card associated with a second individual.

7. The method of claim 1, further comprising: generating a signature based on the first data, wherein minting the non-fungible token includes storing the signature on the blockchain.

8. The method of claim 1, further comprising: generating digital content; transmitting the digital content to a content storage system; and receiving a static uniform resource locator from the content storage system identifying a network location where the digital content is stored, wherein minting the non-fungible token includes storing the static uniform resource locator on the blockchain.

9. The method of claim 8, further comprising: generating a hash of the digital content, wherein minting the non-fungible token includes storing the hash of the digital content on the blockchain.

10. The method of claim 8, further comprising: generating a signature based on the hash of the digital content, wherein minting the non-fungible token includes storing the signature on the blockchain.

11. A system for generating non-fungible tokens, comprising: one or more processors; and memory in communication with the one or more processors, the memory including program code that, when executed by the one or more processors, causes the system to: receive a first dynamic uniform resource identifier at a first computing device, the first dynamic uniform resource identifier including a unique identifier and a hostname that identifies a host system; transmit first data from the first computing device to the host system identified by the hostname, the first data including the unique identifier and at least one of a time the first computing device received the first dynamic uniform resource identifier and a physical location of the first computing device when the first dynamic uniform resource identifier was received; and mint a non-fungible token on a blockchain that documents at least one of the time the first computing device received the first dynamic uniform resource identifier and the physical location of the first computing device when the first dynamic uniform resource identifier was received.

12. The system of claim 11, wherein the first computing device is a user device, and the first dynamic uniform resource identifier is received from a near- field communication card associated with one of an event or an individual.

13. The system of claim 12, wherein the unique identifier includes a card number, and the card number is used to identify the event or the individual with which the near-field communication card is associated.

14. The system of claim 11, wherein the first computing device is a card reader associated with an event, and the first dynamic uniform resource identifier is received from a near-field communication card associated with an individual.

15. The system of claim 11, wherein the program code further causes the system to: receive, by the first computing device, a second dynamic uniform resource identifier that includes a second unique identifier and the hostname identifying the host system; and transmit second data from the first computing device to the host system identified by the hostname, the second data including the second unique identifier and at least one of the time the first computing device received the second dynamic uniform resource identifier and the physical location of the first computing device when the second dynamic uniform resource identifier was received, wherein the non-fungible token further documents at least one of the time the first computing device received the second dynamic uniform resource identifier and the physical location of the first computing device when the second dynamic uniform resource identifier was received.

16. The system of claim 15, wherein the first computing device is a user device, the first dynamic uniform resource identifier is received from a near-field communication card associated with a first individual or an event, and the second dynamic uniform resource identifier is received from a near-field communication card associated with a second individual.

17. The system of claim 11, wherein the program code further causes the system to: generate a signature based on the first data, wherein minting the non-fungible token includes storing the signature on the blockchain.

18. The system of claim 11, wherein the program code further causes the system to: generate digital content; transmit the digital content to a content storage system; and receive a static uniform resource locator from the content storage system identifying a network location where the digital content is stored, wherein minting the non-fungible token includes storing the static uniform resource locator on the blockchain.

19. The system of claim 18, wherein the program code further causes the system to: generate a hash of the digital content, wherein minting the non-fungible token includes storing the hash of the digital content on the blockchain.

20. The system of claim 18, wherein the program code further causes the system to: generate a signature based on the hash of the digital content, wherein minting the non-fungible token includes storing the signature on the blockchain.

21. A computer program product comprising: a non-transitory computer-readable storage medium; and program code stored on the non-transitory computer-readable storage medium that, when executed by one or more processors, causes the one or more processors to: receive a first dynamic uniform resource identifier at a first computing device, the first dynamic uniform resource identifier including a unique identifier and a hostname that identifies a host system; transmit first data from the first computing device to the host system identified by the hostname, the first data including the unique identifier and at least one of a time the first computing device received the first dynamic uniform resource identifier and a physical location of the first computing device when the first dynamic uniform resource identifier was received; and mint a non-fungible token on a blockchain that documents at least one of the time the first computing device received the first dynamic uniform resource identifier and the physical location of the first computing device when the first dynamic uniform resource identifier was received.