Most PGP guides are written for people who live in a terminal. Most people do not. They are on Windows, or they are on Tails and would rather not type commands at all, and the result is a lot of buyers who never set up encryption properly and a lot of vendors who receive unencrypted addresses. Kleopatra is the answer to that. It is a graphical front end to GnuPG, it ships with Tails, and it does everything a darknet buyer or vendor actually needs: create keys, import someone else's, encrypt, decrypt, sign and verify.
This is the practical version. It assumes you want a working key and a repeatable routine, not a lecture on the web of trust.
Before anything else: keep the key
On Tails, everything you do disappears at shutdown unless you tell it otherwise. If you create a key and reboot, it is gone. Open the Persistent Storage settings and enable the GnuPG feature, which stores your keys and configuration across sessions. Do this before generating anything, because re-creating a key later means every vendor or buyer holding your old one is now talking to a stranger.
The Persistent Storage is encrypted with LUKS and unlocked by a passphrase. Choose a long one made of several random words, and understand that the storage is not hidden: anyone holding the USB stick can see it exists. That is a physical-security problem, not a cryptographic one, and it is worth thinking about before you put a vendor identity on a stick you carry around.
On Windows, the equivalent package is Gpg4win, which installs Kleopatra alongside GnuPG. The interface is the same; the storage question is yours to solve, ideally with a VeraCrypt volume rather than a folder on the desktop.
Create your key pair
Open Kleopatra from the activities menu. Choose File → New Key Pair, then Create a personal OpenPGP key pair. Put in a name and email. They do not have to be real, but they should match the identity you use on the market, because the key is how people will recognise you.
In the advanced settings you can pick the key type and size, and set an expiry. The defaults are fine. An expiry is not a weakness; a key that never expires and is never rotated is. Two years is a reasonable starting point, and Kleopatra will warn you when it is close. Add a passphrase and do not store it next to the key.
When it finishes, the key appears in the list with a fingerprint. That fingerprint is the only thing that matters when someone claims to be you. Copy it down somewhere offline.
Back up the secret key
Right-click the key, choose Export Secret Keys, and save the file to an encrypted volume, not to a cloud folder and not to the same USB stick you use for everything else. A vendor who loses their key loses their reputation overnight. A vendor whose key is stolen has something worse: someone else answering their customers.
Import the other side's key
Vendors publish their public key on their market profile. Copy the whole block, including the BEGIN and END lines, open Kleopatra's Notepad, paste it, and choose Import. Or use File → Import Certificates if you have it as a file.
Then check the fingerprint against the one published in the market, character by character. This is the step people skip, and it is the step that defeats the entire exercise. A key with the right name and the wrong fingerprint is a man in the middle.
Encrypt a message
Open the Notepad, write your message, and click Encrypt (the button reads Sign / Encrypt Notepad if you have also selected signing). Pick the recipient's key and confirm. You get an ASCII-armoured block beginning with BEGIN PGP MESSAGE. Paste the whole thing into the market's message field.
Two things to get right. First, encrypt to the recipient, not to yourself. Second, if you are sending an address, write it in the Notepad and encrypt there rather than typing it into a browser field first. Tails' own documentation makes this point: JavaScript in a page can read what you type, so the plaintext should only ever exist inside Kleopatra.
Decrypt and verify
Paste the incoming block into the Notepad and click Decrypt / Verify Notepad. Kleopatra will decrypt it and, if the sender signed it, report whether the signature is good and which key made it. A "good signature" from a key you have verified is worth something. A good signature from a key you have never checked is worth nothing at all.
If decryption fails, the usual causes are a truncated paste, the wrong key, or a message encrypted to a key you do not hold. Do not ask the other side to resend in plaintext to "check". That is how addresses end up in a chat log.
The mistakes that actually bite
Not enabling the GnuPG persistence feature, then rebooting and losing the key. Encrypting to your own key by accident and sending a block the vendor cannot open. Verifying the name but not the fingerprint. Keeping the key and its passphrase in the same VeraCrypt volume. Using Thunderbird's OpenPGP for one thing and Kleopatra for another, and wondering why the keys do not appear in both: they are separate keyrings, and Tails' documentation says so explicitly.
None of this is difficult. It is a routine, and the point of a routine is that you do not have to think about it at 2am when you are tired and the order is waiting.
