IP Library › Granted Patent US 12,256,028
Granted Patent B2
US 12,256,028 · App. 17/851,446 · Granted Mar 18, 2025

Cross chain access granting to applications

Inventors: Aaron Quirk (Raleigh, NC); Braden River Pezeshki (Reno, NV); Lisa Seacat DeLuca (Bozeman, MT)
Assignee: Unstoppable Domains, Inc.
H04L9/50H04L9/3239H04L9/3247
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,256,028
App. No.
17/851,446
Granted
Mar 18, 2025
Kind
B2
Abstract

According to a present invention embodiment, a system for granting access to applications associated with different blockchains comprises one or more memories and at least one processor coupled to the one or more memories. The system verifies a non-fungible token of a first blockchain is owned by a user. The non-fungible token is indicated by the user for access to an application associated with a second blockchain. Information for the second blockchain is retrieved from information for different blockchains associated with the non-fungible token. A blockchain address of the second blockchain is verified as being associated with the user based on the information for the second blockchain to grant access to the application. Embodiments of the present invention further include a method and computer program product for granting access to applications associated with different blockchains in substantially the same manner described above.

Claims (65)

1. A method of granting access to applications associated with different blockchains comprising:

receiving, via at least one processor, a non-fungible token of a first blockchain indicated by a user as a login credential for an application associated with a different second blockchain;

verifying, via the at least one processor, the non-fungible token is owned by the user;

retrieving, via the at least one processor, information for the different second blockchain from information for different blockchains stored in association with the non-fungible token; and

verifying, via the at least one processor, a blockchain address of the different second blockchain is associated with the user based on the information for the different second blockchain to grant access to the application based on the non-fungible token of the first blockchain.

2. The method of claim 1 , wherein the non-fungible token corresponds to a blockchain domain name.

3. The method of claim 1 , wherein verifying the non-fungible token comprises:

sending a message to a blockchain address of the first blockchain associated with the non-fungible token; and

detecting signing of the message by the user.

4. The method of claim 1 , further comprising:

verifying, via the at least one processor, the blockchain address of the different second blockchain is associated with the user based on the user signing a message; and

storing, via the at least one processor, information pertaining to verification of the blockchain address of the different second blockchain, wherein the information pertaining to verification is associated with the non-fungible token.

5. The method of claim 4 , wherein the information pertaining to verification is stored on the first blockchain.

6. The method of claim 4 , wherein verifying the blockchain address of the different second blockchain comprises:

sending the message to the blockchain address of the different second blockchain; and

detecting signing of the message by the user.

7. The method of claim 6 , wherein the information pertaining to verification includes the message signed by the user and the blockchain address of the different second blockchain, and verifying the blockchain address of the different second blockchain based on the information for the different second blockchain comprises:

decoding the signed message based on the blockchain address of the different second blockchain to determine content of the signed message; and

determining that the content of the signed message matches content of the message and indicates the non-fungible token and a blockchain address of the first blockchain associated with the non-fungible token.

8. The method of claim 1 , further comprising:

granting access to the application, via the at least one processor, in response to verifying the blockchain address for the different second blockchain based on the information for the different second blockchain, wherein the blockchain address of the different second blockchain is used as a login credential for the application.

9. A system for granting access to applications associated with different blockchains comprising:

one or more memories; and

at least one processor coupled to the one or more memories, the at least one processor configured to:

receive a non-fungible token of a first blockchain indicated by a user as a login credential for an application associated with a different second blockchain;

verify the non-fungible token is owned by the user;

retrieve information for the different second blockchain from information for different blockchains stored in association with the non-fungible token; and

verify a blockchain address of the different second blockchain is associated with the user based on the information for the different second blockchain to grant access to the application based on the non-fungible token of the first blockchain.

10. The system of claim 9 , wherein the non-fungible token corresponds to a blockchain domain name.

11. The system of claim 9 , wherein verifying the non-fungible token comprises:

sending a message to a blockchain address of the first blockchain associated with the non-fungible token; and

detecting signing of the message by the user.

12. The system of claim 9 , wherein the at least one processor is further configured to:

verify the blockchain address of the different second blockchain is associated with the user based on the user signing a message; and

