Go Live Checklist
A checklist to help you go live with the Para SDK.
Before going live, ensure you’ve completed the following steps:
Create a Developer Portal Account and Configure API Key
- 🔑 Request Access to the Developer Portal to manage your integration
- Create and configure a
BETAAPI Key for testing the integration
Quickstart
- Quickstart: Get the SDK or Modal Up and Running
- Check out the Examples or Troubleshooting sections for help!
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.jssigner 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
Security and Session Management
- 🔒 Ensure Security and Session Management works for your app
- OAuth and Social Logins: Decide what login methods you’d like to use
- Implement Session Management Logic
- Decide if you want to enable Two-Factor Authentication
Finishing Touches
- 🎨 Make Para your own with by adding the visual finishing touches
- Customize Para: Configure Branding, UI and more
Test and Go Live
- 🚀 Test and go live!
- Make a
PRODUCTIONAPI 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
BETAcan be used with any plan, including the free tier- This is the correct environment to use for local or staging builds
BETAusers 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
PRODUCTIONrequires a paid plan- This is the correct environment to use for release or production builds
PRODUCTIONusers can NOT be deleted, and have no per-project limit
Go Live Checklist
A checklist to help you go live with the Para SDK.
Before going live, ensure you’ve completed the following steps:
Create a Developer Portal Account and Configure API Key
- 🔑 Request Access to the Developer Portal to manage your integration
- Create and configure a
BETAAPI Key for testing the integration
Quickstart
- Quickstart: Get the SDK or Modal Up and Running
- Check out the Examples or Troubleshooting sections for help!
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.jssigner 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
Security and Session Management
- 🔒 Ensure Security and Session Management works for your app
- OAuth and Social Logins: Decide what login methods you’d like to use
- Implement Session Management Logic
- Decide if you want to enable Two-Factor Authentication
Finishing Touches
- 🎨 Make Para your own with by adding the visual finishing touches
- Customize Para: Configure Branding, UI and more
Test and Go Live
- 🚀 Test and go live!
- Make a
PRODUCTIONAPI 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
BETAcan be used with any plan, including the free tier- This is the correct environment to use for local or staging builds
BETAusers 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
PRODUCTIONrequires a paid plan- This is the correct environment to use for release or production builds
PRODUCTIONusers can NOT be deleted, and have no per-project limit