Feature Flags

​

Overview

​

Example Usage:

import PortalSwift

// Initialize Portal with custom feature flags
let portal = try Portal(
  "CLIENT_API_KEY_OR_CLIENT_SESSION_TOKEN",
  featureFlags: FeatureFlags(
    useEnclaveMPCApi: true
  )
)

​

Available Feature Flags

​

1. useEnclaveMPCApi

• Type: Bool?
• Default: nil (disabled)
• Description: Enables the use of the Enclave MPC API for signing transactions. When enabled, MPC operations are executed server-side in a secure AWS Nitro Enclave, ensuring consistent and faster signing times.

1. Encrypted Memory: All data processed in the enclave is encrypted and inaccessible to anyone, including Portal employees.
2. Verified Execution: Users can cryptographically verify that their request was handled in a secure enclave using signed measurements.

import PortalSwift

// Initialize Portal with the Enclave MPC API enabled
let portal = try Portal(
  "CLIENT_API_KEY_OR_CLIENT_SESSION_TOKEN",
  featureFlags: FeatureFlags(
    useEnclaveMPCApi: true
  )
)

​

2. usePreGeneratedWallet

• Type: Bool?
• Default: nil (disabled)
• 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.

• Enclave-side fallback—invisible to the SDK. If the pool is empty or a share can’t be claimed, the enclave generates the shares on demand and returns them in a normal 200 OK response. The SDK can’t tell the two responses apart, and it doesn’t need to: the resulting wallet is the same either way, and generation still happens server-side rather than on the device.
• SDK-side fallback—only on an HTTP 5xx. If the enclave responds with a 5xx, the SDK falls back to running the standard on-device DKG protocol. The fallback is transparent, and createWallet returns or throws exactly as it would through the standard flow.

• This is a performance optimization only; it doesn’t change the API surface, the resulting wallet, or how backup and recovery work.
• The SDK only retries on the device when the enclave returns an HTTP 5xx. Other errors, including network failures, propagate normally—so a misconfigured API key, or calling createWallet for a client that already has a wallet, produces a failed wallet creation rather than a slow one. Keep your existing error handling around createWallet.
• Because the enclave generates on demand when the pool is empty, enabling this flag doesn’t guarantee the share came from the pool—only that wallet creation didn’t run on the device.

import PortalSwift

// Initialize Portal with pre-generated wallets enabled
let portal = try Portal(
  "CLIENT_API_KEY_OR_CLIENT_SESSION_TOKEN",
  featureFlags: FeatureFlags(
    usePreGeneratedWallet: true
  )
)

do {
  let addresses = try await portal.createWallet()

  print("My Portal EVM address: \(addresses.ethereum)")
  print("My Portal Solana address: \(addresses.solana)")
} catch {
  // The SDK already retried on the device if the enclave returned a 5xx, so
  // reaching this point means the failure was not retryable—most commonly
  // because this client already has a wallet.
  print("Failed to create wallet: \(error)")
}

// A single curve's share. `share` is the base64-encoded serialized MPC share.
public struct GenerateApiCurveShare: Decodable {
  public let share: String
  public let id: String
}

public struct GenerateApiResponse: Decodable {
  public let secp256k1: GenerateApiCurveShare
  public let ed25519: GenerateApiCurveShare

  // The enclave returns uppercase curve names on the wire.
  enum CodingKeys: String, CodingKey {
    case secp256k1 = "SECP256K1"
    case ed25519 = "ED25519"
  }
}