store information pertaining to verification of the blockchain address of the different second blockchain, wherein the information pertaining to verification is associated with the non-fungible token.

13. The system of claim 12 , wherein the information pertaining to verification is stored on the first blockchain.

14. The system of claim 12 , wherein verifying the blockchain address of the different second blockchain comprises:

sending the message to the blockchain address of the different second blockchain; and

detecting signing of the message by the user.

15. The system of claim 14 , wherein the information pertaining to verification includes the message signed by the user and the blockchain address of the different second blockchain, and verifying the blockchain address of the different second blockchain based on the information for the different second blockchain comprises:

decoding the signed message based on the blockchain address of the different second blockchain to determine content of the signed message; and

determining that the content of the signed message matches content of the message and indicates the non-fungible token and a blockchain address of the first blockchain associated with the non-fungible token.

16. The system of claim 9 , wherein the at least one processor is further configured to:

grant access to the application in response to verifying the blockchain address for the different second blockchain based on the information for the different second blockchain, wherein the blockchain address of the different second blockchain is used as a login credential for the application.

17. A computer program product for granting access to applications associated with different blockchains, the computer program product comprising one or more computer readable media having instructions stored thereon, the instructions executable by at least one processor to cause the at least one processor to:

receive a non-fungible token of a first blockchain indicated by a user as a login credential for an application associated with a different second blockchain;

verify the non-fungible token is owned by the user;

retrieve information for the different second blockchain from information for different blockchains stored in association with the non-fungible token; and

verify a blockchain address of the different second blockchain is associated with the user based on the information for the different second blockchain to grant access to the application based on the non-fungible token of the first blockchain.

18. The computer program product of claim 17 , wherein the non-fungible token corresponds to a blockchain domain name.

19. The computer program product of claim 17 , wherein verifying the non-fungible token comprises:

sending a message to a blockchain address of the first blockchain associated with the non-fungible token; and

detecting signing of the message by the user.

20. The computer program product of claim 17 , wherein the instructions executable by the at least one processor further cause the at least one processor to:

verify the blockchain address of the different second blockchain is associated with the user based on the user signing a message; and

store information pertaining to verification of the blockchain address of the different second blockchain, wherein the information pertaining to verification is associated with the non-fungible token.

21. The computer program product of claim 20 , wherein the information pertaining to verification is stored on the first blockchain.

22. The computer program product of claim 20 , wherein verifying the blockchain address of the different second blockchain comprises:

sending the message to the blockchain address of the different second blockchain; and

detecting signing of the message by the user.

23. The computer program product of claim 22 , wherein the information pertaining to verification includes the message signed by the user and the blockchain address of the different second blockchain, and verifying the blockchain address of the different second blockchain based on the information for the different second blockchain comprises:

decoding the signed message based on the blockchain address of the different second blockchain to determine content of the signed message; and

determining that the content of the signed message matches content of the message and indicates the non-fungible token and a blockchain address of the first blockchain associated with the non-fungible token.

24. The computer program product of claim 17 , wherein the instructions executable by the at least one processor cause the at least one processor to:

