In this browser Recommended Faster
Keys never leave your device.
- Expected
- –
- Half the time within
- –
- 95% of the time within
- –
- This computer
- measuring…
What to search for
Up to 8 hex digits, with or without a leading !. Shorter is a prefix (dc80 means !dc80????). * ? . x match any digit. A comma list (dead,beef,cafe, up to 64) accepts any of them; every entry must fix the same positions. Needs firmware 2.8 or later.
Hex characters at the start of the Ed25519 public key; each one makes the search 16 times longer. The remote GPU takes up to 11; in this browser there is no limit. Prefixes starting 00 or FF are reserved by MeshCore.
–
Where to run it
Remote GPU Faster
Much faster for long patterns, but your private key is generated on a server you do not control.
- Expected total
- –
- Made up of
- –
- GPU service
- checking…
Against best practice. A private key should be made on a device you control. With this option it is made on a rented GPU.
How the exposure is limited, and what remains
- The result is encrypted end to end (P-256 ECDH, HKDF-SHA256, AES-256-GCM) to a key that is created for this one job, exists only in this browser tab, cannot be exported, and is discarded afterwards. The website, Cloudflare and RunPod's job store only ever handle ciphertext.
- Only the pattern and that one-time public key are sent. Nothing is logged and nothing is stored.
- The search engine is open source: MeshVanityKey (MIT).
- What remains: while the search runs, the key exists in the GPU's and the worker process's memory. The operator of this service or the GPU host could, in principle, read it there. If you cannot accept that, use this browser.
Searching
- Queued
- Starting GPU worker
- Searching
- Decrypting
- Done
- Chance found by now
- –
- Keys tried
- –
- Speed
- –
- Elapsed
- –
- Expected remaining
- –
- Keys found
- –
Your key
Shown once. This key is not stored anywhere: not on a server, not in this browser. Copy it or download it now; reloading or leaving the page loses it. Keep the private key secret.
Installing it on a Meshtastic radio
Needs firmware 2.8 or later (older firmware takes the node number from the MAC address). Back up first: a new private key gives the node a new public key and a new node ID, so other nodes see a new node and existing direct messages break until they learn the new key.
meshtastic --get security.private_key --get security.public_key
meshtastic --export-config > before-vanity.yamlThen run the meshtastic --set security.private_key … command shown above. After the reboot, meshtastic --info shows the new node ID.
Installing it on a MeshCore radio
Import the 128-hex-character private key as the device's identity key with your MeshCore client or firmware tooling (the exact menu depends on the client; the key format is the one MeshCore uses for identity import and export). The public key is the node's identity, so existing contacts see a new node.