Private Key Generator for BTC, ETH, Solana and 10+ Networks

How the private key generator works

Each click creates a fresh random 12-word BIP39 phrase with your browser's cryptographic random number generator, turns it into a seed and derives one key pair for the selected network at that network's standard path. The page shows the private key, the public key and the addresses; the phrase itself is not shown, so the private key is what you save.

Curves, paths and address formats

The generator supports 18 networks. They differ in the elliptic curve, the coin type in the path and the way an address is encoded:

The second number in each path is the coin type registered in SLIP-44, which keeps the keys of different networks apart even when they come from the same phrase. Solana, Aptos, SUI and IOST keys come from SLIP-10 derivation, which on ed25519 only supports hardened steps; that is why every step of their paths carries an apostrophe.

Polkadot wallets do not share one scheme. The generator follows Ledger's Polkadot app, which derives ed25519 keys from the BIP39 seed with BIP32-Ed25519, a scheme different from SLIP-10, and hardens every step of the path as well. Polkadot.js, Subkey and the wallets built on them create sr25519 keys by default, straight from the phrase and without a BIP44 path, so the same phrase opens a different account there. A Polkadot key from this page is an ed25519 key, and a wallet has to import it as one.

Private key, public key and address

The private key is a 256-bit secret: whoever holds it controls the funds. The public key is computed from it and cannot be turned back into the private key. The address is a shorter, checksummed encoding of the public key (or of its hash) that you share to receive funds. EOS and IOST have no address derived from the key: an account there is a name registered on the chain and linked to one or more public keys. For these two networks the generator shows the public key in the chain's own format instead (EOS… for EOS, Base58 for IOST).

Check the derivation with the public test phrase

The generator only makes random phrases, but it derives keys exactly as described above. For the public BIP39 test phrase abandon abandon … about with no passphrase, its paths give these addresses. The phrase is public, so never send funds to them.

The four Bitcoin addresses come from one key. Wallets that follow BIP49, BIP84 or BIP86 keep nested SegWit, native SegWit and Taproot accounts on their own paths, so for the same phrase they show different addresses; see the derivation path guide. The legacy Bitcoin, Ethereum and TRON rows match the BIP44 results of the mnemonic code converter for the same phrase, and the Solana address is the first account at the path Phantom uses by default. The Polkadot address is the first account of Ledger's Polkadot app; with default settings, Polkadot.js and Subkey show 13KVd4f2a4S5pLp4gTTFezyXdPWx27vQ9vS6xBXJ9yWVd7xo for the same phrase, because they use sr25519 and no BIP44 path.

Documents on private key formats for Bitcoin, Ethereum, TRON, Solana and other networks are collected in the private key PDF archive.

Frequently asked questions

Can I import a generated key into a wallet?

Yes, in the format the wallet expects. Ethereum, TRON and other EVM wallets import the hex private key. Bitcoin, Litecoin, Dogecoin and Bitcoin Cash wallets import the key in WIF, which the generator also shows for these coins. Phantom and other Solana wallets import the Base58 key shown for Solana: the private key followed by the public key, 64 bytes in all. IOST's command-line wallet iwallet imports the Base58 key shown for IOST, built the same way. EOS wallets such as Anchor import the WIF key that starts with 5 or the PVT_K1_ key, and the generator shows both for EOS. Slush and other Sui wallets import the Bech32 key that starts with suiprivkey1, shown for SUI. The address the wallet shows must match the one generated here; for Bitcoin and Litecoin, the address of the script type the wallet uses. EOS and IOST have no such address: the key controls only an account linked to its public key.

Why does Bitcoin show four addresses?

They all belong to the same key pair, encoded in the four Bitcoin script types. Wallets choose one of them; funds sent to any of the four are controlled by the same private key.

Is a key generated twice?

No. Each click uses new randomness, and 2¹²⁸ possible phrases make a repeat practically impossible.