IP Library Granted Patent US 12,375,281
Granted Patent B2
US 12,375,281 · App. 18/646,319 · Granted Jul 29, 2025

Systems and methods for token metadata management

Inventors: Kevan Connor Mordan (Ogden, UT); Mohammad Reza Kavian (Toronto, CA); Benjamin Ilan Weinberg (Toronto, CA)
Assignee: DK Crown Holdings Inc.
H04L9/3213H04L9/50
View Patent ↗
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 12,375,281
App. No.
18/646,319
Granted
Jul 29, 2025
Kind
B2
Abstract

Systems and methods for token metadata management are disclosed. A system can determine that a token has been minted on a blockchain based on a smart contract identifying an identifier of the token and a base uniform resource identifier (URI). Responsive to determining that the token has been minted on the blockchain, the system stores metadata for the token at a location in a database. The database corresponds to the base URI and the location in the database is identified by the identifier of the token. The system generates a metadata URI for the token based on the base URI and the identifier for the token, detects a change to a status of a contest identified in the metadata of the token, and upon detecting the change to the status of the contest, modifies the metadata of the token using the metadata URI.

Claims (63)

1. A system, comprising:

one or more processors and non-transitory memory storing instructions that, when executed, cause the one or more processors to:

receive, from a blockchain node of a blockchain, an identifier of a token that has been minted on the blockchain;

generate a metadata uniform resource locator (URI) for the token based on the identifier of the token and a base URI identifying a database;

generate a data record in the database at a location identified by the metadata URI;

determine that metadata associated with the token is to be updated; and

upon determining that the metadata is to be updated, modify the data record associated with the token using the metadata URI.

2. The system of claim 1 , wherein the one or more processors are further configured to:

determine that the metadata associated with the token is to be updated based on a change to a contest identifying the token.

3. The system of claim 1 , wherein the one or more processors are further configured to:

generate the metadata URI by appending the identifier of the token to the base URI as a URI parameter.

4. The system of claim 1 , wherein the one or more processors are further configured to:

cause information on the blockchain associated with the token to be updated in response to determining that the metadata associated with the token is to be updated.

5. The system of claim 1 , wherein the one or more processors are further configured to:

receive an indication that the token has been entered into a contest; and

update the data record to include the indication that the token has been entered into the contest.

6. The system of claim 1 , wherein the one or more processors are further configured to:

determine that the token is assigned to a player profile; and

update the data record to include an indication that the token has been assigned to the player profile.

7. The system of claim 1 , wherein the one or more processors are further configured to:

identify an outcome of a contest identifying the token; and

update the data record associated with the token based on the outcome of the contest.

8. The system of claim 1 , wherein the data record identifies the token as an entrant to a first contest, and wherein the one or more processors are further configured to:

receive a request to enter the token in a second contest;

determine that the data record includes an indication that the token is to be restricted from entry to further contests; and

restrict entry of the token to the second contest responsive to determining that the data record includes the indication.

9. The system of claim 8 , wherein the one or more processors are further configured to:

determine that the first contest has terminated; and

update the data record to remove the indication.

10. The system of claim 1 , wherein the one or more processors are further configured to:

determine that the token has been burned on the blockchain; and

remove the metadata from the database according to the metadata URI.

11. A method, comprising:

receiving, by one or more processors and non-transitory memory, from a blockchain node of a blockchain, an identifier of a token that has been minted on the blockchain;

generating, by the one or more processors, a metadata uniform resource locator (URI) for the token based on the identifier of the token and a base URI identifying a database;

generating, by the one or more processors, a data record in the database at a location identified by the metadata URI;

determining, by the one or more processors, that metadata associated with the token is to be updated; and

upon determining that the metadata is to be updated, modifying, by the one or more processors, the data record associated with the token using the metadata URI.

12. The method of claim 11 , further comprising:

determining, by the one or more processors, that the metadata associated with the token is to be updated based on a change to a contest identifying the token.

13. The method of claim 11 , further comprising:

generating, by the one or more processors, the metadata URI by appending the identifier of the token to the base URI as a URI parameter.

14. The method of claim 11 , further comprising:

causing, by the one or more processors, information on the blockchain associated with the token to be updated in response to determining that the metadata associated with the token is to be updated.

15. The method of claim 11 , further comprising:

receiving, by the one or more processors, an indication that the token has been entered into a contest; and

updating, by the one or more processors, the data record to include the indication that the token has been entered into the contest.

16. The method of claim 11 , further comprising:

determining, by the one or more processors, that the token is assigned to a player profile; and

updating, by the one or more processors, the data record to include an indication that the token has been assigned to the player profile.

17. The method of claim 11 , further comprising:

identifying, the one or more processors, an outcome of a contest identifying the token; and

updating, by the one or more processors, the data record associated with the token based on the outcome of the contest.

18. The method of claim 11 , wherein the data record identifies the token as an entrant to a first contest, and further comprising:

receiving, by the one or more processors, a request to enter the token in a second contest;

determining, by the one or more processors, that the data record includes an indication that the token is to be restricted from entry to further contests; and

restricting, by the one or more processors, entry of the token to the second contest responsive to determining that the data record includes the indication.

19. The method of claim 18 , further comprising:

determining, by the one or more processors, that the first contest has terminated; and

updating, by the one or more processors, the data record to remove the indication.

20. The method of claim 11 , further comprising:

determining, by the one or more processors, that the token has been burned on the blockchain; and

removing, by the one or more processors, the metadata from the database according to the metadata URI.

Assignments (2)
SECURITY INTEREST Recorded Nov 7, 2024
From: DK CROWN HOLDINGS INC.; JACKPOCKET LLC
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 069320/0109 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 26, 2024
From: MORDAN, KEVAN CONNOR; KAVIAN, MOHAMMAD REZA; WEINBERG, BENJAMIN ILAN
To: DK CROWN HOLDINGS INC.
Reel/Frame 067232/0993 →
Continuity (2)
Continuation 18336732 · Jun 16, 2023
Related Publication 20240421996A1 · Dec 19, 2024
References Cited (15)
US 11469886B2 · Padmanabhan · 2022 [cited by examiner]
US 11723391B2 · Morita · 2023 [cited by examiner]
US 11824970B2 · Padmanabhan · 2023 [cited by examiner]
US 11880372B2 · Padmanabhan · 2024 [cited by examiner]
US 20190130391A1 · Wright · 2019 [cited by examiner]
US 20210226774A1 · Padmanabhan · 2021 [cited by examiner]
US 20220006642A1 · Maj · 2022 [cited by examiner]
US 20230006976A1 · Jakobsson · 2023 [cited by examiner]
US 20230034169A1 · Ferenczi · 2023 [cited by examiner]
US 20230356091A1 · Eisenberg · 2023 [cited by examiner]
US 20230367776A1 · Padmanabhan · 2023 [cited by examiner]
US 20230371995A1 · Vogt · 2023 [cited by examiner]
US 20240289783A1 · Alsahnawi · 2024 [cited by examiner]
Non-Final Office Action on U.S. Appl. No. 18/336,732 dated Sep. 8, 2023. [cited by applicant]
Notice of Allowance on U.S. Appl. No. 18/336,732 dated Dec. 28, 2023. [cited by applicant]