Monero / Wallets
Feather Wallet Setup: Your First Monero Payment
Set up Feather Wallet, verify the download, back up your seed, choose a node and send a small Monero payment. Learn what to check when funds seem missing.
Monero / Wallets / Privacy
Create a VeraCrypt container, understand hidden-volume protection, and build a LUKS2 file container on Linux for Feather wallet files and backups.

VeraCrypt and LUKS2 let you keep wallet files inside encrypted storage that you unlock when needed. VeraCrypt has a graphical container wizard and an optional hidden-volume feature. LUKS2 is a Linux encryption format managed with cryptsetup. Both can protect stored files, but neither protects an unlocked wallet from malware running on your computer.
If you are starting with Monero, follow Feather Wallet Setup: Your First Monero Payment for download verification, wallet creation and seed backup. This guide adds encrypted storage for the wallet files and records you want to keep.
A file container is one ordinary file on your computer that holds an encrypted filesystem. Unlocking and mounting it exposes a directory or drive where applications can read and write files. Dismounting closes that access.
| Option | Useful for | Main limitation |
|---|---|---|
| Standard VeraCrypt container | A graphical workflow across supported Windows, macOS and Linux systems | Each computer needs compatible VeraCrypt support and a readable filesystem inside the container |
| VeraCrypt hidden volume | A separate encrypted area inside an outer volume | Requires careful handling and cannot guarantee plausible deniability |
| LUKS2 file container | Linux users comfortable with terminal commands | Has recognizable encryption metadata and no VeraCrypt-style hidden-volume feature |
Use a standard container first unless you have a specific reason to accept the hidden-volume requirements. Check VeraCrypt's current downloads and platform requirements. For Linux storage behavior, consult the cryptsetup FAQ.
Full disk encryption remains useful alongside a container. Applications can leave temporary files, recent-file records or other traces outside the mounted volume. A container also cannot stop someone deleting its backing file. Keep a separate backup and use a computer you trust. VeraCrypt describes these boundaries in its security model.
Install VeraCrypt from its official download page and follow its verification instructions. The official beginner tutorial illustrates the Windows wizard. Other platforms may present controls differently.
wallet-records.hc. Selecting an existing file overwrites it rather than encrypting its contents.Keep this first test separate from your only wallet backup. You want to discover a forgotten password or filesystem compatibility problem before the container holds anything irreplaceable.
A hidden volume occupies space that the outer filesystem treats as free. It has its own password and filesystem. The outer password opens the outer files, while the hidden password opens the hidden files. Select the same container file for either volume. See VeraCrypt's hidden-volume documentation.
To practice with a new container:
Do not manually guess where the hidden volume should begin. Let the wizard calculate its placement.
The outer filesystem does not know that its free space contains hidden data. Writing to the outer volume can overwrite the hidden volume.
When you need to write to the outer volume, enter the outer password, open Mount Options, and enable Protect hidden volume against damage caused by writing to outer volume. Supply the hidden password there. VeraCrypt uses it to identify the protected area without mounting the hidden filesystem. Repeat this protection step every time you mount the outer volume for writing. Mounting the outer volume read-only is another option when you only need to read it. Follow the hidden-volume protection instructions.
VeraCrypt's hidden-volume precautions warn about comparing container snapshots over time, filesystem traces and wear leveling. The project specifically advises against hidden volumes on SSDs and USB flash storage because older fragments may remain on the medium.
Cloud version history and repeated backups can give an observer multiple snapshots to compare. Applications may also leave evidence elsewhere on the computer. If your plan depends on concealing the existence of files, read the full precautions before using real data. A successful mount test proves that you can open the volume, not that your setup provides plausible deniability.
This example uses a new 1 GiB file, LUKS2 and an ext4 filesystem. It needs cryptsetup, e2fsprogs and the usual Linux filesystem tools. Install them through your distribution's package manager. Mapping and mounting require administrative access.
Run the blocks one at a time in the same terminal. Stop if any command fails. These instructions create a file, not a partition. Do not replace the file path with a disk such as /dev/sda or /dev/nvme0n1. Formatting the wrong target can destroy data.
Create a private directory with a unique name. The new directory prevents this example from reusing an existing container.
umask 077
vault_dir=$(mktemp -d "$HOME/monero-vault.XXXXXXXX")
vault_file="$vault_dir/wallet.luks"
printf 'Container path: %s\n' "$vault_file"
dd if=/dev/zero of="$vault_file" bs=1M count=1024 conv=excl status=progress
Record the printed path. Check that dd completed successfully and that you have enough free disk space. This allocates the practice file. It does not encrypt anything yet.
sudo cryptsetup luksFormat --type luks2 "$vault_file"
sudo cryptsetup open --type luks2 "$vault_file" monero_wallet_vault
Inspect the target named in the confirmation prompt before typing YES. Enter the passphrase interactively, without putting it in a command or shell-history entry. Use a new, strong passphrase.
The first command initializes encryption metadata and keyslots. The second creates /dev/mapper/monero_wallet_vault, the decrypted block-device view. Cryptsetup handles a regular backing file through a loop device. If the mapping name already exists, stop and investigate rather than using it. Sources: luksFormat manual and open manual.
Run mkfs.ext4 only once, during creation. It replaces the filesystem on its target.
sudo mkfs.ext4 /dev/mapper/monero_wallet_vault
mount_dir=$(mktemp -d /tmp/monero-wallet-mount.XXXXXXXX)
sudo mount /dev/mapper/monero_wallet_vault "$mount_dir"
sudo chown "$(id -u):$(id -g)" "$mount_dir"
printf 'Mounted directory: %s\n' "$mount_dir"
The ownership change applies to the root of this newly mounted filesystem so your normal user can save files there. Do not run Feather as root. The plaintext view is the printed mounted directory, while the .luks file remains the encrypted backing storage. The mke2fs manual documents filesystem creation, and the mount manual explains attaching it to a directory.
Write and read a harmless test file:
printf 'Container test\n' > "$mount_dir/test.txt"
cat "$mount_dir/test.txt"
Close applications using the mounted directory. Move your terminal outside it, then run:
cd "$HOME"
sync
sudo umount "$mount_dir"
sudo cryptsetup close monero_wallet_vault
rmdir "$mount_dir"
Run the close command only after unmount succeeds. A busy-volume error means something is still using it. Close the relevant application or terminal and retry rather than forcing removal. See the umount manual and cryptsetup close manual.
In a later terminal session, set vault_file to the actual path you recorded. Replace the example path below before running it.
vault_file="$HOME/monero-vault.REPLACE-ME/wallet.luks"
sudo cryptsetup open --type luks2 "$vault_file" monero_wallet_vault
mount_dir=$(mktemp -d /tmp/monero-wallet-mount.XXXXXXXX)
sudo mount /dev/mapper/monero_wallet_vault "$mount_dir"
cat "$mount_dir/test.txt"
The test text should return. Reuse the unmount-and-close steps when finished. Do not repeat dd, luksFormat or mkfs.ext4 to reopen a container.
A LUKS header backup protects against some metadata damage. It does not contain your wallet files and cannot replace a data backup. Choose a new backup filename on separate storage you control:
sudo cryptsetup luksHeaderBackup "$vault_file" \
--header-backup-file /path/to/separate-backup/wallet-luks2-header.img
Replace that placeholder with a real destination. Protect this backup as sensitive recovery material. Someone with the backup, a passphrase valid when it was made and the corresponding encrypted data can decrypt that data even if you later change or remove that passphrase. The header-backup manual explains the consequence.
Keep a separate copy of the closed container as well, and test recovery using a copy rather than experimenting on your only original. A copied container retains its volume key. Changing its passphrase does not revoke older copies. Cryptsetup's backup and recovery FAQ covers this distinction.

