Custody Model and Regulatory Classification
Para uses a 2-of-2 Multi-Party Computation (MPC) architecture where the private key is split between the user’s device and Para’s hardware security modules. Because the full key is never held by any single party:- Classification: Para wallets are self-custodial / non-custodial. Your application does not take custody of user funds.
- Faster global expansion: Non-custodial architecture simplifies regulatory requirements, enabling faster launches in new markets without the licensing overhead associated with custodial wallet models.
- Audit posture: SOC 2 Type II compliant. Para regularly undergoes system-wide audits and penetration tests. Contact the Para team at security@getpara.com to request audit details.
- Data handling: All key material is encrypted at rest and in transit. User shares never leave the user’s device unencrypted.
For detailed security mechanisms and audit information, see Security & Trust Model.
How the System Fits Together
Para’s architecture has four pillars that work together to provide secure, portable, and controllable wallets:Key Management & Security
2-of-2 MPC key splitting, hardware secure enclaves, passkey-based authentication, and phishing-resistant signing.
Permissions & Access Control
Policy-based rules that control what each application can do with a user’s wallet. Server-side enforcement, default deny.
Wallet Recovery
Recovery secrets, backup devices, and key rotation ensure users never lose access to their assets.
Universal Wallets
One wallet across your entire ecosystem. Users onboard once and use the same wallet in every connected app.
Integration Patterns
Para supports multiple integration approaches depending on the product’s needs:Drop-in Modal
The fastest path to integration. Use Para’s pre-built modal component for wallet creation, login, and signing. Fully customizable styling and copy.
Custom UI
Build a fully custom wallet experience with Para’s headless SDK. Full control over every screen and interaction while Para handles the cryptography.
Server-side
Pre-generate wallets for users, sign transactions server-side, or build automated workflows. Ideal for onboarding users before they visit the app.
Supported Platforms and Chains
Frameworks
Para provides SDKs for all major platforms:- Web: React, Next.js, Vue, Svelte, vanilla JavaScript
- Mobile: React Native, Flutter, Swift
- Server: Node.js and REST API
- CLI: Command-line SDK for scripting and automation
Blockchain Networks
Para is designed to be blockchain-agnostic with native support for:| Network | Coverage |
|---|---|
| EVM chains | Ethereum, Polygon, Arbitrum, Optimism, Base, and all EVM-compatible networks |
| Solana | Native support |
| Stellar | Native support |
| Cosmos ecosystem | Native support via CosmJS |
Architecture FAQs
Can Para integrate with Account Abstraction (AA) systems?
Can Para integrate with Account Abstraction (AA) systems?
Yes. Para is designed to work with ERC-4337 (Account Abstraction) out of the box. This allows developers to leverage Para’s MPC security while taking advantage of AA capabilities like gas sponsorship, batched transactions, and custom validation logic.
What SDKs does Para offer for integration?
What SDKs does Para offer for integration?
Para offers SDKs for React, Next.js, Vue, Svelte, and vanilla JavaScript on the web; React Native, Flutter, and Swift for mobile; Node.js and REST API for server-side; and a CLI SDK for scripting and automation.
What blockchain networks does Para support?
What blockchain networks does Para support?
Para is blockchain-agnostic with native support for all EVM-compatible chains, Solana, Stellar, and the Cosmos ecosystem. Developers can integrate using popular libraries like ethers.js, viem, wagmi, CosmJS, and the Stellar SDK. For the full list, see the chain support documentation.