Documentation Index
Fetch the complete documentation index at: https://developers.fireblocks.com/llms.txt
Use this file to discover all available pages before exploring further.
Initialize the EW SDK
- Initialize a new
EmbeddedWalletSDK instance - Call
ew.assignWallet()- the wallet is created if doesn’t exist yet.
authClientId: Your OAuth client ID configured in the Fireblocks ConsoleauthTokenRetriever: Provides a method to fetch the end user’s IDP token (viagetAuthToken()).reporting(optional): When enabled, the SDK sends error reports to Fireblocks to help diagnose failures.
Initialize the EW Core SDK
Generate adeviceId. This value is unique per SDK instance.
Each embedded wallet (EW) walletId correlates to one or more deviceId:
deviceId: The device ID associated with the end user and the Embedded Wallet.messagesHandler: The outgoing message handler.keyStorage: The key storage handler.eventsHandler(optional): The events handler.
Example
Note
All SDKs (JS, Android, iOS) can be initialized with one of the following environments: sandbox, production.The environment initialization value will affect the selection of the correct root certificate in the SDK. If your tenant resides in the production environment (whether it be testnet or mainnet), then choose production. If you are exploring NCW using the sandbox, then simply choose sandbox.Device ID
AdeviceId is a UUID you generate to uniquely identify a client device. It must be provided when initializing the EW Core SDK. Store the deviceId locally and reuse it on every SDK initialization for that device.
When to generate a new deviceId:
- New wallet on a new device.
- Adding a new device to an existing wallet.
deviceId:
- Same device and wallet — retrieve from local storage.
- Recovering a lost device using the last backup.
deviceId used during the last backup. You can retrieve this info via ew.getLatestBackup().
Note
If a wallet is fully initialized with a givendeviceId, its key share can only be transferred to a new device via the recovery procedure. After recovery, the original device will no longer be able to participate in MPC operations.