One-page overview for engineers and product owners: how Ledger Live integrations work, what integration paths exist, and links to official resources.
Ledger Live is Ledger’s cross-platform companion app (desktop & mobile) that lets users securely manage crypto assets using Ledger hardware devices. Integrations enable blockchains, apps, and services to appear natively inside Ledger Live so users can view accounts, sign transactions, and access Live Apps (dApps) with hardware security. :contentReference[oaicite:0]{index=0}
Add native support for a blockchain so users can create and view accounts in Ledger Live. This path requires working with Ledger’s teams and meeting submission requirements (including agreements & documentation). :contentReference[oaicite:1]{index=1}
Live Apps are web3 apps embedded into Ledger Live (Discover). They use Ledger Services Kit / Wallet API to talk to Ledger Live, enabling secure interactions and clear signing flows inside the app environment. This is the recommended path for dApps and browser-style integrations. :contentReference[oaicite:2]{index=2}
Device apps (C/Rust) run on Ledger hardware and are submitted through Ledger’s device app process. This path is for protocol-level signing that requires a device app or plugin. See the submission and deliverables guidance to be review-ready. :contentReference[oaicite:3]{index=3}
Pick Accounts, Live App, or Device App based on whether your integration needs on-device logic, in-app UX, or both. Use the official tutorials and example repos as a template. :contentReference[oaicite:4]{index=4}
Use the Ledger Services Kit (client) to build a Live App prototype and enable developer mode in Ledger Live to test in the Discover environment. Developer mode is accessible from Ledger Live settings (developer toggles). :contentReference[oaicite:5]{index=5}
Prepare clear documentation, install instructions, test accounts, and security notes per Ledger’s submission checklist. For device apps, include installable binaries and usage guides. :contentReference[oaicite:6]{index=6}
Implement clear signing (especially for EVM flows) so users can understand exactly what they are signing on-device. Ledger emphasizes explicit transaction details and consent. :contentReference[oaicite:7]{index=7}
Keep the device-side code minimal: perform sensitive cryptography on device, and avoid sending seeds or private keys to any remote service. Follow Ledger’s API contracts and best practices documented in the Developer Portal. :contentReference[oaicite:8]{index=8}