There are several options available to manage your NEAR and NEAR-based assets.
As with all blockchains, to claim or receive tokens you will need to generate a keypair which stores your crypto. You can do this directly by using a hardware wallet and the command line or indirectly by using a commercially available web or mobile wallet. All of these options are described below.
- Mobile Wallets
- Web Wallets
This list will be regularly updated as more products and providers offer NEAR support.
Option 1: Trust Wallet
- Trust Wallet is a very popular, non-custodial, wallet available on iOS and Android.
Setup Trust wallet and generate public key
- Install Trust Wallet on your phone from App Store or Play Store
- Create a new wallet (or use existing if you already have one setup)
- Make sure to back up your recovery seed phase as you would usually do.
- In "Settings" in upper right corner, toggle NEAR.
- In the main wallet view, click on "NEAR" and then "Receive".
- You will see QR code and address in the form
NEAR2F4vDeD9Brbo6cgPAPLMzXrZXza3EXfwS7hrK76SpHwBH4sEud- this is public key you can use to claim your tokens.
Option 2: TBD
(more added soon!)
CLI (Recommended for developers and validators)
Option 1: Ledger via CLI
For users with advanced security requirements and the need for flexibility (developers and validators), we highly recommend using our command line interface (NEAR-CLI) with a Ledger hardware device.
This community-authored guide walks through several common commands.
Installing the NEAR Ledger App
You can install the NEAR Ledger app using Ledger Live by:
- Open Ledger Live and install any available firmware updates
- Go to
Developer Modeis switched on
- Return to the
Managertab and search for NEAR
- Follow instructions to install the NEAR app on your device
Updating the NEAR Ledger App
You will need to have the latest Ledger device firmware installed (which can be done in Ledger Live's "Manager" tab) and the latest NEAR app. If you previously installed the NEAR app, it may need to be updated.
Currently, while the NEAR app is in Development Mode (while Ledger finishes reviewing it), this update may only be possible by uninstalling and reinstalling the app from the "Apps Installed" section of the "Manager" tab.
Make sure to quit the Ledger Live app when interacting with your ledger from the CLI or you'll get an error like
Error: cannot open device with path IOService ..........
To generate public keys
Make sure you have npm installed
Make sure you have quit Ledger Live (or you'll get a
Error: cannot open device with path IOService ..........error)
sudo npm install -g near-cli(or similar command on Windows).
near generate-key key --useLedgerKeycommand to generate the key for your Ledger device. It will output a public key that can be used to claim your NEAR tokens. Note 1: in the case of generating a key using the Ledger device, the 2nd argument is ignored and can thus be anything.
Note 2: This command will output the same key no matter how many times it is run.
If you want to generate more keys, you will need to provide an HD path as a value to the
--useLedgerKeyflag. Each change in the last number will produce a new key and you can use any number, as the following examples show:
# Example 1: near generate-key key --useLedgerKey="44'/397'/0'/0'/2'" # Example 2: near generate-key key --useLedgerKey="44'/397'/0'/0'/11'"
After confirming the key on your Ledger device (which should be opened to the NEAR app), the result you will see output in the console is in the format:
Using public key: ed25519:D9Brbo6cgPAPLMzXrZXza3EXfwS7hrK76SpHwBH4sEud
...which is the public key you can use to claiming your NEAR tokens. Note: the key includes the
ed25519:portion, so the full key is
ed25519:D9Brbo6cgPAPLMzXrZXza3EXfwS7hrK76SpHwBH4sEudin this example.
Best Practice: Keep a log (eg spreadsheet) of which HD paths map to which keys and what their purpose is so you don't end up accidentally re-using public keys and potentially de-anonymizing yourself
Option 2: Self custody
For professionals who have their own setup, you can self custody on an offline device or any other custom method (CloudHSM, etc).
Generally, any software that can produce valid
ed25519 key pair can be used to generate the keys. For NEAR consumption they should be encoded in base58 encoding.
For example, if you have offline device - you can install near-cli via
sudo npm install -g near-cli and generate keys in the following way:
export NEAR_ENV=mainnet near generate-key some-account-name
It will output the public key in the format
Using public key: ed25519:D9Brbo6cgPAPLMzXrZXza3EXfwS7hrK76SpHwBH4sEud, which is the public key which you can then use for claiming your NEAR tokens (it includes the
ed25519: portion, so the full key is
ed25519:D9Brbo6cgPAPLMzXrZXza3EXfwS7hrK76SpHwBH4sEud in this example).
The private key is stored in the plain-text format in
Custodians (Recommended for institutional users)
Option 1: Finoa
Status: Currently available
Option 2: Coinbase
Status: Implementation Phase, no estimated date
Option 3: TBD
(more added soon!)
Option 1: NEAR Wallet
The NEAR Web Wallet provides a way to interact with NEAR network from web without needing to install a wallet.
Currently, the NEAR Wallet doesn't allow you to create just a public key. Instead, if you have an allocation of NEAR tokens, ask your facilitator (eg CoinList or the NEAR Foundation) to send you a NEAR Drop and follow this guide.
NEAR Wallet also supports Ledger hardware devices for improved security. Note: currently NEAR Wallet only supports single HD path on Ledger, meaning that all accounts will use the same public key.