Ledger® Live Wallet – Getting Started™ Developer Portal

Why build for Ledger Wallet?

Ledger provides a secure, hardware-backed platform and a companion app (Ledger Wallet, formerly known as Ledger Live) that millions of users rely on to manage crypto assets. Integrating with Ledger gives your application a strong security posture, a familiar user interface for users with Ledger devices, and access to distribution channels inside the Ledger ecosystem such as the Discover/Live Apps section. If you want to support hardware-backed signatures, account management, or embed a “live” experience that runs inside Ledger Wallet, the Developer Portal is the place to begin.

Reference: Ledger's official Developer Portal. :contentReference[oaicite:0]{index=0}

What you’ll find in this guide

• High-level overview of Ledger Wallet and how it relates to Ledger devices and apps
• Where to download the app & SDKs and where to read the docs
• Example integration patterns (Web + Native + Live App)
• Submission tips for publishing Live Apps and Device Apps

Step 1 — Install Ledger Wallet and set up a device

Download & verify

Always download Ledger Wallet (the official Ledger Live successor) from Ledger’s official domain. Install the app for your platform and follow the onboarding prompts to initialize or restore a Ledger device. Never enter your recovery phrase into a computer or mobile app — Ledger will never ask for your seed phrase.

References: download and support pages. :contentReference[oaicite:1]{index=1}

Step 2 — Explore the Developer Portal & documentation

Core docs

The Developer Portal contains documentation for device interaction, Live Apps (Discover), Wallet API clients, submission requirements, and a submission checklist for publishing apps. Start at the "Documentation" section and follow the getting-started guides for the specific integration you plan to build (web app connected to a Ledger signer, a Live App embedded inside Ledger Wallet, or a Device App running on the device itself).

Reference: device interaction and Wallet API docs. :contentReference[oaicite:2]{index=2}

Step 3 — SDKs, examples & GitHub

Where the code lives

Ledger maintains several official repositories — including the Ledger Live monorepo — with reference implementations, SDKs and example Live Apps. Clone the official repos to explore how Ledger interacts with crypto protocols, how the wallet manages accounts, and how Live Apps are packaged.

Reference: official GitHub repositories. :contentReference[oaicite:3]{index=3}

Integration patterns (practical)

Web app + Ledger extension / Wallet

For web apps that want to interact with a user's Ledger signer, you can either communicate via the Wallet API client targeted at Live Apps or connect to the Ledger device using standard transport libraries (WebUSB, WebHID) and the Ledger device protocol. The Wallet API client is the recommended path for apps that will be embedded inside Ledger Wallet's Discover/Live Apps area.

Live Apps

Live Apps run inside Ledger Wallet and have a sandboxed environment with controlled access to device features through the wallet. Follow the Live App packager instructions and adhere to the submission requirements so users can discover your app in Ledger Wallet.

Device Apps (on-device)

If you need a companion on-device app (for protocol signing that must run on the device), follow the device-app guidelines, prepare the deliverables (documentation, installation instructions, tests) and submit through the Developer Portal submission flow.

Example: minimal discovery link (snippet)

How to declare an app manifest (concept)

That manifest is illustrative — always consult the official manifest schema from the Developer Portal before packaging and submitting your Live App.

Submission checklist & best practices

Documentation & UX

Provide a short introduction of what your app does, clear installation steps, recovery guidance, screenshots, and a privacy/security section. Ledger’s submission docs detail the required deliverables for review.

Security

Be explicit about what your app needs (signing, account read-only, etc.). Never request a user's recovery phrase. Use hardware-backed signing flows wherever possible and minimize exposure of private data.

Testing

Test on device models supported by Ledger and include test vectors or a test plan in your submission. Automated tests and a clean CI build massively speed up review cycles.

Helpful official resources (10 links)

Below are ten official Ledger resources (direct links). These are the most useful starting points for any developer integrating with Ledger Wallet or preparing apps for submission. All links are official Ledger domains or Ledger-maintained GitHub repos.

Selected references: Developer Portal, docs, GitHub and official start/support pages. :contentReference[oaicite:4]{index=4}

Troubleshooting & security tips

Protect users

Warn users to only download Ledger Wallet from the official site and to never type or paste their recovery phrase. Be aware of malicious fake apps and installers; verify checksums where provided and prefer platform stores only when Ledger explicitly distributes through them. Ledger has published security guidance and support articles that you should reference in your app's help pages.

Security note & example reporting guidance. :contentReference[oaicite:5]{index=5}

Final checklist before submitting

1. Follow the Developer Portal documentation and manifest schema exactly.
2. Include user-facing help and security advice inside your app pages.
3. Provide test vectors & automated tests if possible.
4. Ensure your CI produces deterministic build artifacts.
5. Label permissions clearly and minimize scope — request only what you need.