Feature flags

Overview

Feature flags are set on the featureFlags option when you create a Portal instance. They control optional behavior such as signing performance and backup options. You do not need to change your signing or wallet code when enabling flags—the SDK adapts automatically.

Enabling feature flags

Pass featureFlags in the Portal constructor:

import Portal from '@portal-hq/web'

const portal = new Portal({
  rpcConfig: {
    'eip155:1': 'https://mainnet.infura.io/v3/YOUR_KEY',
  },
  apiKey: 'YOUR_PORTAL_CLIENT_API_KEY',
  featureFlags: {
    usePresignatures: true,
  },
})

Available flags

`usePresignatures`

Type: boolean
Default: false
Description: When enabled, the SDK uses presignatures to improve signing latency. You do not call any presignature APIs yourself; the SDK generates presignatures in the background and uses them automatically when you sign (e.g. via portal.request() or portal.rawSign()).

What presignatures do Presignatures pre-compute part of the MPC signing protocol ahead of time. When the user triggers a sign (EVM transaction or raw sign), the SDK consumes one presignature if available and completes the signature faster. If no presignature is available, the SDK falls back to normal signing. Behavior is transparent to your app. When to enable Enable usePresignatures when you want lower latency on EVM signing without changing your integration. The SDK fills a small buffer after wallet creation or recovery and replenishes it as presignatures are used. Limitations

Applies only to SECP256K1 (EVM) signing. Solana (ED25519) signing is unchanged.
Presignatures are single-use; the SDK manages creation and consumption for you.

Example

const portal = new Portal({
  rpcConfig: { 'eip155:1': 'https://...' },
  apiKey: 'YOUR_API_KEY',
  featureFlags: {
    usePresignatures: true,
  },
})

// Signing uses presignatures automatically when available
const signature = await portal.request({
  chainId: 'eip155:1',
  method: 'personal_sign',
  params: [message, address],
})

`usePreGeneratedWallet`

Type: boolean
Default: false
Description: When enabled, portal.createWallet() attempts to claim a pre-generated wallet share instead of running the standard interactive MPC generation. This can make wallet creation faster. You do not need to change how you call createWallet.

What it does Normally, createWallet runs the interactive MPC key generation protocol in real time. With this flag enabled, the SDK first tries to claim a share from a pre-computed pool. If that fails with an HTTP 5xx response from the enclave, the SDK automatically falls back to the standard generation flow—the fallback is transparent, and createWallet resolves or rejects exactly as it would through the standard flow. Failures that aren’t a 5xx (for example, a malformed request or a network failure) are not retried and propagate as usual. When to enable Enable usePreGeneratedWallet when you want faster wallet creation without changing your integration. The resulting wallet is identical to one created through the standard flow. Limitations

This is a performance optimization only; it doesn’t change the API surface, the resulting wallet, or how backup/recovery works.

Example

const portal = new Portal({
  rpcConfig: { 'eip155:1': 'https://...' },
  apiKey: 'YOUR_API_KEY',
  featureFlags: {
    usePreGeneratedWallet: true,
  },
})

Reference

For all constructor options and the featureFlags property, see the Web SDK Reference.

Getting Started

SDKs

APIs

Integrations

Resources

Overview

Enabling feature flags

Available flags

`usePresignatures`

`usePreGeneratedWallet`

Reference

​Overview

​Enabling feature flags

​Available flags

​usePresignatures

​usePreGeneratedWallet

​Reference

Overview

Enabling feature flags

Available flags

`usePresignatures`

`usePreGeneratedWallet`

Reference