hw-subproviders-klaytn

A higher-level JS package to work with hardware wallets that support Klaytn. Encodes Klaytn transactions using CaverJS and signs with HD keys managed by corresponding HW subprovider:

• LedgerSubprovider supports Ledger App Klaytn for Ledger Blue, Nano S and (possibly) Nano X.
• TrezorSubprovider — TODO 😏
• D'Cent Wallet — TODO 😏

Notice

The package is made and provided by community of Klaytn and it is not affiliated with GroundX and other Klaytn official partners. However, we work close with Klaytn and Ledger teams to make the original Ledger app approved.

Contact

For any feedback and communication about this package and "Klaytn" app for Ledger, please join Telegram group @kompose

API

• Documentation: hw-subproviders-klaytn.kompose.app
• NPM: @kompose-app/hw-subproviders-klaytn

Examples

The LedgerSubprovider internally relies on @kompose-app/hw-app-klaytn which makes all heavy lifting of APDU communication according to this spec.

Simple start with U2F Transport (Chrome, Brave, Firefox)

import {
    LedgerSubprovider,
    ledgerKlaytnBrowserClientFactoryAsync
} from '@kompose-app/hw-subproviders-klaytn'

(async () => {
    const subprovider = new LedgerSubprovider({
        networkId: 8217,
        ledgerKlaytnClientFactoryAsync: ledgerKlaytnBrowserClientFactoryAsync,
    })

    try {
        const accounts = await subprovider.getAccountsAsync()
        console.log("Address:", accounts[0])
    } catch (e) {
        console.log(`Error (${e.name}): ${e.message}`)
    }
})()

If you get Error (TransportError): U2F browser support is needed, then your environement (e.g. NodeJS) is not supporting U2F. And you must use HID or another transports, see the full list at LedgerHQ's documentation on transports.

IMPORTANT! ⚠️ Recently U2F support has been degraded in Windows 10 operating system, which may cause some issues with Ledger interaction and bad user experience. More information about this can see in this post by Ledger team. ledgerKlaytnBrowserClientFactoryAsync provided by this package automatically tries to use WebUSB by default, compatible with all major platforms. If failed, U2F will be used as a fallback.

Using a HID transport (e.g. from NodeJS)

import TransportNodeHid from '@ledgerhq/hw-transport-node-hid'
import { LedgerSubprovider } from '@kompose-app/hw-subproviders-klaytn'
import Klaytn from '@kompose-app/hw-app-klaytn'

(async () => {
    const subprovider = new LedgerSubprovider({
        networkId: 8217,
        ledgerKlaytnClientFactoryAsync: async () => {
            const ledgerConnection = await TransportNodeHid.create()
            return new Klaytn(ledgerConnection)
        }
    })

    try {
        const accounts = await subprovider.getAccountsAsync()
        console.log("Address:", accounts[0])
    } catch (e) {
        console.log(`Error (${e.name}): ${e.message}`)
    }
})()

Result when Ledger Nano S app is locked:

$ BABEL_ENV=development babel-node src/index.js
Error (TransportStatusError): Ledger device: UNKNOWN_ERROR (0x6804)
✨  Done in 3.30s.

Result when app is unlocked:

$ BABEL_ENV=development babel-node src/index.js
Address: 0x0cbe753e2c47f383eb8c9186f20b660c6e3f79ae
✨  Done in 2.62s.

License

Apache License 2.0