Originally written Mar Ten 2018 with title “Can I Use The Ledger Nano S Without Chrome?”. Updated Mar 11 2018, renamed to “Using The Ledger Nano S With MyEtherWallet And Go Ethereum, Without Chrome”). Updated Mar 12 2018 with Parity testing. The associated reddit postbode is Can I Use The Ledger Nano S Without Chrome?. Updated Mar 15 2018 with more information on Parity and renamed to “Using The Ledger Nano S With MyEtherWallet, Go Ethereum and Parity, Without Chrome”. Updated Mar Eighteen 2018 with the same mnemonic key derivation te MyEtherWallet. Updated Mar 31 2018 with informatie on ERC20 tokens. Updated Apr 17 2018 – latest stable geth 1.6.0 works well with the Nano S. Updated Apr Legal 2018 with comparison of key derivation with the Trezor.
MyEtherWallet With Firefox
The Ledger Nano S works well with Firefox with the U2F addon and MyEtherWallet without having to use Chrome for any configuration. You need Browser support enabled to use the Nano S with MyEtherWallet.
geth 1.Five.9 1.6.0, Install Nano S 1.Three.1 Firmware
geth (Go Ethereum) v1.Five.9 did not recognise the Nano S correctly, so I had to install the developer v1.6.0 version and the Nano S wasgoed then recognised. The next problem wasgoed that I had to install a fresh version 1.Three.1 firmware on the Nano S ter order to authorise EIP155 (replay protection) transactions te geth . I had to install the open source Chromium (not the proprietary Chrome) on my Linux machine to update the firmware, and had to set some udev rules to enable connectivity with the Nano S. You need Browser support disabled to use the Nano S with geth .
Testing The Mnemonic Key Derivation
I used the same mnemonic phrase into MEW’s Mnemonic Phrase wallet and selected the m/44’/60’/0′, (Ledger) HD derivation path and MEW produced the same set of keys spil the Nano S. You can therefore access all your accounts from MEW using the same seed phrases – only use this method if you are on a secure offline pc.
Parity 1.6.Two recognises the Nano S hardware account, but only the very first account presently. Hopefully support for more than the very first account will be available soon.
The Ledger Nano S works well with ERC20 tokens on geth (1.6.0 develop) with or without Ethereum Wallet / Nevel, MyEtherWallet and Parity (limited to one account presently). You will need the Contract gegevens setting to be switched on to be able to transfer ERC20 tokens from the Nano S account.
Table of contents
Ledger Nano S. The supplied lanyard is too flimsy, so my Nano S is affixed to a 7 core paracord with a 200+ kg ondergrens cracking strength. I have tied a figure-of-eight wrong ter the middle of the lanyard spil it is not intended to be worn around necks, being stronger than the standard human neck.
The Ledger Nano S by default requires Chrome to interact with the Ledger apps and https://www.myetherwallet.com.
I avoid using Chrome spil I don’t want to give any more gegevens to Google than I have to.
Based on the information te the Reddit postbode above, I ordered Two x Nano S via the affiliate listig on https://www.myetherwallet.com. One device for use and one device for a backup. Ordering the Nano S through the affiliate listig is a painless way to support the MEW team with a few extra keystrokes and clicks. My order wasgoed placed on Mar 8 2018.
It is still the morning of Mar Ten 2018 ter Sydney and I received a verrassing package delivered to my doorstep. It wasgoed my Two x Nano S from Ledger’s Fulfilment Center te Sydney, ter Two days. The housing is sturdy, the two buttons are crisp to click, and it does not have the liberate swivel cap reported by some people on the Reddit forums.
1. Ledger Nano S Setup Without Chrome
I open one of the boxes, and connect the Nano S to my Macbook Air (yeah, I’ve got privacy issues with this too) with the supplied USB cable.
Using one or both of the two buttons on the side of the Nano S I:
- Come in my Four digit Speld – 1234. From https://www.ledgerwallet.com/embark/ledger-nano-s, Three successive wrong PINs will wipe the dongle.
- Write down my 24 word recovery phrase, te the juist order.
- Confirm that I have written down my 24 word recovery phrase.
I then selected the Ethereum icon on the Nano S screen and switched the following settings:
I installed the U2F addon https://addons.mozilla.org/en-US/firefox/addon/u2f-support-add-on/ into my Firefox browser. From the U2F addon Github repository, the U2F addon should work with OS/X, Linux and Windows.
Without restarting Firefox, I navigated to https://www.myetherwallet.com/#send-transaction. I selected the Ledger Nano S on the left mitt of the screen and clicked on the Connect to Ledger Nano S button:
And got the following screen that gives mij a scrollable list of Ethereum accounts secured by the 24 word HD mnemonic phrase on the Nano S:
I selected one of the accounts, and it seems to be working.
Trio. geth 1.Five.9 1.6.0
I upgraded geth , my Go Ethereum client, via Homebrew to Davy Jones’ Locker (v1.Five.9). I restarted geth and got the following error:
I0310 Ten:42:43.508836 cmd/geth/main.go:275] Failed to open wallet ledger://020:005: ledger wallet [ledger://020:005] input open failed: usb: eis: libusb: bad access [code -3]
When I attempted to send a transaction from the HD account, I got the following error:
The Nano S 1.Three.1 firmware and the Ethereum app 1.0.Trio need to be loaded on the Nano S to sign the geth transactions. And this requires the Ledger Manager application that runs te Chrome or Chromium.
Four. Chrome Te A Virtual Machine To Upgrade The Firmware
So I indeed have to run Chrome to run the Ledger app to update the firmware from v1.0.Two to v1.0.Three? I fired up a Windows XP VM ter a VirtualBox host running on Ubuntu Linux. But the USB device wasgoed not recognised by the VM host, so I skipped this VM Chrome installation option.
Five. Ledger Manager Te Chromium Te Ubuntu
I then attempted installing Chromium (the open source version on which the proprietary Chrome is based on) te Linux to run the Ledger Manager.
I installed Chromium using the directives
But the following screen wasgoed displayed. Unplugging, plugging and coming in the Speld did not resolve the kwestie.
6. Nano S Not Recognised Te Linux
Very first I checked if the USB device wasgoed recognised. From /var/loom/syslog:
I then checked the USB device list:
From What if Ledger Wallet is not recognized on Linux?, I would need to create a set of udev rules to permit access to the device on Linux:
I would need to add my user to the plugdev group using the directive:
Unplugged, plugged, entered the Speld but Ledger Manager wasgoed still not recognising the Nano S.
So I added the following two statements to /etc/udev/rules.d/20-hw1.rules :
Success! After unplugging and plugging back the Nano S, the Ledger Manager application now recognises the Nano S:
Unluckily, updating the firmware requires the recovery phrase to be entered again:
I clicked on the Install button, and the following screen wasgoed displayed:
After many minutes, I got a failure message. How tedious.
Ok. I witnessed what needed to be done. The Nano S device wasgoed prompting for a confirmation to install the fresh firmware. I clicked the 2nd button on the device, and there wasgoed a message “Update” displayed on the Nano S screen. The device displayed a “Processing” message, then eventually a message “Press both buttons to begin”.
After Ten minutes of coming in ter my Speld and the 24 word recovery phrase, I got the message “Your device is now ready”. Phew.
No. It’s not fairly overheen yet. I attempted to install all the application available ter the Ledger Manager screen, but the Nano S ran out of space.
Back te geth , after setting Browser support to false, I attempted sending a transaction:
And I got the messages “Amount ETH 0.0000…01”, “Address 0x00…9af”, “Maximum Fees 0.0018”, “Confirm transaction” on the Nano S screen. Success.
7. Very first Mnemonic Key Derivation Test – Fail
I dreamed to test that I could recover my derived keys using the same mnemonic phrase ter case I lose my Nano S or determine not to use it.
I downloaded the Mnemonic Code Converter software from https://iancoleman.github.io/bip39 onto my rekentuig (Significant: only use on a secure and offline laptop), loaded the software into my browser and pasted my 24 word mnemonic phrase license diagram pelican spy monitor persuade harm script wall hockey goose month popular swamp sugar rose mystery gap regular acquire bottom sea modify eyebrow and selected the Ethereum coin to check the derived keys:
The following screen shows the derivation path:
And the following screen shows the derived keys that DO NOT MATCH MyEtherWallet’s derived keys and geth :
The following screen shows the keys derived by MyEtherWallet:
And geth shows that the very first key matches MyEtherWallet’s very first key:
Note that geth only reports the very first unused derived key.
8. 2nd Mnemonic Key Derivation Test – Pass
To have the confidence when using my Nano S, I need to know that the keys can be derived by a separate process.
I searched the televisiekanaal and from Restoring your Ethers (ETH or ETC) without a Ledger Nano S, I got the listig to https://github.com/btchip/bip39/tree/ledger-ethereum. So I cloned the repository, selected the juist branch and compiled the code:
(Significant: Only use the following on a secure and offline rekentuig, or for testing with throwaway mnemonic phrases.)
I then loaded the opstopping bip39-standalone.html into my browser and pasted the 24 word mnemonic phrase license diagram pelican spy monitor persuade harm script wall hockey goose month popular swamp sugar rose mystery gap regular acquire bottom sea modify eyebrow and selected the Ethereum coin:
The following screen shows the derivation path:
And the following screen shows the derived keys that MATCHES MyEtherWallet’s derived keys and geth :
The following screen shows the keys derived by MyEtherWallet:
And geth ‘s very first key that matches the software above and MyEtherWallet’s very first key:
9. MyEtherWallets Mnemonic Phrase Key Derivation Test – Pass
I entered the same mnemonic phrase into MEW’s Mnemonic Phrase wallet:
And I then selected the m/44’/60’/0′, (Ledger) HD derivation path, and MEW generated the same set of keys spil the Nano S:
Nice work Ledger, the MyEtherWallet team and the geth team.
Ten. Comparing The Key Derivation With The Trezor, Using MyEtherWallet
A user on a forum asked whether the seed from the Nano S can be restored onto the Trezor. So I used MyEtherWallet to test this, using the 24 word mnemonic phrase license diagram pelican spy monitor coax harm script wall hockey goose month popular swamp sugar rose mystery gap regular acquire bottom sea modify eyebrow .
Here is the screen from MyEtherWallet displaying the addresses derived using the Trezor:
And here is the screen from MyEtherWallet showcasing the addresses derived using the Nano S:
So you cannot use the Nano S seed with the Trezor to derive the same accounts.
11. Parity 1.7.0
I desired to see if Parity supports the Nano S, so I downloaded and compiled the fresh version of Parity 1.7.0 on my Macbook using the following instructions:
After the compilation, I ran parity on the Ropsten testnet using the following guideline:
I opened up the Parity browser pagina on localhost:8080 and navigated to the ACCOUNTS tabulator and found my NANO S hardware account on the pagina:
A good embark. I transferred some testnet ethers to my Nano S account.
While waiting for Parity to sync, I transferred Ten Ropsten ETH to my very first Nano S account, and found it using MyEtherWallet on the Ropsten network: