NFT Fundamentals - Beyond the Hype | XRP Gaming & NFTs | XRP Academy - XRP Academy
3 free lessons remaining this month

Free preview access resets monthly

Upgrade for Unlimited
Skip to main content
intermediate55 min

NFT Fundamentals - Beyond the Hype

Learning Objectives

Explain the technical definition of non-fungibility and how blockchain implements unique token identification

Distinguish what NFT ownership proves (on-chain token control) from what it doesn't (legal rights, authenticity, permanence)

Identify the metadata problem and assess how different storage approaches affect NFT durability

Compare major NFT standards (ERC-721, ERC-1155, XLS-20, Solana Metaplex) on technical merits

Evaluate NFT use cases beyond art, particularly for gaming items, identity, and credentials

In March 2021, Christie's auctioned "Everydays: The First 5000 Days" by Beeple for $69.3 million. The buyer received... what exactly?

Not the copyright. Not exclusive viewing rights. Not a physical object. They received a token on the Ethereum blockchain pointing to a JPEG file stored on a server.

This isn't a criticism—it's a clarification. Understanding what that $69 million actually purchased requires understanding what NFTs technically are, which is different from what marketing implies they are.

The same clarity is essential for gaming NFTs. When someone "owns" a sword in a blockchain game, what do they actually own? The answer determines whether blockchain gaming represents genuine innovation or elaborate theater.


Fungible: Interchangeable units where any one unit is equivalent to any other.

  • US Dollars: Any $1 bill equals any other $1 bill
  • Bitcoin: Any 1 BTC equals any other 1 BTC
  • XRP: Any 1 XRP equals any other 1 XRP
  • Commodities: Any ounce of 99.9% gold equals another
  • Real estate: 123 Main St is not equivalent to 456 Oak Ave
  • Art: Original Mona Lisa ≠ any other painting
  • Airline tickets: Seat 14A on Flight 302 is unique
  • Your house keys: Specifically cut for your locks

Fungibility is about substitutability. Can you swap one for another without caring which specific one you have?

Blockchains are ledgers tracking ownership. Creating non-fungibility requires tracking unique items, not just balances.

Fungible Token Tracking (like XRP):

Account A: 1,000 XRP
Account B: 500 XRP
Account C: 2,500 XRP

Transaction: A sends 100 XRP to B
Result: A has 900, B has 600

No individual XRP units are tracked—just totals.
```

Non-Fungible Token Tracking:

NFT #0001: Owner = Account A, Metadata = "Sword of Fire"
NFT #0002: Owner = Account A, Metadata = "Shield of Ice"  
NFT #0003: Owner = Account B, Metadata = "Helmet of Wind"

Transaction: A transfers NFT #0001 to C
Result: NFT #0001 now owned by C, NFT #0002 still owned by A

Each token tracked individually with unique identifier.
```

The blockchain maintains a registry: "Token #X is owned by Address Y." This creates provable, transferable uniqueness.

Different blockchains identify NFTs differently:

Ethereum (ERC-721):

Contract Address + Token ID = Unique NFT
Example: 0x1234...abcd (CryptoPunks contract) + Token #7804

The contract is the "collection"
The token ID is the specific item within collection

Ethereum (ERC-1155):

Contract Address + Token ID + Amount = Position
Allows "semi-fungible" tokens (100 copies of same item)
Used for gaming items with multiple identical copies

XRPL (XLS-20):

NFToken ID = Hash of (Issuer + Taxon + Sequence)
256-bit unique identifier per token
Stored in NFTokenPage objects (up to 32 per page)

Solana (Metaplex):

Mint Address = Unique NFT identifier
Each NFT is its own "mint" with supply of 1
Metadata stored in associated accounts

The technical implementation varies, but the core concept is consistent: assign unique identifiers to individual tokens and track their ownership on-chain.


  • Cryptographically verifiable (anyone can check)
  • Historically traceable (full ownership chain visible)
  • Transferable (you can send it to other addresses)
  • Secured by private key (only you can transfer it)
What the blockchain proves:
✅ Address 0xABC... controls Token #1234
✅ Token #1234 was minted at block 12,000,000
✅ Previous owner was 0xDEF...
✅ Transfer occurred at block 15,000,000
  • Discord channels for holders
  • Exclusive content or airdrops
  • Voting rights in DAOs
  • Early access to future releases

