Determining consensus in a decentralized domain name system

A method for determining consensus in a decentralized domain name system, comprising:

• A. forming a consortium blockchain network that includes a plurality of domain network computer nodes and selecting a plurality of committee member computer nodes from the plurality of domain network computer nodes, wherein
• each committee member computer node, selected from the plurality of domain network computer nodes, is located within a different second level domain name system in the decentralized domain name system, and wherein
• each second level domain name system shares distributed databases with one or more other second level domain name systems, but is operated and managed independently from the one or more other second level domain name systems;
• B. generating, by the committee member computer node, which receives the most votes from other consortium member computer nodes, a genesis block of the consortium blockchain network and randomly selecting, by the committee member computer node, a first housekeeper computer node from among all housekeeper computer nodes which are on-duty during a first duty cycle, wherein
• consortium member computer nodes consist of one or more committee member computer nodes and one or more housekeeper computer nodes;
• C. generating, by the first housekeeper computer node, a first block of the first duty cycle and randomly selecting, by the first housekeeper computer node, a next housekeeper computer node from among the housekeeper computer nodes which are on-duty during the first duty cycle;
• determining (1) that the first block, which differs from the genesis block, is verified and signed by more than half of the committee member computer nodes;
• and
• responsive to the determining (1), adding the first block to the consortium blockchain network;
• D. generating, by one or more of the housekeeper computer nodes which are on-duty during the first duty cycle, one or more next blocks and randomly selecting, by the one or more housekeeper computer nodes which are on-duty during the first duty cycle, one or more next housekeeper computer nodes from among the housekeeper computer nodes which are on-duty during the first duty cycle, including:
• determining (2) that a next block, in the one or more next blocks, is not verified and signed by more than half of the committee member computer nodes or (3) that the next block is not generated within a predefined time period,
• responsive to the determining (2) or (3), generating, by a different housekeeper computer node which is randomly selected from among the housekeeper computer nodes which are on-duty during the first duty cycle, the next block again;
• E. generating, by the last housekeeper computer node selected during the first duty cycle, a first block of a second duty cycle, and repeating Step C to Step E to generate blocks in the second duty cycle, wherein
• generating a first block in each duty cycle includes:
• storing information identifying all housekeeper computer nodes which are on-duty in that duty cycle in the first block generated during that duty cycle.