NFTs and Digital Ownership

The Concept

The tokens lesson introduced ERC-20, the standard for fungible tokens — units that are completely interchangeable, like dollar bills: any 1 ERC-20 token of a given type is identical in value and function to any other unit of that same token. A Non-Fungible Token (NFT), most commonly built on the ERC-721 standard, flips that assumption: each token is unique, individually identified, and not interchangeable with any other token in the same collection, even one from the same contract.

Technically, an ERC-721 contract keeps a ledger not of balances, but of ownership of specific numbered tokens — token #1, token #2, token #3, each with its own owner address and, usually, a pointer to metadata describing what that specific token represents (an image, a video, a ticket, an in-game item, a deed). The blockchain doesn't typically store the actual image or video file itself — that would be prohibitively expensive in gas costs — it stores a reference (often an IPFS hash or URL) to where that content lives, plus the immutable, publicly verifiable record of who currently owns token #47 of a given collection. This separation matters: if the server hosting the image disappears, the token's ownership record on-chain is unaffected, but the image itself may become unreachable unless it was pinned to a durable, decentralized storage system like IPFS.

What an NFT actually guarantees is narrower than marketing often implies, and it's worth being precise about it: owning an NFT guarantees that you control the private key associated with the address recorded as the current owner of that specific token number, verifiable by anyone who checks the blockchain. It does not automatically guarantee copyright ownership of the underlying artwork, prevent anyone from viewing or copying the image file itself, or grant any real-world legal rights beyond whatever the project's terms explicitly state — those are separate questions governed by ordinary law and by whatever the project's creator chose to attach to the NFT (sometimes nothing beyond "you own this specific token"). Someone can right-click and save an NFT's image regardless of who owns the token; ownership is a blockchain record, not a copy-protection mechanism.

What NFTs are genuinely good at is creating scarce, independently verifiable, transferable proof of ownership for a specific, unique digital (or digitally-represented) item — without a company's database being the sole source of truth for who owns what. This has found real uses beyond collectible art: event tickets (each seat is a unique token, preventing duplicate-ticket fraud and letting resale happen transparently with provable authenticity), in-game items with provable scarcity and the ability to trade or sell them outside the game's own marketplace, and membership tokens that grant access to a community or service, verified by simply checking which wallet holds which token — no centralized login database required.

Worked Example

Imagine an ERC-721 contract for a collection of 10,000 unique digital artworks. When the collection launches, the contract mints tokens #1 through #10,000, each pointing to a different image file's metadata, and assigns initial ownership to whichever addresses minted them. Alice buys token #4,521 directly from the original minter for 0.5 ETH — the smart contract updates its internal ledger so that the owner of token #4,521 is now Alice's address, an update anyone can verify on a block explorer (covered in Module 4). Later, Alice sells token #4,521 to Bob on a marketplace for 0.8 ETH; the contract again updates ownership, this time to Bob's address, and — if the contract includes a royalty mechanism — automatically routes a percentage of that sale back to the original creator, enforced by code rather than by a marketplace's internal accounting. If Bob later checks the metadata pointer and finds the image was hosted on a centralized server that has since gone offline, he still provably owns token #4,521 on-chain — but the artwork it was meant to represent may no longer be viewable, which is exactly why reputable projects pin their assets to IPFS rather than a single company's server.

Exercise

In two or three sentences, explain the difference between "owning an NFT of a digital artwork" and "owning the copyright to that artwork" — and give one real example (ticketing, gaming items, or membership access) of an NFT use case where that distinction barely matters because the value is in provable, transferable ownership itself, not in copyright. Then, in one more sentence, explain why storing an NFT's image on a single company's server (instead of IPFS) is a risk, even though the ownership record on-chain stays intact either way.

Recap

• NFTs (commonly ERC-721) represent unique, individually tracked ownership of a specific token, unlike fungible ERC-20 tokens where every unit is identical.
• Owning an NFT proves control of a specific token on-chain; it does not automatically confer copyright or other legal rights unless a project explicitly grants them, and it does not stop anyone from copying the underlying image file.
• Real NFT use cases extend well beyond art: tickets, game items, and membership access all benefit from scarce, independently verifiable, transferable ownership — but durable storage of the linked metadata and media is a separate concern from the ownership record itself.