← Protocols
Para (formerly Capsule)
Wallet / Auth·EVM · Solana · Cosmos

Para (formerly Capsule)

01Description

Embedded MPC wallets with email, phone, social, or passkey login. Non-custodial 2-of-2 MPC keeps a key share with the user device and a share with Para — no seed phrases, recoverable across devices. Capsule rebranded to Para in 2024; the SDK package namespace moved from `@usecapsule/*` to `@getpara/*`.

02Best for
  • 01embedded wallets
  • 02email / phone / social login
  • 03passkey-backed MPC
  • 04cross-app wallet portability
  • 05consumer + fintech onboarding
03Install
  • pnpm add @getpara/react-sdk
04Environment variables
VariableScopeDescription
NEXT_PUBLIC_PARA_API_KEYClientPara (formerly Capsule) API key from the Para developer portal.
05Prompt snippet
Use Para (formerly Capsule) for embedded MPC wallets. Wrap the app in `<ParaProvider paraClientConfig={{ apiKey: NEXT_PUBLIC_PARA_API_KEY, env: 'PROD' }}>` and render `<ParaModal />` for the auth UI. Read auth state with `useAccount()` / `useWallet()` hooks from `@getpara/react-sdk`, and sign with `useSignMessage()` or by getting a viem-compatible signer via Para's wagmi / ethers / Solana adapters. Manage user sessions and JWTs server-side; configure branding and supported login methods in the Para developer portal. Migrating from Capsule? Swap `@usecapsule/*` → `@getpara/*` and update the API key origin.
06Gotchas
  • Capsule rebranded to Para in 2024 — old npm packages under `@usecapsule/*` still work but are frozen; new projects must use `@getpara/*`. Search docs / Stack Overflow for both names.
  • MPC means the user share + Para share together sign — if Para's signing service is down, users cannot sign. Build retry / fallback UX and check Para's status page.
  • Recovery flows require email / passkey access. Users who lose both their device and their email account can lose the wallet — surface backup setup explicitly during onboarding.
  • Chain coverage varies by SDK module: EVM and Solana are first-class, Cosmos via separate adapters; non-EVM features (e.g. token metadata helpers) lag the EVM SDK.
  • Server-side trust: verify Para session JWTs in your backend rather than trusting a client-supplied wallet address.
07Alternatives