What OAuth is to web2, DAuth Protocol is to web3
The next billion users who will enter Web3 will have a hard time entering without the empowerment of social accounts. The current OAuth protocol is based on centralized verification architecture and it brings the problem of centralization to Web3.
DAuth is not another authentication service provider, but rather a decentralized authentication protocol that replaces the OAuth protocol in Web3.0. DAuth will let Web3.0 platforms take advantage of users' social accounts without the sin of centralization that causes privacy leakage and data abuse.
DAuth uses TEE and ZK technologies to reconstruct the OAuth and SMTP protocols (widely used in Web2.0) to be like a normal OAuth flow but makes it trustless and private. DAuth also builds a decentralized network to make the process trustless and verifiable.
The main issues that DAuth Protocol solves are:
User social profiles that are authenticated in a centralized way are difficult to massively adopt in Web3 due to the need for trust when DID projects provide user profile aggregation services.
The suffering of social account information abuse due to the exposure of the combination of web2 and web3 accounts when SSO platforms store social login data.