Vision and Ecosystem

Particle Network's road from a Wallet-as-a-Service tool to becoming a standalone layer for Web3.

Particle Network debuted as a Wallet-as-a-Service (WaaS) tool for developers. Our WaaS offering leveraged MPC-TSS and social logins to enable self-custodial, dApp-embedded wallets, accessible through users’ Web2 accounts. Then, as account abstraction (AA) debuted and became a fundamental component of Web3, we saw the opportunity to integrate it into our offering, adapting to upgraded account structures. We aimed to offer developers a seamless experience while aiming for maximum flexibility, and so Modular Smart WaaS was born.

800+ integrations and more than 15 Million activated users later, always focused on propelling Web3’s growth, we decided to shift our focus. We announced the release of our Intent Fusion Protocol and Confidential zkStack, supported by proprietary technology (i.e., the Particle Chain and Omnichain Account Abstraction), to encompass privacy, data sovereignty, and efficiency, enabling dynamics true to Web3’s ethos.

This section will give you a glimpse into our full vision: a deeply intertwined, synergetic ecosystem driving Web3’s adoption, empowering developers to create better products, and streamlining user experience across the board. We will cover the components of this vision and their underlying technologies and token economy, as well as their interactions and possible evolutionary steps.

Vision

Our vision begins with an understanding that, for Web3 to continue accelerating and attracting creativity and talent, our ecosystem must solve the infrastructure and design constraints holding it back.

With this goal in mind, and with Modular Smart WaaS already in the market, we saw that the next evolutionary step in our mission was to build the infrastructure to make Web3 interactions easier for developers and end-users alike. This gave birth to the ideas for our confidential zkStack and Intent Fusion Protocol. To unify these concepts and bring them to life, we conceptualized a transition to a token-centric economic model, powered by a new underlying technology, Omnichain Account Abstraction and the Particle Network Token.

Particle Network is uniquely positioned in the Web3 ecosystem, bridging dApps and end-users (a la B2B2C). Because of this, we are positioned to capture and distribute the value created by our contributions to Web3’s efficiency and privacy. This motivates us to complete an ecosystem design that meets the needs of:

  • End-users, who demand simplicity and security.
  • Developers, who require low development costs, high efficiency, and user acquisition effectiveness to succeed.
  • Public blockchains, which need to drive value and foster their ecosystems to grow.

As such, and from this privileged position, we set out to create an ecosystem that could align these values and create incentives for all stakeholders.

Particle's unique positioning as a bridge between dApps and end users.

Particle's unique positioning as a bridge between dApps and end users.

Components’ roles and synergies

The product offering of Particle Network aims to enhance the Web3 ecosystem through a deeply interconnected, synergetic approach. The key different components of this evolution include:

  • Modular Smart Wallet-as-a-Service (WaaS): This service allows developers to efficiently integrate account abstraction (AA) into their decentralized applications (dApps), enabling complex application construction while retaining flexibility.
  • BTC Connect: The first account abstraction protocol for Bitcoin, allowing users to create and manage a smart account on an EVM-compatible Bitcoin L2 chain via their native Bitcoin wallets, extending ERC-4337 AA to the Bitcoin ecosystem.
  • Intent Fusion Protocol: A permissionless, universal framework designed to simplify the dApp development experience. It enables developers to express user intents and outsource their execution, streamlining interactions with various Web3 protocols.
  • Confidential zkStack: This component enhances privacy by allowing users to verify their information without disclosing it and execute transactions privately, leveraging zero-knowledge technology.
  • Omnichain Account Abstraction: This technology facilitates a unified smart contract account address across different EVM chains. It also removes the friction for users conducting cross-chain transactions via the Particle Network Token.
  • Particle Chain: A proprietary zkEVM that acts as a full-chain storage database for smart accounts and plays a central role in Omnichain AA and the Confidential zkStack.
  • Particle Network Token: The key to the network’s economic model, serving multiple purposes like paying gas fees, generating cryptographic proofs, and participating in governance. It plays a significant role in capturing value for the network and its stakeholders.
Different Particle Network components are accessible at different stages of the user journey within Web3.

Different Particle Network components are accessible at different user journey stages within Web3.

Example: Possible user flow

The following diagram illustrates how the above components are used and interact within a typical user journey (for deeper explanations on these components, visit their respective pages):

Possible user journey with UI examples.

Possible user journey with UI examples.

A concrete user journey, therefore, could be as follows:

  1. A user lands on a social game they’re interested in, native to the zkSync ecosystem.
  2. Using a Google account, they access a wallet generated for them within three seconds. This process is fully privacy-preserving. The resulting wallet is directly built into the application.
  3. The user doesn't need to understand what gas or Layer-2 network bridges are. They can start collecting and trading in-game NFTs directly. Any additional on-chain needs are expressed through intents and instantly fulfilled by the underlying Solver network.
  4. The process above enables a natural onboarding path with an intuitive difficulty curve, as opposed to the current transaction-centric, user-driven setups.

This documentation contains dedicated deep dives for each component under the "Technology" section. These are also linked under their respective names above.

📘

This section is supported by a dedicated article on our blog. Visit it here.