SuperEx Educational Series: Understanding Why Doesn’t an Increase in Token-Holding Addresses Necessarily Mean Real User Growth?

#SuperEx #EducationalSeries

In Web3 project reports, a rising holder count is almost automatically treated as good news.

A token had 10,000 holding addresses yesterday and 50,000 today. A promotional poster can quickly announce: “The community grew by 400%, and the ecosystem is exploding.”

The arithmetic may be correct, but the claim of 400% user growth may be several steps ahead of reality.

Blockchain records addresses, not legal identities or unique human accounts.

One person may control many addresses. One address may represent thousands of users. Some token-holding addresses are not people at all, but exchange wallets, liquidity pools, bridge contracts, staking contracts, or project treasuries.

More importantly, an address may be counted as a holder after receiving only a tiny amount of tokens. It does not need to make a purchase, open the application, or even know that the token arrived.

Holder count answers, “How many addresses show a balance?” It does not answer, “How many real users are using the product?”

Addresses, Wallets, Accounts, and Users Are Not the Same Thing

To understand the issue, we first need to separate four terms that are often used interchangeably: address, wallet, account, and user.

An address is an on-chain identifier used to record balances and interactions. A wallet is a tool for managing keys, addresses, and transactions. A platform account is a login identity managed by a product system. A user may be a person, institution, bot, or even a group jointly controlling assets.

On Ethereum, accounts can be externally owned accounts controlled by private keys or contract accounts controlled by code. Both can receive, hold, and send tokens. Ethereum account documentation

Therefore, when a block explorer shows that a token has 100,000 holders, that number may include both personal wallets and smart contracts.

One real user may also control many addresses.

A person may keep long-term assets in a cold wallet, daily trading funds in a hot wallet, and create separate addresses for NFTs, DeFi, airdrop campaigns, and different blockchains. Institutions may use operational wallets, treasury wallets, market-making wallets, and multiple permissioned accounts.

One active user may therefore appear as more than a dozen holders.

If a project encourages users to create a new wallet for every campaign, the holder count can rise rapidly while the number of participants barely changes.

The opposite is also possible: one address may represent many real users.

Centralized exchanges often use omnibus or custody wallets to manage assets belonging to many customers. On-chain data may show one holder address, while the platform’s internal ledger records balances for thousands of users.

Holder counts can therefore both overestimate and underestimate user numbers.

The relationship between addresses and users is many-to-many and must be inferred. Treating address growth as direct user growth is like seeing 100 illuminated windows and announcing that 100 families live in the building. Maybe they do, or maybe one household simply turned on every light.

Why Can Holder Counts Rise Without Real User Growth?

The simplest reason for holder growth is genuine users buying or claiming a token.

But blockchain data does not automatically label an address as “a new human who discovered the project.” Once the balance changes from zero to a positive number, many analytics tools may count it as a holder.

This gives project teams and marketers considerable room to influence the metric.

One common method is an airdrop. 

A project distributes tiny amounts of tokens to tens of thousands of addresses, and the holder count rises immediately. Yet those addresses may never have requested the tokens or interacted with the project.

Some airdrops genuinely acquire users, but receiving a token and becoming a user are still very different events.

The recipient may never check the balance, may sell immediately after noticing it, or may complete one claim task and never return.

A second method is dust distribution.

A project sends extremely small amounts of tokens to many active addresses, perhaps less than one cent per address. The cost may be low, but the resulting holder-growth chart can look impressive.

ERC-20 balance queries only show how many tokens an address owns. They do not distinguish between purchases, airdrops, and unsolicited dust transfers. OpenZeppelin ERC-20 documentation

If the metric only requires a balance greater than zero, an address holding 0.000001 tokens and an address investing 10,000 dollars each contribute exactly one holder.

A third source is Sybil participation.

When airdrops, points, allowlists, or governance rights are linked to address count, one person may create many wallets. Scripts can automate transfers, interactions, and campaign tasks, making the addresses appear independent.

Creating blockchain addresses is inexpensive, and small interactions on some networks cost very little. If each address may receive rewards worth more than the operating cost, mass identity creation becomes a business.

In that case, what is growing is not the community. It is a reward-claiming production line.

This is why some systems use Sybil-resistant identity, social credentials, behavioral clustering, or proof-of-personhood mechanisms. World ID, for example, can limit repeated verification by the same person for a specific action, reducing the problem of one person appearing as many accounts.

A fourth source comes from the protocol’s own technical structure.

Liquidity pools, staking contracts, bridges, vesting contracts, DAO treasuries, and burn addresses may all hold tokens. As ecosystem integrations expand, the number of contract holders naturally rises, but these contracts are not new users.

A fifth source is address migration.

Users may replace wallets, upgrade multisignature accounts, move assets from old addresses, or redeploy funds after a security incident. The new address becomes a holder, while the old address may remain counted because a tiny residual balance remains.

One user is then represented by both the old and new addresses.

Even Genuine Addresses May Be Holders Without Being Users

Suppose contracts, dust addresses, and obvious Sybil clusters have been removed. Can the remaining addresses be treated as real users?

Not automatically, because holding a token and using a product are different relationships.

A person may buy a token for speculation without ever using its DApp. Another may hold the token on an exchange without participating in governance, staking, or payments.

Some people may simply forget that they own it. The balance remains, while the user relationship has effectively ended.

Holder count is therefore closer to a stock measure.

It shows how many addresses retain a balance at a particular moment. It does not independently reveal where users came from, whether they are active, whether they remain engaged, or whether they intend to continue using the product.

Even active addresses cannot be treated as unique humans without qualification.

