Pavel Surkov e58f21e4eb Small additions.		3 yıl önce
..
README.md	e58f21e4eb Small additions.	3 yıl önce

Community Bounty #8. Ledger for Joystream

Environment:

Arch Linux
Google Chrome 89.0.4389.114
polkadot{.js} extension 0.37.1
Joystream Node 5.1.0-9d9e77751-x86_64-linux-gnu
Ledger Live 2.25.1
Ledger Nano X (firmware 1.2.4-5)

1. Test compatibility of Ledger on Joystream

Can a Ledger be used to sign transactions on Pioneer w/o an extension?

Ledger Nano doesn't show up on https://testnet.joystream.org/#/accounts without polkadot {.js} extension (1 screenshot). If you enable the extension, all the addresses that are associated with it appear (2 screenshot). My hardware wallet is respectively Ledger Nano X (Extension). The name can be changed to any other in the extension when adding the wallet (3 screenshot), but the inscription Extension in brackets on the My Keys page will remain. The Add account button is only for creating a new or restoring an old paper wallet (4 screenshot). Ledger cannot be connected here: this requires an extension.

1	2	3	4

Can a Ledger be used to sign transactions on Polkadot JS apps w/o an extension?

Here it is also suggested to download the polkadot {.js} extension, if it is not installed (5 and 6 screenshots). But there is another option:

Go to Settings and select "Attach Ledger via WebUSB" under "manage hardware connections" (7 screenshot). There is no such item on the page: https://testnet.joystream.org/#/settings.
Return to the Accounts page and click on the "Add via Ledger" button (8 screenshot).
Specify name, type and index (9 screenshot).

5	6	7	8	9

When you create a transaction on the Ledger Nano, information about it is displayed (11 photo). It can be approved (12 photo) or rejected.

10	11	12

Can a Ledger be used to sign transactions on Pioneer with the extension

No, I get an error when sending coins from Ledger Nano to other addresses:

Something went wrong with the query and rendering of this component. Unable to find supported chain for 0xabf929bb2e7d75083f6f7b5f5ad3dd6ef94cab0c1db12cc1a0a4ddccf76c18a9

Can a Ledger be used to sign transactions on Polkadot with the extension

In this case, when sending coins, you will first need to click on the "Sign on Ledger" button, then confirm the transaction on the hardware wallet.

2. Which substrate keytypes are supported by Ledger

Schnorrkel (`sr25519`), Edwards (`ed25519`), `ECDSA`?

Now only ed25519. Sr25519 planned. Source: Polkadot Accounts · Polkadot Wiki

3. Transaction testing

Test (at least) a single transaction from each section, and log:
- method
- input
- data displayed on ledger (can be image)
- data displayed in Pioneer/extension (can be screenshot)
- if fail:
  - error message(s) displayed Pioneer/extension (can be screenshot)
  - error message displayed on node (if any)

Node start command

$ ./joystream-node --pruning archive --validator --dev --log runtime,txpool,transaction-pool

I created ordinary transactions for sending coins through the "Send" button: an error appears in the extension (see point 1), but there is nothing about it in the logs.

On the Extrinsics page, I tried to create a transaction system.remark(0x7465737420746573742074657374). Result: again the error Something went wrong, as in point 1. As I understand it, these transactions do not even get into the blockchain.

4. What are the derivation paths, and recovery mechanism, for each keytype supported

Find the derivation path used for each of the keytypes supported.
Check if you are able to successfully recover the key without using a Ledger, and sign a transaction with it, by some mix of:
- the BIP39 tool
- Subkey
- Pioneer
- Polkadot/substrate documentation
If successful: note down all steps, and results in such a way that your results are reproducible
- Your seed
- All commands
- All results
- Everything you inserted in to the browser
If unsuccessful: note down all steps of your attempts, and results in such a way that your results are reproducible, and/or can be ruled out by someone else attempting this

Seed: defy embark buzz express keep chat melody diagram cherry bag office race

Ledger Live and the extension display this address: 16Vchf4ANYiHjHALzVeDKEvNjY7i4Ynn1AEfdJwAVwyb43u3. If you do not connect Ledger Nano in the extension, but restore the wallet by phrase, the address is: 15Vdpb2YMECWyjRzoFjgMQA5bpSLMyGdFfKr7Hf4paebMbTf.

From https://testnet.joystream.org/ Ledger Nano connected via extension: 5HZKZKo6WmSpHk9q2rbDB66Dsv84NFEdvfWBU1wowrx4sbZC. Wallet imported using the phrase: 5GZLgFmUVSw3YCRUqcggDFKvkCSgffiVBAbMwzfiGVd5BPjz.

From Ledger Live

{
  "index": 0,
  "freshAddressPath": "44'/354'/0'/0'/0'",
  "id": "js:2:polkadot:16Vchf4ANYiHjHALzVeDKEvNjY7i4Ynn1AEfdJwAVwyb43u3:polkadotbip44",
  "blockHeight": 4633191
}

Ledger does not support the Joystream network. It only supports Polkadot, Kusama, Dock and Polymath. Task in the polkadot {.js} extension repository with details: https://github.com/polkadot-js/extension/issues/694. To work with any network, you first need to install the appropriate application in Ledger Live. Source code of applications for working with Polkadot, Kusama and Polymesh:

It is also worth adding that in the extension you can select "Allow use on any chain" for paper wallets. For a hardware wallet, this option is not available, you must definitely select a specific network.

Magnum Gold in PolkadotRu

Regarding Ledger, by the way, I would just like to draw your attention to the fact that due to hardware limitations, derivation of the key from the seed phrase is not compatible with most other projects in the ecosystem.

Ledger-compatible key derivation in subkey · Issue #7824 · paritytech/substrate

Background to current problem: The key derivation function Ledger uses is different from all other places (built on top of our Rust or JS libraries): it's a hardware limitation of Ledger's and there's little we can do about this.

Feature request: Add a Ledger compatibility layer in Subkey — basically a CLI mode where you type in a Ledger phrase and get back a json file with a key which you can import in other places.

The goal is to be able to use subkey to convert a Ledger seedphrase into a format you can later import into, say, PolkadotJS.

Any way to customize the derivation path format? · Issue #39 · Zondax/ledger-polkadot

Ledger devices follow the de-facto standard BIP39 and BIP44. Substrate unfortunately is not BIP39/BIP44 compatible. You can find parity's decision here: https://github.com/paritytech/substrate-bip39#substrate-bip39

5. Research, without any testing required, if any other hardware wallet manufacturer supports Polkadot/substrate (and by extension Joystream)

Trezor doesn't support: https://trezor.io/coins/

BitBox02 too: https://shiftcrypto.ch/coins/

Keepkey: the official page indicated that it supports 40+ coins, but the full list is currently not available (after authorization, the error "This page doesn't exist"): https://keepkey.zendesk.com/hc/en-us/articles/360003047479-What-Digital-Assets-Does-KeepKey-Support-. From this article), Keepkey does not support Polkadot. I have not found information about this anywhere else.

Cobo Vault: you can add Polkadot and Kusama: https://cobo.com/hardware-wallet/supported-crypto-assets . You can also add this wallet to polkadot{.js}.

SafePal S1 supports Polkadot and Kusama: https://shop.safepal.io/products/safepal-hardware-wallet-s1-bitcoin-wallet . But derivation paths like the Ledger Nano: https://stackoverflow.com/questions/66323948/polkadot-js-import-bip44-address-w-derivation

README.md