Particle Network

• Name: Particle Network
• URL: https://particle.network/
• Category: Chain abstraction / smart-account / wallet-infrastructure platform
• Tags: ethereum-ecosystem
• Summary: Particle Network is best cataloged as a chain-abstraction and universal-liquidity stack rather than as a generic wallet kit. The useful mechanism is one account, one balance backed by solver-fronted routing, repayment, and account middleware. Keep this note on Universal Accounts, Universal Liquidity, and the coordination design itself; the named operator boundary for hosted onboarding, current liquidity operation, and the developer-service shell now lives separately in particle-network.
• What it does:
  • Provides Universal Accounts that let apps present users with one account and one balance across multiple chains instead of separate per-chain wallets and manual bridging
  • Uses a Universal Liquidity model in which solvers front liquidity and repay themselves from a user’s balances across chains after the user signs a single authorization
  • Offers account-abstraction infrastructure including bundlers, paymasters, session keys, gas sponsorship, and SDKs for web and mobile integrations
  • Supports social-login onboarding so apps can create and manage user wallets behind familiar Web2-style authentication methods
  • Publishes extensive developer docs, llms.txt indexes, network-coverage references, example repos, and audit references that function as the main source of truth more than any classic whitepaper
• Key claims:
  • Official docs describe Particle’s mission as making Web3 “retail-ready” by solving multi-chain fragmentation with “one account, one balance, any chain”
  • Universal Accounts docs say Particle automatically routes liquidity, bridges assets, and manages cross-chain logic through Universal Liquidity so users do not need to bridge manually
  • Universal Liquidity docs say solvers provide destination-chain liquidity up front and later recoup repayment from the user’s balances across chains based on signed authorization
  • Official docs position Particle as both a wallet/onboarding provider and an account-abstraction stack, not merely a chain-abstraction frontend
  • Public docs and GitHub materials show a broad operating surface including AA RPC methods, SDKs, audits, examples, and an MCP server for documentation access
• Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Particle Network’s homepage, docs portal, llms.txt index, product-overview docs, Universal Accounts and Universal Liquidity docs, audit references, and official GitHub presence; see ../whitepapers/particle-network-primary-sources-2026-04-25.md.
• Sources:
  • https://particle.network/
  • https://developers.particle.network/
  • https://developers.particle.network/llms.txt
  • https://developers.particle.network/intro/what-is-particle-network
  • https://developers.particle.network/intro/universal-accounts
  • https://developers.particle.network/intro/what-is-ul
  • https://developers.particle.network/intro/more/audits
  • https://github.com/Particle-Network

Internal linkages

• Company boundary for the hosted onboarding, docs, and current liquidity-operation shell: particle-network.
• Best comparison points: onebalance, across, and privy.

Protocol / company boundary

• Keep this note on the mechanism layer: Universal Accounts, Universal Liquidity, solver-fronted execution, repayment semantics, gas abstraction, and the broader one account, one balance coordination thesis.
• Use particle-network when the sharper question is who currently operates the liquidity pools, packages social-login onboarding, owns the docs and developer-tool terms, or defines the easiest hosted path most integrators inherit first.
• That split matters because Particle can describe a reusable chain-abstraction design while the live day-1 product shell still routes through one named operator boundary.

Control surface

• The leverage sits in solver admission, repayment rules, Particle-operated liquidity pools, sponsored-execution defaults, and how the stack decides which route and balance to touch.

• Keep the company layer visible too: particle-network is the cleaner note once the question becomes hosted onboarding, developer-surface authority, legal/privacy shell, or present-tense liquidity operation rather than mechanism design.

• Read this as a chain-abstraction mechanism with a still-important operator shell, not as a clean baseline account layer.

• Last reviewed: 2026-08-13 UTC