DPKI solves many usability and security problems that plague traditional public key infrastructure (PKI). DPKI has advantages in every stage of PKI life cycle. It makes it possible to boot online (a programming language compiler compiles itself with its own language and features) and provides a simpler and more powerful method to create SSL certificates. In use, it can help "Johnny" to finally encrypt, which benefits from the degradation of public key management to ensure scattered data storage. Finally, it also includes a mechanism to recover lost or damaged identifiers.
In modern society, third-party organizations (such as DNS registration service, ICANN, X.509 certification authority (CA) and social media companies) are responsible for creating and managing online identifiers and secure communication between them. Unfortunately, this design shows serious usability and security flaws. Online interaction is protected by secure public key transmission. These keys correspond to identities. Entities represented by these identities (called principals) use corresponding private keys to decrypt messages sent to them and prove that they sent messages (by signing them with private keys). PKI system is responsible for the secure transmission of public keys. However, the common X.509PKI and PKIX destroy the creation and secure transmission of these keys. Unlike PKIX, the goal of DPKI is to ensure that no third party can endanger the integrity and security of the whole system. Decentralize trust through technology so that geographically and politically different entities can acquire * * * knowledge about database status. DPKI mainly focuses on decentralized key-value data storage, which is called blockchain, but it can fully support other technologies that provide similar or more secure attributes.