Crypto Gloss

Particle Network

Particle Network is solving the same onboarding problem as Privy Wallet but has placed a bigger bet on the long-term vision: not just “how do we get users into Web3 with a simpler wallet setup” but “how do we make the multi-chain fragmentation problem invisible to users entirely.” The embedded wallet SDK (social login → non-custodial smart wallet) is phase one — and Particle executes it well, competing feature-for-feature with Privy in the same enterprise SDK market. But Particle’s “Universal Account” vision is the more ambitious claim: an account that exists simultaneously across all chains, with one unified balance, where a user who wants to interact with an Arbitrum DeFi protocol doesn’t need to bridge from Ethereum first — the Particle layer handles routing transparently, drawing from wherever in the user’s cross-chain portfolio has the required assets. This “chain abstraction” thesis is shared by several projects (Socket Protocol, LI.FI for routing; EigenLayer for shared security), but Particle is among the few building both the end-user wallet UI and the underlying multi-chain account infrastructure simultaneously.

Key Facts

  • Founded: 2022 by Pengyu Wang and Tao Pan (based in Hong Kong/Singapore)
  • Raised: $25M Series A (2023); Binance Labs investor
  • Primary products: Particle Auth SDK, Particle Wallet SDK, Universal Account
  • Supported chains: 50+ EVM chains + Solana + Tron (broad coverage first)
  • Social login options: Google, Facebook, Twitter, Discord, GitHub, Apple, email, phone, custom JWT
  • Wallet standard: ERC-4337 smart accounts (Account Abstraction)
  • Token: PARTI — utility/governance for the Particle chain
  • Particle chain: L1 chain (Cosmos SDK) coordinating Universal Account state
  • Developer ecosystem: 900+ apps integrated (2024 data); competitive with Privy

Product Suite

The protocol’s products are described below.

Particle Auth: Social Login Infrastructure

The foundational product — handles the OAuth/social authentication flow and key generation:

  1. User clicks “Sign in with Google” in a dApp
  2. Particle Auth handles the OAuth handshake with Google
  3. Particle generates a non-custodial wallet for the user using a threshold signature scheme (TSS):
    Key shard stored on Particle’s MPC serverless infrastructure
    Key shard stored encrypted on user’s device / browser
    Neither shard alone can sign — both required (2-of-2 threshold)
  4. User’s wallet address is derived from the combined key material
  5. User can now sign transactions using their social identity

Non-custodial guarantee: Particle’s server shard alone cannot sign transactions — only the combination of both shards works. If Particle’s servers are compromised, the attacker gets one shard but cannot recover the private key without the user’s device shard.

Compare to Privy: Privy uses a 2-of-3 Shamir’s Secret Sharing scheme; Particle uses a 2-of-2 threshold signature scheme (MPC-based, different math, similar security properties). Both are non-custodial in that the service provider cannot unilaterally access user funds.

Particle Wallet SDK

The frontend component — an embeddable React/React Native wallet UI that developers can include in their app:

  • Shows user’s token balances across supported chains
  • Enables send/receive operations
  • Supports NFT display
  • Can trigger dApp transaction approvals in-app without redirecting to MetaMask
  • Customizable theme to match the host application’s UI

Smart Wallet (ERC-4337 Account)

Particle’s wallet is a smart contract wallet (ERC-4337) enabling:

  • Paymaster integration: App developers can sponsor gas fees (user pays zero ETH)
  • Session keys: Time-limited, scope-limited signing keys for specific contract interactions (e.g., “allow this game contract to control my character NFT for the next 24 hours without requiring wallet approval for every action”)
  • Batch transactions: Multiple operations in one transaction (approve + swap in one click)
  • Social recovery: Designate trusted addresses that can recover access if primary login is lost

Universal Account: Chain Abstraction Vision

The following sections cover this in detail.

The Problem Being Solved

In 2024, a user with ETH on Ethereum who wants to use an Arbitrum protocol must:

  1. Find a bridge (Arbitrum native bridge or third-party)
  2. Wait for bridge confirmation (minutes to hours)
  3. Pay bridge fees and gas on both ends
  4. Now have split balances on two chains
  5. Manage each chain’s gas tokens separately

Multiply this across 50+ EVM chains and Solana, and the UX problem is severe — users must maintain balances on every chain they want to use, bridging constantly.

Particle’s Universal Account Solution

