Offline wallet generator

This page generates a new
wallet. It is self contained and
does all the necessary calculations locally, so is suitable for generating a new wallet on a machine
that is not connected to the network, and may even never be. This way, you can create
a Monero/Aeon wallet without risking the keys. This file is GPG signed, see GPG instructions.
You can check for up to date versions of this page
here.

Custom entropy for deterministic wallet (leave empty to use the browser's PRNG)

WARNING: entropy is way too low for the wallet to be secure: aim for 256 bits (about a hundred dice throws)

or

(very slow for more than a few characters)

(restoring non English language seeds needs a recent simplewallet)

Public address

This is the address you give to third parties to send aeon/monero to you.
It is the only information here that's meant to be public.

generating...

Mnemonic seed

The mnemonic seed is a string that comprises 24 (Aeon) or 25 (Monero) words and allows you to recreate your
private keys. Keep it secure!

Generating...

Private keys (optional)

The spend key and view key are the raw private keys for the
new wallet.
They are here for your information, since they can be recovered using the mnemonic
seed in the above box.
If you decide to keep them, keep them secure.

Spend key:

Generating...

View key:

Generating...

Credits

Made by moneromooo, based on code from MyMonero. Copyright notices in the source.
Thanks to antanst for the CSS, and to luigi1111 for crypto fixes and improvements.
If you found this useful, a donation would be appreciated:

How to verify GPG signatures

All released versions of this page will be GPG signed by moneromooo, to avoid trojaned versions
being passed around. It is in your interest to check the signature.

This page is maintained as a
git repository.
All commits are signed. In addition, released versions of the page are signed separately.
In order to check either, you first need to import
moneromooo's GPG key
from the Monero source tree:

gpg --import moneromooo.asc

Checking a standalone signature

You need to get the signature file corresponding to the version of the page you're using.
Original signature files are
in the git repository
as well. Save it as monero-wallet-generator.html.asc, then:

gpg --verify monero-wallet-generator.html.asc

You should see a message similar to:

gpg: Good signature from "moneromooo-monero <moneromooo-monero@users.noreply.github.com>"

Check the signature is from the key you imported previously! If not, you may be checking
that file was properly signed by an attacker instead of moneromooo. Beware that anyone can
place any email address in a new GPG key, so the right email being shown is no guarantee.

NOTE: you will probably also see a warning like this:

gpg: WARNING: This key is not certified with a trusted signature!

That is expected, as you only told GPG to import the signature in the steps above, but not
to trust it. Look for tutorials on GPG if you want to do this, but it is not necessary here.

If you want to verify an old version of the file, you will have to retrieve the matching
signature file from git.

Checking a git commit's signature

If you're using git to get the latest and greatest, it's even simpler:

git show --show-signature

You should see a message similar to:

gpg: Good signature from "moneromooo-monero <moneromooo-monero@users.noreply.github.com>"

Check the signature is from the key you imported previously! If not, you may be checking
that file was properly signed by an attacker instead of moneromooo. Beware that anyone can
place any email address in a new GPG key, so the right email being shown is no guarantee.