IP Library Granted Patent US 12,192,385
Granted Patent B1
US 12,192,385 · App. 18/135,620 · Granted Jan 7, 2025

Transferring a domain name on a secondary blockchain market and in the DNS

Inventors: Andrew Kaizer (Arlington, VA); Swapneel Sheth (Fairfax, VA)
Assignee: Verisign, Inc.
H04L9/3297G06F16/22G06F21/31G06Q20/3678H04L9/0869H04L41/08H04L61/302H04L61/3025H04L61/4511G06Q2220/00
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,192,385
App. No.
18/135,620
Granted
Jan 7, 2025
Kind
B1
Abstract

Techniques for transferring registration of a domain name from a first registrant to a second registrant for cryptocurrency in a blockchain network and in the Domain Name System (DNS) are disclosed. The techniques can include receiving a purchase request message comprising the domain name, at least one purchase parameter, and a second registrant network identifier, and sending a purchase instruction message to an executable program on a blockchain for the blockchain network, the purchase instruction message including the domain name and the second registrant network identifier, such that the executable program writes at least the domain name, the second registrant network identifier, and an identifier of a gaining registrar to a deed contract for the domain name and emits an event representing a request to transfer registration of the domain name.

Claims (63)

1. A computer-implemented method comprising:

determining that a domain name is available for re-registration;

sending, based at least in part on the domain name being available for re-registration, a first message to an executable program of a blockchain network that:

configures the executable program to identify the domain name as available for re-registration; and

configures a deed contract associated with the domain name to request information for verifying a first registrant associated with the domain name; and

sending, based at least in part on receiving a request to re-register the domain name, a second message to the executable program that configures the executable program to cause re-registration of the domain name to a second registrant.

2. The computer-implemented method of claim 1 , wherein:

a Domain Name System (DNS) registration of the domain name is to be transferred to a gaining registrar upon re-registration.

3. The computer-implemented method of claim 1 , wherein the first message comprises a network identifier associated with the domain name.

4. The computer-implemented method of claim 3 , wherein the first message further comprises at least one of:

pricing information;

bidding information;

a first blockchain address associated with a registry;

a second blockchain address for an authoritative resolver associated with the domain name; or

identity information associated with the registry.

5. The computer-implemented method of claim 1 , wherein the executable program is a decentralized program with interface accessible via at least one of a website or a web service.

6. The computer-implemented method of claim 1 , wherein the executable program comprises a wallet.

7. The computer-implemented method of claim 1 , further comprising: initiating sending of the first message to the executable program.

8. The computer-implemented method of claim 1 , wherein:

causing the re-registration of the domain name to the second registrant by the executable program comprises:

communicating with the deed contract to associate the domain name with the second registrant, and

emitting a transfer event; and

the computer-implemented method further comprises:

detecting the transfer event;

determining, based on the deed contract, that the first registrant is associated with a first registrar;

receiving, from the first registrar, authorization information associated with the first registrant; and

submitting, to a registry, a request to transferring registration of the domain name, wherein the request comprises the authorization information.

9. A system comprising:

one or more processors; and

one or more non-transitory computer readable media storing computer executable instructions that, when executed, cause the one or more processors to perform operations comprising:

determining that a domain name is available for re-registration;

sending, based at least in part on the domain name being available for re-registration, a first message to an executable program of a blockchain network that:

configures the executable program to identify the domain name as available for re-registration; and

configures a deed contract associated with the domain name to request information for verifying a first registrant associated with the domain name; and

sending, based at least in part on receiving a request to re-register the domain name, a second message to the executable program that configures the executable program to cause re-registration of the domain name to a second registrant.

10. The system of claim 9 , wherein a Domain Name System (DNS) registration of the domain name is to be transferred to a gaining registrar upon re-registration.

11. The system of claim 9 , wherein the first message comprises a network identifier associated with the domain name.

12. The system of claim 11 , wherein the first message further comprises at least one of:

pricing information;

bidding information;

a first blockchain address associated with a registry;

a second blockchain address for an authoritative resolver associated with the domain name; or

identity information associated with the registry.

13. The system of claim 9 , wherein the executable program is a decentralized program with interface accessible via at least one of a website or a web service.