grant access to the application in response to verifying the blockchain address for the different second blockchain based on the information for the different second blockchain, wherein the blockchain address of the different second blockchain is used as a login credential for the application.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 28, 2022
From: QUIRK, AARON; PEZESHKI, BRADEN RIVER; DELUCA, LISA SEACAT
To: UNSTOPPABLE DOMAINS, INC.
Reel/Frame 060337/0287 →
Continuity (1)
Related Publication 20230421399A1 · Dec 28, 2023
References Cited (56)
US 9553981B2 · Czarnecki et al. · 2017 [cited by applicant]
US 10846762B1 · Dennis et al. · 2020 [cited by applicant]
US 11558344B1 · Pezeshki et al. · 2023 [cited by applicant]
US 11750570B1 · Eby et al. · 2023 [cited by applicant]
US 11902444B2 · Kurian · 2024 [cited by examiner]
US 12010240B2 · Advani · 2024 [cited by examiner]
US 20150356523A1 · Madden · 2015 [cited by applicant]
US 20160217436A1 · Brama · 2016 [cited by applicant]
US 20160330027A1 · Ebrahimi · 2016 [cited by applicant]
US 20190096021A1 · Jarvis et al. · 2019 [cited by applicant]
US 20200364703A1 · Joveski · 2020 [cited by examiner]
US 20200406859A1 · Hassani · 2020 [cited by applicant]
US 20210058353A1 · Creech et al. · 2021 [cited by applicant]
US 20220198049A1 · Dumas et al. · 2022 [cited by applicant]
US 20220198444A1 · Mee et al. · 2022 [cited by applicant]
US 20230108983A1 · Vosseller · 2023 [cited by examiner]
US 20230171225A1 · Pezeshki et al. · 2023 [cited by applicant]
US 20230206216A1 · Lehmann · 2023 [cited by examiner]
US 20230291575A1 · Riva · 2023 [cited by examiner]
US 20230418979A1 · DeLuca et al. · 2023 [cited by applicant]
US 20240056525A1 · DeLuca · 2024 [cited by applicant]
US 20240146523A1 · DeLuca et al. · 2024 [cited by applicant]
CN 1984185A · 2007 [cited by applicant]
KR 20210111066A · 2021 [cited by examiner]
WO 2020010023A1 · 2020 [cited by applicant]
International Search Report and Written Opinion in International Application No. PCT/US23/68858, dated Oct. 19, 2023, 8 pages. [cited by applicant]
“Allowlists, denylists, and approved senders”, Google Workspace Admin Help, https://support.google.com/a/answer/60752?hl=en#:˜:text=Email allowlist-A list of,allowlist the contact's IP address 1, downloaded from the int… [cited by applicant]
“S/MIME Digital Signatures”, GlobalCerts, https://globalcerts.com/smime-digital-signatures, downloaded from the internet on Oct. 31, 2022, 5 pages. [cited by applicant]
Blog, “Introducing Humanity Check—100% Opt-In”, Unstoppable Domains, https://unstoppabledomains.com/blog/introducing-humanity-check, Mar. 13, 2022, downloaded from the internet on Mar. 25, 2022, 8 pages. [cited by applicant]
Antoni Zolciak, “Beyond KYC: Stricter Privacy Policies are Looming, But DeFi is Here to Stay”, https://www.nasdaq.com/articles/beyond-kyc%3A-stricter-privacy-policies-are-looming-but-defi-is-here-to-stay, Dec. 8, 2021, … [cited by applicant]
“Humanity Check Overview”, https://docs.unstoppabledomains.com/login-with-unstoppable/humanity-check/humanity-check-for-login/, downloaded from the internet on Apr. 7, 2022, 5 pages. [cited by applicant]
“Progressive risk segmentation: your secret to balancing fraud prevention and conversion”, https://withpersona.com, downloaded from the internet on Apr. 1, 2022, 7 pages. [cited by applicant]
Jennifer Lowe, “What is KYC and why does it matter?”, Plaid.com, Aug. 12, 2021, 15 pages. [cited by applicant]
Alex Gomez, “Unstoppable Domains Email (What Is it and How Does it Work?)”, Cyber Scrilla, https://cyberscrilla.com/unstoppable-domains-email/#:˜:text=How, Sep. 1, 2022, 43 pages. [cited by applicant]
Adriel Estrada, “Introducing Unstoppable Email with Skiff”, Unstoppable Domains, https://unstoppabledomains.com/blog/categories/announcements/article/unstoppable-email-skiff, Aug. 30, 2022, 7 pages. [cited by applicant]
“ERC: Claim Holder—Issue #735”, https://github.com/ethereum/eips/issues/735, GitHub, ethereum/EIPs, downloaded from the internet on Oct. 14, 2022, 21 pages. [cited by applicant]
“LIPs/LSPs/LSP-6-KeyManager.md”, GitHub, lukso-network/LIPS, https://github.com/lukso-network/LIPs/blob/main/LSPs/LSP-6-KeyManager.md, downloaded from the internet on Oct. 14, 2022, 13 pages. [cited by applicant]
International Search Report and Written Opinion in International Application No. PCT/US23/71399, dated Nov. 16, 2023, 10 pages. [cited by applicant]
“DNS records for unstoppabledomains.com”, Unstoppable Domains, https://www.nslookup.io/domains/unstoppabledomains.com/dns-records/, downloaded from the internet on Nov. 16, 2023, 5 pages. [cited by applicant]
“Why Are Some Domains Protected?”, Unstoppable Domains, Mar. 11, 2022, https://support.unstoppabledomains.com/support/solutions/articles/48001186091-why-are-some-domains-protected, 3 pages. [cited by applicant]
Wikipedia, “Blockchain”, https://en.wikipedia.org/wiki/Blockchain, downloaded from the internet on Mar. 25, 2022, 27 pages. [cited by applicant]
“How does a transaction get into the blockchain?”, Euromoney Learning, https://www.euromoney.com/learning/blockchain-explained/how-transactions-get-into-the-blockchain, downloaded from the internet on Mar. 25, 2022, 9 p… [cited by applicant]
Benjamin Powers, “Brave Integrates Crypto Blockchain Domains, Expanding Access to Web 3.0—CoinDesk”, https://www.coindesk.com/tech/2021/05/13/brave-integrates-crypto-blockchain-domains-expanding-access-to-web-30/, May 1… [cited by applicant]
“What is a non-fungible token (NFT)?”, https://www.coinbase.com/learn/crypto-basics/plp-what-is-nft, downloaded from the internet on Mar. 25, 2022, 10 pages. [cited by applicant]
Michele D'Aliessi, “How Does the Blockchain Work? A Guide to Everything You Need to Know”, OneZero, https://onezero.medium.com/how-does-the-blockchain-work-98c8cd01d2ae, Jun. 1, 2016, 21 pages. [cited by applicant]
James Beck, Blog, “Mirror.xyz Review: How to Use MetaMask to Compete in the $WRITE Race”, Jul. 30, 2021, https://consensys.net/blog/metamask/mirror-xyz-review-how-to-use-metamask-to-compete-in-the-write-race, 14 pages. [cited by applicant]
Amaury Martiny, “One-click Login with Blockchain: a MetaMask Tutorial”, https://www.toptal.com/ethereum/one-click-login-flows-a-metamask-tutorial, downloaded from the internet on Mar. 25, 2022, 16 pages. [cited by applicant]
“Introducing Blend: the Peer-to-Peer Perpetual Lending Protocol for NFT's”, https://x.com/blur_io/status/1653051809240604674?s=20, downloaded from the internet Jun. 26, 2024, 2 pages. [cited by applicant]
Owen Fernau, “Blur Launches NFT Lending Protocol”, The Defiant, https://thedefiant.io/news/nfts-and-web3/blur-nft-lending, May 2, 2023, 7 pages. [cited by applicant]
“Unstoppable Domains launches Login with Unstoppable”, https://unstoppabledomains.com/blog/introducing-login-with-unstoppable, Jan. 9, 2022, 7 pages. [cited by applicant]
Jeff Benson, “You Can Now Use Your .com Domain to Send and Receive Ethereum”, https://decrypt.co/79517/you-can-now-use-your-com-domain-send-receive-ethereum Decrypt, Aug. 26, 2021, 8 pages. [cited by applicant]
“Claim your DNS name onchain in ENS”, ENS, https://support.ens.domains/en/articles/7882690-claim-your-dns-name, downloaded from the internet on Feb. 9, 2024, 10 pages. [cited by applicant]
“Ethereum Name Service (ENS)”, https://etherscan.io/token/0xc18360217d8f7ab5e7c516566761ea12ce7f9d72#readContract, downloaded from the internet on Feb. 9, 2024, 4 pages. [cited by applicant]
“Ethereum Name Service (ENS)”, https://etherscan.io/token/0xc18360217d8f7ab5e7c516566761ea12ce7f9d72#writeContract, downloaded from the internet on Feb. 9, 2024, 2 pages. [cited by applicant]
“Unstoppable Domains (UD)”, https://polygonscan.com/token/0xa9a6a3626993d487d2dbda3173cf58ca1a9d9e9f#readProxyContract, downloaded from the internet on Feb. 9, 2024, 3 pages. [cited by applicant]
“Unstoppable Domains (UD)”, https://polygonscan.com/token/0xa9a6a3626993d487d2dbda3173cf58ca1a9d9e9f#writeProxyContract, downloaded from the internet on Feb. 9, 2024, 3 pages. [cited by applicant]