This works because ownership is programmatically verifiable.

Legal Ownership of Underlying Asset:

Common Misconception:
"I own this NFT art, so I own the artwork."

Reality:
You own a token on a blockchain.
The token contains a pointer (URL/hash) to an image file.
Copyright and intellectual property rights are separate.
Unless explicitly transferred, the creator retains rights.

Analogy:
Buying a movie poster doesn't give you rights to the movie.
Buying an NFT of an image doesn't give you rights to the image.
  • License the image commercially (usually)
  • Prevent others from viewing/copying it
  • Sue for copyright infringement
  • Create derivatives (usually)

Some projects (like BAYC) explicitly grant commercial rights to holders. But this is the exception, not the default.

Authenticity Guarantee:

What people think:
"If it's an NFT, it must be authentic/legitimate."

Reality:
Anyone can mint an NFT of any image.
Right-clicking and saving an image, then minting it as NFT = trivial.
The NFT proves you own THAT token, not that the token represents 
something legitimate.

The blockchain verifies: "This token exists and you own it."
The blockchain cannot verify: "This token was minted by the actual 
artist" or "This image isn't stolen."

Authenticity depends on the minting address being verified as the legitimate creator—information external to the blockchain.

Permanence:

This is the critical one for gaming, and it deserves deep examination.

An NFT on a blockchain typically contains:

  • Token ID

  • Owner address

  • Minting information

  • Transfer history

  • Maybe: Some attributes (varies by standard)

  • Image/media file

  • Metadata JSON (name, description, attributes)

  • High-resolution assets

  • Game-specific data

The Problem: Most NFT "content" isn't on the blockchain at all.

Typical NFT Metadata Structure:

{
  "name": "Sword of Fire #1234",
  "description": "A legendary flaming sword",
  "image": "https://someserver.com/images/sword1234.png",
  "attributes": [
    {"trait_type": "Damage", "value": 50},
    {"trait_type": "Element", "value": "Fire"},
    {"trait_type": "Rarity", "value": "Legendary"}
  ]
}

Where This JSON Lives:

  • Company goes bankrupt → server goes offline → NFT shows nothing

  • Company decides to change → your metadata can be modified

  • Domain expires → link breaks

  • DDOS/hack → temporary or permanent loss

  • Content-addressed (hash of content = address)

  • Distributed storage (multiple nodes can host)

  • Immutable (changing content changes hash)

  • Someone must pin the content (pay for storage)

  • If no one pins it, content can disappear

  • Gateway dependency (ipfs.io going down affects access)

  • One-time payment for "permanent" storage

  • Economic incentives for long-term preservation

  • Truly decentralized

  • "Permanent" assumes Arweave network survives

  • Higher upfront cost

  • Less commonly used

Option 4: Fully On-Chain

All data stored directly in blockchain
Examples: Some pixel art collections, ASCII art

- Extremely expensive for large files
- Limits what can be stored (no high-res images, video)
- Only viable for small/simple content

For gaming NFTs, the metadata problem is acute:

Scenario: You buy a rare sword NFT in "Blockchain Warriors" for $500

- You own Token #5678
- It was minted by address 0xGame...

- Image of the sword
- Stats (damage: 100, speed: 50)
- Game integration (how it works in-game)
- 3D model files

- You still "own" Token #5678
- The token points to a dead URL
- No image, no stats, no game to use it in
- Your $500 NFT is now a receipt for nothing

Your "permanent ownership" is permanent.
Your ability to use or even view what you own is not.

This Is Not Theoretical:

Multiple gaming projects have shut down, leaving NFT holders with worthless tokens. The blockchain preserved ownership records of assets that no longer exist in any meaningful sense.

Honest Assessment:

  • Transferability (can sell on secondary markets while game exists)

  • Provenance (track ownership history)

  • Potential interoperability (if other games choose to honor them—rare)

  • Permanence of the actual game asset

  • Ability to use in any context if original game dies

  • Value retention if game loses players

  • Any utility outside the specific game ecosystem


