Welcome to Ledger's JavaScript libraries.
See also:
To communicate with a Ledger device, you first need to identify which transport(s) to use.
The hw-transport libraries implement communication protocol for our hardware wallet devices (Ledger Nano / Ledger Nano S / Ledger Nano X / Ledger Blue) in many platforms: Web, Node, Electron, React Native,... and using many different communication channels: U2F, HID, WebUSB, Bluetooth,...
Channels | U2F/WebAuthn | HID | WebUSB | Bluetooth |
---|---|---|---|---|
Blue | YES | YES | NO | NO |
Nano S | YES | YES | YES | NO |
Nano X | YES | YES | YES | YES |
Summary of implementations available per platform
Platforms | U2F/WebAuthn | HID | WebUSB | Bluetooth |
---|---|---|---|---|
Web | @ledgerhq/hw-transport-u2f (Chrome, Opera) | NO | @ledgerhq/hw-transport-webusb (Chrome) | @ledgerhq/hw-transport-web-ble (Chrome) |
Electron/Node.js | NO | @ledgerhq/hw-transport-node-hid1 | NO | @ledgerhq/hw-transport-node-ble |
iOS | NO | NO | NO | @ledgerhq/react-native-hw-transport-ble |
Android | @ledgerhq/hw-transport-u2f2 | @ledgerhq/react-native-hid | @ledgerhq/hw-transport-webusb2 | @ledgerhq/react-native-hw-transport-ble |
- 3 implementations available
- via Android Chrome
Please find respective documentation for each transport:
- @ledgerhq/hw-transport-u2f [Web] (U2F) (legacy but reliable) – FIDO U2F api. check browser support.
- @ledgerhq/hw-transport-webauthn [Web] (WebAuthn) (experimental) – WebAuthn api. check browser support.
- @ledgerhq/hw-transport-webusb [Web] (WebUSB) (experimental) – WebUSB check browser support.
- @ledgerhq/hw-transport-web-ble [Web] (Bluetooth) – check browser support.
- @ledgerhq/hw-transport-node-hid [Node]/Electron (HID) – uses
node-hid
andusb
. - @ledgerhq/hw-transport-node-hid-noevents [Node]/Electron (HID) – uses only
node-hid
. Does not provide USB events. - @ledgerhq/hw-transport-node-hid-singleton [Node]/Electron (HID) (experimental) – uses
node-hid
andusb-detection
. Focus on supporting one device at a time (potentially will have more robust events and less blocking cases) - @ledgerhq/hw-transport-node-ble [Node]/Electron (BLE) (experimental) – uses
@abandonware/noble
. - @ledgerhq/react-native-hw-transport-ble [React Native] (Bluetooth) – uses
react-native-ble-plx
- @ledgerhq/react-native-hid [React Native] (HID) Android – Ledger's native implementation
- @ledgerhq/hw-transport-http [DEV only] universal HTTP channel. NOT for PROD.
All these transports implement a generic interface exposed by @ledgerhq/hw-transport. There are specifics for each transport which are explained in each package.
A Transport is essentially:
Transport.listen: (observer)=>Subscription
Transport.open: (descriptor)=>Promise<Transport>
transport.exchange(apdu: Buffer): Promise<Buffer>
transport.close()
and some derivates:
transport.create(): Promise<Transport>
: make use oflisten
andopen
for the most simple scenario.transport.send(cla, ins, p1, p2, data): Promise<Buffer>
: a small abstraction ofexchange
NB: APDU is the encoding primitive for all binary exchange with the devices. (it comes from smart card industry)
As soon as your Transport is created, you can already communicate by implementing the apps protocol (refer to application documentations, for instance BTC app and ETH app ones).
We also provide libraries that help implementing the low level exchanges. These higher level APIs are split per app:
- @ledgerhq/hw-app-eth: Ethereum Application API
- @ledgerhq/hw-app-btc: Bitcoin Application API
- @ledgerhq/hw-app-xrp: Ripple Application API
- @ledgerhq/hw-app-str: Stellar Application API
Community packages:
-
@cardano-foundation/ledgerjs-hw-app-cardano: Cardano ADA Application API
-
ledger-cosmos-js: Cosmos/Tendermint Application API
We invite all third party app developers to not send PR to this repository to provide more implementations but instead to maintain your own version in your own repository and we would be happy to reference them here ♥.
Package | Version | Description |
---|---|---|
create-dapp |
Ledger DApp Ethereum starter kit | |
@ledgerhq/web3-subprovider |
web3 subprovider implementation for web3-provider-engine | |
Development Tools | ||
@ledgerhq/hw-http-proxy-devserver |
HTTP server proxy to use with hw-transport-node-hid NB: DEV & testing purpose only. DO NOT use in PROD |
|
@ledgerhq/hw-hid-cli |
CLI utility to send APDU to the device via node-hid | |
@ledgerhq/hw-transport-mocker |
Tool used for test to record and replay APDU calls. |
import Transport from "@ledgerhq/hw-transport-node-hid";
// import Transport from "@ledgerhq/hw-transport-web-usb";
// import Transport from "@ledgerhq/react-native-hw-transport-ble";
import AppBtc from "@ledgerhq/hw-app-btc";
const getBtcAddress = async () => {
const transport = await Transport.create();
const btc = new AppBtc(transport);
const result = await btc.getWalletPublicKey("44'/0'/0'/0/0");
return result.bitcoinAddress;
};
getBtcAddress().then(a => console.log(a));
Please read our contribution guidelines before getting started.
You need to have a recent Node.js and Yarn installed.
yarn
Build all packages
yarn build
Watch all packages change. Very useful during development to build only file that changes.
yarn watch
Lint all packages
yarn lint
First of all, this ensure the libraries are correctly building, and passing lint and flow:
yarn test
then to test on a real device...
Plug a device like the Nano S and open Bitcoin app.
Then run the test and accept the commands on the devices for the tests to continue.
yarn test-node
You can also test on the web:
yarn test-browser
make sure to configure your device app with "Browser support" set to "YES".
Checklist before deploying a new release:
- you have the right in the LedgerHQ org on NPM
- you have run
npm login
once (checknpm whoami
) - Go to master branch
- your master point on LedgerHQ repository (check with
git config remote.$(git config branch.master.remote).url
and fix it withgit branch --set-upstream master origin/master
) - you are in sync (
git pull
) and there is no changes ingit status
- your master point on LedgerHQ repository (check with
- Run
yarn
once, there is still no changes ingit status
deploy a new release
yarn run publish
then, go to /releases and create a release with change logs.
alternatively:
deploy a canary release (beta, etc)
yarn run publish -c
NB: if there is a new package, AFAIK you need to manually
npm publish
it once on NPM.