Skip to main content
Wallet pregeneration means creating a wallet before a Para user owns it. The wallet is keyed by an identifier, such as an email, phone number, OAuth ID, or custom ID. The pregenerated wallet can later be claimed by the user associated with that identifier, transferring ownership to them if your application permits it. To claim a wallet, the wallet’s user share must be loaded into the client and the wallet identifier must match the user’s authenticating identifier.
If you create a wallet with an internal custom ID, store your own mapping from that ID to the future claimant. Before returning the user share for claim, update the wallet identifier to the identifier the user is authenticating with.

​
Choose Your Approach

Use REST API by default for new server-created or pre-created wallet integrations. Your backend creates wallets, Para persists shares server-side, and signing happens over HTTP with your API key.

​
SDK Integrations

Use SDK pregen when your flow depends on direct user-share control, SDK ecosystem signing before claim, or client/Portal private-key export paths. SDK pregen is still valid for those cases, but it is no longer the default for new server-side wallet creation.

​
Common use cases

  • Mass User Onboarding: Create wallets for your existing user base or email lists instantly
  • Social Integration: Generate wallets based on social identifiers like Twitter followers
  • Agent-Owned Wallets: Allow AI agents or bots to create and manage wallets for specific functions
  • Server-Side Operations: Create app-managed wallets to perform operations on behalf of users
  • Airdrops and Rewards: Preload funds or NFTs into wallets that users can claim later
  • Staged Onboarding: Let users experience your application before formally creating their wallet
If you already have SDK pregen wallets and want to move server-side signing to REST, use the migration guide.