The original and most widely used NFT standard.

  • Each token is unique and indivisible
  • One contract = one collection
  • Token ID + Contract Address = unique identifier
  • Supports approval/operator patterns for marketplaces
  • Events for transfers and approvals
  • ownerOf(tokenId) → returns owner address
  • transferFrom(from, to, tokenId) → transfer ownership
  • approve(to, tokenId) → allow address to transfer
  • setApprovalForAll(operator, approved) → allow operator for all tokens
  • Maximum compatibility (most wallets, marketplaces support)
  • Simple mental model (one token = one NFT)
  • Extensive tooling and documentation
  • Battle-tested security (billions in value secured)
  • Gas costs for minting/transferring on Ethereum L1 ($5-100+)
  • No native royalty enforcement (marketplaces can bypass)
  • Separate transaction for each transfer (no batch operations in base spec)
  • No built-in marketplace functionality

Multi-token standard supporting both fungible and non-fungible tokens.

  • Single contract can hold multiple token types
  • Each token ID can have supply > 1 (semi-fungible)
  • Batch transfer operations native
  • Used heavily in gaming

Example:
Token ID 1: "Gold Coin" - supply 1,000,000 (fungible within this ID)
Token ID 2: "Legendary Sword #1" - supply 1 (non-fungible)
Token ID 3: "Health Potion" - supply 10,000 (fungible within this ID)
Token ID 4: "Legendary Sword #2" - supply 1 (non-fungible)

All managed in one contract.
```

  • Gas efficient (batch operations, shared contract)
  • Flexible (fungible, non-fungible, semi-fungible in one contract)
  • Ideal for gaming (multiple item types in one system)
  • Native batch transfers
  • More complex implementation
  • Some wallets/marketplaces have inconsistent support
  • Semi-fungibility can confuse users expecting unique items
  • Metadata handling more complex

XRPL's native NFT standard, enabled October 2022.

  • Native to ledger (no smart contracts required)
  • NFTokenPage objects store up to 32 NFTs
  • Automatic royalty enforcement via transfer fees
  • Built-in marketplace via DEX offers
  • 256-bit identifier
  • Derived from: Issuer + Taxon + Sequence + Flags
  • NFTokenMint: Create new NFT
  • NFTokenBurn: Destroy NFT
  • NFTokenCreateOffer: List for sale/create buy offer
  • NFTokenAcceptOffer: Complete trade
  • NFTokenCancelOffer: Remove offer
  • Extremely low cost (~0.00001 XRP per transaction)
  • Fast finality (3-5 seconds)
  • Native royalty enforcement (cannot be bypassed)
  • No smart contract vulnerabilities
  • Built-in DEX for trading
  • No programmable logic (can't build complex mechanics on-chain)
  • Smaller ecosystem (fewer wallets, tools, marketplaces)
  • Less flexible than ERC-1155 (no semi-fungible tokens)
  • Metadata still stored off-chain
  • Limited developer familiarity

Solana's dominant NFT framework.

  • Each NFT is its own Mint account with supply of 1
  • Metadata stored in Program Derived Addresses (PDAs)
  • Candy Machine for collection launches
  • Auction House for marketplace functionality
  • Mint Account: The NFT itself
  • Metadata Account: Name, symbol, URI, creators, royalties
  • Master Edition: For editions/prints
  • Token Account: Ownership record
  • Very low cost (~$0.00025 per mint)
  • Fast transactions (~400ms)
  • Rich tooling (Candy Machine, Metaplex SDK)
  • Large ecosystem and marketplace support
  • Compressed NFTs for ultra-low-cost minting
  • Solana network stability concerns (historical outages)
  • More centralized than Ethereum
  • Royalty enforcement issues (marketplaces can bypass)
  • Complex account model (higher learning curve)
| Feature              | ERC-721  | ERC-1155 | XLS-20   | Metaplex |
|----------------------|----------|----------|----------|----------|
| Minting Cost         | $5-100+  | $3-50+   | <$0.01   | <$0.01   |
| Transfer Cost        | $2-50+   | $1-30+   | <$0.01   | <$0.01   |
| Transaction Speed    | 12-60s   | 12-60s   | 3-5s     | ~0.4s    |
| Smart Contract Logic | Yes      | Yes      | No       | Yes      |
| Native Royalties     | No       | No       | Yes      | No*      |
| Batch Operations     | No       | Yes      | Limited  | Yes      |
| Semi-Fungible        | No       | Yes      | No       | Limited  |
| Ecosystem Size       | Largest  | Large    | Small    | Large    |
| Gaming Suitability   | Medium   | High     | Medium   | High     |

*Metaplex has royalty specification but marketplace enforcement is optional
```


