Hop Docs
User Docs
Developer Docs
Developer Docs
  • Welcome
  • JavaScript SDK
    • Welcome
    • Getting started
    • API Reference
  • API
    • API Endpoints
  • Hop Node
    • Running a Hop Bonder
      • Bonder Requirements
      • Choosing a Platform
        • EC2 Setup
      • Securing your Server
        • Add SSH 2FA
      • Installing the Bonder
        • Installing the Bonder with Docker (recommended)
      • Configuring the Bonder
        • Keystore
          • Keystore AWS Parameter Store (recommended)
          • Keystore Local Passphrase
        • Configuration
      • Testing the Bonder
      • Running the Bonder
        • Staking
        • Starting the Bonder
      • Next Steps
    • Bonder Options
      • CLI Commands
      • Keystore Options
      • AWS KMS Signer
      • Monitoring
        • Docker CloudWatch Logs
        • Prometheus
      • Running Docker Container Options
      • Contract State
    • Resources and Best Practices
      • Securing Cloud Instance
      • Additional Security & Node Best Practices
      • Additional questions
  • Subgraphs
    • Welcome
    • Entities
    • Queries
    • Subgraph Info
  • Smart Contracts
    • Welcome
    • Integration
    • Contract Addresses
  • Fees
    • Fee Calculation
  • RPC
    • RPC Endpoints
  • Other
    • Assets
    • On the web
    • FAQ
Powered by GitBook
On this page
  • Use a custom keystore location
  • Use an existing private key
  • Decrypt keystore
  • Re-encrypt keystore with a new passphrase
  • View keystore address
Edit on GitHub
  1. Hop Node
  2. Bonder Options

Keystore Options

Options when Using your Keystore

Use a custom keystore location

To use a custom keystore location, use the -path flag:

hop keystore generate --path /my/path/keystore.json
hop-node keystore generate --path ~/my/path/keystore.json

The default location is ~/.hop/keystore.json

Use an existing private key

You may generate an encrypted keystore using an existing private key by using the --private-key flag:

hop keystore generate --private-key=0x4f3edf983ac636a65a842ce7c78d9aa706d3b113bce9c46f30d7d21715b23b1d
hop-node keystore generate --private-key=0x4f3edf983ac636a65a842ce7c78d9aa706d3b113bce9c46f30d7d21715b23b1d

Note that you will no be prompted with the mnemonic in this case.

Decrypt keystore

Use the keystore decrypt command to decrypt an encrypted keystore:

hop keystore decrypt
hop-node keystore decrypt

It will prompt you for the passphrase required to decrypt it:

keystore passphrase: ********

It will display the private key if the passphrase is correct:

4f3edf983ac636a65a842ce7c78d9aa706d3b113bce9c46f30d7d21715b23b1d

Re-encrypt keystore with a new passphrase

Use the keystore reencrypt command to re-encrypt an encrypted keystore with a new passphrase:

hop keystore reencrypt
hop-node keystore reencrypt

View keystore address

Use the keystore address command to print the keystore public address:

hop keystore address
hop-node keystore address

Example output:

0x90f8bf6a479f320ead074411a4b0e7944ea8c9c1

Last updated 1 year ago