Blog

/

Exporting Keys from Substrate ...

Exporting Keys from Substrate apps in Ledger

December 20, 2022

1 min read

Security


The use of different algorithms can affect the use of the same mnemonic phrase in multiple wallets.

Even though most wallets generate a mnemonic phrase for users to back up their wallets and generate a private key from the mnemonic, not all wallets use the same algorithm tor this key generation process. This variety of  algorithms cause unexpected behavior when using the same mnemonic phrase in multiple wallets. Indeed, wallets that use different processes will arrive at a different set of addresses from the exact mnemonic phrase.

Ledger, the three-part system comprising a hardware device, the Ledger Live app, and a platform of integrated dApps, or better known as the the Most Secure self-custody option, uses a standard called BIP 39 for the generation and interpretation of the master seed on all of its' devices. BIP 39 is an industry standard used by many other hierarchical deterministic wallets. The exact type of BIP 39 seed used by Ledger devices by default is a 24-word mnemonic. Accounts generated by a Ledger device can be recovered on any (third-party) hardware or software wallet that supports the same standards as Ledger (BIP32/BIP39/BIP44).

It is important to understand that the same mnemonic may generate different private keys on other wallets due to the various cryptographic algorithms used. For example,  Subkey and Polkadot-JS based wallets use the BIP39 dictionary for mnemonic generation, but use the entropy byte array to generate the private key, while full BIP39 wallets (like Ledger) use 2048 rounds of PBKDF2 on the mnemonic. The above explains why users may have trouble exporting their keys from substrate based applications on the Ledger device. See Substrate BIP39 Repo for more information.

  • Instructions on how to export your accounts here (Ledger Developers Portal)


Read More


What Every Developer Needs to Know About Paseo Testnet

Paseo is the go-to testnet for Polkadot developers—offering a stable, community-driven space to test and refine projects. Zondax ensures seamless support and innovation.


Making the Most Out of the Beryx API: Your Ally for Filecoin Development

For over a year, Zondax has developed the Beryx Explorer and API. With over 90 endpoints, it streamlines interactions with the FVM and FEVM.


Bridging the Gap: A Guide to the ICP-EVM Proxy

The ICP-EVM Proxy is a PoC bridging ICP and Ethereum ecosystems. It translates ICP canister data into Ethereum-compatible formats, enabling cross-chain interaction and use of tools. Opeing doors for cross-chain dApps and simplified on-chain event tracking.

Other Articles


678514d06dc6b200aabd5efa

Protocol

January 14, 2025

What Every Developer Needs to Know About Paseo Testnet

Paseo is the go-to testnet for Polkadot developers—offering a stable, community-driven space to test and refine projects. Zondax ensures seamless support and innovation.

6710ee28526e0c00aab62892

October 17, 2024

Making the Most Out of the Beryx API: Your Ally for Filecoin Development

For over a year, Zondax has developed the Beryx Explorer and API. With over 90 endpoints, it streamlines interactions with the FVM and FEVM.

67a62c4696ac8500ab5a3dd7

February 7, 2025

Bridging the Gap: A Guide to the ICP-EVM Proxy

The ICP-EVM Proxy is a PoC bridging ICP and Ethereum ecosystems. It translates ICP canister data into Ethereum-compatible formats, enabling cross-chain interaction and use of tools. Opeing doors for cross-chain dApps and simplified on-chain event tracking.

Making the Most Out of the Beryx API: Your Ally for Filecoin Development

For over a year, Zondax has developed the Beryx Explorer and API. With over 90 endpoints, it streamlines interactions with the FVM and FEVM.

6710ee28526e0c00aab62892
Bridging the Gap: A Guide to the ICP-EVM Proxy

The ICP-EVM Proxy is a PoC bridging ICP and Ethereum ecosystems. It translates ICP canister data into Ethereum-compatible formats, enabling cross-chain interaction and use of tools. Opeing doors for cross-chain dApps and simplified on-chain event tracking.

67a62c4696ac8500ab5a3dd7