The most natural NFT use case after art.

  • Tradeable items with secondary market value
  • Provenance for rare items ("This sword was owned by top player X")
  • Cross-platform potential (if platforms agree to honor)
  • Player-owned economies (items have value outside game)
  • Items requiring complex on-chain logic (most chains can't support)
  • Fast-paced gameplay (blockchain latency too high)
  • Items that need constant stat updates (expensive/slow on-chain)
  • Interoperability fantasy (games rarely honor external NFTs)
  • Core ownership on blockchain
  • Game logic and real-time mechanics off-chain
  • Periodic syncs between on-chain state and game state
  • Marketplace for trading outside game client

Using NFTs as verifiable credentials.

  • Event attendance (POAPs - Proof of Attendance Protocol)
  • Educational certificates
  • Professional credentials
  • Membership tokens
  • Verifiable without contacting issuer
  • Portable across platforms
  • Cannot be forged (if issuer address is trusted)
  • Composable (can gate access based on credential combinations)
  • Issuer reputation must be established externally
  • Privacy concerns (all credentials publicly visible)
  • Revocation is problematic (burned NFT leaves trace)
  • Adoption requires ecosystem buy-in

NFTs as event tickets or access passes.

  • Eliminates ticket fraud (verifiable authenticity)
  • Enables controlled secondary market (royalties to organizers)
  • Creates collectibles (ticket stub as memorabilia)
  • Allows token-gated experiences (holder-only content)
  • QR code scanning UX is worse than traditional tickets
  • Crypto onboarding friction for mainstream events
  • Price volatility concerns for event access
  • Scalping still possible (just on blockchain now)

Representing physical assets as NFTs.

  • Real estate deeds
  • Vehicle titles
  • Luxury goods authentication
  • Art provenance for physical pieces
  • Legal recognition is limited/nonexistent in most jurisdictions
  • The "oracle problem"—blockchain can't verify physical world
  • Existing systems (title companies, registries) work fine
  • Adoption requires regulatory change, not just technology

This is more speculative than current; don't expect near-term impact for gaming evaluation.


Technical Red Flags:

🔴 Metadata on centralized servers without IPFS backup
🔴 No transparency about where content is stored
🔴 Smart contract not verified on block explorer
🔴 Admin keys that can modify token properties
🔴 Unlimited minting capability without clear rules
🔴 Contract upgradability without governance

Economic Red Flags:

🔴 Promise of returns/appreciation
🔴 Emphasis on floor price over utility
🔴 "Invest early" language
🔴 Royalties above 10% (indicates extraction focus)
🔴 No clear utility beyond speculation
🔴 Airdrop/reward schemes requiring purchases

Team Red Flags:

🔴 Anonymous team with no track record
🔴 No technical documentation
🔴 Copied artwork or derivative content
🔴 Aggressive marketing, minimal development
🔴 Promises of future utility with no roadmap specifics
🔴 Discord/community focus without product

Technical Green Flags:

✅ Metadata on IPFS or Arweave with permanence plan
✅ Verified and audited smart contracts
✅ Open-source code
✅ Clear documentation of token mechanics
✅ Reasonable reserve requirements and fee structures
✅ No admin keys or transparent key management

Economic Green Flags:

✅ Clear utility independent of price appreciation
✅ Sustainable revenue model for project
✅ Reasonable royalties (2-5%)
✅ No unrealistic promises
✅ Value proposition makes sense at lower prices
✅ Active use case beyond trading

Team Green Flags:

✅ Identified team with relevant experience
✅ Track record in gaming/tech
✅ Regular, substantive development updates
✅ Community engagement on technical topics
✅ Realistic roadmap with achieved milestones
✅ Focus on product, not price

NFTs work technically: Blockchains can track unique token ownership reliably and securely

Secondary markets function: NFT trading generates billions in volume with functional price discovery

Token-gating is useful: NFT ownership can control access to content, communities, and features

The metadata problem is real: Most NFT content lives off-chain and can disappear

Legal ownership is separate: Buying an NFT typically doesn't transfer intellectual property rights

⚠️ Long-term metadata preservation: Will IPFS content remain pinned for decades?

⚠️ Legal framework evolution: Will jurisdictions recognize NFT ownership legally?

⚠️ Gaming NFT interoperability: Will any games actually honor each other's NFTs?

⚠️ User experience improvement: Will onboarding become accessible to mainstream users?

⚠️ Regulatory treatment: Will gaming NFTs face gambling or securities regulations?

🔴 Assuming NFT = permanent ownership: The token is permanent; the content it points to often isn't

🔴 Assuming NFT = authenticity: Anyone can mint an NFT; the blockchain doesn't verify legitimacy

🔴 Assuming NFT = legal rights: Copyright and IP are separate from token ownership

🔴 Ignoring metadata storage: Always ask "where does the actual content live?"

🔴 Treating all NFT standards as equivalent: XLS-20, ERC-721, etc., have meaningfully different properties

NFTs are a genuine technical innovation for tracking unique digital asset ownership on blockchains. However, "ownership" of most NFTs means controlling a token that points to content stored elsewhere—content that can disappear, change, or become inaccessible. For gaming, this means NFTs enable tradeable items and provable ownership history, but don't solve the fundamental dependency on game developers and their servers. The technology works; the promises often exceed what the technology actually delivers.


Assignment: Examine the metadata and storage of 5 NFT projects, documenting what's actually on-chain versus off-chain.

Requirements:

  • 1 major art collection (CryptoPunks, BAYC, or equivalent)

  • 1 gaming NFT collection (Gods Unchained, Axie, etc.)

  • 2 XRPL NFT collections (Zerpmon, any other)

  • 1 project of your choice

  • Blockchain and standard used (ERC-721, XLS-20, etc.)

  • Contract/issuer address

  • What data is stored on-chain (token ID, owner, any on-chain attributes)

  • Minting transaction example (link to explorer)

  • Find the metadata URI (where the JSON lives)

  • Document the storage solution (centralized server, IPFS, Arweave)

  • If IPFS: check if content is pinned and accessible

  • Screenshot or document the actual metadata structure

  • Where is the actual media file stored?

  • What happens if that storage goes offline?

  • Is there a backup storage solution?

  • Rate durability: High/Medium/Low with justification

Part 5: Comparison Table
Create summary table:

| Project | Chain | Standard | Metadata Storage | Asset Storage | Durability |
|---------|-------|----------|------------------|---------------|------------|
| ...     | ...   | ...      | ...              | ...           | ...        |
  • Which projects have the most durable setups? Why?

  • What's the most common weakness you found?

  • How does this affect your evaluation of gaming NFTs?

  • What questions will you now ask of any NFT project?

  • Etherscan.io (Ethereum)

  • Solscan.io (Solana)

  • XRPScan.com / Bithomp.com (XRPL)

  • IPFS gateways: ipfs.io, cloudflare-ipfs.com

  • Token metadata: Check tokenURI/uri functions

  • Completeness (25%): All 5 projects fully analyzed

  • Technical accuracy (25%): Correct identification of standards and storage

  • Critical analysis (25%): Thoughtful assessment of durability and risks

  • Synthesis quality (25%): Insights demonstrate understanding of implications

Time investment: 3-4 hours
Value: You'll never look at an NFT the same way. Understanding what you're actually buying (a pointer, not necessarily permanent access to content) is essential for any NFT investment or gaming evaluation.


1. Technical Definition Question:

What makes a token "non-fungible"?

A) It's expensive to create
B) It's stored on a blockchain
C) Each token has a unique identifier and cannot be substituted for another
D) It represents digital art