Keep the wallet's own password protection enabled. The container passphrase and Feather wallet password protect different layers, and neither replaces the recovery seed.
For an existing wallet, close Feather before copying its complete wallet files into the mounted container. Keep the original backup until you have successfully opened the copy from its new location and checked the wallet. Use Feather's file-opening controls to select that copy. Feather stores wallet data in a keys file and a cache file. Check Wallet → Information for their location and copy both, as described in its wallet-file documentation.
For a new wallet, choose a location inside the mounted container when saving the wallet. Confirm the actual path before funding it. Then use the receive-and-send checks in our Feather setup and first-payment guide.
Keep a separate offline seed backup. Feather's seed restoration guide explains that restoring funds does not recover all local information, including labels, descriptions and transaction keys. Wallet-file backups help preserve those records.
After each session, close Feather before dismounting VeraCrypt or unmounting and closing LUKS2. Copy a whole container for backup only after closing it so the copy is consistent. Files copied out of the mounted volume are readable unless separately encrypted. Deleting an old plaintext copy does not prove that snapshots, backups or flash-storage remnants are gone.
Before relying on the setup, check that you can unlock it, open the correct wallet, close it cleanly and recover from a separate backup. Keep those recovery steps with your backup plan, without putting the only copy of a password inside the volume it unlocks.