What is Particle Network?

Welcome to Particle Network: The Intent-Centric Modular Access Layer of the Open Web.

Particle Network: The Modular Intent-Centric Access Layer of the Open Web

Particle Network's goal is to elevate users' experience within dApps while simplifying the task of building them, paving the way for mass Web3 adoption.

Launched in 2022, Particle Network's original product offering revolved around Wallet-as-a-Service, providing Web2 social logins and embedded wallets for dApps. Driving more than 15 Million wallet activations and 800+ dApp integrations, we are now evolving towards a comprehensive ecosystem of Web3 onboarding and usage solutions.

This page will give you a quick overview of our live products. We'll also touch on future releases within our stack to portray the full picture.

Particle Network's product suite.

Particle Network's product suite.

Our flagship product: Modular Smart WaaS

Particle's Modular Smart Wallet-as-a-Service (WaaS) tools allow developers to tap into MPC-TSS and social logins to enable self-custodial, dApp-embedded wallets accessible through users' Web2 accounts. It also empowers them to leverage the potential of ERC-4337 account abstraction, enabling a seamless, flexible experience.

In short, Modular Smart WaaS allows developers to interact natively with AA while directly tied to an instance of Particle’s WaaS. This fulfills the following critical points:

  • Seamless onboarding via WaaS & non-custodial key management: Particle’s existing implementation of WaaS features advanced MPC-TSS private key management. Combined with social authentication, this ensures that end users can be swiftly and securely onboarded –regardless of their level of familiarity– into Web3.
  • Leveraging AA’s flexibility without compromising application complexity: This empowers developers to build all kinds of applications, making the most out of AA’s capabilities. Particle’s AA-SDK enables very familiar mechanisms of interacting with smart accounts programmatically –such as familiar transaction structures, building, and account management– all handled seamlessly by the SDK. This results in a short path to start using AA with Particle’s WaaS, simplifying interactions with dApps.
  • AA modularity via WaaS: Particle’s AA SDK allows developers to approach AA modularly, plugging into their preferred smart account implementations, Bundlers, Paymasters, etc., with ease. As a WaaS provider, Particle can also be plugged into any initial/onboarding point within AA applications, even if they don’t natively use the AA SDK. As such, even non-native AA applications can leverage Particle’s WaaS for onboarding. This creates a wholly customizable building experience for native and non-native applications alike.

BTC Connect: The first account abstraction protocol for Bitcoin

Particle Network has released BTC Connect –the first EVM-compatible ERC-4337 AA protocol for Bitcoin, supported by leading players in the BTC universe.

We are deeply committed to spreading ERC-4337 account abstraction as a path to improve and simplify Web3's user experience (UX). As such, we've brought this standard to the Bitcoin ecosystem by combining Bitcoin L2s and ERC-4337 AA design. Users can enjoy all the UX benefits of AA on Bitcoin without the need for secondary interfaces (such as a MetaMask wallet). This enables them to control a smart account on an EVM-compatible Bitcoin L2 with a "regular" Bitcoin Wallet as its Signer, such as UniSat, Xverse, Leather, etc. As a result, a user can interact with these networks while holding either only native BTC or no assets at all (due to gasless transactions).

By implementing BTC Connect, developers can offer their users all of the benefits of account abstraction within EVM-compatible Bitcoin L2 chains, including session keys, account programmability, gasless interactions, batched transactions, etc., all while only using their native BTC wallet as a Signer.

Upcoming releases and realized vision

Particle's next evolutionary steps include the introduction of various solutions positioned to solve friction present after the initial onboarding process (which has already been streamlined through the two former solutions), this includes Omnichain Abstraction, a Confidential zkStack, and the Intent Fusion Protocol. These are supported by the Particle Chain and the Particle Network Token to round up the network's economic model.

Here's a quick outline of the different components of the Particle Network ecosystem. We conceptualize the above evolution as the combination of three pillars, their underlying tech, and an economic system holding them all together. For a deeper overview, visit their respective pages linked above.

The three pillars are:

  • Modular Smart Wallet-as-a-Service, explained above.
  • Particle's Confidential zkStack: We are improving upon the WaaS framework by tackling the issues of identity disclosures in WaaS products and the inherent transparency of the most popular L1 and L2 blockchains. By introducing zero-knowledge technology, we are able to provide two services: Confidential Login and Confidential Transaction. As a result, Particle will facilitate a system in which users’ data is wholly owned and managed by them.
  • The Intent Fusion Protocol: The Intent Fusion Protocol is a permissionless universal framework for expressing, transforming, and executing users’ goals. It can enable the creation of intent- and user-centric products, integrating a DSL (Domain Specific Language) to radically simplify the dApp development experience. Developers can use the Intent Fusion Protocol’s DSL to express user intents through Input and Output constraints instead of transactions, submitting them to a network of Solvers for on-chain execution. This relieves users of the burden of self-defining and executing all the steps to meet their goals and shifts developers' focus to simply outlining intents.

These pillars are supported by the following:

  • Omnichain Account Abstraction: This technology addresses two critical issues for Web3 adoption: The management and standardization of users’ accounts across chains and the cognitive load and friction of interacting with a complex multi-chain ecosystem. With Omnichain AA, users can have a unified Smart Contract Account address across different EVM chains. Omnichain AA additionally addresses the issue of facilitating compatibility with chains that are EVM-friendly but have different AA implementations and, as such, cannot be unified with ERC-4337 addresses. Similarly, in combination with third-party cross-chain messaging solutions (such as LayerZero, CCIP, Axelar, Connext, etc,) it can also facilitate seamless cross-chain interactions. To an extent, BTC Connect is the first released component of this vision.
  • The Particle Chain: Particle Network will use an independent zkEVM to act as the full-chain Storage database for smart accounts. Changes to an account's Storage are handled by the Particle Chain and eventually synchronized to the Account's local storage on other chains. This not only plays a role in Omnichain AA, but also acts as the zk-proof generator for the Confidential zkStack. The Particle Network Token serves as the native token of the Particle Chain.
  • The Particle Network Token: Particle's token acts as a unified gas unit to abstract elaborate gas mechanisms, simplifying the usage of smart accounts across chains. Inspired by previous successful economic models, Particle Network’s accrues value for the ecosystem and its stakeholders via network effects. This aligns the incentives of different types of stakeholders, helps accelerate the network’s growth, and ignites a virtuous value accrual cycle. The token also secures the Particle Chain via a Proof-of-Stake system and may eventually be used for governance.

Using Particle Network across different industries

📘

We are in the process of publishing different deep dives especifically for this section. As such, it will be constantly updated.

Particle's solutions can be attractive for all kinds of Web3 projects. However, to help developers understand how our technology stack might be leveraged for specific use cases, we are constantly creating industry-specific guides.

Whether you're merely interested in a given field or actively seeking to implement Particle's tools within it, we recommend exploring them for historical context, specific problems that can be addressed by integrating with us, and overall industry insights.

So far, we have dedicated deep dives for: