Nault Docs

How to use Nault on a bootable Linux flash drive

2021-07-11T00:00:00+00:00

Using a wallet on an online machine comes with a risk. The OS can contain malicious software such as keylogger, screen recorder or code that looks for and replaces crypto addresses without your consent. In that case, it doesn’t matter if you use Nault on the web or as a desktop app. One way to protect against this is to use a Ledger device, another is to only sign transactions via an offline Nault on another machine.

This guide is about a third option:

Make Nault portable by booting up a clean Linux distro and install the Nault desktop app within it

This will reduce the risk of getting viruses if you never use the OS for anything other than Nault and never install any other software. It’s nice to have Nault in your pocket when travelling, visiting friends, school or workplace.

============================

Table of Contents
Introduction
Preparing the USB flash drive with Slax
Install Nault inside Slax
Advanced: Protect your persistent data
Advanced: How to compile Nault from source code inside Slax
Advanced: Store Nault as a Slax module

============================

Introduction

We will use a Linux distro called Slax which is a modern graphical light-weight OS that runs directly from a USB flash drive.

Benefits with Slax:

Truly portable: No installation needed
Nice spec: Only 128MB of RAM needed (512 if running it in ram), 32 or 64 bit (x86_64 CPU)
Pre-installed apps such as a web browser, file manager and terminal
Based on Debian: Can install thousands of precompiled apps via the APT command just like in Ubuntu
Super light-weight: Under 300MB total disk (Plus Nault 100MB). Fast boot.
Persistent changes or optionally choose to do a fresh start every time
Customizable: Changes can be exported as a module or as a whole new ISO to be loaded on the next boot
Can be loaded into RAM only
Free

============================

Preparing the USB flash drive with Slax

A. Download the Slax ISO. Currently has to be done with a little compromise since Nault requires Ubuntu20 or Debian10 and the latest Slax uses Debian9. A new version will hopefully come and this guide will update accordingly.

Option 1: Download official Slax 9 (32 or 64 bit). At this time limited to Nault 1.10.2 desktop app or nault.cc web app. Could also compile Nault from source code, see the advance section below.

Option 2: Dowload unofficial Slax 10 (32 or 64 bit). It can run the latest Nault desktop app or nault.cc web app. More info about the unofficial build can be found here and here.

Please be aware that running unofficial versions of Linux distros comes with its own risk. Even the official Slax. We do not endorse Slax or make promises about security.

B. Copy the slax folder from the ISO to a USB flash drive with at least 1GB in order to have some extra space. Or burn the ISO on a DVD but then you can’t have persistent storage. More info here

C. Make the USB bootable by running bootinst.bat (if Windows) or bootinst.sh (if Linux) from slax/boot. The USB should now look like this:

============================

Install Nault inside Slax

A. Launch Slax by restarting the computer with the USB flash drive. If it’s not automatically booting, most computers allow you to press F8 to override the boot drive. During boot you can press ESC for more options, for example, erase any changed data or load into RAM.

B. When Slax has been launched you may want to change keyboard layout if not English. Right-click on the desktop and select keyboard layout of your choice. Possibly also change the screen resolution. If you rely in WiFi you need to launch the “Net Manager” and connect.

C. Start the built-in browser from the bottom left start button. Go to Nault Github releases and download the latest appImage for Linux.

If using Slax 9 (Debian 9) you are limited to Nault 1.10.2 desktop app or you have to compile Nault from source code.

D. Open a terminal (xterm). Also from the start button.

E. Create a script to launch Nault more easily since it can’t run under “root” without a special flag.

To paste clipboard (ctrl+c) into xterm you can use the middle mouse button.

Make sure to type the correct Nault version below. Chmod is to make the script executable.

cd Downloads
chmod +x Nault-1.13.3-Linux.AppImage
echo '#!/bin/bash' >> start.sh
echo '/root/Downloads/Nault-1.13.3-Linux.AppImage --no-sandbox' >> start.sh
chmod +x start.sh

If using Slax 9 (Debian 9) you also need these before you can launch the AppImage:

apt update
apt install libatk-bridge2.0-0 libgtk-3-0 -y