Correct Answer: C
Explanation: Non-fungibility means tokens are not interchangeable—each has a unique identity. A dollar bill is fungible (any $1 = any other $1). An NFT is non-fungible because Token #1234 is specifically identified and tracked, not substitutable for Token #5678. Being on blockchain, being expensive, or representing art are not what makes something non-fungible—unique identification is.


2. Ownership Rights Question:

When you purchase a standard NFT of digital artwork, what rights do you typically acquire?

A) Full copyright and commercial licensing rights to the image
B) Control of a token on the blockchain that points to the image, but not copyright
C) Exclusive viewing rights—others cannot see the image
D) Legal ownership of the artwork recognized by courts

Correct Answer: B
Explanation: Standard NFT purchases transfer token ownership, not intellectual property rights. You control a token that contains a pointer (URL) to an image file. The original creator typically retains copyright. You cannot prevent others from viewing or copying the image. Legal ownership of "the artwork" is not established by token purchase. Some projects (like BAYC) explicitly grant commercial rights, but this is exceptional, not default.


3. Metadata Problem Question:

An NFT's metadata lives on a centralized server at api.gamename.com. The game company goes bankrupt. What happens to the NFT?

A) The NFT is automatically destroyed
B) The NFT transfers to a backup storage system
C) You still own the token on the blockchain, but it points to a dead URL—no image, no metadata
D) The blockchain preserves all metadata automatically

