Skip to main content
Portal provides MPC wallets and dApp connections for organizations and their users.

To integrate Portal, an organization adds a client library to their mobile app and a few server API endpoints.

Basic setup

The basic Portal setup consists of three packages:
  • @portal-hq/core - The core Portal library
  • @portal-hq/keychain - An adapter for storing MPC signing shares on-device
  • @portal-hq/gdrive-storage - An adapter for storing MPC backup shares off-device
These pieces allow you to initialize Portal in your app.

Authentication

Follow this guide to gather all of the credentials you need to Authenticate to Portal.

Installation

Dependency linking

Because these packages have native module dependencies there is some additional linking required to make it work with your React Native project. Explicitly install the native module packages in your project.

MPC

The core Portal library relies on a native module to support MPC behaviors. In order to enable this functionality, you must properly link Portal’s MPC client to your React Native project.
To learn more about how to use Portal MPC, see: @portal-hq/core

Initializing Portal

When gatewayConfig is omitted, the SDK automatically routes RPC traffic through Portal’s managed gateway for 10 built-in chains. No third-party RPC provider setup is required to get started.
The 10 built-in chains covered by the default gateway config are: Ethereum Mainnet (eip155:1), Ethereum Sepolia (eip155:11155111), Polygon Mainnet (eip155:137), Polygon Amoy (eip155:80002), Base Mainnet (eip155:8453), Base Sepolia (eip155:84532), Monad Mainnet (eip155:143), Monad Testnet (eip155:10143), Solana Mainnet (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp), and Solana Devnet (solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1). Polygon Mumbai (eip155:80001) has been removed — use Polygon Amoy (eip155:80002) instead.

Custom RPC configuration

If your app needs chains beyond the 10 built-in ones, or you prefer to use your own RPC provider, pass a gatewayConfig object. When provided, it is used exactly as supplied — the SDK does not merge defaults into a custom config.
Requests to Portal’s managed gateway automatically include your apiKey as a Bearer token — no extra setup required. Custom RPC URLs (e.g. Infura, Alchemy) are called without it, since third-party providers require their own credentials.
Optional Logging ConfigurationYou can enable logging for debugging and monitoring by setting the logLevel parameter. For advanced logging configuration, including custom loggers and external service integration, see Logging Configuration.
For more information on how to use the Portal class, see: @portal-hq/core

Next Steps

Now that you’ve initialized your Portal instance, you can generate a wallet!
If you are using Client Session Tokens (CSTs), this hint is for you.When your user’s CST expires, all Portal SDKs will throw an error on the next MPC Operation the user makes (e.g. creating a wallet, backing up a wallet, recovering a wallet, or signing). That error will include a code SESSION_EXPIRED in the SDK methods, which you can use as an indicator to refresh your CST.