para-primary-sources-2026-04-25

Para primary-source snapshot

Fetched: 2026-04-25 UTC

1) Official homepage

Source: https://www.getpara.com/

Selected excerpts from the official site:

Para is the most comprehensive wallet and authentication suite for crypto developers and apps.

Build, customize, and scale with embedded wallets, authentication, and money movement.

On and off ramp, send, bridge, and swap via APIs that abstract liquidity, compliance, and cross-chain complexity.

Additional signals from the homepage:

• Para is positioning itself as more than wallet-auth middleware by foregrounding money movement and fintech use cases alongside wallet creation
• The homepage suggests Para wants to bridge crypto-native and fintech onboarding patterns rather than serve only one of those audiences

2) Official docs introduction

Source: https://docs.getpara.com/

Selected excerpts from the docs:

Para is the most comprehensive wallet and authentication suite for crypto and fintech developers.

Documentation Index Fetch the complete documentation index at: https://docs.getpara.com/llms.txt

Additional signals from the docs:

• The docs are a primary source of truth for Para’s product surface and implementation detail
• The docs frame Para explicitly for both crypto and fintech builders

3) llms.txt documentation index / SDK supplement

Source: https://docs.getpara.com/llms.txt

Selected excerpts/signals from the docs index:

Non-custodial embedded wallet infrastructure using MPC for building embedded wallet integrations across web, mobile, and server platforms supporting EVM, Solana, and Cosmos chains.

All @getpara/* packages must use the same version as each other.

Account Abstraction Companion Deps … Alchemy, ZeroDev, Gelato, Thirdweb, Rhinestone, Porto

Additional signals from the docs index:

• Para’s llms.txt is unusually detailed and functions more like an implementation supplement than a simple sitemap
• The index reveals substantial work around multi-framework SDKs, account abstraction, authentication, signing, connectors, and configuration

4) Architecture docs

Source: https://docs.getpara.com/v2/concepts/architecture

Selected excerpts from the docs:

Para provides non-custodial embedded wallet infrastructure: secure key management, cross-app portability, and policy-based access control

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.

Para wallets are self-custodial / non-custodial.

Additional signals from the docs:

• Para explicitly ties its non-custodial claim to architecture and regulatory classification, not just marketing language
• The architecture docs also place universal wallets, permissions, recovery, and account abstraction at the center of the product story

5) Key-management docs

Source: https://docs.getpara.com/v2/concepts/key-management

Selected excerpts from the docs:

How Para’s 2-of-2 MPC system protects private keys across generation, signing, and recovery

The two key shares are: User Share … Para Share

Para uses the DKLS19 MPC algorithm

To sign a transaction, both shares participate in a cryptographic signing ceremony that produces a valid signature without ever reconstructing the full private key.

Additional signals from the docs:

• Para’s docs are concrete about the cryptographic model, including user/device share, Para cloud share, secure enclaves, and WebAuthn/passkey bridging
• The DKLS19 mention and open-source implementation reference make the security docs stronger than generic “MPC wallet” marketing copy

6) Permissions docs

Source: https://docs.getpara.com/v2/concepts/permissions

Selected excerpts from the docs:

Control exactly what each application can do with a user’s wallet: scoped, transparent, and enforced server-side

Policies are defined per API key, enforced server-side on every transaction, and presented to users as plain-language consent items.

Default deny: any action not explicitly allowed in the policy is blocked

Additional signals from the docs:

• Para’s permissions system looks like a meaningful differentiator for cross-app embedded-wallet deployments and compliance-sensitive use cases
• The plain-language scopes plus immutable policy-versioning model are useful signals that Para is thinking about consent and app isolation, not only signing APIs

7) Official GitHub organization

Source: https://github.com/getpara

Selected excerpts/signals from the org page:

Para is a simple web3 signing solution that enables you to build secure cross-application embedded wallets using social logins and passkeys.

The Para Docs are the best place to view a full reference.

We also have a variety of Starter Templates and Per-Framework Examples

Additional signals from the org page:

• The GitHub organization reinforces Para’s cross-application and passkey-centered wallet positioning
• Public starter templates and examples support the view that Para is actively shipping for developers across frameworks rather than hiding the product behind sales-led integration only

Notes

• This pass did not locate a classic Para whitepaper or litepaper from official sources.
• The strongest primary materials were the homepage, docs index / SDK supplement, architecture docs, key-management docs, permissions docs, and GitHub organization.
• Para appears best categorized as a wallet / auth / MPC key-management platform with unusually explicit policy controls and bundled money-movement ambitions.