Before going live, ensure youโ€™ve completed the following steps:

1

Create a Developer Portal Account and Configure API Key

  • ๐Ÿ”‘ Request Access to the Developer Portal to manage your integration
  • Create and configure a BETA API Key for testing the integration
2

Quickstart

3

Signing & On-Chain Connectivity

  • โ›“ Get signing & on-chain connectivity set up and make sure youโ€™re able to sign transactions
  • [EVM] Wagmi, Viem, Ethers
  • [Cosmos] Cosmos Integration: Add on the cosm.js signer or plug in one of our wallet adapters for popular libraries
  • Account Abstraction: Decide if youโ€™ll be using Account Abstraction with Para
  • Managing Users and Data: Connect Para users to your existing infrastructure
4

Security and Session Management

5

Finishing Touches

  • ๐ŸŽจ Make Para your own with by adding the visual finishing touches
  • Customize Para: Configure Branding, UI and more
6

Test and Go Live

  • ๐Ÿš€ Test and go live!
  • Make a PRODUCTION API Key (Note: youโ€™ll need to set up billing first)
  • Ping us if youโ€™d like help testing anything

Para Environments: BETA vs PRODUCTION

Para has two different environments. NOTE: Wallets are not shared across environments

BETA is intended for you to develop and test against, not for production builds or real users and funds

  • BETA can be used with any plan, including the free tier
  • This is the correct environment to use for local or staging builds
  • BETA users can be deleted for your convenience while testing, and is limited to 50 max users per project

PRODUCTION is intended for any real users/funds

  • PRODUCTION requires a paid plan
  • This is the correct environment to use for release or production builds
  • PRODUCTION users can NOT be deleted, and have no per-project limit