Skip to main content

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.

​
Before you begin

Before starting your Fireblocks Embedded Wallet (EW) implementation, it’s important to distinguish between the SDKs involved:
  • The Fireblocks EW client SDKs (also referred to as the EW SDK and the EW Core SDK).
  • The Fireblocks SDK.
Each serves a different purpose:
  • The EW SDKs consist of platform-specific SDKs used in your client app implementation
  • The Fireblocks SDK can be used for administrative EW operations and is initialized with an API user’s private key. It can be used with one of two roles: EW Admin and EW Signer.

​
Embedded Wallet glossary

  • EW: Embedded Wallet.
  • Customer: A business entity using Fireblocks’ services.
  • Backend: Optional server-side logic operated by the customer. Not required in the current architecture. Learn more about backend use cases.
  • End User: Fireblocks customers’ end-user (i.e., the consumer).
  • Device ID: A logical identifier representing an entity that stores a user key share and can participate in MPC operations for a given wallet. There is a unique identifier per SDK instance.
  • Physical Device ID: A logical identifier representing a single mobile or web device.
  • Passphrase: An end-user passphrase created for backup encryption.
  • Master Key: A unique master key used for key share derivation.
  • Key Share: One-half of the master key. Key Share #1 is at Fireblocks servers, and Key Share #2 is on the client side.