Now you can run ./start.sh from a terminal or double click it in the file manager. It should open up Nault and you are ready to go! The changes you made will be available during the next boot (because it’s being saved to the USB/slax/changes/changes.dat, including the wallet if not setting up Nault to erase cache on exit. It’s recommended to disable the auto-login, please see the next section.

Do not unplug the flash drive or cut the power to the computer while Slax is running. This will invalidate changes made. If you want persistent data you must shut down properly from the OS (bottom right) and wait to unplug the drive until the machine has turned off.

============================

Advanced: Protect your persistent data

Slax logs in automatically and if someone finds your flash drive they can see your data, for example the wallet balance if you have that saved. It’s recommended to change the root password and disable auto-login.

From a terminal run (one line at a time):

passwd
systemctl disable xorg

The next time you boot, use “root” as username and your new password. To start the GUI, run:

startx

If there is a better method to achieve this, please let us know!

Advanced: How to compile Nault from source code inside Slax

You may want to compile Nault, for example, if you have made your own changes to the code or do not trust the official build. Tested with Slax 9.11.

This procedure will require at least 1.5GB extra space on the USB

A. Install dependencies not included with Slax

From a terminal run (one line at a time):

apt install curl -y
curl -sL https://deb.nodesource.com/setup_12.x | bash -
apt install nodejs -y
apt install git libudev-dev libusb-1.0-0-dev make build-essential pkg-config -y

If using Slax 9 (Debian 9) you will also need to change the source list and install gcc and g++:

nano /etc/apt/sources.list

..and add these lines at the bottom:

deb http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.us.debian.org/debian/ jessie main contrib non-free

When finished, exit the nano editor by ctrl+x and run these commands. gcc and g++ is for compiling Nault and the other for running the AppImage:

apt update
apt install gcc-4.8 g++-4.8 libatk-bridge2.0-0 libgtk-3-0 -y

B. Compile Nault

From a terminal run (one line at a time):

git clone https://github.com/Nault/Nault
cd Nault
npm install -g @angular/cli
npm install
npm run desktop:build-local

The binary is located in desktop-app\build. Run it with

./Nault/x.xx.AppImage --no-sandbox

============================

Advanced: Store Nault as a Slax module

This will allow you to erase user data and start fresh every launch with Nault still installed. Useful if you never want to connect to the internet and just use Nault in offline mode.

How to use multi-signature (multisig) in Nault

2021-04-20T00:00:00+00:00

Multi-signature is a way for multiple participants to own one private key each and combining them in a way so that only one common account is used to store the funds. Each participant only needs to know their particular key. Then by exchanging safe cryptographic data between the participants, a block signature is produced that can publish the corresponding block to the network.

A demo video can be found here

============================

Table of Contents
Introduction
Generate a Multisig Address
Create a New Transaction Block
Sign the Transaction Using Multisig
Publish the Multisig Transaction
Troubleshooting

============================

Introduction

The most common approach is to enforce at least 50% of the participants to take part, while the current Nano implementation requires 100%. It’s more secure but also involves a higher risk since it’s a higher chance that one of the keys goes missing and funds locked forever. This type of implementation, also called M of M, will probably change in the future to the less risky M of N. It will require a new multisig library to be developed.

The multisig procedure involves some manual steps and is aimed at advanced users with high security in mind:

A multisig address is created by combining normal Nano addresses
The address is used in the Nault “block explorer” to create SEND, RECEIVE or CHANGE blocks
A signature is generated (online or offline) for the block using private keys from the same amount of participants as you decided when you created the multisig address
Finally, the block is processed on the public Nano network

============================

Generate a Multisig Address

Visit the Multi Signature screen under Advanced Tools.
Add the addresses you want to participate with. Each one must have a known private key that will be used during the block signing. Any Nano account can be used, even if they have funds in them, but if you want to start with new fresh key/address pairs you can create them in the Keypair Generator.
Press Generate Multisig and make a note of the generated Multisig Address. The private keys are sensitive information that should never be shared.

Make sure each account you used has the corresponding private key stored safely. Tell your participants to do the same.

============================

Create a New Transaction Block

Paste your multisig address either on the multisig page or in the bottom left search bar. It will take you to the account detail page where you can see any incoming transaction or create new ones.
Depending on how you got to the Account Detail page, you may need to expand the “Advanced Options” and “Enable Remote Signing / Multisig”.
You can “Create New Block” to SEND funds or to CHANGE representative. You can also receive incoming transactions in the list by using the SIGN BLOCK button. Both will create an Unsigned Block that you copy to the next step. Either by text or QR depending on where you will do the signing.
The signing step can be offline for maximum security. In that case, you (or your participants) can run the Nault desktop app on another machine and go to either the Remote Signing screen, the Multi Signature screen or scan from a QR directly.
If using Remote Signing screen: Use the “Sign Block”
If using Multi Signature screen: Use the “Multisig for Participants”

============================

Sign the Transaction Using Multisig

If you own all keys, you can use multiple tabs/browser screens and the “Multi-Tab Mode” (requires the web version):

Enter the number of participants and copy the browser URL or use the “Copy Signing Link”. Open the same URL in all tabs.
Enter one private key in each tab, doesn’t matter which one as long as all belong to the multisig address you are about to sign.
Check “Multi-Tab Mode” and press “Start Multi-Signing”.
If it went well it will display a QR code and data for the signed block you can copy to the final step.

If you are multiple participants on different machines (web version or desktop app):

Enter the number of participants and copy the browser URL or use the “Copy Signing Link”. Share it with your participants who will enter it in the Multi Signature screen as “Multisig for Participants”.
Each participant will enter their private key and press “Start Multi-Signing”.
For each step all participants will copy the output data and give it to the others. They will in turn paste it as input data, one string for each participant. Then proceed with the next step.
When all three steps are done it will display a QR code and data for the signed block that any of the participants can copy to the final step.

============================

Publish the Multisig Transaction

Use the signed block from the previous step and paste it in the Remote Signing screen as “Process Block”
Once you have manually confirmed that the details are correct, press “Confirm & Process”
The block can now be validated on the network

============================

Troubleshooting

The signing fails: Wrong block hash

Make sure you use the same signing link for all participants, who must sign the same block.

The signing fails: Wrong private key

Make sure you use the same signing link for all participants. It must be the same block you try to sign. Plus the private keys must match the multisig account you are signing for.

Nault doesn’t work, any other tools I can use to recover my multisig funds?

Yes, the multisig account and signing is compatible with the following

I’m missing private keys for my multisig, how to recover?

Sorry but you simply can’t. There were several warnings in place to make sure you saved ALL private keys for the multisig you created and funded.

Custom Work Server

2021-02-13T00:00:00+00:00

The default option in Nault is to generate proof of work from the backend servers. That, in turn, is using services such as dPoW and boomPoW. That is fine for most users but it comes with limitations.

The services can be offline or you want to do higher multiplier than what’s allowed. As a backup, Nault has also supported local CPU or GPU PoW using the browser.

A third option is to use a custom work server running either remotely or localhost. The official work server has been tested with an RTX 2080 GPU with normal 1x pow comnputed in 0.25sec compared to around 5sec with webGL PoW. 64x pow can be made in 16sec on average. This can be useful if the network is saturated for example and you want higher priority on your transactions.

============================

Table of Contents
Features
How To
1. Work Server
2. Nault Settings
Limitations

============================

Features

Supports any node, work server or compatible API
Huge speed improvement of 10-40x compared to webGL
Allows custom multiplier up to 64x
Works in both web and desktop app (with limitations mentioned below)
Future-proof in case of the work algorithm changes and webGL can’t be done

How To

Work Server

Download the latest work server and start it e.g. with your default GPU on port 9999:

nano-work-server.exe -g 0:0 -l 127.0.0.1:9999

Example using both GPU and 12 CPU cores:

nano-work-server.exe -g 0:0 -c 12 -l 127.0.0.1:9999

Full instructions:

nano-work-server.exe --help

Nault Settings

Specify the work server in the Nault app settings e.g.:

http://127.0.0.1:9999

Limitations

Nault web app will not allow direct connection to 127.0.0.1 due to CORS policy. To get that working you have to use a local proxy server that allows cross-origin calls. In Apache that’s just a Header set Access-Control-Allow-Origin "*"

The desktop app works fine with any work server source.

Nault advanced features: Changing backend servers and using the block explorer

2020-12-02T00:00:00+00:00

Nault uses the Nano RPC protocol for communication with network nodes. This is done via backend servers, also called proxy servers. To ensure robustness and stability if a backend should go down Nault uses several of them. Some main servers are chosen by random on each wallet load (page refresh) if the connection is interrupted or hitting the rate limit. Others are used as a backup for manual selection.

But stability is not the only reason for having this unique possibility. Nault can also be used on other networks, which will be described further down.

Additionally, Nault has a built-in block explorer that is often overlooked.

============================

Table of Contents
When to change server and how to do it
What other networks exist and how to use them
The Nault block explorer
Other Wallet Settings

============================

When to change server and how to do it

A nano node may suffer from some problem, is stalled or behind in blocks. In that case, the Wallet may indicate that the node is connected and working, but new transactions are not coming in. Could also be that you can send transactions but not receive. If that happens you can go to Nault app settings and check the stats of each server, comparing the block count and stake (total needs to be above required), and switch to another server if needed.

Random is default. A server will be selected for you on each visit.
Custom: You can enter any private or public Nano node RPC interface and/or websocket. Then you have full control over your wallet. The auth header can be used to authenticate locked backends or by using tokens for unlimited RPC requests that can for example be purchased at MyNano.ninja.
Offline mode can be useful if using the desktop app on a remote offline device together with the remote signing procedure. No network actions will be used (less popups).

============================

What other networks exist and how to use them

Nault is not only bound to function with the Main public network. In fact, you can choose an RPC backend of any direct Nano fork. That includes the public beta network, the public test network or even a single or multi-node local network using something like the linuxserver docker images.

Just point the backend server to the node RPC address and you are good to go. If Nault.cc doesn’t work, try the desktop app. Usually, you can’t mix https and http sources in the browser. The node settings (config-node.toml) must allow RPC (and websocket if you want automatic receive). If you are using a proxy server in between like the NanoRPCProxy, Noxy or the linuxserver docker with its internal proxy you just have to make sure to allow the RPC commands Nault is using:

accounts_balances
accounts_frontiers
account_history
account_info
accounts_pending
blocks_info
confirmation_quorum
pending
process
representatives_online
version
work_generate

To send and receive transactions you need to generate work. Either set the PoW source in the wallet settings to CPU or GPU, or if using server PoW, you can must allow the “work_generate” command with any either of:

Use the node itself by setting enable_control = true in the config-rpc.toml (and enable opencl in the config-node.toml if you have a GPU)
Use a work server by adding one or several work_peers in the config-node.toml (currently require a code change in Nault to pass “use_peers” as a parameter for the work_generate command)
Use a proxy server like NanoRPCProxy that has support for both dpow and bpow as a middleman
Use some other proxy server that can connect to work peers

============================

The Nault block explorer

Regardless if you are using the wallet on the Nano main network or some other fork, a block explorer is always useful!

You reach it from:

The accounts page and click on an account

Or enter an address or block hash at the bottom

Once you are in the explorer you can further click on other accounts or blocks to drill down. It will grab the latest info, including any balance and pending/incoming transactions.

============================

Other Wallet Settings

There are also some other useful options in the “App settings”:

Lock After Inactivity: Shorten to increase the security or turn off automatic lock.
Wallet Storage: Select None if you want Nault to reset and delete the seed, settings and everything after browser exit. WARNING: You must write down your seed or your funds will be lost!
PoW Source: Let Nault decide or force it to use local GPU / CPU or remote server PoW.
Receive Method: If you get annoying auto receives, you can set it to manual. Then you receive all transactions when needed from the Receive page. Useful when using a Ledger hardware wallet.
Min Receive: Use this to ignore small spam transactions. 0.000001 is the smallest amount possible to send in most wallets.
Default Representative: Override the rep that is set to all new accounts you open in the wallet. If blank, one will be selected for you.

The security of your Nano

2020-08-05T00:00:00+00:00

Let us talk about the security of Nano and using Nault. But before we dive in, you should understand the fundamentals of the Nano protocol and what it means to own Nano. This article will then divide the overall security into the following sections: The Nano protocol, The storage of keys and The usage of keys.

============================

Table of Contents
What does it mean to own Nano?
The Nano Protocol
The Storage of Keys
The usage of Keys

============================

What does it mean to own Nano?

As with most other cryptocurrencies, the Nano protocol is designed to transfer ownership of a stake in the currency total supply. By owning 1 NANO means you own the keys that control an account which is set to a balance of 1 NANO. Any fraction of that, down to the smallest possible unit called raw, can be moved to any other account. That is done by a set of parameters called a block, which is stored on the distributed Ledger. Two of the parameters are the account and the latest balance the account holds. Before the network can accept a new block, it needs to be signed. That can only be done by the private key for that specific account.

The private keys are derived from a 64-char hexadecimal entropy string called a Nano seed. A single seed contains a total of 4,294,967,295 keys (or indexes) where each one unlocks a valid account (Nano address). In many wallets, we are only interested in the first account (index 0) but Nault, for example, can access any index if you so want. That’s the principle and also why owning the seed means owning the Nano. Storing Nano at an exchange does NOT technically mean you own them, because the exchange handles the seed for you. They can be hacked or closed down without warning and in that case, the Nano is no longer under your control.

============================

The Nano Protocol

The blocks are validated and voted on in a distributed consensus model across the world using network nodes. If the nodes agree a block is valid, it’s stored in the Ledger which is synchronized between the nodes.

The security of your Nano is bound to the security of the network. Without a functioning network, the Nano can’t be transferred and the value of the network (the value of 1 NANO) would eventually drop to zero. That topic is too broad for this article and we will simply assume the network is functioning. There is plenty of material available as it’s been discussed for years but easiest would be to refer to the successful official security audit that was made in 2018. The network has additonally been heavily improved since then.

============================

The Storage of Keys

There are many ways to store keys/seeds and this is where Wallets come in. A wallet can be digital, analogue, online, offline, encrypted or open. How YOU decide to store the seed is often bound to the level of convenience you are after. That is further described in this article. We will be focusing on storing the keys in Nault, a hardware wallet or offline using the remote-signing procedure.

Keys in Nault

Nault is a fully client-side wallet meaning it will never send the keys to a remote server. They are stored only in browsers local storage. The default usage in Nault is to encrypt the seed using a password of your choice. The strength of the password will decide the level of security and it will be stored as long as the browser cache lives, which can be forever if you want. Nault can also be set to remove all wallet data on browser exit. Then you will enter your seed/key the next time you need access. Using that method probably means you would store the seed on a paper and scan it using the QR reader. A password manager is also an option but it’s recommended to always have a non-digital backup in case the electronic fail. Nault can be used Online or Offline which is described in the the usage of keys section. You can for example store the keys / seeds in Nault but on a machine that is always offline.

Keys in a Hardware Wallet

Nault supports the Ledger Nano S and Ledger Nano X devices. This is one of the most secure methods where the keys are encrypted inside the device and can only be unlocked with a 4-8 digit PIN. The wrong PIN will erase the device, and a 24-word backup mnemonic is stored on a paper during the device initialization. The device is known as “unhackable” yet very easy to access. Plug it in via USB, unlock and transact on the Nano network. We can call this method semi-offline since the device is not known to be maliciously accessible but theoretically attached to an online wallet (if not using the remote signing procedure described in the usage of keys).

Keys on Paper

This is arguable the safest method since a paper is hopefully offline and hidden from prying eyes but also arguably LESS safe than a hardware wallet because if anyone would find the paper it’s also directly accessible and unencrypted. The safety relies on where you hid it. A seed on a paper can be scanned by Nault and used when you need access to it, either doing an online signing or offline signing.

============================

The usage of Keys

The third factor that decides the overall security of your Nano is how you choose to transact it. Using Nault is very secure in itself because no sensitive data is sent over the Internet. Nault connects to a backend server where commands are sent to the Nano network, but the block signing is done on your device using keys on your device. Only the final signed block is sent over the Internet but the signature can’t be reversed or tampered with. However, what will reflect the security is the key storage method described in the previous chapter.

Transact with an online Nault

Your keys are stored encrypted in the browser storage and you unlock the wallet/ decrypt the keys before doing any transactions. This is the most convenient method but not the most secure. Worst case, the wallet is hacked and you are tricked to enter your seed.

Transact with the Ledger hardware wallet

Your keys are secured by the Ledger device and unlocked before doing any transactions. A difference from the native Nault is you have to validate the destination and balance on the device display and manually approve with the device button. A hacked wallet can’t trick you in this case because what’s shown on the device is always true. This is medium convenient but not even this is the most secure option. Worst case, an unknown vulnerability exists in the device that tricks you into sending funds to someone else. A full Ledger/Nault user guide is found here.

Transact using a remote-signing procedure

Your keys are stored offline, thus avoiding any leaks to the Internet due to malware, hacked password manager or other things that can go wrong in any online device. The principal follows:

Create an unsigned block for account X (using the latest data from the network)
Transfer it to an offline device where it’s signed using a key that owns X
Transfer the signed block to any online device where it’s sent to the live network

Now, this is the most secure method with the cost of convenience. Nault makes this somewhat usable but you should be prepared for some extra steps. Steps that may, however, be well worth it if transacting large amounts! A full walkthrough can be found here, or a speed demo showing that offline-signing can be done in less than 5 seconds.

The full procedure is also described below

Go to the remote signing page on an online Nault (no wallet is required). Paste any account you wish to transact on (SEND, RECEIVE or CHANGE representative). Press the CREATE button that will take you to the account detail page with remote signing enabled.
For SEND or CHANGE, press “CREATE NEW BLOCK”. Select block type and fill in the destination and amount for SEND, or the new representative for CHANGE. Press “GENERATE BLOCK”
A big QR is shown. This is the unsigned block you will now scan or transfer to the offline Nault, which you preferably run using the desktop version. If the offline machine doesn’t have a camera you can manually copy the unsigned block using the button above the QR and paste it in STEP 2 over at the remote signing page.
When the block has been imported in the offline Nault, user verification is required. This is an important step security-wise where the balance is calculated from the new and previous block provided. Another step happening behind the scenes is the previous block hash is calculated and compared against the new block’s frontier parameter. This is to ensure the online Nault can’t be hacked and giving you false information like the wrong balance or destination. If the data don’t match, the final block will never be accepted by the network. You can also optionally chose to include proof of work here, but if not done it will automatically be included in the final online step. If the data is correct, accept and sign the block with the methods provided. A secure method here would be to use the Ledger device or scan the seed, mnemonic or private key from a paper wallet. But having a wallet set up in Nault already encrypted with a password is arguably even more safe since it’s completely offline. The password you chose should be brute-force proof.
The final step is to read back the signed block in the online Nault using either the QR reader or manually copy it by other means using the remote signing page. Now, you just confirm and process! The block will be published and proof of work included if it was not done in the offline device.
You can view the result in the block explorer and optionally also do the same procedure for any incoming transactions by pressing the “REMOTE SIGN” button in the table.

How to use the Ledger Nano in Nault

2020-08-04T00:00:00+00:00

If you have a Ledger device, you can use it with Nault to securely access and send your Nano. Paired together, it is the safest and yet highly convenient way to send and receive Nano! Using this guide you can learn everything needed to send and receive Nano on your Ledger device with Nault.

============================

Table of Contents
Installing The Nano Application
Configuring Your Ledger With Nault
Your Ledger Status
Using Nault to Send, Receive or Change representative via the Ledger
Final Words
1. Data Storage
Troubleshooting

============================

Installing The Nano Application

Connect your Ledger device via USB to your computer and use your PIN to unlock it. If it hasn’t been set up yet, follow this procedure.
Open the Ledger Live and choose how to connect your device.
Open the Ledger Live Manager.
Confirm on the device to allow the Ledger Manager. Search for nano and install. When the nano app has been installed you should close Ledger Live because a Nano wallet is not yet supported from inside the application. You will use nault.cc for that.
Open the Nano application on your Ledger device, you should see ‘Use wallet to view accounts’. If so, you are ready to go!

============================

Configuring Your Ledger With Nault

To be able to use your Ledger device with the web wallet, it's recommended to use a Chrome, Brave or Opera browser, and the Ledger Manager application must be closed. There may be an annoying pop-up in Windows 10 so it's even more recommended to use the desktop version found here.

Make sure the Nano app on the Ledger device is started, referring to the last point from previous chapter.
From Nault.cc, choose the option to ‘Import An Existing Wallet’, and then select the ‘Ledger Nano S’ option from the import type dropdown. Ledger Nano X should work as well even if you choose S. If the device is not detected, try exit and re-open the Nano app on the device or switch USB-port or even try a new cable. Then just hit the “refresh ledger status button” in Nault.
Once the Ledger is detected, your Nano account will be imported into Nault and your wallet is ready to use! If you have been using more Nano accounts in the Ledger, they should be detected and imported as well.

Other wallets supporting Ledger and Nano (or import of the Ledger mnemonic) may not support the use of multiple Nano accounts. So keep that in mind if you choose to use more than one account (at index 0).

============================

Your Ledger Status

On the left navigation, you can find the current status of your Ledger device. When it is not connected, you will be unable to sign any new transactions or add new accounts. If the device status seems wrong, you can click on it to attempt to reconnect to the Ledger device. Your Ledger will only be marked as ready when it is unlocked and the Nano application is open.

============================

Using Nault to Send, Receive or Change representative via the Ledger

Once your ledger wallet is imported, you can use the ‘Accounts’ page to view the current status of all your Nano accounts. By clicking on one of your accounts, you can view the full details including transaction history.

Before accepting any transaction with the Ledger button, always verify the amount and destination on the device display. This is YOUR responsibility of making sure everything is in order.

Sending Nano

Open the ‘Send’ page from the left navigation
Select the account you would like to send from and enter the address of the Nano account you would like to send to (Or select a contact from your address book)
Enter the exact amount of Nano you would like to send (Or use the FIAT input below to have it automatically converted)
Press ‘Send Nano’, then use the confirmation page to ensure the destination and amount are correct.
If they are, press ‘Confirm Transaction’ which will send the transaction information to your Ledger device.
On your Ledger device, ensure that the destination and amount look accurate, then use the buttons on your Ledger device to confirm or deny the transaction.

Receiving Nano

By default, Nault will attempt to receive incoming transactions automatically. This means that when leaving the wallet open, or re-opening it, incoming transactions will be sent to your Ledger device for on-device confirmation as soon as possible. Most of the time, you should not have to worry about manually receiving a transaction, but if it gets stuck or you have set Nault to “Manual Receive” in the app settings, you can use the following process:

Open the ‘Receive’ page from the left navigation
Press the ‘Receive’ button on the transaction you want to approve. This will trigger a confirmation on your Ledger device.
On your Ledger device, ensure that the transaction information looks correct, then use the buttons on your Ledger device to confirm or deny the transaction.

There is also a setting in the Nano app on the Ledger as well called auto-receive. That will skip the manual approval on the device. If you can't receive a transaction, try change this setting. It has happened it's not working properly.

Changing Your Representative

If you want to change your account’s representative, or if Nault has detected you are using a rep not optimal for the Nano network, you can easily do so from the settings/Representatives or from the Account view for any of your accounts.

Easiest way is to go to settings -> Representatives
Select one of your accounts (or all) that you want to change
Paste any representative account or select one from the Nault recommendations
Press the update button and confirm on the Ledger device

You can also find what representative you are using for individual accounts via the ‘Accounts’ page. Also change them with the edit button.

============================

Final Words

With that information, you are ready to store Nano with your Ledger Device and access it easily at any time using Nault! Besides just supporting Ledger devices, Nault also adds in lots of helpful features such as local currency values, a fully integrated address book, QR-reader, offline signing capabilities and more which make sending and receiving Nano simple and secure.

Data Storage

Nault does not store any information about you on a server. The only information stored is in your local browser storage (if not set the app setting to delete it when the browser is closed, or using an incognito tab) which allows you to use your wallet more easily on subsequent visits. With a Ledger device, the only information stored is your public account addresses, since that is the only information exposed by the Ledger device. It’s also recommended to secure your Nault wallet with a password and lock it everytime you are done with it. That way your funds can only be accessed with the password.

============================

Troubleshooting

Some Ledger problems are not related to Nault but to the device itself and limited compatibility.

Failed to connect the ledger in Nault

If you get errors while importing the ledger or when reconnecting to it, try one or several of the following most common issues. Make sure to reload the Nault app or web page after each step.

Close other application that may disturb, especially Ledger Live, other running Nault or crypto wallets.
Make sure the Nano app in the Ledger is running, or restart it.
Use the latest Nault desktop app. The Ledger protocol used in the Desktop app is usually less sensitive compared to the web version as well. At least try with another browser. Chrome is usually the best one. Latest Edge, Brave and other Chromium based browsers work well too. Firefox currently uses an older protocol but could be more stable.
Change USB port. It can be in bad shape or just changing from USB2/USB3 or vice versa can help. Try a port that is directly from the computer motherboard, no hubs.
Change USB cable. A low-quality or very long cable can be problematic. We recommend using the one the came with the Ledger.
Restart the computer or try with another. Open ledger live and manager to make sure the Ledger works. Upgrade to the latest Ledger firmware. Try a different operating system.

Failed to connect using Bluetooth

PC: Requires BLE support
Android: Currently not supported

This is a Windows thing when using the legacy U2F protocol. Usually seen in Firefox or older browsers. Try to use the latest Nault desktop app. The Ledger protocol used in the Desktop app is usually less sensitive compared to the web version as well. At least try with another browser. Chrome is usually the best one. Latest Edge, Brave and other Chromium based browsers work well too.

The transactions are not received

There is a setting in the device Nano app that enables automatic receive. Then another setting in Nault app settings for automatic receive. If enabling both of them still doesn’t work, go to the “Receive screen” in Nault and manually receive the transaction. That is usually the preferred method when dealing with the Ledger to avoid getting spam transactions.
It could be an error with the backend server or heavy network traffic going on that has introduced a delay. Try changing to another server from the app settings. More info here. You can also copy your account and open it in another block explorer like nanocrawler to verify the pending/incoming transaction.

The wallet shows zero balance

Do not panic, this is a common error. If no one else has access to your Ledger backup mnemonic or PIN code, the funds are going nowhere.

Make sure the Ledger is connected. Should be a green notification.
Go to the account screen. Make sure the account displayed are the one you sent Nano to. Click on it to check the history. If the account is missing, try “Add new account” or several like 20. If it still doesn’t show, you have not sent Nano to the Ledger but to an account that belongs to another seed not stored in the Ledger. You need to find that and import to Nault.
It could be an error with the backend server or heavy network traffic going on that has introduced a delay. Try changing to another server from the app settings. More info here. You can also copy your account and open it in another block explorer like nanocrawler to verify the balance.

Nault Docs

How to use Nault on a bootable Linux flash drive

Table of Contents

Introduction

Preparing the USB flash drive with Slax

Install Nault inside Slax

Advanced: Protect your persistent data

Advanced: How to compile Nault from source code inside Slax

Advanced: Store Nault as a Slax module

How to use multi-signature (multisig) in Nault

Table of Contents

Introduction

Generate a Multisig Address

Create a New Transaction Block

Sign the Transaction Using Multisig

Publish the Multisig Transaction

Troubleshooting

Custom Work Server

Table of Contents

Features

How To

Work Server

Nault Settings

Limitations

Nault advanced features: Changing backend servers and using the block explorer

Table of Contents

When to change server and how to do it

What other networks exist and how to use them

The Nault block explorer

Other Wallet Settings

The security of your Nano

Table of Contents

What does it mean to own Nano?

The Nano Protocol

The Storage of Keys

Keys in Nault

Keys in a Hardware Wallet

Keys on Paper

The usage of Keys

Transact with an online Nault

Transact with the Ledger hardware wallet

Transact using a remote-signing procedure

How to use the Ledger Nano in Nault

Table of Contents

Installing The Nano Application

Configuring Your Ledger With Nault

Your Ledger Status

Using Nault to Send, Receive or Change representative via the Ledger

Sending Nano

Receiving Nano

Changing Your Representative

Final Words

Data Storage

Troubleshooting

Failed to connect the ledger in Nault

Failed to connect using Bluetooth

Annoying popup

The transactions are not received

The wallet shows zero balance