📖🔍 Documents of the Zilliqa Name Service.
Zilliqa is the world's first high-throughput public blockchain platform - designed to scale to thousands of transactions per second.
BNS – or blockchain name system – is the protocol on the internet that turns human-comprehensible decentralized website names such as ‘website.perl’ or ‘mywebsite.eth’ into addresses understandable by decentralized network machines.
ZNS is the Zilliqa Name Service, a distributed, open, and extensible naming system based on the Zilliqa blockchain.
ZNS plays an connecting and entry layer in Web3.0 services. It connects with Zilliqa wallet, blockchain server, decentralized content resources, and decentralized database.
Zilliqa Name Service (ZNS) governs by three smart contract components, registrar, registry, and resolver. The three smart contracts contain the core logic for the whole Zilliqa Name System implementation which is from the ownership managment for a domain, how to securely save the data, to the global resolving layer. The ZNS global resolving layer can connect different tech stacks and enhances the usability for different infrastructures.
Zilliqa servers as the fundamental blockchain state layer. It stores each of the transactions and record the related data transformation. This layer give the participants the ability to control and own their state and data. ZNS stores the data and state in the state layer.
Developers can utlize Scilla to implement their business logic to the smart contract. The paradigms of functional programming and formal verification of Scilla enhance the security of smart contracts.
The design of digital assets can have more functions through combing the State Layer and Computation Layer, such as: crypto assets, and identities. Those programmable assets has many more potential usages and sub-economies within.
The sharding mechnaism of Zilliqa provides high throughput and eliminates the obstables about network congestion, high transaction fees or related security issues.
The BNS protocol is a standard which can make the Zilliqa Name Service more efficient. The protocol essentially for the user control layer and the application layer which can let more applications and services can be built on top of it.
This layer is in charge of managing a user’s private keys and the interaction with the State Layer. Before the Zilliqa wallet published, the users should use command line interface (CLI) to talk directly with the computation layer. ZNS plays an crucial rule to transfer hashes to human-meaningful names. Zilliqa wallet and browser extension can resolve ZNS to wallet address, contract address and IPFS hash.
The above features provided by different layers enables more use cases. For example, developers can utilize the tech stacks to build a decentralized website which can interact with the Zilliqa and hosted on IPFS. Users can view the decentralized resources through simply typing yourwebsite.zil on the domain url bar with our further enhancement in browser extension.
Zilliqa dynamically splits the network of blockchain nodes into different subgroups, called shards, with each shard formed to process and reach consensus on a subset of transactions. This way, disjoint subsets of transactions can be processed in parallel, and significantly boost the transaction throughput by orders of magnitude. Eventually, such transactions are merged into a new block that is committed to the blockchain.
Dividing the mining network into smaller shards is a two-step process. First, a dedicated set of nodes called the directory service committee (or DS committee) are elected which then shard the network and assign nodes to their shard. The directory service committee is tasked to coordinate the sharding process, as well as validate the blocks of transactions proposed by each shard and verify if they have received approval from a sufficiently large quorum within the shard.
Within the directory service committee and each shard that processes and accepts transactions, Zilliqa runs a secure and efficient consensus protocol. The protocol enables each shard to reach an agreement on the blocks to propose. The consensus protocol is based on the idea of byzantine fault tolerance (BFT) with heavy optimizations of improving its efficiency by using the idea of employing EC-Schnorr multisignature in the PBFT protocol as developed in CoSi.
For better scalability, Zilliqa makes two conscious choices in the design of transaction sharding:
-
Zilliqa provides atomic transaction commits without involving cross-shard communication that is often costly and complex.
-
Zilliqa allows transactions to be processed asynchronously with the consensus processes of the blockchain. Zilliqa adopts a “reject-and-retry” mechanism to asynchronously process transactions as and when the majority of nodes become up-to-date.
With scalability as the main goal of Zilliqa, it proposes a new smart contract language Scilla that scales much better for a multitude of applications that range from automated auctions, shared economy to financial modelling. Beyond verifiability of security and correctness properties, Zilliqa’s smart contract language will run efficiently on a blockchain architecture with sharding. Moreover, it will enable sharding of computational resources in the blockchain network via an overlay above the consensus process, i.e., computational sharding. Computational sharding allows users of Zilliqa and applications running on Zilliqa to specify the sizes of consensus groups to compute for each of the subtasks. Each consensus group will then be tasked to compute the same subtask, and produce the results. The user specifies the condition on acceptance of the results, e.g., all in the consensus group must produce the same results, or 3/4 of them must produce the same results, etc.
Wallet that is connected to a wallet and Zilliqa testnet.
- Access Wallet and click
Create New Wallet->Click to Generate Address. And you will see the newly created wallet:
Remember to back up the private Key!
- And click
continueto download JSON keyfile that encrypted with passphrase:
- Now you can send the transaction on Wallet IDE:
See CONTRIBUTING.md for how to help out.
See LICENSE for details.