Secure Digital Signature System
The private key used for a digital signature is distributed and stored separately on devices such as the Mobile App and RFID card. At the time of signing, the private key is restored from the shared values exists only for the instant that the signature is signed before it disappears again. Even if a phone or card is lost, the private key cannot be compromised. In addition, the shared values of the private key are never online, so there is no danger of being hacked. Even if your mobile phone gets lost, stolen, damaged, or you forget your PIN, you can easily restore access to your funds.
Ability To Run Your Own Private Chain
ZDL nodes are light enough that as well as running on cloud servers they can mounted on personal computers, smartphones, and even IOT devices, and are designed to be able to configure a large number of nodes. It can operate in private chain of any size from small to very large. Large-scale distribution protects information from external attacks and achieves the highest level of disaster resistance.
Currently, Bitcoin and Ethereum have around 10,000 operational full nodes. If the number of nodesof these networks is increased further, there is a concern that the performance will level off or decrease due to collisions caused by chain forks. ZAKZAK is designed to perform optimally with hundreds of thousands, millions, an infinite number of nodes. It can be bundled and installed with various apps to create a private chain for each community.
ZDL has a community ID. This community mechanism allows each community to have its own economic sphere, similar to the deployed addresses of ERC20. However, while ERC20 runs on Ethereum, ZDL allows each community to be implemented independently and form a community for any application they wish by assigning a community ID to the application. As mentioned above, there are endless possibilities for applications that involve information and value sharing.
Proof of Zone
In the ZDL approval process, a signature is issued by an approver for each zone. Adding transactions records using energy intensive mining, as in the Bitcoin blockchain, is not necessary. The amount of tokens is managed for each zone, and the movement of tokens within the zone is realized only by the signature of the sender and the approval node. Authorization in sending the token is completed with the signature of the approver in the zone in addition to the signature of the sender. Moving tokens across zones requires mutual recognition with the other zone. The size of the zone is configured according to the purpose of use, such as national scale, local scale, small community scale or family scale.
ZDL achieves a processing speed of about 1 to 1.5 millisecond per transaction (reference value measured with AWS t3.micro). It works very fast compared to Bitcoin’s tens of minutes, Ethereum’s minutes, and Ripple’s seconds. A ZDL node is implemented with a small core module of about 10MB and a data storage area for each address. Major cryptocurrency blckchain systems store all transactions on all nodes, along with much irrelevant data. For example, Ethereum nodes have a huge data volume of several hundred GB or more. With the ZDL, a general node holds only necessary information, so about 1/10,000 the size of an Ethereum node, and even an master node can be realized with about 1/100 the amount of information.
The ZAKZAK distributed ledger holds only transaction information related to its own node. Each node configures a zone to which it belongs. Regular transaction information is shared only locally within the zone. Only when transacting outside your own zone is transaction information is shared with other zones. Even in this case, only the zone of the two parties needs to be shared, not the entire network. Similar to a bank, this keeps transaction information local and shared with other only when there is a transaction with another bank.