How-To: Claim neurons for seed participants
You are a seed participant if you donated to the DFINITY foundation in February of 2017. At that time, 30 tokens per Swiss Franc of value donated were allotted to your key. These tokens are now called "ICP tokens" or, shortly, "ICP".
At Genesis Unlock your ICP were then disbursed to you in the form of a basket of 49 voting neurons (insert link "NNS" here). These neurons already exist inside the Network Nervous System (insert link "NNS" here). Your neurons contain the ICP you have been awarded, staked inside.
Your neurons have been configured to vote automatically and are already earning voting rewards for you. You do not need to do anything to initialize your neurons in order to continue earning voting rewards.
The 49 neurons created for you have dissolve delays (insert link "NNS" here) of 0 days, 30 days, 60 days, 90 days and so on. Apart from the first neuron which has a dissolve delay of 0 days (which can be dissolved immediately), the other dissolve delays may have a small random number of days either added or removed.
We are pleased to inform you that your neurons have been pre-aged! At the moment of Genesis Unlock, their age was already set to 18 months old. This is important, because neuron age significantly increases your voting power and the voting rewards you receive.
To control your neurons you must use the same secret key that you generated when the donation was made. It was recorded as a 12-word mnemonic phrase. In order to control your neurons you need to first claim the whole basket. This article explains how to do the claiming. For how to control your neurons after claiming them see this article (insert link here).
Claiming with a Ledger Nano device
Coming soon. This will come with the next update of the IC's app for the Ledger Nano. The current release can manage neurons but cannot yet claim them.
Claiming with an air-gapped computer
Claiming requires access to your secret mnemonic phrase and to secret keys derived from it. It is highly advised that you use an air-gapped computer for the purpose of claiming. If you are not comfortable with such a setup or with any of the following steps then you have to wait for the next release of the IC's app for the Ledger Nano device.
As an air-gapped device you can use a Windows, Linux or MacOS machine. Linux includes Raspberry Pi.
Download the tools
To download the tools you need a second, networked computer. The tools are called keysmith and quill. We describe here how to find and download a binary for your architecture. If you want to compile the tools yourself then we provide more information for you at the end of the document (TODO).
Binaries are available for the following hardware architectures. Here, architecture refers to the air-gapped computer, not the networked computer.
| Hardware | keysmith | quill |
|---|---|---|
| Mac, Intel silicon | darwin-amd64 | macos-x86_64 |
| Mac, Apple silicon (M1) | darwin-arm64 | not available |
| Linux (x86) | linux-amd64 | linux-x86_64 |
| Raspberry Pi | linux-arm32 | arm_32 |
| Linux (arm) | linux-arm64 | not available |
| Windows | windows-amd64 | windows-x86_64 |
Download keysmith
Go to keysmith, choose the latest release (currently v1.6.2) and fetch the .tar.gz file that matches the air-gapped machine's architecture in the table above.
Download quill
Go to quill , choose the latest release (must be >= 0.2.12) and fetch the .tar.gz file that matches the air-gapped machine's architecture in the table above.
Copy to air-gapped machine
Copy the .tar.gz files from the networked machine to the air-gapped machine. For example, you can do so with a USB drive.
Verify the hashes
On the air-gapped machine, go to the terminal. Change the directory to the folder where the .tar.gz files are. Compute the SHA256 hashes with the commands
openssl dgst -sha256 keysmith-*.tar*
and
openssl dgst -sha256 quill-*.tar*
The hashes should match the following entries:
SHA256(keysmith-darwin-amd64.tar.gz)= a53bad6fa36c1eb35cd36059ffe9cbf4c063b515e47ccf666b7e1c174a7d1088
SHA256(keysmith-darwin-arm64.tar.gz)= 47932452353fe7f921b4ac41828dd19530ae0c4bdb72bcbb016a0715ca80e879
SHA256(keysmith-linux-amd64.tar.gz)= cb283dac031d8676f25e72d19115be347d2b85c864a17dd563104bf496b14a06
SHA256(keysmith-linux-arm32.tar.gz)= b28670e2b3483ea9f9ba691e9f76f99df31b2678db33b69c888fb08b634de162
SHA256(keysmith-linux-arm64.tar.gz)= ebe9cde3cf440ebbfb53dd10bf7f412cbff8b089551100ee0fa48f3ac9bd66c3
SHA256(keysmith-windows-amd64.tar.gz)= 1ef9b77ccaae980aad4a227fe1a817821245da491a90f0e6ad323426b49ae40a
and
(enter quill hashes here)
Unpack and install
For keysmith:
tar -f keysmith-*.tar* -x
sudo install -d /usr/local/bin
sudo install keysmith /usr/local/bin
You will be prompted to enter your laptop password. The password itself will not appear, simply type it and press enter. For quill:
tar -f quill-*.tar* -x
sudo install quill /usr/local/bin
Run keysmith
keysmith
You should see:
usage: keysmith <command> [<args>]
Available Commands:
account Print your account identifier.
generate Generate your mnemonic seed and write it to a file.
legacy-address Print your legacy address.
principal Print your principal identifier.
private-key Derive your private key and write it to a file.
public-key Print your public key.
shortlist Print the available commands.
version Print the version number.
x-private-key Derive your extended private key and write it to a file.
x-public-key Print your extended public key.
If you are using macOS, making the keysmith binary executable might require you to change a permission setting using System Preferences > Security & Privacy > General.
Enter your mnemonic phrase (aka "seed")
If you confident that your environment is secure, then you are ready to enter your seed for use with keysmith. For the duration of your session, you store your seed phrase in an environment variable. It will be eliminated from your system when you turn your computer off.
read seed
Enter your seed phrase and finish with Return.
If you prefer to not have your seed phrase displayed as you type then use this command instead:
read -s seed
Optional: check your legacy address and balance
At this point you can already verify your legacy address and ICPT balance. The legacy address matches to what was formerly called "DFN address" in the Dfinity Chrome extension. You may have copied it from the Chrome extension for your records back when you used the extension.
echo $seed | keysmith legacy-address -f -
The output is a 40 character hex string. It looks something like this:
2d89d96b10f7a9456a9154b2f5309ee70df5bce1
You can check your ICPT balance as follows: Go to https://ic.rocks/principal/renrk-eyaaa-aaaaa-aaada-cai, look for "Canister interface" and the method "balance". There, paste your DFN address in to the field labeled "text" and click the button labeled "Query". Your ICP balance will appear below "nat32".
Create your private key (.pem file)
Derive your private key from your seed phrase.
echo $seed | keysmith private-key -f -
This creates a file identity.pem containing your private key.
Run quill
On the air-gapped computer run:
quill --pem-file identity.pem claim-neurons >msg.json
Copy the resulting file `msg.json` back to the networked computer. On the networked computer, change into the directory where `msg.json` is and run:
quill send msg.json
Your neurons should now be claimed.
You can double-check if you claim was successful in the following way: Go to https://ic.rocks/genesis/2d89d96b10f7a9456a9154b2f5309ee70df5bce1 where you replace 2d89d96b10f7a9456a9154b2f5309ee70df5bce1 with your own DFN address. Under "Status" you should see "Claimed".
If your claim was successful then do not forget to remove the .pem file on the air-gapped computer:
rm identity.pem