Correct Answer: C
Explanation: The blockchain only stores the token ownership record and pointer to metadata. If that pointer leads to a server that no longer exists, you own a token pointing to nothing. The blockchain doesn't store the actual metadata or images—it just stores where to find them. Your "permanent ownership" of the token remains, but what the token represents is gone.


4. Standard Comparison Question:

Which NFT standard provides native, enforceable royalties that cannot be bypassed by marketplaces?

A) ERC-721 (Ethereum)
B) ERC-1155 (Ethereum)
C) XLS-20 (XRPL)
D) Metaplex (Solana)

Correct Answer: C
Explanation: XLS-20 has transfer fees built into the protocol level—when an NFT transfers, the royalty is automatically enforced; there's no way for a marketplace to avoid paying it. ERC-721 and ERC-1155 have no native royalty mechanism (it's just metadata that marketplaces may or may not honor). Metaplex has royalty specification, but enforcement depends on marketplace cooperation—many now allow bypassing royalties.


5. Gaming Implication Question:

For gaming NFTs specifically, what is the most significant limitation of current blockchain implementations?

A) Transaction costs are too high
B) Transactions are too slow for real-time gameplay
C) The game content, logic, and utility depend on centralized servers that can disappear
D) Players don't want to own their items

Correct Answer: C
Explanation: While costs and speed are factors (and XRPL addresses these), the fundamental issue is that gaming NFTs only record ownership on-chain. The actual game—the 3D models, game mechanics, stats that make items meaningful, servers that run the game—all exist off-chain under developer control. If developers shut down, your NFT ownership is preserved but meaningless. This is more fundamental than cost or speed issues.


  • "NFTs Weren't Supposed to End Like This" (The Atlantic)
  • Various analyses of failed NFT projects and broken metadata
  • OpenSea and marketplace royalty debates
  • "NFTs and Copyright" (Stanford Law Review and similar)
  • IP attorney analyses of NFT ownership

For Next Lesson:
Lesson 3 dives deep into XRPL's XLS-20 standard—the specific technical implementation, advantages (cost, speed, native royalties), limitations (no smart contracts), and how it compares to alternatives for gaming use cases.


End of Lesson 2

Total words: ~6,400
Estimated completion time: 55 minutes reading + 3-4 hours for deliverable exercise

Key Takeaways

1

Non-fungibility is about unique identification

: Blockchains assign unique IDs to tokens and track ownership. This works reliably—it's the rest of the promises that need scrutiny.

2

NFT ownership ≠ asset ownership

: You own a token on a blockchain. That token may point to an image, but you typically don't own the copyright, can't prevent copying, and may not even have permanent access to view it.

3

The metadata problem is critical for gaming

: Most NFT content lives off-chain. When game companies shut down, you keep the token but lose everything it represented. "Permanent ownership" of a dead link has zero value.

4

Different standards, different tradeoffs

: ERC-721 is most compatible, ERC-1155 is best for gaming, XLS-20 is cheapest with native royalties, Metaplex is fast and developer-friendly. Choose based on use case.

5

Red flags matter more than green flags

: It's easier to identify bad projects (centralized metadata, anonymous teams, unrealistic promises) than to guarantee good ones will succeed. Due diligence is about elimination. ---