"You can't just right-click and save it — I own the original." That line got repeated thousands of times during NFT debates, and it has a problem: technically, it's almost always false. Right-click works fine. The file saves. The pixels are identical. So what did the person who paid house-money prices for a JPEG actually buy? There's a real answer, and it's more honest than either the hype or the ridicule — an NFT guarantees something genuine. It's just not what most buyers think it is.
What's actually on the chain
An ERC-721 token (or its equivalents on other chains) is an entry in a smart contract: a unique ID tied to an owner's address. That's it. The blockchain doesn't store the picture — it's too heavy and too expensive to store on-chain at normal gas prices. Instead, the contract holds a `tokenURI` — a pointer to metadata that usually lives somewhere else entirely: on IPFS, on Arweave, or, quite often, on an ordinary web server run by the project.
What's actually recorded and cryptographically verifiable is a fact: "address X holds token #Y of collection Z, as of this block." That's immutable, publicly checkable, and can't be quietly rewritten by a centralized database later. That's a real achievement, and it shouldn't be dismissed. But it's a record of owning a token — not of owning the image, not of holding copyright over it, and not a guarantee that the image the token points to will keep existing at all.
Where the picture actually lives
This is where the myth usually falls apart. If the metadata sits on a project's own centralized server rather than on IPFS, the moment the company stops paying for hosting — shuts down, loses interest, goes bankrupt — the link turns into a 404. The token still exists on-chain, still belongs to your address, it just points at nothing. This has happened repeatedly to lower-profile collections: the project quietly dies, the site goes dark, and the "asset" on a marketplace turns into a gray box that says "image unavailable."
IPFS only solves this halfway. Content addressing on IPFS does give the file itself real immutability — the hash changes if a single byte changes. But IPFS doesn't store anything forever on its own: a file survives only as long as someone is "pinning" it — paying for a node to keep serving it. If the pinning service a project relied on shuts down and nobody else picks the file up, you get the same outcome, just delayed. Only a small minority of projects have gone all the way and written the image directly into the contract as an SVG or compressed data — those pieces live exactly as long as the network itself. That group is small.
Ownership and copyright are different things
Buying a Bored Ape Yacht Club token in 2021–2022 meant getting more than a record of ownership — it came with an explicit license. Yuga Labs spelled out that the holder could commercially use the corresponding image: put it on T-shirts, make a cartoon out of it, sell merchandise. That became a precedent many people mistook for a rule governing the whole NFT market. It isn't one. It's a term of that specific contract from that specific project, written as an ordinary license — a legal document that lives off-chain and is enforced (or not) by regular courts in a regular jurisdiction, not by smart-contract code.
Most other projects either transfer no usage rights at all, or leave the wording vague enough to keep lawyers employed indefinitely. Owning the token by itself — absent an explicit license — does not by default give you the right to print the image on mugs or resell it as a standalone work. The creator typically retains copyright unless they've explicitly waived it in writing. "Code is law" is a nice slogan, but copyright doesn't live in code — it lives in the legislation of whatever country you're in, and it's enforced by courts, not by a blockchain.
Our Record: the Maat system distinguishes Ren — a name, a recorded status — from Ba, the living substance that name refers to. A token gives you Ren: a public, unchallengeable record that something is attached to your address. But Ren is not Ba. A name in a registry is not the same as possession of the thing the name points to. Confusing the two is classic Shadow Thoth work — propaganda that makes the label feel like the substance.
Scarcity isn't always what it looks like either
Part of a collection's value rests on a promise of scarcity: "only 10,000 will ever exist." That claim isn't a property of the blockchain itself — it's a term of that specific smart contract, and it's only as reliable as that contract's immutability. A meaningful share of contracts, especially early ones that never went through serious audit, were written with functions that let an owner-admin mint additional tokens, alter metadata after the fact, or even pause transfers entirely. None of that is technically a violation — it's simply written into code that almost none of the buyers ever read.
This is checkable, not a matter of trust. The contract is public, and questions like "does it have a `mint` function callable by the owner after the initial sale" or "can `tokenURI` be changed after minting" are concrete, verifiable facts — not something you take on faith from a project's Discord announcements. A stated scarcity without an immutable contract is a human promise wrapped in code that the same human can still rewrite.
What an NFT actually guarantees
Strip away the mythology and there's a concrete list left — and it isn't empty:
- A verifiable ownership history. Who bought the token from whom, and when — public, permanent, with no trust required in a centralized registry that could be altered or edited.
- Instant, permissionless transfer. The token can be sold or given away directly, with no intermediary able to refuse the transaction, freeze the account, or take an opaque cut.
- Programmable logic. Resale royalties to the original creator (where the contract supports it and the marketplace honors it), access to gated communities, DAO voting rights tied to holding the token — these are real, functioning mechanisms.
- A censorship-resistant pass. A token used as a key to a community or service can't be stripped the way a social-media account gets banned — provided the access logic itself doesn't run through that same centralized platform.
This isn't "owning digital art" in the sense that someone owns a framed canvas. It's a cryptographically verified, transferable pass and ownership record — a genuinely useful thing, once you understand it for what it is.
Before buying an NFT, the question isn't "is this rare art?" — it's three concrete ones: where does the file the token points to physically live, and what happens to it if the project disappears tomorrow; what rights does the license actually transfer, if any, beyond the bare record of token ownership; and can the contract be changed by anyone other than you after the token is already in your wallet. If you have clear, checkable answers to all three, you're buying something that genuinely exists. If you don't, you're buying a nice story about ownership, told by someone who gets paid exactly to the extent that you believe it.