14. The system of claim 9 , wherein the executable program comprises a wallet.

15. The system of claim 9 , the operations further comprising:

initiating sending of the first message to the executable program.

16. One or more non-transitory computer readable media storing computer executable instructions that, when executed, cause one or more processors to perform operations comprising:

determining that a domain name is available for re-registration;

sending, based at least in part on the domain name being available for re-registration, a first message to an executable program of a blockchain network that:

configures the executable program to identify the domain name as available for re-registration; and

configures a deed contract associated with the domain name to request information for verifying a first registrant associated with the domain name; and

sending, based at least in part on receiving a request to re-register the domain name, a second message to the executable program that configures the executable program to cause re-registration of the domain name to a second registrant.

17. The one or more non-transitory computer readable media of claim 16 , wherein:

a Domain Name System (DNS) registration of the domain name is to be transferred to a gaining registrar upon re-registration.

18. The one or more non-transitory computer readable media of claim 16 , wherein the first message comprises a network identifier associated with the domain name.

19. The one or more non-transitory computer readable media of claim 18 , wherein the first message further comprises at least one of:

pricing information;

bidding information;

a first blockchain address associated with a registry;

a second blockchain address for an authoritative resolver associated with the domain name; or

identity information associated with the registry.

20. The one or more non-transitory computer readable media of claim 16 , wherein the executable program is a decentralized program with interface accessible via at least one of a website or a web service.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 17, 2023
From: KAIZER, ANDREW; SHETH, SWAPNEEL
To: VERISIGN, INC.
Reel/Frame 063349/0749 →
Continuity (1)
Continuation 16515825 · Jul 18, 2019
References Cited (97)
US 10721060B1 · Kaizer et al. · 2020 [cited by applicant]
US 11159326B1 · Nelson et al. · 2021 [cited by applicant]
US 11354658B2 · Lyons et al. · 2022 [cited by applicant]
US 11392579B2 · Kasimov et al. · 2022 [cited by applicant]
US 11587071B2 · Ravinathan et al. · 2023 [cited by applicant]
US 11621829B2 · Kaizer et al. · 2023 [cited by applicant]
US 11632236B1 · Kaizer et al. · 2023 [cited by applicant]
US 20050204064A1 · Ruiz · 2005 [cited by applicant]
US 20050216567A1 · Ruiz · 2005 [cited by applicant]
US 20070130316A1 · Turakhia · 2007 [cited by applicant]
US 20070143469A1 · Adams et al. · 2007 [cited by applicant]
US 20080235383A1 · Schneider · 2008 [cited by applicant]
US 20110296440A1 · Aurich et al. · 2011 [cited by applicant]
US 20120011360A1 · Engels et al. · 2012 [cited by applicant]
US 20120174198A1 · Gould et al. · 2012 [cited by applicant]
US 20150278820A1 · Meadows · 2015 [cited by applicant]
US 20160173439A1 · Kaliski, Jr. et al. · 2016 [cited by applicant]
US 20160182490A1 · Gupta et al. · 2016 [cited by applicant]
US 20160196300A1 · Kamdar · 2016 [cited by examiner]
US 20160292672A1 · Fay et al. · 2016 [cited by applicant]
US 20170046689A1 · Lohe et al. · 2017 [cited by applicant]
US 20170180134A1 · King · 2017 [cited by applicant]
US 20170310484A1 · Kaliski, Jr. et al. · 2017 [cited by applicant]
US 20170324738A1 · Hari et al. · 2017 [cited by applicant]
US 20170330174A1 · Demarinis et al. · 2017 [cited by applicant]
US 20170344988A1 · Cusden et al. · 2017 [cited by applicant]
US 20170346833A1 · Zhang · 2017 [cited by applicant]
US 20180227275A1 · Russinovich et al. · 2018 [cited by applicant]
US 20180262493A1 · Andrade · 2018 [cited by applicant]
US 20180276663A1 · Arora · 2018 [cited by applicant]
US 20180287997A1 · Li et al. · 2018 [cited by applicant]
US 20190121988A1 · van de Ruit et al. · 2019 [cited by applicant]
US 20190156040A1 · Sasin et al. · 2019 [cited by applicant]
US 20190166085A1 · Li et al. · 2019 [cited by applicant]
US 20190220831A1 · Rangarajan et al. · 2019 [cited by applicant]
US 20190236571A1 · Arora et al. · 2019 [cited by applicant]
US 20190253252A1 · Qiu · 2019 [cited by applicant]
US 20190333054A1 · Cona · 2019 [cited by examiner]
US 20200021446A1 · Roennow et al. · 2020 [cited by applicant]
US 20200058023A1 · Travizano et al. · 2020 [cited by applicant]
US 20200145373A1 · Richardson · 2020 [cited by applicant]
US 20200314055A1 · Blinn · 2020 [cited by applicant]
US 20200328883A1 · Kaizer et al. · 2020 [cited by applicant]
US 20200382372A1 · Easwar Prasad et al. · 2020 [cited by applicant]
US 20200403809A1 · Chan et al. · 2020 [cited by applicant]
US 20210037013A1 · Salkintzis · 2021 [cited by applicant]
US 20210135867A1 · Zeng et al. · 2021 [cited by applicant]
US 20210243028A1 · Song et al. · 2021 [cited by applicant]
US 20210256622A1 · Hartley et al. · 2021 [cited by applicant]
US 20210385268A1 · Cirillo et al. · 2021 [cited by applicant]
US 20220103370A1 · Alwen et al. · 2022 [cited by applicant]
US 20220173894A1 · Cain, Jr. et al. · 2022 [cited by applicant]
US 20220376889A1 · Kaizer et al. · 2022 [cited by applicant]
US 20220376925A1 · Kaizer et al. · 2022 [cited by applicant]
CN 107705114A · 2018 [cited by applicant]
CN 109981633A · 2019 [cited by applicant]
CN 112671950A · 2021 [cited by applicant]
CN 112765684A · 2021 [cited by applicant]
JP 2021524978A · 2021 [cited by applicant]
WO 2018007828A2 · 2018 [cited by applicant]
WO 2020150741A1 · 2020 [cited by applicant]
WO 2022246189A1 · 2022 [cited by applicant]
WO 2022246193A1 · 2022 [cited by applicant]
US 11,645,370 B1, 05/2023, Kaizer et al. (withdrawn) [cited by applicant]
Baritz et al., ID4me—Technical White Paper Draft, Version 14. Retrieved online at: https://gitlab.com/ID4me/documentation/-/blob/001e297be93ed3f9f0d11e8daf0c4cd019f03377/id4ME%20Technical%20Specification.adoc. 39 pages,… [cited by applicant]
Bertola, IDme, General Overview, Version 1.3. 5 pages, Oct. 6, 2019. [cited by applicant]
Bertola, IDme, Technical overview. Version 1.4, 16 pages, Oct. 4, 2019. [cited by applicant]
Dan.com, Domain Industry, Let US Innovate. Retrieved online at: https://medium.com/undeveloped/domain-industry-join-us-in-becoming-innovative-thriving-again-a751d2e17ae9. 6 pages, Nov. 21, 2017. [cited by applicant]
Domraider, ICO: Whitepaper. Retrieved online at: https://cryptoactu.com/wp-content/uploads/2017/11/DomRaiderICOWhitepaperEN.pdf. 126 pages, May 9, 2017. [cited by applicant]
Einarrson, [DNSOP] Verifying TLD operator authorization. Retrieved online at: https://mailarchive.ietf.org/arch/msg/dnsop/qaDjnArp98TOgIBYQbUfswwaxrg. 1 page, Jun. 2019. [cited by applicant]
Hollenbeck, Extensible Provisioning Protocol (EPP) Domain Name Mapping. Network Working Group. 46 pages, May 2007. [cited by applicant]
Hollenbeck, Extensible Provisioning Protocol (EPP). Network Working Group. 67 pages, Aug. 2009. [cited by applicant]
Hollenbeck, Security Services for the Registration Data Access Protocol (RDAP). Network Working Group. 13 pages, Mar. 2015. [cited by applicant]
Johnson, [DNSOP] Verifying TLD operator authorization. Retrieved online at: https://mailarchive.ieft.org/arch/msg/dnsop/AXfD3cqSTWF69pAWqu5Pn6SGXDs. 1 page, Jun. 2019. [cited by applicant]
Johnson, ENS Root Change Will Allow Easy Integration of More Than 1300 TLDs. Retrieved online at: https://weka.medium.com/upcoming-changes-to-the-ens-root-a1b78fd52b38. 4 pages, Feb. 25, 2019. [cited by applicant]
Johnson, How to claim your DNS domain on ENS. Retrieved online at: https://medium.com/the-ethereum-name-service/how-to-claim-your-dns-domain-on-ens-e600ef2d92ca. 4 pages, Nov. 11, 2017. [cited by applicant]
Johnson, Introducing .luxe on ENS. Retrieved online at: https://weka.medium.com/introducing-luxe-on-ens-35a9ee2383ce. 4 pages, Oct. 2, 2018. [cited by applicant]
Kuhl, [DNSOP] Verifying TLD operator authorisation. Retrieved online at: https://mailarchive.ietf.org/arch.msg/dnsop/DQEjRQZAafeGoMckNTI5GxSTe9g. 1 page, Jun. 2019. [cited by applicant]
Millegan, ENS+ .KRED: Major Integration of DNS and ENS Launches. Ethereum Name Service. https://medium.com/@brantly.eth/ens-kred-major-integration-of-dns-and-ens-launches-e7efb4dd872a. 3 pages, Feb. 19, 2020. [cited by applicant]
Millegan, Ethereum Name Service. Retrieved online at: https://vir.isi.edu/events/dinr2020/S/blantly-ENS.pdf. 24 pages, retrieved Sep. 7, 2021. [cited by applicant]
Millegan, Linking DNS with blockchain-based ENS records. Retrieved online at: https://conso.icann.org/sites/default/files/field-attached/presentation-dns-blockchain-ens-24jun19-en.pdf. 31 pages, retrieved Sep. 7, 2021. [cited by applicant]
Monster, Domain Leasing: How we do it at Epik, and how you can too! epik, EPIK.com. 14 pages, Mar. 27, 2020. [cited by applicant]
Moosavi, Rethinking Certificate Authorities: Understanding and decentralizing domain validation. A thesis in the Concordia Institute for Information Systems Engineering, Presented in Partial Fulfillment of the Requireme… [cited by applicant]
Tarasov, Internet Voting Using Zcash. Thesis, Presented to the University of Dublin, Trinity College in fulfillment of the requirements for the Degree od Master of Computer Science. 89 pages, May 2017. [cited by applicant]
Verisign Technical Note, Ethereum Name Service (ENS) Root Change Issues. VeriSign, Inc., 2 pages, Apr. 12, 2019. [cited by applicant]
Verisign, Inc., DNS Registrar guide. Ethereum Name Service. Retrieved online at: https://docs.ens.domains/dns-registrar-guide. 2 pages, retrieved Sep. 22, 2021. [cited by applicant]
International Preliminary Report on Patentability for Application No. PCT/US2019/038447, dated Jan. 7, 2021, 13 pages. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2019/038447, dated Sep. 30, 2019, 15 pages. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2022/030241, dated Oct. 6, 2022, 8 pages. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2022/030248, dated Oct. 6, 2022, 6 pages. [cited by applicant]
US Final Office Action for U.S. Appl. No. 16/402,047, dated May 11, 2021, 9 pages. [cited by applicant]
US Final Office Action for U.S. Appl. No. 16/515,825, dated Sep. 20, 2021, 19 pages. [cited by applicant]
US Non-Final Office Action for U.S. Appl. No. 16/402,047, dated Aug. 9, 2021, 10 pages. [cited by applicant]
US Non-Final Office Action for U.S. Appl. No. 16/402,047, dated Feb. 1, 2021, 14 pages. [cited by applicant]
US Non-Final Office Action for U.S. Appl. No. 16/515,825, dated Apr. 15, 2021, 14 pages. [cited by applicant]
US Notice of Allowance for U.S. Appl. No. 16/024,488, dated Mar. 13, 2020, 30 pages. [cited by applicant]
US Notice of Allowance for U.S. Appl. No. 17/325,687, dated Apr. 17, 2023, 25 pages. [cited by applicant]