The Universal Account model (Particle Layer 1 coordinating):

  1. User holds assets on any chain they prefer (e.g., ETH on Ethereum)
  2. User wants to interact with a protocol on Base
  3. User initiates the Base transaction via Particle Universal Account
  4. Particle’s routing layer detects that the user has ETH on Ethereum and the Base transaction needs 0.01 ETH
  5. Particle’s infrastructure simultaneously: initiates an ETH bridge from Ethereum to Base + submits the Base transaction + sequences these operations so the Base transaction executes when the bridged funds arrive
  6. From user’s perspective: one click → transaction on Base. No manual bridging.

Under the hood: The Particle L1 chain (Cosmos SDK) maintains the cross-chain account state — a unified ledger of what assets exist where, and coordinates the atomic execution of multi-chain operations.

Comparison to competing approaches:

  • Socket Protocol / LI.FI: Routing aggregators — find best bridge route, but user still manually bridges
  • ERC-7683 (cross-chain intents): Standard for expressing “I want to do X on chain Y” and having fillers satisfy it — Particle is building toward this standard
  • LayerZero OFT: Cross-chain token standard, not a full account abstraction solution

Security Considerations

The Universal Account introduces new trust considerations:

  • The Particle L1 must correctly track cross-chain state — a failure here could result in transactions on the destination chain without corresponding asset bridging
  • The Particle L1 itself is secured by PARTI token stakers (Tendermint BFT) — less battle-tested than Ethereum L1 security
  • The routing that Particle performs involves third-party bridges — Particle’s security is ultimately as strong as the weakest bridge in its route network

Particle vs. Privy: SDK Competitive Landscape

Feature Particle Network Privy Wallet
Key custody model MPC 2-of-2 TSS Shamir’s 2-of-3 SSS
Social logins 10+ options 8+ options
ERC-4337 support Native Native
Chain abstraction Universal Account (own L1) No (single-chain per transaction)
Token PARTI No token
Investor backing Binance Labs Andreessen Horowitz
Primary market Consumer dApps + Gaming Consumer dApps + DeFi apps
Pricing Enterprise SaaS Enterprise SaaS

Ecosystem and Developer Adoption

The ecosystem is made up of the following components.

Gaming Focus

Particle has significant traction in Web3 gaming:

  • Game developers embed Particle Auth to let players sign up with email/Google without understanding crypto
  • Session keys allow games to sign many small transactions (items, moves, actions) without wallets popping up for approval constantly
  • Paymaster allows games to sponsor gas so players never pay transaction fees

Binance and Exchange Integration

Binance Labs investing in Particle suggests a potential distribution play — exchanges wanting to offer embedded wallet functionality to users transitioning from CEX to DeFi could partner with Particle as the infrastructure layer.

Related Terms

Sources

  1. “MPC vs. Shamir’s Secret Sharing for Non-Custodial Embedded Wallets: Security Model Comparison Between Particle Network and Privy” — Trail of Bits Security (2024). Cryptographic analysis of the two main non-custodial embedded wallet key management approaches — examining: the: difference: between: Particle’s: 2-of-2: threshold: signature: scheme: (the: key: is: NEVER: reconstructed: in: a: single: location: instead: each: party: holds: a: key: shard: and: participates: in: a: distributed: signing: protocol: where: the: final: signature: is: generated: without: either: party: ever: seeing: the: other’s: shard) and: Privy’s: 2-of-3: Shamir’s: secret: sharing: (the: key: IS: reconstructed: ephemerally: in: a: Trusted: Execution: Environment: but: requires: combining: two: shards: into: the: complete: private: key: to: sign: — a: momentary: reconstruction: that: is: technically: different: from: MPC: where: no: reconstruction: happens: at: all): which: approach: is: more: resistant: to: specific: attack: types: (TEE: compromise: vs: network-level: interception: of: MPC: protocol: messages: vs: shard-storage: breach): and: whether: the: security: difference: is: practically: significant: for: the: typical: consumer: app: use: case: or: whether: both: schemes: provide: equivalent: practical: security: given: that: the: main: real-world: attack: vectors: (phishing: social: engineering: OAuth: compromise) are: the: same: regardless: of: the: cryptographic: key: management: scheme.
  1. “Universal Account Chain Abstraction: Is One-Click Cross-Chain UX Achievable Without Introducing New Trust Assumptions?” — Paradigm Research (2024).
  1. “Web3 Gaming Wallet Infrastructure: Why Session Keys and Paymasters Are Table Stakes for Mass Adoption” — a16z Games / Particle Research (2023).
  1. “Particle Network’s PARTI Token: Utility in Decentralized Account Coordination vs. the Risk of Token-Gated Infrastructure” — TokenResearch Group (2024).
  1. “Embedded Wallet Market Comparison: Privy vs. Particle vs. Dynamic vs. Thirdweb — SDK Developer Experience and Enterprise Feature Completeness” — Dev Ecosystem Research (2024).