Bots can trade repeatedly, market makers can generate daily interactions, and arbitrage programs can move assets across multiple protocols. They are real economic participants, but they may not be the “community users” described in marketing materials.

Before discussing growth, a project must first define what it means by “user.”

For a DEX, a user may mean an independent participant who completes a trade. For a game, it may mean someone who reaches the core gameplay loop and returns. For a payment product, it may mean real payers and recipients. For governance, it may mean independent entities that are eligible and actually vote.

Without a clear definition, “user growth” becomes a number whose methodology changes whenever convenient.

When holder count rises, the project talks about holders. When volume rises, it talks about active users. When social-media attention rises, it talks about community size. Each metric may be real, but they may describe entirely different groups.

How Can Real User Growth Be Measured More Reliably?

No single on-chain metric can perfectly answer how many real users exist.

A more reliable approach combines address quality, behavioral depth, and retention over time rather than replacing holder count with another impressive-looking number.

The first layer is address classification.

Analysts can identify exchange wallets, liquidity pools, bridges, protocol contracts, team treasuries, burn addresses, and known market-making wallets. These entities matter to the ecosystem, but they should not automatically be counted as human users.

A reasonable balance or economic-activity threshold may also filter obvious dust addresses.

But the threshold should not be set so high that genuine small users disappear. A better method combines balance, funding source, voluntary interaction, and holding duration.

The second layer is voluntary behavior.

Did the user actively buy, swap, stake, vote, pay, or use the DApp? Or did the address merely receive tokens and never act again?

A voluntarily signed transaction is closer to real usage than a passive balance, although bots and reward-driven interactions must still be filtered.

The third layer is retention.

Real growth is not only about how many new addresses appeared this week. It also concerns whether they return next week or next month.

If an airdrop attracts 100,000 addresses but only 1,000 continue using the product after 30 days, the project gained campaign traffic, not 100,000 durable users.

Cohort analysis is more useful than a simple cumulative address count.

Addresses with similar first-use dates can be grouped and examined for 7-day, 30-day, and 90-day retention. This reveals whether the product consistently attracts and retains users instead of relying on one-time campaigns to push up a lifetime total.

Ten thousand addresses making one repetitive micro-transaction are not necessarily stronger growth than one thousand users repeatedly completing meaningful product actions.

The fourth layer is economic quality.

Does volume come from many independent participants, or is it concentrated among a few market-making or wash-trading addresses? Are users paying reasonable fees? Do active users complete core product actions? Are balances and transactions highly concentrated?

The fifth layer is identity and deduplication.

For high-value airdrops, governance, or one-person-one-vote systems, projects may combine KYC, proof of personhood, social credentials, device and behavioral risk controls, and privacy-preserving uniqueness proofs to reduce duplicate counting.

Identity strength should match the use case.

Ordinary browsing and low-risk interactions do not require full identity disclosure. High-value rewards and governance rights may need more than one-wallet-one-entry. Mature systems increase verification with risk rather than applying the same requirement everywhere.

Case Study: Holder Count Rises from 20,000 to 120,000

Suppose a project launches a new ecosystem campaign. One month later, the number of holder addresses rises from 20,000 to 120,000.

At first glance, the project gained 100,000 token holders, representing 500% growth.

Further analysis shows:

• 40,000 addresses received unsolicited dust airdrops.
• 25,000 belong to mass-created Sybil clusters.
• 10,000 claimed once and immediately sold.
• 5,000 are exchange, contract, and liquidity-infrastructure addresses.
• 15,000 still hold the token but never used the product.
• Only 5,000 continue completing core actions after 30 days.

This does not mean the campaign completely failed.

The project broadened token distribution, gained attention, and may have acquired potential future users. But describing all 100,000 new addresses as real user growth hides the most important information.

A more accurate report might say:

• 100,000 new holder addresses;
• Approximately 25,000 valid new addresses after filtering dust, known contracts, and suspected Sybil clusters;
• 10,000 new addresses completed at least one core action;
• 5,000 remained active after 30 days.

These figures may be less exciting on a promotional poster, but they are far more useful for product decisions.

They show how much attention, experimentation, real usage, and retention the campaign produced, and where users dropped out. Data should do more than announce victory. It should reveal what needs improvement.

Conclusion

An increase in holder addresses shows that a token is distributed across more on-chain accounts. It does not automatically prove proportional growth in real users.

• One person can create many addresses.
• One custody address can represent many users.
• Contracts, bridges, exchanges, and liquidity pools can hold tokens.
• Airdrops and dust transfers can passively create holders.
• Sybil accounts and bots can imitate independent participation.
• Genuine addresses may hold tokens without using the product.

Holder count is useful for answering, “How widely is the token distributed?” It is not sufficient for answering, “How well is the product growing?”

A more reliable growth assessment combines address classification, voluntary behavior, core-feature usage, transaction quality, funding sources, repeated interactions, and long-term retention. High-value scenarios may also require identity deduplication and Sybil resistance.

Holder growth is not meaningless.

If new addresses acquire tokens voluntarily, continue using the product, improve distribution, and remain active for weeks or months, holder growth can become strong evidence of genuine adoption.

Evidence still needs interpretation. A rising chart does not automatically mean that one hundred thousand new users have enthusiastically joined the community.

About SuperEx

SuperEx is committed to building a Web3-centered digital asset ecosystem, offering global users crypto trading, Web3 wallet, DAO, earning, and educational services. Through its account system, Web3 tools, risk controls, and continuous user education, SuperEx aims to help users understand on-chain data and evaluate project growth and market activity more objectively.