Cosmos wallet integration
This guide will walk you through the process of integrating Cosmos Wallets into your Para Modal and Para-enabled application, allowing you to onboard new users and connect with existing users who may already have external wallets like Keplr, Leap, Cosmostation and more.

​
Prerequisites

Before integrating wallet connections, ensure you have an existing Para project with the Para Modal set up. If you haven’t set up Para yet, follow one of our Framework Setup guides like this guide.

Looking for a lighter version?

​
Setting up Cosmos Wallets

Para integrates with leading Cosmos wallets. Our integration leverages a modified fork of the React library.

​
Supported Wallets

Para supports the following Cosmos wallets:
  • - A secure and user-friendly wallet for the Cosmos ecosystem
  • - The interchain wallet for the Cosmos ecosystem
  • - A comprehensive wallet and validator operator for Cosmos SDK-based blockchains
1

Import components

Import the necessary wallet connectors and chain configurations:
main.tsx
import { useState } from "react";
import {
  ParaProvider,
  ExternalWallet,
} from "@getpara/react-sdk";
import { cosmoshub, osmosis } from "@getpara/graz/chains";
import { type ChainInfo } from "keplr-wallet/types";
import { QueryClient, QueryClientProvider } from "@tanstack/react-query";
If you encounter type issues with @getpara/graz/chains,@alpha you’ll need to generate the chain files. You can:
  1. Add a postinstall script to your package.json:
{
  "scripts": {
    "postinstall": "graz --generate"
  }
}
  1. Or run npx graz --generate manually after installation
2

Configure chains

Set up your Cosmos chain configurations with the necessary RPC and REST endpoints. You can extend the existing chain configurations with your custom endpoints:
main.tsx
const cosmosChains: ChainInfo[] = [
  {
    ...cosmoshub,
    rpc: "https://rpc.cosmos.directory/cosmoshub", // Replace with your RPC endpoint
    rest: "https://rest.cosmos.directory/cosmoshub", // Replace with your REST endpoint
  },
  {
    ...osmosis,
    rpc: "https://rpc.cosmos.directory/osmosis",
    rest: "https://rest.cosmos.directory/osmosis",
  },
];
3

Configure the provider

Similar to the Cosmos and Solana providers, configure the ParaProvider component by wrapping your application content in the ParaProvider component. Pass in the required configuration props:
main.tsx
export const App = () => {
  const [chainId, setChainId] = useState<string>(cosmoshub.chainId);

  return (
    <QueryClientProvider client={queryClient}>
      <ParaProvider
        // ... rest of your provider config
        externalWalletConfig: {
          wallets: [ExternalWallet.Keplr],
          cosmosConnector: {
            config: {
              selectedChainId: chainId,
              multiChain: true,
              onSwitchChain: chainId => {
                setChainId({ selectedChainId: chainId });
              },
              chains: cosmosChains,
            },
            // grazProviderProps={}
          },
          walletConnect: {
            projectId: 'your_walletconnect_project_id',
          },
        }>{
        /* Your app content */}
      </ParaProvider>
    </QueryClientProvider>
  );
};
For the ParaCosmosProvider wrapping you don’t need to include a QueryClientProvider as the provider already includes one.

​
External Wallet Configuration

The ParaProvider is built on top ofand supports all of its configuration options.

​
External Wallets with Linked Embedded Wallets

You can also provision linked embedded wallets for external wallets. In this case, the external wallet would be the Para auth method for the user’s embedded wallet (instead of an email or social login). Embedded wallets would be created according to your API key settings. To enable this, you can include the createLinkedEmbeddedForExternalWallets prop to indicate which external wallets this setting should be applied to.

​
Advanced Provider Pattern

Setting up a dedicated provider component that encapsulates all the necessary providers and modal state management is considered a best practice. This pattern makes it easier to manage the modal state globally and handle session management throughout your application.

​
Server-Side Rendering Considerations

When using Next.js or other SSR frameworks, proper client-side initialization is crucial since web3 functionality relies on browser APIs. There are two main approaches:
  1. Using the 'use client' directive in Next.js 13+:
    • Add the directive at the component level where browser APIs are needed
    • Ensures the CosmosProvider component and its dependencies only run on the client
    • Maintains better code splitting and page performance
  2. Using dynamic imports:
    • Lazily loads the provider component
    • Automatically handles client-side only code
    • Provides fallback options during loading

​
Configuring the Para Modal

After setting up your providers you need to configure the ParaModal component to display the external wallets and authentication options to your users. You need to pass in the externalWallets and authLayout configuration options to the ParaModal component to control which of the wallets show in the modal that were specified in the provider configuration.

​
Set the modal props

paraModalConfig={{
  authLayout: ["AUTH_FULL","EXTERNAL_FULL"]
  theme: {
    mode: "light",
    foregroundColor: "#000000",
    backgroundColor: "#FFFFFF",
    accentColor: "#007AFF"
  }
  logo: yourLogoUrl
  // ... other modal config
}}
Modal prop options for customizing the Para Modal are included below. For advanced customization options, refer to .

​
External Wallet Verification

External wallet verification adds a verification step during external connection to ensure the user owns the wallet. Enabling this feature establishes a valid Para session, which you can later use in your app to securely validate wallet ownership. To enable this, set the following option on your externalWalletConfig of your ParaProvider: 
externalWalletConfig={{
  includeWalletVerification: true,
  ...REST_OF_CONFIG
}}

​
Connection Only Wallets

Connection only external wallets bypass all Para functionality (account creation, user tracking, etc.) when connecting an external wallet. To enable this, set the following option on your externalWalletConfig of your ParaProvider: 
externalWalletConfig={{
  connectionOnly: true,
  ...REST_OF_CONFIG
}}
Since connection only wallets bypass Para, most Para functionality will be unavailable. This includes linked embedded wallets, external wallet verification, on & off ramping, etc.

​
Examples

For an example of what the Para External Wallets Modal might look like in your application, check out our live demo:

Modal Designer

 For an example code implementation using Cosmos Wallets, check out our GitHub repository:

GitHub Repository

​
Next Steps

Now that you have integrated Cosmos wallets into your Para Modal, you can explore more advanced features like signing using the Para SDK with popular libraries like CosmJS.

Cosmos Integrations