Comment on page
Particle Network
Particle Network is a prominent Multi-Party Computation (MPC) powered Authentication and Wallet-as-a-Service Middleware utilized by Web3 developers. To enhance user privacy and security during social account authentication, Particle Network sought to integrate a decentralized and anonymous solution. The partnership with DAuth, a privacy-preserving OAuth alternative, allows Particle Network to provide an improved social login experience for its users while maintaining a focus on user privacy and data security.
- Ensuring user privacy and data security
- Reducing reliance on centralized identity providers
- Simplifying the integration process for developers
Particle Network partnered with DAuth, a decentralized, privacy-preserving version of OAuth, to upgrade its social account authentication services. The integration process involved the following steps:
- 1.User logs into DApp through DAuth using their Google account.
- 2.DAuth's OAuth engine securely obtains user information from Google via a private TLS connection.
- 3.User authenticates with Google and is redirected back to DAuth.
- 4.DAuth's OAuth engine receives an access token from Google through the private TLS connection.
- 5.Google sends user profile to the OAuth engine over the private TLS connection.
- 6.DAuth's ZK engine then generates a Zero-Knowledge (ZK) proof for the user.
- 7.The user uses the proof to access their wallets in the Particle Network.
- 8.Particle verifies the proof and allows the user to create or link a wallet.
.png?alt=media&token=04b3a1db-59c1-4fab-87ab-8f9c48202460)
- 1.User logs into DApp through DAuth using their Gmail account.
- 2.DAuth's OAuth engine securely obtains the user's email address via a private TLS connection.
- 3.The DAuth Email engine establishes a privacy channel and sends an email containing an authentication code to the user.
- 4.DAuth's OAuth engine receives an access token from Google through the private TLS connection.
- 5.Google sends the user profile to the OAuth engine over the private TLS connection.
- 6.DAuth's ZK engine then generates a Zero-Knowledge (ZK) proof for the user.
- 7.The user uses the proof to access their wallets in the Particle Network.
- 8.Particle verifies the proof and allows the user to create or link a wallet.
The steps marked in blue arrows are protected by the DAuth Enclave, making the DAuth node invisible to any user information. DAuth, as a private layer, helps to protect user privacy and keeps the Web2-Web3 association information of the user from being exposed.
Last modified 6mo ago