IP Library › Patent Application 19284936
Patent Application
App. No. 19/284,936

CLIENT DEVICE FOR GENERATING NFTS IN RESPONSE TO IN-APP ISSUANCE REQUESTS AND METHODS FOR USE THEREWITH

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
19/284,936
Abstract

An NFT system operates by receiving an application launch request for a game application having a game non-fungible token (NFT) associated therewith; generating, via the game application and in response to the application launch request, launch metadata; sending the launch metadata to an NFT wallet, the NFT wallet containing a private key associated with the game NFT; receiving, from the NFT wallet, a launch response that is generated based on the private key; generating, via the game application and based on the launch response, an ownership check; sending the ownership check to a blockchain system that stores the game NFT; receiving, from the blockchain system, an ownership validation response; and enabling, via the game application, play of the game when the ownership validation response indicates ownership of the game NFT is verified.

Claims (45)

1 . A method for use with a client device that includes a processor and a memory, the method comprising:

receiving, at the client device and from a game application associated with an electronic game played by a user of the client device, an in-app issuance request for an in-app NFT;

generating, via the client device, an ownership check;

sending the ownership check to a blockchain system that stores a game NFT associated with the electronic game and the user;

receiving, from the blockchain system, an ownership validation response that indicates whether user's ownership of the game NFT is verified; and

facilitating, via the game application, a minting of the in-app NFT when the ownership validation response indicates the user's ownership of the game NFT is verified.

2 . The method of claim 1 , further comprising:

generating a payment request in response to the in-app issuance request; and

receiving a payment response verifying the in-app issuance request;

wherein the ownership check is generated in response to the payment response.

3 . The method of claim 1 , wherein the in-app NFT has in-app NFT metadata associated therewith, wherein the in-app NFT metadata includes achievement data associated with the electronic game and the user.

4 . The method of claim 1 , wherein the in-app NFT has in-app NFT metadata associated therewith, wherein the in-app NFT metadata an application identifier associated with the electronic game.

5 . The method of claim 1 , wherein the in-app NFT has in-app NFT metadata associated therewith, wherein the in-app NFT metadata includes a user identifier associated with the user.

6 . The method of claim 1 , wherein the in-app NFT has in-app NFT metadata associated therewith, wherein the in-app NFT metadata includes an instance identifier indicating an instance of the electronic game associated with the user.

7 . The method of claim 1 , further comprising:

preventing, via the game application, the minting of the in-app NFT when the ownership validation response indicates the user's ownership of the game NFT is not verified.

8 . The method of claim 1 , wherein the game application is configured to determine if the user's play of the electronic game is permitted based on ownership of the game NFT.

9 . The method of claim 1 , further comprising:

generating a payment request in response to the in-app issuance request; and

preventing, via the game application, the minting of the in-app NFT when the payment request is denied.

10 . The method of claim 1 , wherein the in-app issuance request is generated automatically by the gaming application.

11 . A client device comprises:

a network interface configured to communicate via a network;

at least one processor;

a non-transitory machine-readable storage medium that stores operational instructions that, when executed by the processor, cause the at least one processor to perform operations that include:

receiving, at the client device and from a game application associated with an electronic game played by a user of the client device, an in-app issuance request for an in-app NFT;

generating, via the client device, an ownership check;

sending the ownership check to a blockchain system that stores a game NFT associated with the electronic game and the user;

receiving, from the blockchain system, an ownership validation response that indicates whether user's ownership of the game NFT is verified; and

facilitating, via the game application, a minting of the in-app NFT when the ownership validation response indicates the user's ownership of the game NFT is verified.

12 . The client device of claim 11 , wherein the operations further include:

generating a payment request in response to the in-app issuance request; and

receiving a payment response verifying the in-app issuance request;

wherein the ownership check is generated in response to the payment response.

13 . The client device of claim 11 , wherein the in-app NFT has in-app NFT metadata associated therewith, wherein the in-app NFT metadata includes achievement data associated with the electronic game and the user.

14 . The client device of claim 11 , wherein the in-app NFT has in-app NFT metadata associated therewith, wherein the in-app NFT metadata an application identifier associated with the electronic game.

15 . The client device of claim 11 , wherein the in-app NFT has in-app NFT metadata associated therewith, wherein the in-app NFT metadata includes a user identifier associated with the user.

16 . The client device of claim 11 , wherein the in-app NFT has in-app NFT metadata associated therewith, wherein the in-app NFT metadata includes an instance identifier indicating an instance of the electronic game associated with the user.

17 . The client device of claim 11 , wherein the operations further include:

preventing, via the game application, the minting of the in-app NFT when the ownership validation response indicates the user's ownership of the game NFT is not verified.

18 . The client device of claim 11 , wherein the game application is configured to determine if the user's play of the electronic game is permitted based on ownership of the game NFT.

19 . The client device of claim 11 , wherein the operations further include:

generating a payment request in response to the in-app issuance request; and

preventing, via the game application, the minting of the in-app NFT when the payment request is denied.

20 . The client device of claim 11 , wherein the in-app issuance request is generated automatically by the gaming application.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2025
From: MEYERS, MARK; STUCKMAN, BRUCE E.
To: GALIANT ARTS, LLC
Reel/Frame 072418/0918 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2025
From: HOWARD, JOHN W.; HOWARD, BRIAN G.; MEADOR, GREGORY
To: INMOTION SOFTWARE, LLC
Reel/Frame 072419/0039 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2025
From: INMOTION SOFTWARE, LLC
To: GALIANT ARTS, LLC
Reel/Frame 072419/0084 →