# The Problem

Few expected NFTs to take off the way they did in 2021.&#x20;

Bored Ape Yacht Club (BAYC) popularized the 10,000 supply collection that year. &#x20;

CryptoPunks—who were the first to do it in 2017—were also rediscovered and became the gold standard.&#x20;

Soon, many 10,000-supply NFT collections spawned with their own unique traits — Cool Cats, Pudgy Penguins, Azuki, Doodles, and so many more. All of these iterations were built and deployed using the <mark style="color:red;">ERC721</mark> token standard. This meant that every NFT was a unique and differentiable coin.&#x20;

At the time, this made sense. But there were many downsides. Most obviously, NFTs couldn't be cost-effectively sent or traded in bulk. Collections also had to be limited in size due to gas limitations. 10,000-supply collections therefore became the norm. But this made them too exclusive and expensive to a fault, sidelining the vast majority of people.&#x20;

With the ERC721 standard, a high-supply NFT collection on Ethereum was just not possible. This unfortunately placed a hard cap on community growth because there could only ever be \~10,000 unique owners.&#x20;

As a result, many pfp collections now look stale. People have gotten bored of their lack of customization and variety.&#x20;

Unsurprisingly, NFTs have completely collapsed in price and interest in 2023.

***

### **The old NFT model is...**

❌ too exclusive (\~often only 10,000 supply)

❌ expensive

❌ illiquid

❌ limited in variety

### **An actually scalable NFT should be...**

✅ mass-supply

✅ ultra-affordable & cheap to send in bulk

✅ liquid in all crypto markets

✅ infinitely customizable but also easily recognizable&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.npc.com/introduction/the-problem.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
