> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getpara.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Universal Wallets

> One wallet across your entire ecosystem. Users onboard once and use the same wallet in every connected application

With traditional embedded wallets, every application creates a separate wallet for each user. Users end up managing multiple wallets, moving assets between them, and repeating onboarding flows. For developers, this means every new user starts from zero: no history, no liquidity, no existing trust.

Para [universal embedded wallets](https://blog.getpara.com/universal-embedded-wallets/) solve this by associating wallets with **user identities** rather than individual applications. A user creates one wallet and uses it everywhere, across first party and partner apps, as well as the broader Para ecosystem.

<Note>
  Universal wallets are about accessing the same wallet from different applications, not transferring assets between separate wallets.
</Note>

## Benefits

**Faster onboarding:** Users who already have a Para wallet can start using new apps immediately. No wallet creation, no seed phrase backup, no friction.

**Richer user context:** Shared wallets mean shared transaction history and token balances. An application can offer better experiences when it knows what users already hold.

**Ecosystem play:** Build a network of interconnected apps where users move fluidly between experiences. A DeFi protocol, an NFT marketplace, and a portfolio tracker can all share the same wallet while each maintaining their own permission boundaries.

**Reduced support burden:** One wallet means one recovery flow, one set of backup devices, one identity to manage, regardless of how many apps the user connects to.

<Tip>
  We have also seen data-driven evidence that using a universal embedded wallet can boost retention and conversion for ecosystems. [Read more here](https://blog.getpara.com/para-gelato/).
</Tip>

## Key Components

<CardGroup>
  <Card title="Unified User Identity" icon="user-gear">
    Wallets are associated with user identities (typically email addresses) rather than individual applications.
  </Card>

  <Card title="Permissions Framework" icon="lock" href="/v2/concepts/permissions">
    Each application gets its own permission policy; users approve access per-app, and no app can exceed its granted scope.
  </Card>

  <Card title="Seamless Authentication" icon="key">
    Users log in to new applications with their Para credentials and automatically gain access to their existing wallet.
  </Card>

  <Card title="MPC Key Sharing" icon="key-skeleton">
    Para's MPC-based key management enables secure key sharing across applications without exposing the full private key.
  </Card>
</CardGroup>

## Benefits

<CardGroup cols={2}>
  <Card title="For Users" icon="user">
    * Access the same wallet across multiple applications without complex key exports
    * No need to manage multiple wallets or move assets between them
    * Consistent user experience across different platforms
    * Transparent permissions with granular access control per app
  </Card>

  <Card title="For Developers" icon="code">
    * Easier onboarding of users who already have a Para wallet
    * Access to richer transaction history and liquidity from shared wallets
    * Build multi-app experiences and ecosystems with ease
    * Request specific permissions tailored to each application's needs
  </Card>
</CardGroup>

## Universal Wallets vs. Traditional Approaches

| Feature                                                      | Third-Party Wallets | Traditional Embedded Wallets | Universal Embedded Wallets |
| ------------------------------------------------------------ | :-----------------: | :--------------------------: | :------------------------: |
| Portable across apps                                         |          ✔️         |                              |             ✔️             |
| Smooth in-app UX                                             |                     |              ✔️              |             ✔️             |
| Integrated with app functionality                            |                     |              ✔️              |             ✔️             |
| No browser extensions required                               |                     |              ✔️              |             ✔️             |
| Granular permissions per app                                 |                     |                              |             ✔️             |
| Cross-application capabilities without manual key management |                     |                              |             ✔️             |

## Security Features

<CardGroup>
  <Card title="Granular Permissions" icon="user-gear">
    Each application is granted specific permissions, limiting potential damage if one app is compromised.
  </Card>

  <Card title="Encrypted Key Sharing" icon="key-skeleton">
    The User Share is encrypted specifically for each application, preventing unauthorized access.
  </Card>

  <Card title="Signature Verification" icon="check">
    Each key sharing process includes a signature verification step to ensure authenticity.
  </Card>

  <Card title="No Full Key Exposure" icon="key">
    Thanks to MPC, the full private key is never exposed to any single application or stored in one place.
  </Card>
</CardGroup>

## How Wallet Portability Works

<Steps>
  <Step title="Initial Wallet Creation">
    A user creates a Para wallet in one application. The wallet is associated with their identity (e.g., email address).
  </Step>

  <Step title="Accessing New Applications">
    When the user wants to use their wallet in a new application, they log in with their Para credentials. The new application requests specific permissions, and upon approval, gains access to the user's wallet.
  </Step>

  <Step title="Secure Key Sharing">
    Para securely shares the necessary key information with the new application without exposing the full private key.
  </Step>

  <Step title="Ongoing Usage">
    The user seamlessly uses their wallet across all connected applications, with each app respecting its granted permissions.
  </Step>
</Steps>

## Example Use Cases

1. **DeFi Dashboard**: An app that aggregates data from multiple DeFi protocols could request read-only permissions across various chains.

2. **Consortium / Chain Ecosystem Wallets**: A Layer 1 or app chain ecosystem could offer a single wallet that works across all apps built on their network, with each app scoped to its own permissions.

3. **Cross-Chain DEX**: Might request permissions for swap transactions across multiple chains.

4. **Identity Credentials for Payments**: A wallet that holds verifiable credentials (KYC, accreditation, age verification) could authorize payments across merchant apps without re-verifying at each one.

## Universal Wallets FAQs

<AccordionGroup>
  <Accordion title="How does Para's multi-app architecture work?">
    Para's multi-app architecture allows the same wallet to be used across different applications while maintaining security. It uses a permissions scheme that specifies what types of transactions an application can perform and which ones require user approval. This is implemented through encrypted User Shares specific to each application and an allow-list mechanism managed by Para.
  </Accordion>

  <Accordion title="How can developers implement Para's universal embedded wallet feature?">
    Universal embedded wallets are achieved by associating wallets with user identities (typically email addresses) rather than individual applications, using MPC for secure key sharing across applications, implementing a permissions framework for granular access control, and providing seamless authentication when users access new applications. Developers can leverage these features through Para's SDKs and APIs.
  </Accordion>
</AccordionGroup>