O
O
OpenId3 Docs
Search
K

Particle Network

Overview

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.

Challenges

  • Ensuring user privacy and data security
  • Reducing reliance on centralized identity providers
  • Simplifying the integration process for developers

Solution for OAuth login with DAuth

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. 1.
    User logs into DApp through DAuth using their Google account.
  2. 2.
    DAuth's OAuth engine securely obtains user information from Google via a private TLS connection.
  3. 3.
    User authenticates with Google and is redirected back to DAuth.
  4. 4.
    DAuth's OAuth engine receives an access token from Google through the private TLS connection.
  5. 5.
    Google sends user profile to the OAuth engine over the private TLS connection.
  6. 6.
    DAuth's ZK engine then generates a Zero-Knowledge (ZK) proof for the user.
  7. 7.
    The user uses the proof to access their wallets in the Particle Network.
  8. 8.
    Particle verifies the proof and allows the user to create or link a wallet.

Solution for email login with DAuth

  1. 1.
    User logs into DApp through DAuth using their Gmail account.
  2. 2.
    DAuth's OAuth engine securely obtains the user's email address via a private TLS connection.
  3. 3.
    The DAuth Email engine establishes a privacy channel and sends an email containing an authentication code to the user.
  4. 4.
    DAuth's OAuth engine receives an access token from Google through the private TLS connection.
  5. 5.
    Google sends the user profile to the OAuth engine over the private TLS connection.
  6. 6.
    DAuth's ZK engine then generates a Zero-Knowledge (ZK) proof for the user.
  7. 7.
    The user uses the proof to access their wallets in the Particle Network.
  8. 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.