Using Ledger Nano

banner image

How to use Ledger Nano S and Ledger Nano X

The Ledger Nano S and Ledger Nano X are hardware wallets designed to securely lock private key access inside offline physical storage elements. Installing the Ravencoin application allows you to monitor and signatures regular transactions safely. Note: Native internal management of Ravencoin custom asset layers is currently unsupported on ledger firmware interfaces at this time.

Before you begin

  • Download and deploy the official desktop version of Ledger Live.
  • Initialize and secure your basic Ledger hardware key configuration profile.
  • Verify that your physical device is running the latest baseline core firmware modules.
  • Ensure the official Bitcoin App is installed first, as the Ravencoin engine shares base library files.

Installing the Ravencoin Ledger Module

  • Connect your physical hardware device via USB and input your custom access PIN.
  • Open Ledger Live and navigate directly into the Manager tab menu interface.
  • Confirm and allow device connection permissions on your hardware screen if requested.
  • Locate the Ravencoin entry listing within the App Catalog selection tree.
  • Click Install. If an error block requests dependency profiles, update your Bitcoin client application framework first.

Setting Up Electrum-Ravencoin

To orchestrate external transfers alongside cold-storage device protections, download the specialized desktop utility suite: Electrum-Ravencoin Wallet Client →

  • Attach your Ledger device, enter your lock PIN, and access the native on-device Ravencoin dashboard.
  • Launch the Electrum-Ravencoin application on your workstation while closing default Ledger Live scripts.
  • Select your workspace file path profile name and advance past the wallet profile naming confirmation block.
  • When presented with construction parameters, explicitly mark Standard Wallet as your choice.
  • On keys source allocation steps, click Use a hardware device and advance.
  • Select the scanned hardware identity label: an unnamed ledger [ledger, initialized].
  • Confirm the standard derivation path configurations without manual string overrides.
  • Choose whether to encrypt configuration metadata file caches locally on your computer to finish setup.