Welcome to this presentation on how to integrate with Ledger Live using the Ledger Developer Portal. We will explore the architectures, integration paths, requirements, and best practices for bringing your blockchain, dApp, or service into Ledger Live.
Ledger Live is the flagship software companion for Ledger hardware wallets. By integrating with Ledger Live, developers can allow users to manage accounts, sign transactions, use decentralized apps (Live Apps), and access exchange or staking services — all within a secure, user-friendly environment.
The Developer Portal is Ledger’s official hub for documentation, tools, SDKs, and guides for integration. :contentReference[oaicite:0]{index=0} It offers structured “tracks” and modules such as:
The Portal also supports “Quickstart” guides and integration journeys to bring you from concept to production. :contentReference[oaicite:1]{index=1}
Ledger Live integrations fall broadly into three categories: Accounts / Blockchain support, Live Apps / Discover section, and Exchange / Service providers. :contentReference[oaicite:2]{index=2}
If you support a blockchain or protocol and want Ledger Live users to manage accounts (view balances, send/receive, etc.), you’ll use the “Accounts / Blockchain” path. :contentReference[oaicite:3]{index=3} The first step is to apply via the Ledger Live Integration application form. :contentReference[oaicite:4]{index=4}
After approval, you implement support in Ledger Live (desktop and mobile), integrating with core logic (via Ledger Live Common) to allow operations. :contentReference[oaicite:5]{index=5}
Live Apps (dApps embedded inside Ledger Live) are surfaced in the “Discover” section. :contentReference[oaicite:6]{index=6} There are two main integration models:
The integration is by invitation only—contact Ledger (e.g. via a Discover form) to propose your dApp. :contentReference[oaicite:9]{index=9}
If your project is an exchange, swap provider, staking or card service, you can integrate into Ledger Live as an “Exchange / Service Provider.” :contentReference[oaicite:10]{index=10} Ledger offers endpoints and guides for providers to embed buy/sell, swap, or other services. :contentReference[oaicite:11]{index=11}
To test integrations locally, you must enable Developer Mode in Ledger Live. :contentReference[oaicite:12]{index=12} To do this: go to Settings → About and click the Ledger Live version 10 times. :contentReference[oaicite:13]{index=13} Then you can import a local manifest and test apps before public deployment. :contentReference[oaicite:14]{index=14}
Integrating with Ledger devices (transport, signing, connection) is managed via the Device Management Kit (DMK) and corresponding signer kits. :contentReference[oaicite:15]{index=15} These include JS/TS libraries for transport (USB, BLE), managing device commands, and handling signing logic. :contentReference[oaicite:16]{index=16}
The Services Kit (Wallet API) enables your dApp to talk to Ledger Live, handle account information, and invoke signing via the wallet API. :contentReference[oaicite:17]{index=17} Internally, Ledger Live uses a React hook `useWalletAPIServer`, passing messages between the dApp’s webview and Live app host. :contentReference[oaicite:18]{index=18}
Ledger offers a step-by-step tutorial on building a Live App using Next.js, the Services Kit, and manifest setup. :contentReference[oaicite:19]{index=19} This covers scaffolding, project structure, communication via APIs, and UI integration. :contentReference[oaicite:20]{index=20}
For EVM and smart contract actions, Ledger enforces “Clear Signing,” which ensures that transaction methods and parameters are shown in a user-friendly format rather than raw hex. :contentReference[oaicite:21]{index=21} Your dApp must provide a manifest or metadata defining which contract calls are “clear signed.” :contentReference[oaicite:22]{index=22}
The Ledger review team will validate your app’s flow and compliance. :contentReference[oaicite:24]{index=24}
Device apps (for blockchain account support) must undergo a security audit (e.g. via Ledger’s partners). :contentReference[oaicite:25]{index=25} For Live Apps or Discover integration, Ledger will also review logic, manifest, UX, and security before approval.
Before proceeding with development, you typically need to sign an agreement with Ledger (for integration, support, backend access). :contentReference[oaicite:26]{index=26} Don’t start heavy dev work without prior approval by Ledger team. :contentReference[oaicite:27]{index=27}
The integration is built on a “webview ↔ wallet API server ↔ Ledger Live host” model. :contentReference[oaicite:28]{index=28} The Live App runs in a webview (embedded browser). The webview sends JSON RPC-style messages via `postMessage` to `useWalletAPIServer` hook in Live. :contentReference[oaicite:29]{index=29} The Live host (desktop or mobile container) listens, routes messages, handles UI events (sign prompts, account pickers), and returns responses. :contentReference[oaicite:30]{index=30}
The transport layer (over postMessage, or Electron WebView) conveys messages. The `uiHooks` map RPC methods (e.g. `account.request`, `transaction.sign`) to UI actions (open drawer, modals, etc.). :contentReference[oaicite:31]{index=31} Custom handlers can be defined for special methods via manifest. :contentReference[oaicite:32]{index=32}
The manifest is a JSON file declaring app metadata, allowed RPC methods, permissions, URL entry, and clear signing metadata. :contentReference[oaicite:33]{index=33} Ledger Live reads the manifest and uses it to validate and wire your app correctly. :contentReference[oaicite:34]{index=34}
Start by filling the relevant integration form (Accounts / Live Apps) via Ledger’s Developer Portal. :contentReference[oaicite:35]{index=35} Ledger’s team will review your proposal and scope integration.
Enable developer mode, import manifest, test flows locally, validate signing and UX. :contentReference[oaicite:36]{index=36} Use the Device Management Kit, Services Kit, and sample apps as guides.
For device apps or blockchain support, Ledger’s chosen auditor reviews the code. :contentReference[oaicite:37]{index=37} Ledger reviews Live App flows, UI, manifest, security, and compliance.
After approval, your app or protocol integration is published in Ledger Live (My Ledger, Discover, or Service sections). Ledger may roll out gradually (staging → production). :contentReference[oaicite:38]{index=38}
The Lido dApp is integrated into Ledger Live, enabling ETH staking with hardware wallet security. :contentReference[oaicite:39]{index=39}
Solana and Cosmos are supported blockchains in Ledger Live; their device apps and chain logic are integrated via the portal. :contentReference[oaicite:40]{index=40}
Projects can offer staking/earn functionality via a LiveApp in Earn or Discover sections. :contentReference[oaicite:41]{index=41} They must comply with clear signing, URL parameter schema (e.g. `action=stake, accountAddress`, etc.) :contentReference[oaicite:42]{index=42}
Integrating with Ledger Live via the Developer Portal opens your blockchain or application to a secure, widely adopted ecosystem. The main integration paths are:
The path involves proposal, development, security audit, manual review, and deployment. Use Ledger’s official tools (Device Management Kit, Services Kit, React hooks), and follow UX & security guidelines strictly.
If you want, I can also convert this into a slide deck (PowerPoint / Google Slides) or a printable PDF. Would you like me to do that?