WO2018176406A1 - 一种基于联盟链的顶级域名管理方法及系统 - Google Patents
一种基于联盟链的顶级域名管理方法及系统 Download PDFInfo
- Publication number
- WO2018176406A1 WO2018176406A1 PCT/CN2017/079098 CN2017079098W WO2018176406A1 WO 2018176406 A1 WO2018176406 A1 WO 2018176406A1 CN 2017079098 W CN2017079098 W CN 2017079098W WO 2018176406 A1 WO2018176406 A1 WO 2018176406A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- domain name
- tld
- network
- level domain
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3015—Name registration, generation or assignment
- H04L61/302—Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3005—Mechanisms for avoiding name conflicts
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
Definitions
- the invention belongs to the field of Internet technology improvement, and in particular relates to a method and system for managing a top-level domain name based on a coalition chain.
- the name plays an important role in all computer systems. They are used to share resources, uniquely identify entities, point to locations, and more. An important result of naming is that the name can be resolved to the entity it points to. Thus, name resolution allows processes to access named entities. To resolve the name, you need to implement a naming system. The difference between naming in distributed systems and naming in non-distributed systems is the way the naming system is implemented. Many of today's applications, such as partial file systems and the World Wide Web name system, are based on distributed naming schemes. Both today's Internet and future new networks require a structured naming scheme based on distributed systems to resolve the various entities involved in the network.
- the domain name system is a naming system used by the Internet to convert the name of a machine that is convenient for people to use as an IP address, and uses a hierarchical structured naming scheme in which the domain name is the highest except the root domain name. For the top level domain.
- DNS domain name system
- RFC 1034, 1035 The DNS namespace uses a hierarchical tree-like naming scheme and uses humans to easily remember and understand the name mapping to an IP address with a fixed length of 32 bits (or 128 bits for a fixed length if it is an IPv6 address).
- any host or router has a unique hierarchical name, the domain Name (domain name).
- domain name is a manageable partition in the namespace, the domain can be divided into subdomains, and the subdomains can continue to be divided, thus forming top-level domains, second-level domains, tertiary domains, and so on. Each domain name is separated by a dot.
- the Internet's domain name system is an online distributed database system that uses a client-server approach.
- DNS allows most names to be parsed locally. Only a small amount of resolution needs to communicate over the Internet. Therefore, the DNS system is highly efficient and has a single computer. If the node fails, it will not hinder the normal operation of the entire DNS system.
- the name server program is usually run on a domain name server for domain name to IP address resolution.
- an application process needs to resolve the host name to an IP address, the application process invokes the resolver and becomes a client of the DNS.
- the domain name to be resolved is placed in the DNS request packet and sent as a UDP user datagram. Give the local domain name server. After the local domain name server searches for the domain name, the corresponding IP address is returned in the response message.
- the application process can obtain communication after obtaining the IP address of the destination host. If the local domain name server cannot answer the request, the domain name server temporarily becomes another client in the DNS and issues a query request to other domain name servers.
- Domain names at all levels are managed by their upper-level domain name management agencies, and the highest top-level domain name chain is managed by ICANN, which makes DNS management centralized. Any company or organization that needs to apply for a top-level domain must apply to ICANN.
- Domain name servers on the Internet are also arranged hierarchically. Each domain name server only has jurisdiction over a part of the domain name system, so it can be divided into four different types of servers: root domain name server, top-level domain name server, rights name server and local. Domain name server. When a local domain name server cannot resolve a domain name, it first needs to ask for the root domain name service. Device. However, the distribution of root domain name servers around the world is unreasonable. Take the data of 2012 as an example. In North America, an average of 3.75 million Internet users can be allocated to one root name server, while in Asia, an average of more than 20 million Internet users.
- Blockstack is a decentralized DNS system that implements an open source system based on the Bitcoin blockchain. It combines DNS functionality with a public key infrastructure, primarily for new blockchain applications. Blockstack separates the name registration, the name owner, and the name-related data by separating the control and data layers.
- the control layer includes a blockchain layer and a virtual chain layer, and the data layer is divided into a routing layer and a storage layer, so the system architecture of Blockstack is actually composed of four layers.
- the blockchain layer occupies the lowest layer, stores a series of operations of Blockstack, and provides the order consistency of these operations. Blockstack currently uses the bitcoin blockchain as the blockchain layer.
- the virtual chain layer defines its own protocol on the blockchain layer, and only the transaction records that the Blockstack system software can perceive.
- the routing layer is responsible for mapping the names defined by the control layer to the files that actually store the data, avoiding the system from adopting any specific storage service from the beginning, thereby allowing multiple storage vendors to provide services.
- the top layer is the storage layer, which stores the actual "name-value" pair of data, including large amounts of data.
- Blockstack adopts a hierarchical structure, which does not affect the normal operation of other levels when there is a problem or upgrade in a certain level, and reduces the amount of data transmitted by the control layer.
- Blockstack built a global naming system based on Namecoin's name operation, and proposed the concept of virtual chain, which makes the system more scalable.
- Blockstack A simplified name verification protocol based on consistent hashing is also used to accelerate node verification and the addition of new nodes.
- Blockstack is difficult to be compatible with existing DNS systems.
- the DNS system of the Internet adopts a hierarchical domain name structure, and the hierarchical structure of the domain name server is also arranged according to the hierarchy. But Blockstack does not use a hierarchical domain name structure, and there is no hierarchical relationship between domain names.
- Blockstack's completely decentralized design makes the system difficult to monitor. Although Blockstack allows users to apply for domain names freely, without any agency restrictions and regulations, such a structure will generate many unprotected "zombie" domain names, which can become a hotbed of crime in extreme cases, because you can't know which one. The user holds the private key corresponding to the domain name.
- the top-level domain name is considered to be a true corporate network trademark, which is an important part of the development of corporate brand strategy strategy. Blockstack abandoned the design concept of the existing DNS, and the top-level domain name was introduced at will, making the meaning of the top-level domain name no longer exist.
- the object of the present invention is to provide a method for managing a top-level domain name based on a federation chain, which aims to solve the above technical problem.
- the present invention is implemented in this way, a method for managing a top-level domain name based on a federation chain, and the method for managing a top-level domain name includes the following steps:
- the newly added TLD node may send a message for registering a new authentication node to any node in the TLD network;
- the node that joins the received new node to the message wants all nodes to broadcast the authentication message
- the node in the network selects or opposes the newly joined node according to its own rules and broadcasts the agreed or dissenting information to the remaining nodes;
- each TLD node independently checks each domain name operation according to its own criteria
- C2 randomly selecting a node from the network composed of TLD nodes as a billing node in a preset time;
- TLD node Use the selected TLD node to package the valid domain name operation in the preset time into the block, and broadcast to other TLD nodes and update the TLD database.
- the system architecture is layered into an upper layer and an upper layer, wherein the bottom layer is a blockchain embedded with a domain name operation, and the upper layer is a data layer formed by top-level domain name related data.
- a further technical solution of the present invention is that the TLD node updates the TLD database by processing a series of top-level domain operations in the data layer, and writes all operations to the underlying blockchain at the same time.
- the preset time is 5 minutes.
- Another object of the present invention is to provide a blockchain-based top-level domain name management system, the top-level domain name management system including:
- a separation module for layering a system architecture in an alliance network to separate operations and data
- a node consistency module is used to make nodes in the federation network consistent through a consensus process.
- the newly registered node information sending unit configured to newly join the TLD node, can send a message for registering a new authentication node to any node in the TLD network;
- a broadcast authentication message unit wherein the node that adds the received new node to the message wants all nodes to broadcast the authentication message
- a network node feedback unit configured by the node in the network to agree or oppose the newly joined node according to its own rules and broadcast the agreed or dissenting information to the remaining nodes;
- the network will agree that the node joins and records the message of the node.
- the consensus process of the alliance network node in the node consistency module includes:
- Standard verification unit for each TLD node to independently verify each domain name operation according to its own standards
- a billing node unit configured to randomly select a node from the network formed by the TLD node as a billing node within a preset time
- the package update unit is configured to package the valid domain name operation into the block by using the selected TLD node, and broadcast to other TLD nodes and update the TLD database.
- the system module is layered into an upper layer and an upper layer, wherein the bottom layer is a blockchain embedded with a domain name operation, and the upper layer is a data layer formed by top-level domain name related data;
- the inner TLD node updates the TLD database by processing a series of top-level domain operations and writes all operations to the underlying blockchain simultaneously; the preset time is 5 minutes.
- the invention has the beneficial effects that the present invention differs from the DNS of the Internet in that the DNS of the Internet is centrally managed at each layer of the domain name, and the present invention is based on the blockchain technology to implement a top-level domain name management scheme.
- the registration of top-level domain name managers (TLD nodes) and top-level domains is decentralized, that is, any one or a group of TLD nodes in the alliance cannot control the entire management process.
- the invention divides the domain name system into two layers, each top-level domain name has a corresponding lower-level domain name system, and how the lower-level domain name system is designed by the holder of the top-level domain name, so the lower-level domain name system can be designed according to the concept of the institution Centralized or decentralized system.
- the invention also proposes a management method of the top-level domain name chain, and proposes a data structure of the block header and the domain name operation, so that the data flow of the management process is more clear.
- Blockstack uses a completely decentralized design architecture that makes domain name registration and other issues difficult to manage.
- the present invention solves this problem using a compromise scheme such as a two-layer structure.
- the top-level domain chain is managed by the recognized alliance members rather than having some of them monopolized.
- the members of the alliance maintain the proper operation of the domain name system by formulating corresponding rules, for example, by formulating a series of rules to regulate the application of the top-level domain, thereby avoiding some Meaningless top-level domains appear.
- the maintenance organizations corresponding to each top-level domain can design different levels of management schemes for the sub-domain system according to their own concepts, that is, they can be designed as subsystems with strict management systems, or they can design subsystems such as Blockstack that are completely decentralized. Therefore, users can also apply for the corresponding subordinate domain name according to their own needs.
- the present invention can be fully compatible with today's Blockstack, for example, the alliance can add a "root" top-level domain, and the Internet's DNS can directly serve as the sub-domain system corresponding to the top-level domain. Obviously, the corresponding seed file is actually the interface to the domain name resolution under the existing DNS system.
- the system is guaranteed to be safe and reliable, and the efficiency of the system is improved; the system structure is layered to ensure the efficiency and portability of the system.
- FIG. 1 is a flowchart of a method for managing a top-level domain name based on a federation chain according to an embodiment of the present invention.
- FIG. 2 is a structural block diagram of a top-level domain name management system based on a federation chain according to an embodiment of the present invention.
- FIG. 3 is a system architecture diagram of a method for managing a top-level domain name based on a federation chain according to an embodiment of the present invention.
- FIG. 4 is a schematic diagram of a TLD database in a method for managing a top-level domain name based on a federation chain according to an embodiment of the present invention.
- FIG. 5 is a schematic diagram of a newly added TLD node in a method for managing a top-level domain name based on a federation chain according to an embodiment of the present invention.
- FIG. 1 is a flow chart showing a method for managing a top-level domain name based on a federated chain provided by the present invention, which is detailed as follows:
- Step S1 a network that forms a coalition chain by using TLD nodes; a coalition chain network composed of TLD nodes, that is, a p2p network composed of a group of key TLD nodes.
- TLD node There are two main functions of the TLD node. One is that the node that has joined the alliance audits and authenticates the node that applies to join the alliance. The second is to check and verify the domain name operation, and the extracted data is written into the TLD database, and at the same time, the legal operation is written. Go to the bottom blockchain.
- Step S11 the newly added TLD node can send a message for registering a new authentication node to any node in the TLD network;
- the node joining the TLD may send a message for registering a new authentication node to any node in the TLD network.
- Step S12 will receive The node that joins the message to the new node wants all nodes to broadcast the authentication message; the node that receives the new node join message broadcasts this authentication message to all nodes.
- Step S13 the node in the network selects or opposes the newly joined node according to its own rules and broadcasts the agreed or dissenting information to the remaining nodes; the node in the network selects to agree or oppose the newly joined node according to its own rules, and will agree and The objection is broadcast to other nodes.
- Step S14 if any node receives more than half of the consent to join the information, the network agrees that the node joins and records the message of the node. If a node receives more than half of the information that has been agreed to join, it will assume that the network has agreed to join the node and record the message of the node.
- step S2 the system architecture is layered to separate the operation and the data; the system architecture is divided into two layers, the bottom layer is a blockchain embedded with domain name operations, and the upper layer is a data layer composed of top-level domain name related data.
- a series of top-level domain nodes TLDN Top Level Domain Node construct a p2p network to jointly maintain the top-level domain name.
- Each node maintains a public key (Public key) and private key of the user who records the TLD and registers the top-level domain name.
- the TLD node builds and continually updates this database by processing a series of top-level domain operations.
- the operation of these top-level domains mainly includes the registration of the top-level domain (register) and the update of the seed file (update) corresponding to the top-level domain, as shown in FIG.
- the TLD node updates the TLD database by processing some of the column's top-level domain operations, and all operations are also written to the underlying blockchain.
- the operation of these top-level domains includes registering and deleting the corresponding top-level domain (update). Similar to the Namecoin system, the registration of top-level domains is divided into two phases: preorder and residency, also known as two-phase encryption submission protocol. Preorder operation claims to register one Top-level domain, but does not expose the name, nor does it change the database. The preorder operation prevents eavesdropping attackers from competing to become the sender of the operation and stealing the name. The delete operation deletes the relevant content in the TLD database. The update operation changes the seedfile corresponding to the top-level domain. Some of the operations in the system are assumed as shown in Figure 4, with the content stored in the TLD database on the right.
- step S3 the nodes in the alliance chain are consistent through the consensus process; the blockchain is often regarded as a book for recording transactions, and all nodes in the blockchain network participate in the maintenance of the account book.
- this scheme adopts a simpler consensus process to make the nodes in the alliance consistent.
- the computational power of participating in the alliance chain is insufficient in this scheme, POW is prone to 51% of the computational power attack problem; on the other hand, the alliance chain in this scheme is a trusted node, and does not require the reward and punishment mechanism of the POW.
- Step S31 each TLD node independently checks each domain name operation according to its own criteria; each TLD node according to its own standard, for each Domain name operations are independently verified.
- step S32 a node is randomly selected from the network composed of TLD nodes as a billing node in a preset time; every 5 minutes, a node is randomly selected from the network composed of TLD nodes as a billing node.
- step S33 using the selected TLD node to package the valid domain name operation in the preset time into the block, and broadcast to other TLD nodes and update the TLD database; the selected TLD node packages the valid domain name operation in the 5 minutes into the block. Broadcast to other TLD nodes and update the TLD database.
- the domain name operation and data structure and the structure of the block in the blockchain are very important for the whole system. Under the premise of referring to the existing blockchain related applications, the data structure and block suitable for the domain name operation of the scheme are designed. mechanism.
- the TLD node verifies the operation according to the structure of the domain name operation. Legitimacy, the effective domain name operation is packaged into the specified block header to generate the next block.
- FIG. 2 shows another object of the present invention provided by the present invention to provide a top-level domain name management system based on a federation chain, the top-level domain name management system including:
- a separation module for layering a system architecture in an alliance network to separate operations and data
- a node consistency module is used to make nodes in the federation network consistent through a consensus process.
- the authentication of the newly joined TLD node by the TLD node in the building the alliance chain network module includes:
- the newly registered node information sending unit configured to newly join the TLD node, can send a message for registering a new authentication node to any node in the TLD network;
- a broadcast authentication message unit wherein the node that adds the received new node to the message wants all nodes to broadcast the authentication message
- a network node feedback unit configured by the node in the network to agree or oppose the newly joined node according to its own rules and broadcast the agreed or dissenting information to the remaining nodes;
- the network will agree that the node joins and records the message of the node.
- the consensus process of the alliance network node in the node consistency module includes:
- Standard verification unit for each TLD node to independently verify each domain name operation according to its own standards
- a billing node unit configured to randomly select a node from the network formed by the TLD node as a billing node within a preset time
- the package update unit is used to package the valid domain name operation into the block by using the selected TLD node, and broadcast to other TLD nodes and update the TLD database.
- the system architecture is layered into an upper layer and an upper layer, wherein the bottom layer is a blockchain embedded with a domain name operation, and the upper layer is a data layer formed by top-level domain name related data; in the data layer, the TLD node processes a series of The top-level domain operation updates the TLD database and writes all operations to the underlying blockchain at the same time; the preset time is 5 minutes.
- the invention is based on a two-layer structure design, and proposes a top-level domain name management method based on a coalition chain, which makes the operation of the top-level domain name system decentralized while being suitable Management.
- the top-level domain name chain in the present invention adopts a blockchain as a data structure of transaction records, and the present invention also proposes a specific data structure of block header and domain name operations, which better reflects the decentralization characteristics.
- the present invention introduces the concept of a TLD node to enhance the management of a top-level domain chain.
- the present invention also proposes an implementation of a TLD database that illustrates how to generate a mapping from a blockchain to a seed file.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Power Engineering (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明适用于互联网技术改进领域,提供了一种基于区块链的顶级域名管理方法,所述顶级域名管理方法包括以下步骤:A、利用TLD节点构成在区块链中的联盟网络;B、在联盟网络中对系统架构进行分层使得操作和数据分离;C、通过共识过程使得联盟网络中的节点达到一致。通过更加简洁高效的共识过程,保证了系统的安全可靠性,提高了系统的效率;对系统结构分层,保障系统的效率和可移植性。
Description
本发明属于互联网技术改进领域,尤其涉及一种基于联盟链的顶级域名管理方法及系统。
名称在所有计算机系统中都起着重要的作用。它们用来共享资源、唯一标识实体、指向位置等。命名的一个重要结果是可以把名称解析为它所指向的实体。因而,名称解析允许进程访问命名的实体。要解析名称,需要实现命名系统。分布式系统中的命名与非分布式系统中的命名之间的区别在于命名系统实现的方式。而当今的许多应用,如部分文件系统和万维网名称系统都是基于分布式命名系统方案实现的。无论是现今的因特网,还是未来的新型网络,都需要一种基于分布式系统的结构化命名方案来解析参与到网络中的各种实体。域名系统(domain name system,DNS)是因特网使用的命名系统,用来把便于人们使用的机器名字转换为IP地址,并且采用具有层次的结构化命名方式,其中除了根域名外层次最高的域名称为顶级域名。
当今使用的最大分布式名称服务之一是因特网的域名系统(domain name system,DNS),DNS的因特网标准是RFC 1034,1035。DNS名称空间采用分层树状结构的命名方法,并使用人类容易记忆和理解名称映射为长度固定为32位的IP地址(如果是IPv6地址,则是定长的128位)。在因特网中,任何一个主机或路由器都有一个唯一的层次结构的名字,即域
名(domain name)。这里“域”是名字空间中一个可被管理的划分,域可以划分为子域,而子域还可以继续被划分,这样就形成了顶级域、二级域、三级域,等等。每个域名之间用点隔开。
因特网的域名系统是一个联机分布式数据库系统,采用客户-服务器方式,DNS使大多数名字都在本地进行解析,仅少量解析需要在因特网上通信,因此DNS系统的查询效率很高,并且单个计算机节点出了故障,也不会妨碍整个DNS系统的正常运行。域名服务器程序通常运行在域名服务器上,用于域名到IP地址的解析。当某个应用进程需要把主机名解析为IP地址时,该应用进程就调用解析程序,并成为DNS的一个客户,把待解析的域名放在DNS请求报文中,以UDP用户数据报方式发给本地域名服务器。本地域名服务器在查找域名后,把对应额IP地址放在回答报文中返回。应用进程获得目的主机的IP地址后即可进行通信。若本地域名服务器不能回答该请求,则此域名服务器就暂时成为DNS中的另一个客户,并向其他域名服务器发出查询请求。
各级域名由其上一级的域名管理机构管理,而最高的顶级域名链则由ICANN进行管理,这使得DNS管理中心化,任何公司、机构需要申请顶级域名时,都要向ICANN申请。
因特网上的域名服务器也是按照层次安排的,每个域名服务器都只对域名体系中的一部分进行管辖,所以可以划分为四种不同类型的服务器:根域名服务器、顶级域名服务器、权限域名服务器和本地域名服务器。当一个本地域名服务器无法解析一个域名时,就首先需要求助于根域名服务
器。但目前根域名服务器在世界各地的分布是不合理的,以2012年的数据为例,在北美,平均每375万个网民可以分摊到一个根域名服务器,而在亚洲,平均超过2000万个网民才分摊到一个根域名服务器,这样就会使亚洲的网民域名解析的速度明显地低于北美的,而且当亚洲某个域名服务器出现故障时,就会有2000万个网民的域名解析请求受到严重影响,可见这种现象也导致了亚洲的域名解析系统的可靠性更低。
Blockstack是一个去中心化的DNS系统,是以比特币区块链为底层实现的一个开源系统。它将DNS功能与公钥基础设施相结合,主要用于新的区块链应用程序。Blockstack通过分离控制层和数据层,将名称注册、名字的所有者和名称相关的数据分离开来。其中控制层包含区块链层和虚拟链层,数据层分为路由层和存储层,所以Blockstack的系统架构其实由四层组成。区块链层占据着最底层,存储了Blockstack的一系列操作,并且提供了这些操作写入的顺序一致性,Blockstack当前采用比特币区块链作为区块链层。虚拟链层在区块链层上定义自身协议,只有Blockstack系统软件可以感知到的事务记录。路由层负责将控制层定义的名称映射到实际存储数据的文件上,避免了系统从一开始就采用任意特定的存储服务,从而允许多个存储供应商提供服务。最顶的一层就是存储层,存储实际的“name-value”对数据,包括大容量的数据。Blockstack采用分层结构,当某一层级出现问题或变更升级时不会影响其他层级的正常运行,并且降低了控制层的传输数据量。Blockstack基于Namecoin的名称操作构建了全局命名系统,而且提出虚拟链的概念,使得系统具有更好的扩展性。Blockstack
还使用了一种基于一致性散列的简化名称验证协议,加速节点验证和新节点的加入。
Blockstack难以与现有的DNS系统兼容。因特网的DNS系统采用分层的域名结构,而域名服务器的层次结构也是按照层次安排的。但是Blockstack并未使用分层的域名结构,域名之间也并没有层级关系。
Blockstack完全去中心化的设计使得系统难于监管。虽然Blockstack可以让用户自由的申请域名,不受任何机构的限制和监管,但是这样的结构会产生许多无人维护的“僵尸”域名,极端的情况下可能成为犯罪的温床,因为你无法知道哪个用户持有域名对应的私钥。顶级域名被认为是真正的企业网络商标,是企业品牌策略战略发展的重要内容,而Blockstack抛弃了现有DNS的设计理念,顶级域名随意引入,使得顶级域名的意义不复存在。
发明内容
本发明的目的在于提供一种基于联盟链的顶级域名管理方法,旨在解决上述的技术问题。
本发明是这样实现的,一种基于联盟链的顶级域名管理方法,所述顶级域名管理方法包括以下步骤:
A、利用TLD节点构成在区块链中的联盟网络;
B、在联盟网络中对系统架构进行分层使得操作和数据分离;
C、通过共识过程使得联盟网络中的节点达到一致。
本发明的进一步技术方案是:所述步骤A中TLD节点对新加入TLD节点的认证包括以下步骤:
A1、新加入TLD节点可向TLD网络中任意一节点发送注册新的认证节点的消息;
A2、将收到的新节点加入消息的节点想所有节点广播该认证消息;
A3、网络中节点根据自身的规则选择同意或反对新加入的节点并将同意或反对的信息广播到其余节点;
A4、任意节点收到半数以上同意加入信息会认为网络同意该节点加入并记录该节点的消息。
本发明的进一步技术方案是:所述步骤C中联盟网络节点的共识过程包括以下步骤:
C1、每个TLD节点根据自己的标准,对每个域名操作进行独立校验;
C2、在预设时间内从TLD节点构成的网络中随机选择一个节点作为记账节点;
C3、利用选中的TLD节点将预设时间内有效的域名操作打包进区块,并广播到其它TLD节点和更新TLD数据库。
本发明的进一步技术方案是:所述步骤A中将系统构架分层为底层和上层,其中底层为嵌入域名操作的区块链,上层为顶层域名相关数据构成的数据层。
本发明的进一步技术方案是:在所述数据层内TLD节点通过处理一系列的顶级域名操作更新TLD database,并将所有的操作同时写入底层的区块链中。
本发明的进一步技术方案是:所述预设时间为5分钟。
本发明的另一目的在于提供一种基于区块链的顶级域名管理系统,所述顶级域名管理系统包括:
构建联盟网络模块,用于利用TLD节点构成在区块链中的联盟网络;
分离模块,用于在联盟网络中对系统架构进行分层使得操作和数据分离;
节点一致模块,用于通过共识过程使得联盟网络中的节点达到一致。
本发明的进一步技术方案是:所述构建联盟网络模块中TLD节点对新加入TLD节点的认证包括:
新注册节点信息发送单元,用于新加入TLD节点可向TLD网络中任意一节点发送注册新的认证节点的消息;
广播认证消息单元,用于将收到的新节点加入消息的节点想所有节点广播该认证消息;
网络节点反馈单元,用于网络中节点根据自身的规则选择同意或反对新加入的节点并将同意或反对的信息广播到其余节点;
批准加入记录单元,用于任意节点收到半数以上同意加入信息会认为网络同意该节点加入并记录该节点的消息。
本发明的进一步技术方案是:所述节点一致模块中联盟网络节点的共识过程包括:
标准校验单元,用于每个TLD节点根据自己的标准,对每个域名操作进行独立校验;
记账节点单元,用于在预设时间内从TLD节点构成的网络中随机选择一个节点作为记账节点;
打包更新单元,用于利用选中的TLD节点将预设时间内有效的域名操作打包进区块,并广播到其它TLD节点和更新TLD数据库。
本发明的进一步技术方案是:所述分离模块中将系统构架分层为底层和上层,其中底层为嵌入域名操作的区块链,上层为顶层域名相关数据构成的数据层;在所述数据层内TLD节点通过处理一系列的顶级域名操作更新TLD database,并将所有的操作同时写入底层的区块链中;所述预设时间为5分钟。
本发明的有益效果是:本发明与因特网的DNS的不同之处在于,因特网的DNS在域名各层实行中心化的管理,而本发明是基于区块链技术实现的顶级域名管理方案,在选择顶级域名管理者(TLD节点)和顶级域名的注册上都是去中心化的,即联盟中任意一个或一个小组的TLD节点都不能控制整个管理流程。本发明将域名系统分为两层,每个顶级域名有对应的下级域名系统,而下级的域名系统如何设计由顶级域名的持有机构决定,因此下级域名系统可以根据该机构的理念而设计成中心化的或者去中心化的系统。
此外,由于区块链上的信息是公开并且不可更改的,所以被信任的机构甚至是个人都能获取到区块链上的信息并构建相应的种子文件数据库来保存顶级域名与下级域名系统的映射关系。这就意味着,各地区都能根据实际情况搭建相应数量的域名服务器以保证上网速度,而不必受到某些机构的限制。本发明也提出了一个顶级域名链的管理方法,并提出区块头和域名操作的数据结构,使得管理过程的数据流更加明确。
Blockstack采用完全去中心化的设计架构,使得域名注册等事务难于管理。本发明使用两层结构这样的折中方案解决这个问题。顶级域名链由被认可的联盟成员共同管理而不是有其中一部分成员独揽大权,联盟成员通过制定相应的规则来维护域名系统的合理运行,例如通过制定一系列规则规范顶级域名的申请,从而避免一些毫无意义的顶级域名出现。而各个顶级域名对应的维护机构可以按照自身理念为子域名系统设计不同程度的管理方案,即可以设计成具有严格管理制度的子系统,或者可以设计出如Blockstack这样完全去中心化的子系统,因此用户也可以根据自身需要去申请相应的下级域名。
另外,与Blockstack相比,本发明可以与现今的Blockstack完全兼容,例如联盟可以增加一个“root”的顶级域名,而因特网的DNS可直接作为该顶级域名对应的下级域名系统。显然,对应的种子文件其实就是对现有DNS系统下的域名解析的接口。通过更加简洁高效的共识过程,保证了系统的安全可靠性,提高了系统的效率;对系统结构分层,保障系统的效率和可移植性。
图1是本发明实施例提供的基于联盟链的顶级域名管理方法的流程图。
图2是本发明实施例提供的基于联盟链的顶级域名管理系统的结构框图。
图3是本发明实施例提供的基于联盟链的顶级域名管理方法中系统架构图。
图4是本发明实施例提供的基于联盟链的顶级域名管理方法中TLD数据库示意图。
图5是本发明实施例提供的基于联盟链的顶级域名管理方法中新加入TLD节点示意图。
图1示出了本发明提供的基于联盟链的顶级域名管理方法的流程图,其详述如下:
步骤S1,利用TLD节点构成联盟链的网络;由TLD节点构成的联盟链网络,即一组关键TLD节点构成的p2p网络。TLD节点主要功能有两个,一是已经加入联盟的节点审核并认证申请加入联盟的节点;二是检查、验证域名操作,提取数据写入到TLD数据库中,与此同时将合法的操作写入到底层区块链中。考虑到认证的效率和容错性,本方案中新加入TLD节点的认证要经历下面四个步骤:步骤S11,新加入TLD节点可向TLD网络中任意一节点发送注册新的认证节点的消息;新加入TLD的节点可向TLD网络中任意一节点发送注册新的认证节点的消息。步骤S12,将收到
的新节点加入消息的节点想所有节点广播该认证消息;收到新节点加入消息的节点向所有节点广播这条认证消息。步骤S13,网络中节点根据自身的规则选择同意或反对新加入的节点并将同意或反对的信息广播到其余节点;网络中节点根据自己的规则选择同意或反对新加入的节点,同时将同意和反对的信息广播到其它节点。步骤S14,任意节点收到半数以上同意加入信息会认为网络同意该节点加入并记录该节点的消息。一个节点收到半数以上同意加入的信息就会认为网络已经同意该节点的加入,记录该节点的消息。
步骤S2,对系统架构进行分层使得操作和数据分离;将系统架构分为两层,底层为嵌入域名操作的区块链,上层为顶层域名相关数据构成的数据层。一系列的顶级域名节点TLDN(Top Level Domain Node)构建一张p2p网络共同维护顶级域名,每个节点维护一个记录顶级域名(TLD)、注册顶级域名的用户的公钥(Public key)、私钥签名的下级域名系统的种子文件(Seed file)的TLD数据库。TLD节点通过处理一系列的顶级域名操作来构建和持续更新这个数据库。这些顶级域名的操作中主要包括顶级域名的注册(register)和更新顶级域名对应的种子文件(update),如图3所示。
TLD节点通过处理一些列的顶级域名操作来更新TLD database,所有的操作同时也会被写入底层的区块链中。这些顶级域名的操作包括顶级域名的注册(register)和删除(delete)其对应的seedfile的更新(update)。和Namecoin系统类似,顶级域名的注册分为预定(preorder)和注册(resister)两个阶段,也被称为两阶段加密提交协议。preorder操作宣称要注册一个
顶级域名,但是不会暴露名称,也不会改变数据库。preorder操作可以防止窃听攻击者竞争成为操作发送者并窃取名称。delete操作会在TLD数据库中删除相关的内容。update操作会更改顶级域名对应的seedfile。如图4中所示假设了系统中的一些操作,右边为TLD数据库中存储的内容。
步骤S3,通过共识过程使得联盟链中的节点达到一致;区块链经常被看作一本记录交易的账簿,区块链网路中所有的节点都参与到账簿的维护当中。相比于比特币网络中基于算力的POW共识机制,本方案采用了一种更加简便的共识过程使得联盟中的节点达到一致。主要是因为本方案中参与联盟链的算力不足,POW很容易出现51%算力攻击问题;另一方面,本方案中联盟链都是可信任的节点,不需要POW的奖惩机制。本方案中联盟链节点的共识过程主要经历下面三个步骤:步骤S31、每个TLD节点根据自己的标准,对每个域名操作进行独立校验;每个TLD节点根据自己的标准,对每个域名操作进行独立校验。步骤S32,在预设时间内从TLD节点构成的网络中随机选择一个节点作为记账节点;每5分钟,从TLD节点构成的网络中随机选择一个节点,作为记账节点。步骤S33,利用选中的TLD节点将预设时间内有效的域名操作打包进区块,并广播到其它TLD节点和更新TLD数据库;选中的TLD节点将这5分钟内有效的域名操作打包进区块,广播到其它TLD节点,更新TLD数据库。
域名操作和数据结构以及区块链中块的结构对于整个系统来说非常重要,在参考现有的区块链相关应用的前提下,设计适合于本方案的域名操作的数据结构以及区块的机构。TLD节点根据域名操作的结构验证操作的
合法性,将有效的域名操作打包加入规定的区块头生成下一个区块。
表一域名操作的结构
长度 | 字段 | 描述 |
32字节 | 域名操作hash | 保证域名操作的正确性 |
128字节 | 域名操作发起者的公钥 | 解密私钥签名的数据,保障安全性 |
10个字节 | 具体的域名操作 | Register/delete/update操作 |
4字节 | 时间戳 | 域名操作被验证通过的时间点 |
表二区块头结构
长度 | 字段 | 描述 |
4字节 | 版本 | 版本号,用来跟踪软件的升级 |
32字节 | 前区块的哈希 | 链中前一区块的哈希值 |
32字节 | Merkle根 | 这个区块中全部操纵构成的merkle树的根 |
4字节 | 时间戳 | 域名操作被验证通过的时间点 |
图2示出了本发明提供的本发明的另一目的在于提供一种基于联盟链的顶级域名管理系统,所述顶级域名管理系统包括:
构建联盟网络模块,用于利用TLD节点构成在区块链中的联盟网络;
分离模块,用于在联盟网络中对系统架构进行分层使得操作和数据分离;
节点一致模块,用于通过共识过程使得联盟网络中的节点达到一致。
所述构建联盟链网络模块中TLD节点对新加入TLD节点的认证包括:
新注册节点信息发送单元,用于新加入TLD节点可向TLD网络中任意一节点发送注册新的认证节点的消息;
广播认证消息单元,用于将收到的新节点加入消息的节点想所有节点广播该认证消息;
网络节点反馈单元,用于网络中节点根据自身的规则选择同意或反对新加入的节点并将同意或反对的信息广播到其余节点;
批准加入记录单元,用于任意节点收到半数以上同意加入信息会认为网络同意该节点加入并记录该节点的消息。
所述节点一致模块中联盟网络节点的共识过程包括:
标准校验单元,用于每个TLD节点根据自己的标准,对每个域名操作进行独立校验;
记账节点单元,用于在预设时间内从TLD节点构成的网络中随机选择一个节点作为记账节点;
打包更新单元吗,用于利用选中的TLD节点将预设时间内有效的域名操作打包进区块,并广播到其它TLD节点和更新TLD数据库。
所述分离模块中将系统构架分层为底层和上层,其中底层为嵌入域名操作的区块链,上层为顶层域名相关数据构成的数据层;在所述数据层内TLD节点通过处理一系列的顶级域名操作更新TLD database,并将所有的操作同时写入底层的区块链中;所述预设时间为5分钟。
本发明基于两层结构设计,提出了一个基于联盟链的顶级域名管理方法,该管理方法使得顶级域名系统的运行在去中心化的同时又得到合适
的管理。本发明中的顶级域名链采用了区块链作为事务记录的数据结构,并且本发明也提出了一种具体的区块头和域名操作的数据结构,更好地体现了去中心化的特性。另外,本发明引入了TLD节点的概念来加强顶级域名链的管理。本发明也提出了TLD数据库的一种实现方案,说明如何生成从区块链到种子文件的映射。
以上所述仅为本发明的较佳实施例而已,并不用以限制本发明,凡在本发明的精神和原则之内所作的任何修改、等同替换和改进等,均应包含在本发明的保护范围之内。
Claims (10)
- 一种基于区块链的顶级域名管理方法,其特征在于,所述顶级域名管理方法包括以下步骤:A、利用TLD节点构成在区块链中的联盟网络;B、在联盟网络中对系统架构进行分层使得操作和数据分离;C、通过共识过程使得联盟网络中的节点达到一致。
- 根据权利要求1所述的顶级域名管理方法,其特征在于,所述步骤A中TLD节点对新加入TLD节点的认证包括以下步骤:A1、新加入TLD节点可向TLD网络中任意一节点发送注册新的认证节点的消息;A2、将收到的新节点加入消息的节点想所有节点广播该认证消息;A3、网络中节点根据自身的规则选择同意或反对新加入的节点并将同意或反对的信息广播到其余节点;A4、任意节点收到半数以上同意加入信息会认为网络同意该节点加入并记录该节点的消息。
- 根据权利要求2所述的顶级域名管理方法,其特征在于,所述步骤C中联盟网络节点的共识过程包括以下步骤:C1、每个TLD节点根据自己的标准,对每个域名操作进行独立校验;C2、在预设时间内从TLD节点构成的网络中随机选择一个节点作为记账节点;C3、利用选中的TLD节点将预设时间内有效的域名操作打包进区块,并广播到其它TLD节点和更新TLD数据库。
- 根据权利要求3所述的顶级域名管理方法,其特征在于,所述步骤A中将系统构架分层为底层和上层,其中底层为嵌入域名操作的区块链,上层为顶层域名相关数据构成的数据层。
- 根据权利要求4所述的顶级域名管理方法,其特征在于,在所述数据层内TLD节点通过处理一系列的顶级域名操作更新TLD database,并将所有的操作同时写入底层的区块链中。
- 根据权利要求5所述的顶级域名管理方法,其特征在于,所述预设时间为5分钟。
- 一种基于联盟链的顶级域名管理系统,其特征在于,所述顶级域名管理系统包括:构建联盟网络模块,用于利用TLD节点构成在区块链中的联盟网络;分离模块,用于在联盟网络中对系统架构进行分层使得操作和数据分离;节点一致模块,用于通过共识过程使得联盟网络中的节点达到一致。
- 根据权利要求7所述的顶级域名管理系统,其特征在于,所述构建联盟链网络模块中TLD节点对新加入TLD节点的认证包括:新注册节点信息发送单元,用于新加入TLD节点可向TLD网络中任意一节点发送注册新的认证节点的消息;广播认证消息单元,用于将收到的新节点加入消息的节点想所有节点广播该认证消息;网络节点反馈单元,用于网络中节点根据自身的规则选择同意或反对新加入的节点并将同意或反对的信息广播到其余节点;批准加入记录单元,用于任意节点收到半数以上同意加入信息会认为网络同意该节点加入并记录该节点的消息。
- 根据权利要求8所述的顶级域名管理系统,其特征在于,所述节点一致模块中联盟网络节点的共识过程包括:标准校验单元,用于每个TLD节点根据自己的标准,对每个域名操作进行独立校验;记账节点单元,用于在预设时间内从TLD节点构成的网络中随机选择一个节点作为记账节点;打包更新单元,用于利用选中的TLD节点将预设时间内有效的域名操作打包进区块,并广播到其它TLD节点和更新TLD数据库。
- 根据权利要求9所述的顶级域名管理系统,其特征在于,所述分离模块中将系统构架分层为底层和上层,其中底层为嵌入域名操作的区块链,上层为顶层域名相关数据构成的数据层;在所述数据层内TLD节点通过处理一系列的顶级域名操作更新TLD database,并将所有的操作同时写入底层的区块链中;所述预设时间为5分钟。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2017/079098 WO2018176406A1 (zh) | 2017-03-31 | 2017-03-31 | 一种基于联盟链的顶级域名管理方法及系统 |
CN201780002711.4A CN108124502B (zh) | 2017-03-31 | 2017-03-31 | 一种基于联盟链的顶级域名管理方法及系统 |
US15/921,319 US10178069B2 (en) | 2017-03-31 | 2018-03-14 | Systems and methods for managing top-level domain names using consortium blockchain |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2017/079098 WO2018176406A1 (zh) | 2017-03-31 | 2017-03-31 | 一种基于联盟链的顶级域名管理方法及系统 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/921,319 Continuation US10178069B2 (en) | 2017-03-31 | 2018-03-14 | Systems and methods for managing top-level domain names using consortium blockchain |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018176406A1 true WO2018176406A1 (zh) | 2018-10-04 |
Family
ID=62233597
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/079098 WO2018176406A1 (zh) | 2017-03-31 | 2017-03-31 | 一种基于联盟链的顶级域名管理方法及系统 |
Country Status (3)
Country | Link |
---|---|
US (1) | US10178069B2 (zh) |
CN (1) | CN108124502B (zh) |
WO (1) | WO2018176406A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113067914A (zh) * | 2021-06-02 | 2021-07-02 | 支付宝(杭州)信息技术有限公司 | 一种分配子网标识的方法、装置、电子设备和存储介质 |
Families Citing this family (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107450981B (zh) | 2017-05-31 | 2020-04-24 | 创新先进技术有限公司 | 一种区块链共识方法及设备 |
US11438139B2 (en) * | 2018-02-07 | 2022-09-06 | Raouf Boutaba | Blockchain based secure naming and update verification |
CN108667618B (zh) * | 2018-05-10 | 2020-07-03 | 阿里巴巴集团控股有限公司 | 区块链成员管理的数据处理方法、装置、服务器及系统 |
US11632236B1 (en) | 2018-06-29 | 2023-04-18 | Verisign, Inc. | Establishment, management, and usage of domain name to blockchain address associations |
US10721060B1 (en) | 2018-06-29 | 2020-07-21 | Verisign, Inc. | Domain name blockchain user addresses |
CN111104678B (zh) * | 2018-10-25 | 2022-03-18 | 北京国盾量子信息技术有限公司 | 一种区块链共识方法及装置 |
SG11201903496PA (en) | 2018-11-16 | 2019-05-30 | Alibaba Group Holding Ltd | Cross-chain interactions using a domain name scheme in blockchain systems |
CA3041203C (en) * | 2018-11-16 | 2021-01-19 | Alibaba Group Holding Limited | A domain name management scheme for cross-chain interactions in blockchain systems |
CN109558407A (zh) * | 2018-11-19 | 2019-04-02 | 湖北多羔生物育种科技有限公司 | 一种联盟区块链育种技术 |
CN109495246B (zh) * | 2018-11-20 | 2021-04-20 | 王建新 | 一种联盟链节点验证方法 |
CN110457942B (zh) * | 2018-12-07 | 2022-11-04 | 深圳市智税链科技有限公司 | 对上链数据区块的签名验证方法、业务节点和介质 |
WO2020113545A1 (zh) * | 2018-12-07 | 2020-06-11 | 北京大学深圳研究生院 | 基于联盟链投票共识算法产生及管理多模标识网络的方法 |
CN109327562B (zh) * | 2018-12-10 | 2022-05-13 | 中共中央办公厅电子科技学院 | 一种基于区块链的域名存储系统及方法 |
CN109886036B (zh) * | 2019-01-02 | 2020-12-01 | 广州大学 | 基于区块链的域名分布式认证方法、装置及区块链网络 |
WO2020154865A1 (zh) * | 2019-01-28 | 2020-08-06 | 北京大学深圳研究生院 | 一种支持多模标识网络寻址渐进去ip的方法、系统及存储介质 |
CN109672760B (zh) * | 2019-02-14 | 2022-04-12 | 中国互联网络信息中心 | 基于区块链的dns根数据分发方法及系统 |
CN109756589B (zh) * | 2019-02-20 | 2020-11-13 | 中国互联网络信息中心 | 一种基于区块链多方共治的域名信息维护系统 |
CN109889382B (zh) * | 2019-02-20 | 2020-07-21 | 中国互联网络信息中心 | 一种基于区块链混合共识的域名信息维护系统 |
WO2020168477A1 (zh) * | 2019-02-20 | 2020-08-27 | 北京大学深圳研究生院 | 一种联盟链共识下满足分区容忍性的拓扑构造方法及系统 |
CN110012126B (zh) * | 2019-04-02 | 2022-01-21 | 哈尔滨工业大学(深圳) | 一种基于区块链技术的dns系统 |
CN111817852A (zh) * | 2019-04-10 | 2020-10-23 | 上海旺链信息科技有限公司 | 一种联盟链系统管理方法和装置 |
US10880260B1 (en) * | 2019-06-19 | 2020-12-29 | Etherweb Technologies LLC | Distributed domain name resolution and method for use of same |
CN110288348B (zh) * | 2019-06-20 | 2021-01-26 | 中国传媒大学 | 基于传播活跃度和资产证明的区块链共识方法及系统 |
US11797655B1 (en) | 2019-07-18 | 2023-10-24 | Verisign, Inc. | Transferring a domain name on a secondary blockchain market and in the DNS |
CN110493080B (zh) * | 2019-08-19 | 2021-12-14 | 腾讯科技(深圳)有限公司 | 一种区块链节点监控方法、装置及电子设备和存储介质 |
CN112468602B (zh) * | 2019-09-06 | 2023-09-22 | 傲为有限公司 | 一种基于区块链的去中心化域名注册系统及方法 |
CN110602217B (zh) * | 2019-09-17 | 2022-04-01 | 腾讯科技(深圳)有限公司 | 基于区块链的联盟管理方法、装置、设备及存储介质 |
CN110659264B (zh) * | 2019-09-26 | 2022-09-23 | 联想(北京)有限公司 | 用于计算系统的业务处理方法、装置和计算系统 |
US10715484B1 (en) * | 2019-12-11 | 2020-07-14 | CallFire, Inc. | Domain management and synchronization system |
US12099997B1 (en) | 2020-01-31 | 2024-09-24 | Steven Mark Hoffberg | Tokenized fungible liabilities |
CN111711711A (zh) * | 2020-05-28 | 2020-09-25 | 北京邮电大学 | 基于区块链的顶级域名管理和解析方法及系统 |
CN112134967B (zh) * | 2020-09-30 | 2022-06-28 | 中国互联网络信息中心 | 一种基于共治链的域名解析方法及装置 |
CN112769917B (zh) * | 2020-12-31 | 2022-08-02 | 山西特信环宇信息技术有限公司 | 一种锥体区块链的主权联盟链 |
CN112866437A (zh) * | 2021-02-25 | 2021-05-28 | 中国电子信息产业集团有限公司第六研究所 | 一种数据处理方法及域名解析架构 |
CN113067836B (zh) * | 2021-04-20 | 2022-04-19 | 哈尔滨工业大学 | 一种基于去中心化dns根区管理的智能合约系统 |
US11463581B1 (en) * | 2021-05-13 | 2022-10-04 | International Business Machines Corporation | Managing phone identification via immutable connection verification |
US12003615B2 (en) | 2021-05-20 | 2024-06-04 | Verisign, Inc. | Lifecycle administration of domain name blockchain addresses |
US11750401B2 (en) | 2021-05-20 | 2023-09-05 | Verisign, Inc. | Proving top level domain name control on a blockchain |
US11924161B1 (en) | 2021-05-20 | 2024-03-05 | Verisign, Inc. | Authorization and refusal of modification, and partial modification ability, of a network identifier |
US12052373B1 (en) | 2021-05-20 | 2024-07-30 | Verisign, Inc. | Delegated agent proof of network identifier control |
CN113438214B (zh) * | 2021-06-10 | 2023-04-18 | 国网河北省电力有限公司信息通信分公司 | 一种域名管理系统 |
CN113609215A (zh) * | 2021-07-07 | 2021-11-05 | 深圳云科能源科技有限公司 | 数据处理方法、装置、设备与计算机可读存储介质 |
CN113542040B (zh) * | 2021-09-16 | 2021-11-26 | 中国信息通信研究院 | 时长指示方法、装置及电子设备 |
CN114666043B (zh) * | 2022-03-04 | 2024-09-10 | 江苏梦想物联有限公司 | 一种区块链的差异概率共识算法生成记账者的方法 |
US20230336523A1 (en) * | 2022-04-13 | 2023-10-19 | Unstoppable Domains, Inc. | Domain name registration based on verification of entities of reserved names |
CN114760135B (zh) * | 2022-04-19 | 2023-03-28 | 浙江大学 | 一种区块链容错共识方案的优化方法 |
CN116074082B (zh) * | 2023-01-28 | 2023-06-16 | 鹏城实验室 | 域名保全方法、域名保全装置及可读存储介质 |
CN116155683B (zh) * | 2023-04-21 | 2023-07-04 | 南京信息工程大学 | 基于三层树型通信结构的HotStuff共识机制构建方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101335618A (zh) * | 2008-07-09 | 2008-12-31 | 南京邮电大学 | 一种使用证书对对等网节点进行评价和授权的方法 |
CN103347087A (zh) * | 2013-07-16 | 2013-10-09 | 桂林电子科技大学 | 一种结构化p2p和uddi的服务注册与查找方法和系统 |
CN105978697A (zh) * | 2016-07-25 | 2016-09-28 | 宁圣金融信息服务(上海)有限公司 | 一种区块链域名解析方法 |
WO2016177026A1 (zh) * | 2015-05-07 | 2016-11-10 | 中兴通讯股份有限公司 | 一种去中心化自治组织的数据处理方法及装置 |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7418504B2 (en) * | 1998-10-30 | 2008-08-26 | Virnetx, Inc. | Agile network protocol for secure communications using secure domain names |
EP3872666A1 (fr) * | 2015-01-30 | 2021-09-01 | Enrico Maim | Systèmes et procédés pour la gestion d'engagements en réseau d'entités sécurisées |
US10644885B2 (en) * | 2015-07-14 | 2020-05-05 | Fmr Llc | Firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems |
US20170236123A1 (en) * | 2016-02-16 | 2017-08-17 | Blockstack Inc. | Decentralized processing of global naming systems |
CN106210171A (zh) * | 2016-07-25 | 2016-12-07 | 宁圣金融信息服务(上海)有限公司 | 一种区块链域名解析系统 |
CN106027264A (zh) * | 2016-07-26 | 2016-10-12 | 宁圣金融信息服务(上海)有限公司 | 域名区块链链接保存方法和装置 |
WO2018049523A1 (en) * | 2016-09-14 | 2018-03-22 | Royal Bank Of Canada | Credit score platform |
US10970780B2 (en) * | 2016-11-01 | 2021-04-06 | International Business Machines Corporation | Zero-knowledge predictions market |
US10621511B2 (en) * | 2016-11-09 | 2020-04-14 | Cognitive Scale, Inc. | Method for using hybrid blockchain data architecture within a cognitive environment |
CN106529951A (zh) * | 2016-12-30 | 2017-03-22 | 杭州云象网络技术有限公司 | 一种联盟链网络下采用异步方式的节点共识验证方法 |
-
2017
- 2017-03-31 WO PCT/CN2017/079098 patent/WO2018176406A1/zh active Application Filing
- 2017-03-31 CN CN201780002711.4A patent/CN108124502B/zh active Active
-
2018
- 2018-03-14 US US15/921,319 patent/US10178069B2/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101335618A (zh) * | 2008-07-09 | 2008-12-31 | 南京邮电大学 | 一种使用证书对对等网节点进行评价和授权的方法 |
CN103347087A (zh) * | 2013-07-16 | 2013-10-09 | 桂林电子科技大学 | 一种结构化p2p和uddi的服务注册与查找方法和系统 |
WO2016177026A1 (zh) * | 2015-05-07 | 2016-11-10 | 中兴通讯股份有限公司 | 一种去中心化自治组织的数据处理方法及装置 |
CN105978697A (zh) * | 2016-07-25 | 2016-09-28 | 宁圣金融信息服务(上海)有限公司 | 一种区块链域名解析方法 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113067914A (zh) * | 2021-06-02 | 2021-07-02 | 支付宝(杭州)信息技术有限公司 | 一种分配子网标识的方法、装置、电子设备和存储介质 |
CN113067914B (zh) * | 2021-06-02 | 2021-08-17 | 支付宝(杭州)信息技术有限公司 | 一种分配子网标识的方法、装置、电子设备和存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN108124502B (zh) | 2021-01-05 |
US10178069B2 (en) | 2019-01-08 |
CN108124502A (zh) | 2018-06-05 |
US20180287997A1 (en) | 2018-10-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018176406A1 (zh) | 一种基于联盟链的顶级域名管理方法及系统 | |
CN110945853B (zh) | 基于联盟链投票共识算法产生及管理多模标识网络的方法 | |
CN108064444B (zh) | 一种基于区块链的域名解析系统 | |
CN107613041B (zh) | 基于区块链的域名管理系统、域名管理方法和域名解析方法 | |
KR101330392B1 (ko) | 분산 저장 네트워크에서 데이터 인가를 위한 네트워크 노드 및 방법 | |
WO2020154865A1 (zh) | 一种支持多模标识网络寻址渐进去ip的方法、系统及存储介质 | |
CN101127606B (zh) | 传输数据对象的方法和装置 | |
US11368450B2 (en) | Method for bidirectional authorization of blockchain-based resource public key infrastructure | |
CN109983752A (zh) | 带有编码dns级信息的网络地址 | |
KR101085638B1 (ko) | 피어 투 피어 네트워크에서의 안전한 계층적 이름 공간 | |
US11521205B2 (en) | Method for certificate transaction validation of blockchain-based resource public key infrastructure | |
CN113824563B (zh) | 一种基于区块链证书的跨域身份认证方法 | |
TW200803303A (en) | Inter-proximity communication within a rendezvous federation | |
JP2000349747A (ja) | 公開鍵管理方法 | |
Afanasyev | Addressing operational challenges in Named Data Networking through NDNS distributed database | |
Patsonakis et al. | Towards a smart contract-based, decentralized, public-key infrastructure | |
CN112132581B (zh) | 基于iota的pki身份认证系统及方法 | |
CN103051643B (zh) | 云计算环境下虚拟主机安全连接动态建立方法与系统 | |
Zhang et al. | Blockchain‐Based DNS Root Zone Management Decentralization for Internet of Things | |
Garba et al. | BlockVoke–fast, blockchain-based certificate revocation for PKIs and the Web of Trust | |
García-Martínez et al. | Design and implementation of inblock—a distributed ip address registration system | |
Song et al. | Smart contract-based trusted content retrieval mechanism for NDN | |
US12058024B1 (en) | Distributed ledger network discovery and cross-instance data routing | |
Kim | Comparison and analysis of DNS and DOA for Internet of Things naming system | |
Li et al. | Towards an equitable federated name service for the Internet of Things |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17903243 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 17903243 Country of ref document: EP Kind code of ref document: A1 |