Nobody else has your private key
Your browser makes it and your browser keeps it. It never travels to us, not in full, not in pieces, and not hidden inside anything else we receive.
UNDER THE HOOD
Only you can open
your wallet.
Your private key is created inside your own browser. Our servers never receive it, never store it, and never get a copy of it. You do not even need an account to mine.
0 private keys uploadedAES-256 encrypted backupsSaved on your device only
Open the miner ↗
01 Configure02 Generate03 Match04 Keep
Is my private key ever sent to VAULT?NO
Does VAULT save a copy of my wallet?NO
Is my backup file encrypted?YES
Can I export my keys whenever I want?ANYTIME
Is there a sign-in, account or registration?NONE
Can VAULT restore a key I lost?NO
We do not save your wallet
There is no wallet record sitting on our servers with your name on it. If we were hacked tomorrow, your keys would not be in the pile.
Backups are locked with your password
A backup file is encrypted with a password only you know. We never see the password, and the password is not written inside the file either.
THE EASY VERSION
Think of a mailbox.
Your public address is the mail slot.
Anyone can drop coins through it. That is the whole point of it, so sharing it is completely safe.
Your private key is the only key that opens it.
Whoever holds it owns the money. Keep it to yourself. VAULT never holds it, so VAULT can never open your wallet.
One rule: share the address, never the key. The miner follows that rule for you.
YOUR DEVICE
Public addressyours
Private keyonly here
Backup passwordonly here
Mined wallet listonly here
Keys are born in this browser and stay in this browser.
VAULT SERVERS
Public addressyes
Pattern + proofyes
Private keynever
Backup passwordnever
Your wallet listnever
We only ever receive what you would post publicly.
WHAT LEAVES YOUR DEVICE
Two things go out.
Neither one is a key.
✓Your public addressSENT
✓Matched pattern + signed proofSENT
✗Your private keyBLOCKED
✗Your backup passwordBLOCKED
✗Your saved wallet listBLOCKED
WHERE YOUR WALLETS LIVE
In your browser.
On this device.
Nowhere else.
Every wallet you find is written to this browser's local storage on this computer. That is why the list at the bottom of the miner is still there when you jump over to this page and come back, and why it survives a refresh or restarting the browser.
It is not sent to our servers, not tied to an account, and not stored in a cookie. Clear your site data or move to a different device and the list starts empty, because we never had a copy to give back to you.
Export the wallets you care about.Take the .txt files before you clear anything. We cannot rebuild a private key we never received.
0password stretching rounds on every encrypted backup
0private keys ever sent to VAULT servers
0of key generation happens in your browser
ENCRYPTION
Locked with a password only you know.
- 1You type a password
It sits in the input box while you use it and then disappears. It is never saved and never uploaded.
- 2We stretch it 0 times
PBKDF2-SHA256 turns a short password into a very strong key. Slow on purpose, so guessing it is hopeless.
- 3AES-256-GCM locks the keypair
A fresh random salt and a fresh random IV every single time. Any tampering with the file is detected on open.
- 4You download the file
A small .json lands in your downloads. The password is not inside it. The key is unreadable without your password.
WHAT THE FILE LOOKS LIKE
{"v":1,"salt":"8f3c1d...","iv":"b71a...","ct":"d41d8cd98f00b204e9800998ecf8427e"}Restoring is done right here on the Miner page. Your file is decrypted by your browser, and the raw keypair is downloaded straight back to you.
THE PROCESS
From pattern
to public key.
This is illustrative code so you can follow along. The real miner runs the same idea in background workers.
>_ OUTPUT
Shorter is faster.
Try 2–3 characters first. Longer patterns can take hours or more.
Your CPU. Your call.
Choose your thread count. Stop whenever you want your device back.
Save before you leave.
Grab an encrypted backup or a raw keypair. Keep the password and the file safe.
A FEW DETAILS
Before you mine.
Short answers, no jargon. If anything here is still unclear, the source files are linked at the bottom of this page.
Does VAULT save my wallet?
No. Your browser creates the key, your browser checks the address, and your browser keeps the result. Our servers only receive the public address and a signed proof so it can appear in the shared CLAIMED feed. There is no server-side copy of your wallet.
Who holds my private key?
Only you. It exists in this browser tab and in the files you export. It is never transmitted to us, never written to an account, and never recoverable by anyone but you.
Where is my found-wallet list stored?
In your browser's local storage on this device, which is why it stays put when you switch between the Miner page and this one. It is never uploaded. Clearing site data, using a private window, or switching device starts the list fresh.
What happens if I clear my browser data?
The saved list is deleted. That is the tradeoff for keeping it off our servers. Export the .txt files you want to keep before you clear anything.
Can VAULT restore a key I lost?
No, and no service can without breaking the whole point. We never received your key, so there is nothing to restore from. Your export files are the backup.
How is my backup encrypted?
PBKDF2-SHA256 derives a key from your password with 600,000 iterations, a fresh random salt and a random IV. AES-256-GCM then encrypts the keypair. Your password is not stored in the file and is never sent anywhere. Use Restore encrypted backup on the Miner page to decrypt it locally.
Which characters can I use?
1–5 Base58 characters per pattern. Matching is case-sensitive, and the characters 0, O, I and lowercase l are excluded because they look too much alike.
Does mining cost anything?
No. Generation is free and needs no account. Your device supplies the processing power. Sending the coins later still takes SOL for network fees.
Is the code above a real miner?
No. It shows the process without generating a wallet or using threads. The Miner page runs the real thing in background workers.
CLEAR, CHECKABLE PRIVACY
What happens to your keys.
You should know where a wallet comes from, what leaves your device, and what you need to keep safe. Here is how the current browser miner works, with no marketing in it.
Your browser creates the wallet.
The miner uses your browser's Web Crypto implementation to generate Ed25519 keypairs inside background workers. The server does not choose a private key for you or send a pre-generated wallet to your browser. The worker checks the public address against your pattern and returns a match to the page.
A vanity pattern changes which generated addresses are accepted. It does not turn your chosen word into a password or private key. The wallet still comes from a newly generated cryptographic keypair.
Your private history stays on this device.
Scroll below the miner to see every wallet found. Starting another search keeps earlier matches in Your mined wallets, and that list survives page changes, refreshes and browser restarts, so it is still there when you come back from this page.
The list is stored in your browser's local storage and is never sent to the server, written to cookies or attached to your account. Clearing site data or moving to another device erases it, so export the wallets you want to keep. It cannot recover private keys from a previous device or a cleared browser, and the public CLAIMED feed cannot restore them.
Public discoveries are shared. Keys are not.
To publish a browser discovery, the page sends its public address, matching pattern, match position and a signed proof. The server verifies that proof, adds a time and an anonymous miner label, and stores the public discovery. Other visitors can see it in CLAIMED.
The signed message identifies a VAULT discovery. It is not a Solana transaction or a request to spend funds. The request contains neither the private keypair nor your encrypted-backup password. Like other websites, the server receives ordinary connection information, such as your IP address; the public feed does not display it.
Export a key you control.
Each wallet has an Export private key .txt button. Export all .txt puts every wallet currently in your list into one file. These downloads are assembled locally using a browser Blob; a server does not create or deliver the key file.
The TXT contains the public address and a Base58-encoded 64-byte Solana private keypair. It is not a seed phrase. Use a wallet that supports this import format. A TXT file is unencrypted: anyone who obtains the private key can control that wallet. Do not paste it into support chats, public messages or unfamiliar import pages.
Add a password before storing a backup.
Every wallet in your list also offers an encrypted backup. Your browser derives an encryption key from your password using PBKDF2-SHA256 with 600,000 iterations and a fresh random 16-byte salt. AES-256-GCM encrypts the keypair with a random 12-byte IV and includes an authentication tag to detect alterations.
The downloaded backup contains ciphertext and the parameters needed to decrypt it. The password is not stored in the file or sent to the server. Use a long, unique password and keep it separately. Restore encrypted backup on the Miner page reads and decrypts the file locally, then downloads the raw keypair. There is no password-reset or lost-key recovery service for these backups.
Understand the protection and its limits.
The current browser miner has no private-key upload in its generation, history or export flow. That is a statement about this implementation, not a guarantee that any website or device can never be compromised. The page necessarily handles the key in memory while it is open. Malicious extensions, device malware or modified site code could read it.
No existing-wallet connection or existing private key is needed to generate a new address. Check the site you are using, keep your browser and device secure, and verify an import before putting significant funds in a new wallet. We do not claim an independent security audit or promise that a wallet can never be drained.
At a glance
| Data | Where it lives | Sent by the browser miner? |
|---|---|---|
| Private keypair | Browser local storage and your exported files | No |
| Backup password | Browser input and encryption operation | No |
| Encrypted backup | Your downloaded file | No |
| Saved wallet list | This device only | No |
| Public address, pattern, proof | Browser and shared discoveries service | Yes |
| Thread-count setting | Local browser settings | No |
Browser wallets and the legacy vault are different.
The privacy description above applies to new wallets generated by this browser miner. VAULT no longer has website accounts at all: there is no sign-in, no registration and nothing here is tied to a login. Browser keypairs are never copied into the older desktop vault. Historical public discoveries are shown for activity, not as a source of private keys.
Do not take our word for it.
These are the exact files your browser loads. Open them, or watch the network requests in your own dev tools.
Key generation ↗ Local history & TXT export ↗ Encryption & restore ↗ Discovery requests ↗