# US 12,002,035 B2 · Metaverse authentication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,002,035 B2
- Document ID: US12002035B2
- Status: Granted
- Kind: B2
- Application number: 17/657,331
- Filed: 2022-03-30
- Published: 2023-10-05
- Granted: 2024-06-04
- Earliest claimed: 2022-03-30
- Assignees: American Express Travel Related Services Company, Inc.
- Applicants: American Express Travel Related Services Company, Inc.
- Inventors: Alaric M. Eby; Andras L Ferenczi
- Web page: https://patentgrep.com/patent/US12002035B2

## CPC

- G06Q 20/3674: {involving authentication}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06Q 20/065: {using e-cash}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3271: {using challenge-response}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed are various embodiments for metaverse authentication using NFTs. An authentication setup request for an NFT can be received from an owner of the NFT. Then, a unique authentication credential for the NFT can be requested from an NFT smart contract. In response, URL of an edge wallet associated with an owner of the unique authentication credential is received. Then, a request can be sent to the URI of the edge wallet for the unique authentication credential. In response, a signed challenge is received from the edge wallet and a public key is retrieved from the NFT. A signature of the signed challenge is determined to be valid based at least in part on the public key, and access to an asset or resource is configured based at least in part on the signature of the signed challenge being valid.

## Claims

### Claim 1

A system, comprising:
a computing device comprising a processor and a memory; and
machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:
receive an authentication request for a non-fungible token (NFT) from an NFT smart contract;
request a unique authentication credential for the NFT from the NFT smart contract;
receive a uniform resource identifier (URI) of an edge wallet associated with an owner of the unique authentication credential from the NFT smart contract;
send a request to the URI of the edge wallet for the unique authentication credential;
receive a signed challenge from the edge wallet;
retrieve a public key from the NFT;
determine that a signature of the signed challenge is valid based at least in part on the public key; and
grant access to an asset or resource based at least in part on the signature of the signed challenge being valid.

### Claim 2 (depends on 1)

The system of claim 1, wherein the signed challenge comprises the public key and the machine-readable instructions, when further executed, cause the computing device to at least:
determine that the public key of the signed challenge matches the public key from the NFT; and
access is granted to the NFT in response to the public key of the signed challenge matching the public key retrieved from the NFT.

### Claim 3 (depends on 1)

The system of claim 1, wherein the public key complies with the Boneh-Lynn-Shacham (BLS) signature scheme.

### Claim 4 (depends on 1)

The system of claim 1, wherein the authentication request is received from a client application executing on a client device that is attempting to access the asset.

### Claim 5 (depends on 1)

The system of claim 1, wherein the signed challenge is received from the edge wallet in response to the edge wallet receiving approval of the owner of the NFT.

### Claim 6 (depends on 1)

The system of claim 1, wherein the edge wallet represents a service that can hold or store sensitive or private date on behalf of a user of a blockchain network.

### Claim 7 (depends on 1)

The system of claim 1, wherein the machine-readable instructions are a component of a smart contract stored on a blockchain network.

### Claim 8

A method, comprising:
receiving an authentication setup request for a non-fungible token (NFT) from an NFT smart contract;
requesting a unique authentication credential for the NFT from the NFT smart contract;
receiving a uniform resource identifier (URI) of an edge wallet associated with an owner of the unique authentication credential from the NFT smart contract;
sending a request to the URI of the edge wallet for the unique authentication credential;
receiving a signed challenge from the edge wallet;
retrieving a public key from the NFT;
determining that a signature of the signed challenge is valid based at least in part on the public key; and
configuring access to an asset or resource based at least in part on the signature of the signed challenge being valid.

### Claim 9 (depends on 8)

The method of claim 8, wherein the signed challenge comprises the public key and the method further comprises:
determine that the public key of the signed challenge matches the public key from the NFT; and
access is limited to the asset in response to the public key of the signed challenge matching the public key retrieved from the NFT.

### Claim 10 (depends on 8)

The method of claim 8, wherein granting access to the asset further comprises recording that the NFT can be used to authenticate the owner.

### Claim 11 (depends on 8)

The method of claim 8, wherein the signed challenge is received from the edge wallet in response to the edge wallet receiving approval of the owner of the NFT.

### Claim 12 (depends on 8)

The method of claim 8, wherein the edge wallet represents a service that can hold or store sensitive or private date on behalf of a user of a blockchain network.

### Claim 13 (depends on 8)

The method of claim 8, wherein the method is performed with a smart contract stored on a blockchain network.

### Claim 14 (depends on 8)

The method of claim 8, wherein the public key complies with the Boneh-Lynn-Shacham (BLS) signature scheme.

### Claim 15

A system, comprising:
a computing device comprising a processor and a memory; and
machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:
receive an authentication setup request for a non-fungible token (NFT) from an NFT smart contract;
request a unique authentication credential for the NFT from the NFT smart contract;
receive a uniform resource identifier (URI) of an edge wallet associated with an owner of the unique authentication credential from the NFT smart contract;
send a request to the URI of the edge wallet for the unique authentication credential;
receive a signed challenge from the edge wallet;
retrieve a public key from the NFT;
determine that a signature of the signed challenge is valid based at least in part on the public key; and
configure access to an asset or resource based at least in part on the signature of the signed challenge being valid.

### Claim 16 (depends on 15)

The system of claim 15, wherein the signed challenge comprises the public key and the machine-readable instructions, when executed, further cause the computing device to at least:
determine that the public key of the signed challenge matches the public key from the NFT; and
access is limited to the asset in response to the public key of the signed challenge matching the public key retrieved from the NFT.

### Claim 17 (depends on 15)

The system of claim 15, wherein the machine-readable instructions that cause the computing device to grant access to the asset further cause the computing device to record that the NFT can be used to authenticate the owner of the NFT.

### Claim 18 (depends on 15)

The system of claim 15, wherein the signed challenge is received from the edge wallet in response to the edge wallet receiving approval of the owner of the NFT.

### Claim 19 (depends on 15)

The system of claim 15, wherein the edge wallet represents a service that can hold or store sensitive or private date on behalf of a user of a blockchain network.

### Claim 20 (depends on 15)

The system of claim 15, wherein the public key complies with the Boneh-Lynn-Shacham (BLS) signature scheme.