Solflare
Solflare Ledger: When to Use Hardware Signing
Solflare connects to Ledger hardware wallets for managing Solana accounts, with transaction signing handled by the device. The pairing suits occasional transfers or SOL staking when keeping keys offline outweighs the extra approval step.
· last updated
- Wallet and signer
- Solflare provides the account interface; Ledger holds the private keys and signs transactions that require the selected account’s signature.
- Desktop USB connection
- An unlocked Ledger with the Solana app open, plus browser permission to access the connected device.
- Existing account selection
- The matching Ledger-controlled Solana address and derivation path for the holdings you want to access.
- Account backup
- A connected hardware account uses its Ledger backup. Solflare does not create a separate recovery phrase for it.
Occasional transfers and longer holdings
Ledger signing adds physical approval to transactions that require your account’s signature. That fits holdings you can manage with the device available, without exporting its recovery phrase into software. Assets remain on Solana; the hardware stores the keys that authorize their use.
Frequent signing can make that extra step inconvenient. A separate software account may suit routine activity better, provided you accept keeping its keys on your phone or computer.
Existing Ledger holdings in Solflare
Solflare can provide another interface for SOL and supported Solana tokens held at an existing Ledger address. Its account selection must match that address and the derivation path used to reach it. A derivation path determines which accounts the device derives from its recovery phrase. The holdings stay at the same address when you connect a different interface.
SOL delegation with hardware signing
Native SOL staking through Solflare also works with Ledger-connected accounts. A new stake account needs a minimum delegation of 1 SOL, plus SOL for network and account costs. This fits holders who want validator delegation while retaining device-based transaction approval.
Hardware signing does not remove the epoch-based wait for standard unstaking or its separate withdrawal step. Keeping SOL unstaked suits funds that must remain immediately available for spending.
Application permissions
A spending delegation can authorize an application to move specified tokens later without another signature from your Ledger account. Ledger approval authorizes that permission while its private keys remain on the device. A separate testing account can limit which holdings those permissions reach.
Hardware signing for an existing SOL balance
Adding a Ledger account does not change the keys that control an existing software account.
In this hypothetical case, SOL sits in a Solflare software account, and a separate Ledger account uses a different recovery phrase. The holder wants device approval for their future SOL transfers and keeps both phrases private.
Connecting Ledger makes its own account accessible through Solflare; the original SOL balance remains under the software keys. After a confirmed transfer to the verified Ledger-controlled Solana address, the transferred SOL is controlled by that account’s keys. Any balance left in the original account retains software signing. The Ledger recovery phrase must stay out of software to preserve that separation.
