Holding your own keys

What a private key actually is, what a paper wallet gives you and costs you, and the failure modes that take people's money.

Self-custody means you hold the key to your funds and nobody else does. It is the arrangement cryptocurrency was built for, and it is not the arrangement most people who own cryptocurrency are in.

This page explains what it involves, because the platform is built around it and the reasoning matters more than the slogan.

What a private key is

A blockchain address is not an account someone opened for you. It is derived from a number — a very large random number, your private key.

Whoever knows that number controls the funds at that address. Not "has permission to access". Controls, completely, with no process, no appeal and no one to ask.

There is no registry of who owns what. There is no institution holding the ledger. The key is the ownership.

A recovery phrase is the same thing expressed as words, from which keys can be derived. Twelve or twenty-four words, and the same rule applies: whoever has them has the funds.

Custodial and non-custodial

When you buy cryptocurrency on an exchange and leave it there, the exchange holds the key. Your balance is an entry in their database — a promise that they hold coins for you.

Usually that promise is good. Sometimes it is not, and the pattern is consistent: the failure is not a broken blockchain, it is an institution that held other people's keys and stopped being able to return them. Everyone involved could see their balance in the app the entire time.

Non-custodial means you hold the key. No promise, no counterparty, no one who can freeze the account, no one whose failure becomes your loss.

The trade is that there is nobody to call. Lose the key and the funds are unreachable — visible on the chain forever, belonging to nobody.

Why the platform is built this way

Cryptocurrency was created so that people could hold their own money without an institution in between. Handing your keys to a platform reproduces the thing it was built to avoid, and a platform holding thousands of people's keys is a bank with worse regulation.

So the website holds none. It reads public addresses. SWOP does the signing, on your machine, and erases the key when it closes. Security model has the detail.

The platform's own origin is a paper wallet: an Ethereum wallet generated offline and printed on a plastic card, held for years. Everything here is built from what that was actually like to use.

Paper wallets

A paper wallet is a key generated offline and written down rather than stored on a connected device.

What it protects against: the entire category of attack that requires reaching your key over a network. Malware that scans for wallet files, a compromised phone, a hacked exchange, a browser extension that turned out to be malicious. None of it touches a key that is on a card in a drawer.

What it costs: convenience, and the fact that the card is now the single point of failure. It can burn. It can be found. It can fade.

Generating it correctly matters more than storing it. A key generated on a computer that was online, or by a website, or with a weak source of randomness, is compromised before it is printed. That is why SWOP's Vault recommends disconnecting first and why Whales OS exists — a system booted from a USB stick that has never been online and does not survive the power being cut.

And it needs to be usable. A wallet you cannot spend from is not storage, it is a bet that you will never need it. This is the gap SWOP fills: a printed card that can send and connect to applications without the key ever being typed into a browser.

Hardware wallets

A hardware wallet holds the key in a device that signs without exposing it. It is the standard recommendation, it is a good one, and it solves the same problem from the other direction — convenience with the key isolated.

The differences that matter: a hardware wallet is a device with firmware, a supply chain and a manufacturer, and it can fail or be lost. Paper has none of those and no interface either.

Neither is strictly better. Both are enormously better than a key sitting in a file on a computer that reads email.

What actually takes people's money

Cryptography is not the weak point. These are:

Signing something without reading it. The largest single cause. A valid signature granting someone permission to spend your tokens, made by the owner, on a site reached through a link. Nothing was broken. SWOP decodes requests so you can see what you are approving, and the website's Health & security view lists the permissions you have already granted.

Entering a phrase into a fake recovery page. Wallet software never needs your phrase entered on a website. Nothing legitimate does.

Generating a key somewhere unsafe. A website that generates a wallet for you may have kept a copy. You will not find out until later.

Storing the key digitally. A photograph of a paper wallet is a digital key. So is a note in a password manager that syncs, a text file, an email to yourself.

Address-swapping malware. It replaces the address you pasted with the attacker's. Check the whole address before sending, not the first and last four characters, which is exactly what this attack is designed to survive.

Losing it. Not dramatic, and very common. No backup, or a backup nobody else could find.

A workable arrangement

Not advice about how much to hold, which is not something this documentation offers. Just the mechanics most people converge on:

Keep a small amount somewhere convenient for day-to-day use, and accept that convenience is the risk you are taking with it.

Keep the rest on a key generated offline, backed up on something that survives water and fire, stored where a house fire cannot take every copy, and never photographed.

Know how you would recover it if you were not around. An inheritance nobody can open is a loss with extra steps.

Test the backup before you rely on it. Send a small amount, recover the wallet from the backup alone, send it back. A backup you have never read is an assumption.