Para

• Name: Para
• URL: https://www.getpara.com/
• Category: Wallet infrastructure / authentication / MPC key management / embedded-finance tooling
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Para is mostly embedded-wallet plumbing with auth and server-side policy wrapped around it. The 2-of-2 MPC pitch matters, but the real leverage is still in permissions, recovery, wallet-portability claims, and which money-movement flows Para makes easy to ship.
• What it does:
  • Provides embedded-wallet SDKs and APIs across web, mobile, server, and CLI environments for EVM, Solana, Cosmos, and other chain integrations
  • Uses a 2-of-2 MPC architecture that splits key material between the user device and Para’s HSM-backed cloud share, with biometric/passkey authorization for signing
  • Combines login and wallet creation through email, social, and passkey flows while aiming for cross-app wallet portability and “universal” embedded-wallet behavior
  • Enforces app-specific permissions policies server-side, with default-deny controls over message signing, transfers, contract calls, and deployments
  • Adds account-abstraction and money-movement surfaces including gas sponsorship, onramp hooks, and docs/examples for swaps and bridging
• Key claims:
  • Homepage copy markets Para as “the most comprehensive wallet and authentication suite for crypto developers and apps” and highlights embedded wallets, authentication, and bundled money movement
  • Architecture docs describe Para as “non-custodial embedded wallet infrastructure” with secure key management, cross-app portability, and policy-based access control
  • Key-management docs say Para uses a 2-of-2 MPC system where the private key is never assembled in one place, with the user share on-device and the Para share in cloud HSMs
  • Permissions docs emphasize that policies are defined per API key, enforced server-side on every transaction, and default deny when no rule matches
  • Official docs and SDK references show Para supporting account abstraction, multiple frameworks, passkey-first auth, and multi-chain integrations rather than a single-chain wallet niche
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Para’s homepage, docs index, architecture docs, key-management docs, permissions docs, SDK implementation supplement, and public GitHub organization; see ../whitepapers/para-primary-sources-2026-04-25.md.
• Sources:
  • https://www.getpara.com/
  • https://docs.getpara.com/
  • https://docs.getpara.com/llms.txt
  • https://docs.getpara.com/v2/concepts/architecture
  • https://docs.getpara.com/v2/concepts/key-management
  • https://docs.getpara.com/v2/concepts/permissions
  • https://github.com/getpara

Internal linkages

• Best upward comparison points: privy, turnkey, and coinbase-developer-platform.

Governance / control risk

• The leverage sits in MPC-share recovery, server-enforced permissions, wallet-portability limits, sponsorship defaults, and which partner rails Para bakes into the product surface.

• So the useful cut is simple: Para is a hosted wallet-control plane with app-facing auth, not a new account primitive.

• Last reviewed: 2026-05-25 UTC