Litecoin · LTC
A Litecoin wallet whose key is on another device
LTC in a Chrome and Brave extension, on the same engine that signs Bitcoin - parameterised, never duplicated - while the key that signs stays on a device with no network.
The Bitcoin engine, parameterised
Litecoin is not a second implementation: it is the same UTXO engine, the same PSBT, the same review screen, with this chain’s own parameters. What has been proven on Bitcoin holds here, instead of being written twice and tested once.
A fee above the amount is refused
The classic mistake on these chains is a fee-per-kilobyte read as a fee-per-byte, which turns a small transfer into a large donation to a miner. A send whose fee exceeds what it moves is refused outright, and there is no checkbox to arm it.
Signed off the machine
The unsigned transaction leaves as a QR code and comes back signed. The offline device shows the outputs, the fee as a share of the amount, and any output below the dust limit - then signs, and never sees a network.
The same recovery phrase
The Litecoin address comes from the phrase you already have, on Litecoin’s own derivation path, with ltc1 native SegWit addresses.
Litecoin wallet: questions people ask
Is the Locker Protocol Wallet a Litecoin hardware wallet?
It is the same idea without the hardware: the key lives on a second device you already own, kept offline, and signs through QR codes. There is nothing to buy, nothing to plug in, and the software is open-source and reproducible.
Which Litecoin addresses does it use?
Native SegWit (ltc1), derived from your recovery phrase on Litecoin’s own path.
Can it send to a legacy L-address?
Yes. The review screen on the offline device names every output and the fee before you approve it.
Does it cost anything?
No. The extension and the Vault are free and open-source, and neither carries an account or any telemetry.
