Granted Patent B2

US 12,652,170 · App. 18/927,692 · Granted Jun 9, 2026

Inventors: Kevin Osborn (Newton Highlands, MA); Austin Erickson (Herndon, VA); Christopher Wu (Ashburn, VA); Timur Sherif (Silver Spring, MD)

Assignee: Capital One Services, LLC

H04L9/088G06F16/164H04L9/30

Abstract

Claims (72)

1 . A method for using non-fungible tokens for blockchain functions, the method comprising:

receiving, from a user-specific digital storage resource application on a user device, a user request to generate a non-fungible token with variable metadata properties;

determining a first metadata property threshold for a first metadata property of the non-fungible token;

determining a first encoded instruction for a first smart contract for the non-fungible token, wherein the first encoded instruction comprises a first automatic response to a first type of blockchain function of a plurality of types of blockchain functions interacting with the first smart contract, wherein the first automatic response comprises a comparison of a current state of the first metadata property against the first metadata property threshold, wherein the current state is stored off-chain;

determining a second encoded instruction for the first smart contract, wherein the second encoded instruction comprises a second automatic response to the first type of blockchain function interacting with the first smart contract, wherein the second automatic response comprises querying a non-transferable smart contract address for the current state; and

causing to be generated, at the user-specific digital storage resource application on the user device, a private key for the non-fungible token.

2 . The method of claim 1 , further comprising:

determining a third encoded instruction for the first smart contract, wherein the third encoded instruction comprises a restriction on transferability of the non-fungible token; and

determining a third automatic response to a second type of blockchain function of the plurality of types of blockchain functions interacting with the first smart contract, and wherein the third automatic response comprises a termination of any blockchain functions of the second type.

3 . The method of claim 1 , further comprising:

determining a fourth encoded instruction for the first smart contract, wherein the fourth encoded instruction comprises a list of smart contract addresses that may interact with the first smart contract; and

determining a fourth automatic response, wherein the fourth automatic response comprises a termination of any blockchain functions involving a smart contract address not on the list of smart contract addresses.

4 . The method of claim 1 , further comprising:

generating the first smart contract comprising the first encoded instruction and the second encoded instruction; and

determining a first smart contract address for the first smart contract.

5 . The method of claim 1 , further comprising:

determining, in response to receiving the user request to generate the non-fungible token with variable metadata properties, an identity of a user corresponding to the user-specific digital storage resource application on a user device; and

determining the first metadata property threshold based on the identity.

6 . The method of claim 1 , wherein the variable metadata properties are determined based on metadata updates performed by an off-chain resource, wherein the metadata updates are provided via an oracle controlled by the off-chain resource.

7 . The method of claim 1 , wherein the non-fungible token comprises dynamically updated metadata.

8 . A method for using non-fungible tokens for blockchain functions, the method comprising:

receiving a first request to perform a blockchain function using a non-fungible token, wherein the non-fungible token is identified by a public key for a user-specific digital storage resource application on a user device;

in response to the first request, retrieving an off-chain metadata property of the non-fungible token, wherein the off-chain metadata property is available from an off-chain resource;

authorizing the blockchain function using a smart contract that compares an on-chain characteristic of the blockchain function to the off-chain metadata property;

in response to authorizing the blockchain function, causing performance of the blockchain function and updating the off-chain metadata property.

9 . The method of claim 8 , wherein retrieving the off-chain metadata property of the non-fungible token further comprises:

executing a first encoded instruction for a first smart contract for the non-fungible token, wherein the first encoded instruction comprises a first automatic response, wherein the first automatic response comprises:

determining a current state of the off-chain metadata property;

determining an off-chain metadata property threshold; and

comparing the current state to the off-chain metadata property threshold.

10 . The method of claim 8 , wherein retrieving the off-chain metadata property of the non-fungible token further comprises:

executing a second encoded instruction for a first smart contract for the non-fungible token, wherein the second encoded instruction comprises a second automatic response, wherein the second automatic response comprises:

determining a smart contract address for retrieving a current state of the off-chain metadata property; and

querying the smart contract address for the current state.

11 . The method of claim 8 , wherein authorizing the blockchain function using the smart contract that compares the on-chain characteristic of the blockchain function to the off-chain metadata property further comprises:

determining a first value of the on-chain characteristic;

determining a second value of an off-chain characteristic; and

determining whether the first value corresponds to the second value.

12 . The method of claim 8 , wherein authorizing the blockchain function using the smart contract that compares the on-chain characteristic of the blockchain function to the off-chain metadata property further comprises:

determining a first type of the on-chain characteristic;

determining a second type of an off-chain characteristic; and

determining whether the first type corresponds to the second type.

13 . The method of claim 8 , wherein authorizing the blockchain function using the smart contract that compares the on-chain characteristic of the blockchain function to the off-chain metadata property further comprises:

determining a first user identity corresponding to the on-chain characteristic;

determining a second user identity of an off-chain characteristic; and

determining whether the first user identity corresponds to the second user identity.

14 . The method of claim 8 , wherein authorizing the blockchain function using the smart contract that compares the on-chain characteristic of the blockchain function to the off-chain metadata property further comprises:

determining a first blockchain protocol corresponding to the on-chain characteristic;

determining a second blockchain protocol of an off-chain characteristic; and

determining whether the first blockchain protocol corresponds to the second blockchain protocol.

15 . A method for using non-fungible tokens for blockchain functions, the method comprising:

receiving, from a user-specific digital storage resource application on a user device, a first user input to perform an off-chain function with a first content provider;

in response to the first user input, determining an off-chain characteristic corresponding to the off-chain function;

receiving a second user input selecting a non-fungible token for satisfying the off-chain characteristic;

in response to the second user input, generating a communication to an off-chain resource identified by the non-fungible token for authorization to perform the off-chain function using the non-fungible token, wherein performing the off-chain function causes an off-chain metadata property for the non-fungible token to be modified;

in response to receiving the authorization to perform the off-chain function, performing a blockchain function corresponding to the off-chain function and a modification of the off-chain metadata property.

16 . The method of claim 15 , wherein performing the blockchain function comprises:

receiving a user approval request to perform a blockchain function corresponding to the off-chain function; and

generating, from the user-specific digital storage resource application on the user device, a confirmation of the blockchain function in response to the user approval request, wherein the confirmation is based on a private key for the user-specific digital storage resource application.

17 . The method of claim 15 , wherein satisfying the off-chain characteristic further comprises:

determining the off-chain metadata property for the non-fungible token to be modified; and

determining a location of the off-chain metadata property.

18 . The method of claim 15 , wherein satisfying the off-chain characteristic further comprises:

retrieving a user profile corresponding to the user-specific digital storage resource application; and

determining, based on the user profile, a first metadata property threshold for a first metadata property of the non-fungible token.

19 . The method of claim 15 , further comprising:

in response to determining the off-chain characteristic corresponding to the off-chain function, determining a plurality of non-fungible tokens for satisfying the off-chain characteristic; and

generating for simultaneous display in a user interface, icons for the plurality of non-fungible tokens for satisfying the off-chain characteristic.

20 . The method of claim 15 , wherein the authorization to perform the off-chain function using the non-fungible token comprises:

determining a first value of the off-chain characteristic;

determining a second value of an on-chain characteristic that corresponds to the first value; and

determining whether the off-chain metadata property corresponds to the on-chain characteristic.

Continuity (2)

References Cited (35)