Published on Sat Aug 22 2026 00:00:00 GMT+0000 (Coordinated Universal Time) by Jacob Cavazos

The Problem with Web3 Go-to-Market

Traditional go-to-market strategy relies on knowing who your customers are. You have their email addresses. You have their purchase history. You have their demographics. You can segment them, target them, and measure the effectiveness of your campaigns. You can run A/B tests. You can track conversion funnels. You can attribute revenue to specific marketing channels.

In web3, most of this infrastructure does not exist. Your token holders are wallet addresses. Wallet addresses are pseudonymous. They do not have names. They do not have email addresses. They do not have demographics. You cannot send them an email. You cannot run a Facebook ad targeting them. You cannot look them up in a CRM.

This is the fundamental challenge of web3 go-to-market. You have users — real people who hold your token, use your protocol, and participate in your ecosystem — but you cannot identify them in the way traditional marketing requires. The challenge is not just technical. It is philosophical — and on-chain wallet intelligence is the toolkit for working within it. Web3 users value privacy. They chose pseudonymous wallets precisely because they do not want to be tracked in the traditional sense.

A web3 go-to-market strategy must work within these constraints. It must use on-chain data to understand holder behavior without violating privacy expectations. It must find ways to reach holders without traditional contact methods. It must respect the ethos of the ecosystem while still building a sustainable growth strategy.

What On-Chain Data Tells You

On-chain data is the foundation of web3 GTM. Every token transfer is recorded on a public ledger. Every swap is visible. Every liquidity provision is visible. Every governance vote is visible. This data is public, verifiable, and permanent. It is the richest dataset available for understanding your token holder base.

Here is what you can learn from on-chain data.

Token Holder Distribution

You can query the token contract to retrieve the full list of holders and their balances. On Ethereum, this is available through the balanceOf function on any ERC-20 contract. On block explorers like Etherscan, Basescan, or Arbiscan, the holders page shows every address that holds the token, sorted by balance. On analytics platforms like Dune Analytics, you can write SQL queries against decoded contract data to retrieve holder lists with custom filtering.

The distribution tells you several things. How concentrated is your token? If the top 10 holders control 80% of the supply, your token is highly concentrated. This is a risk signal for potential investors and a governance risk. If the top 10 holders control 15% of the supply, your token is broadly distributed. This is healthier.

How many holders do you have? The raw count of addresses with non-zero balances is a baseline metric. But this number is misleading without context. Many addresses may hold dust amounts — fractions of a cent. Many addresses may be inactive. Many addresses may belong to the same person. The raw count is a starting point, not a conclusion.

Holder Behavior Patterns

Beyond who holds your token, you can analyze how they interact with it. On-chain data reveals behavior patterns that are analogous to traditional user engagement metrics.

Transfer frequency. How often do holders transfer your token? Frequent transfers suggest active trading. Infrequent transfers suggest holding. You can calculate this by querying the token’s Transfer events over a time window and grouping by sender and receiver.

DEX interaction. Are your holders swapping your token on Uniswap, SushiSwap, or other DEXs? You can identify this by monitoring swap events on known DEX router contracts that involve your token address. This tells you whether your token is being used as a trading instrument or held as a long-term position.

Liquidity provision. Are your holders providing liquidity to pools that include your token? You can identify this by monitoring mint and burn events on liquidity pool contracts. Liquidity providers are your most committed holders. They are locking capital into your ecosystem. They deserve special attention in your GTM strategy.

Governance participation. If your token has governance functionality, are your holders voting on proposals? You can query the governance contract for voting records. Governance participation is a strong signal of engagement. Holders who vote are actively involved in the protocol’s direction.

Concentration and Whale Analysis

Not all holders are equal. A holder with 10% of the supply has a different relationship with your project than a holder with 0.01%. Understanding the distribution of holdings — and the behavior of large holders, often called whales — is critical for GTM strategy.

Whale behavior can be monitored by tracking the largest holders’ transaction history. When did they acquire their position? Have they been adding or reducing? Are they active in governance? Are they providing liquidity? This information is all on-chain.

Concentration analysis also reveals risks. If a single exchange address holds a large percentage of the supply, that represents a centralized point of failure. If a single early investor holds a large position that is unlocking, that represents potential selling pressure. These are not just marketing concerns. They are strategic concerns that affect the entire project.

Cross-Chain and Cross-Protocol Activity

Your token holders do not exist in isolation. They use other protocols. They hold other tokens. They transact on other chains. This cross-protocol activity is visible on-chain and provides context for your GTM strategy.

For each holder address, you can query their full transaction history. You can see what other tokens they hold. You can see what protocols they interact with. You can see which chains they are active on. This builds a behavioral profile — not a personal identity, but a pattern of activity that tells you what kind of user they are.

For example, if your holders are also active on lending protocols like Aave or Compound, they are likely sophisticated DeFi users. If your holders are also active on NFT marketplaces like OpenSea or Blur, they are likely NFT-native. If your holders are also active on Layer-2s like Base or Arbitrum, they are likely cost-conscious traders. These profiles inform how you communicate with them and what features you prioritize.

How to Discover Token Holders

The process of discovering your token holders is straightforward in concept but requires the right tools — for a practical guide on building a wallet attribution pipeline, see our companion tutorial.

Block Explorers

The simplest method is to use a block explorer. Etherscan, Basescan, Arbiscan, and other Etherscan-family explorers have a token holders page for every ERC-20 token. The page lists all addresses that hold the token, their balances, and the percentage of total supply. This is a good starting point for small token holders lists. For tokens with thousands or tens of thousands of holders, the block explorer’s pagination limits make it impractical to retrieve the full list.

Dune Analytics

Dune Analytics provides SQL access to decoded blockchain data. You can write a query that retrieves all holders of a specific token, filtered by minimum balance, sorted by balance, with any additional joins or filters you need. Dune’s data is updated in near real time. The platform supports Ethereum, Base, Arbitrum, Optimism, Polygon, and other chains.

A basic Dune query for token holders looks like this conceptually: select all Transfer events for the token contract, compute the running balance for each address, and filter for addresses with non-zero balances. Dune’s decoded contract data makes this straightforward. The result is a table of holder addresses and balances that you can export.

Token APIs

Several API providers offer token holder data as a service. Alchemy, QuickNode, Moralis, and Covalent all provide endpoints for retrieving token holders. These APIs handle the complexity of indexing transfer events and computing balances. They are useful for applications that need real-time holder data without building custom indexing infrastructure.

The Graph

The Graph is a decentralized indexing protocol. Subgraphs — indexing modules deployed on The Graph — can be written for any ERC-20 token to expose holder data through a GraphQL API. Many tokens already have deployed subgraphs. The Graph’s decentralized network means the indexing is performed by independent indexers, not a single centralized service.

Understanding Holder Behavior Beyond the Surface

Once you have your holder list, the next step is behavioral analysis. This is where on-chain data becomes actionable for GTM.

Cohort Analysis

Group your holders into cohorts based on when they acquired your token. The first cohort — early holders who acquired during launch or initial distribution — has a different profile than recent holders who acquired after the token was established. Cohort analysis reveals retention patterns. Are early holders still holding? Have they sold? Are they active in governance?

You can perform cohort analysis by querying Transfer events and grouping holders by the date of their first acquisition. Then track each cohort’s aggregate balance over time. If early cohorts are steadily reducing their positions, that is a retention problem. If recent cohorts are growing, that is acquisition momentum.

Activity Scoring

Not all holders are equally valuable to your ecosystem. An activity score — a composite metric based on on-chain behavior — helps you identify your most engaged holders. The score can incorporate factors like: number of transactions involving your token, frequency of DEX swaps, liquidity provision activity, governance participation, and time since last activity.

An activity score is not a single formula. It is a model you build based on what matters for your project. A lending protocol might weight borrowing activity highly. A DEX might weight swap frequency highly. A governance-focused DAO might weight voting participation highly. The score is a tool for prioritization. It tells you which holders to focus your GTM efforts on.

Holder Lifecycle Stages

On-chain behavior reveals lifecycle stages that are analogous to traditional user lifecycle stages.

New holders. Addresses that acquired your token within the last 30 days. These are your newest users. They need education, onboarding, and activation. On-chain signal: first Transfer event within the last 30 days.

Active holders. Addresses that have transacted with your token within the last 7 days. These are your engaged users. They need feature updates, community engagement, and opportunities for deeper involvement. On-chain signal: Transfer or swap event within the last 7 days.

Dormant holders. Addresses that hold your token but have not transacted in over 90 days. These are users at risk of churning. They need reactivation campaigns — new features, incentives, or communication that brings them back. On-chain signal: no Transfer or swap events in 90+ days.

Exiting holders. Addresses that are reducing their positions. These are users who are leaving. Understanding why they are leaving — through on-chain analysis of where they are moving their capital — informs product improvements. On-chain signal: declining balance over the last 30 days.

Compliance Considerations

Web3 GTM operates in a regulatory environment that is evolving and varies by jurisdiction. Several compliance considerations are relevant.

Privacy Regulations

On-chain data is public, but using it to identify individuals may implicate privacy regulations. The General Data Protection Regulation (GDPR) in the European Union and the California Consumer Privacy Act (CCPA) in the United States regulate the processing of personal data. Whether a wallet address constitutes personal data is an active legal question, and having the right blockchain compliance tools in place is essential for navigating it. If a wallet address can be linked to a specific individual — through off-chain data, KYC records, or publicly known associations — then processing that address may fall under privacy regulations.

The safest approach is to treat wallet addresses as potentially personal data. Do not attempt to deanonymize holders. Do not combine on-chain data with off-chain identity data without legal review. Use on-chain data for aggregate analysis and behavioral patterns, not for individual identification.

Securities Laws

If your token is classified as a security, your GTM strategy must comply with securities regulations. This affects how you can market the token, who you can sell it to, and what claims you can make. The Howey test in the United States and similar frameworks in other jurisdictions determine whether a token is a security. This is a legal determination, not a marketing one. Consult with securities counsel before launching any GTM campaign that involves token promotion.

Anti-Spam Regulations

Reaching token holders through on-chain messaging — for example, by sending small token transfers with metadata attached — may implicate anti-spam regulations. Some jurisdictions have specific rules about unsolicited electronic messages. On-chain messaging is a new medium and the regulatory framework is not fully developed. Use caution and consult legal counsel before using on-chain messaging for outreach.

Outreach Strategy

Once you understand your holders, the question is how to reach them. Traditional channels — email, phone, direct mail — are not available for pseudonymous wallet addresses. Web3 outreach requires different channels.

Community Channels

The primary outreach channel in web3 is community platforms. Discord, Telegram, and Twitter (X) are where web3 users congregate. Your token holders are likely active on these platforms, even if you cannot link their wallet addresses to their social accounts. Building a strong community presence — regular updates, AMAs, governance discussions, developer documentation — reaches your holders indirectly. They will find your community if it provides value.

On-Chain Messaging

Some protocols enable messaging directly to wallet addresses. ENS (Ethereum Name Service) domains can be associated with contact information. Protocols like Lens Protocol and Farcaster link wallet addresses to social identities. These create bridges between on-chain identity and off-chain communication. If your holders have ENS names or Lens/Farcaster profiles, you can reach them through these channels.

Token-Gated Content and Experiences

Rather than pushing messages to holders, you can create pull-based engagement through token-gated content. Holders verify their token balance — typically through a wallet signature, not by transferring tokens — to access exclusive content, features, or experiences. This is a GTM strategy that respects privacy. The holder chooses to engage. You do not need to know who they are. You only need to verify they hold your token.

Token-gated platforms like Collab.Land, Guild.xyz, and TokenGated provide infrastructure for verifying token holdings and gating access. These can be integrated with Discord, Telegram, or custom applications.

Incentive Programs

On-chain incentive programs — liquidity mining, staking rewards, airdrop campaigns — are a direct way to engage holders. These programs are visible on-chain. They do not require off-chain contact. They reward holders for specific behaviors that benefit the ecosystem.

The design of incentive programs is a GTM decision. What behavior do you want to encourage? Providing liquidity? Holding long-term? Participating in governance? The incentive structure should align with your strategic goals. Poorly designed incentives attract mercenary capital that leaves when the incentives end. Well-designed incentives attract committed holders who stay for the ecosystem.

Building the Framework

A web3 go-to-market strategy is not a single campaign. It is a framework that combines on-chain analysis, community building, token-gated experiences, and incentive design. The framework has four stages.

Stage one: Discovery. Use on-chain data to identify your token holders, analyze their behavior, and segment them into cohorts. Tools: block explorers, Dune Analytics, token APIs, The Graph.

Stage two: Understanding. Analyze holder behavior patterns, activity scores, and lifecycle stages. Identify your most engaged holders, your dormant holders, and your exiting holders. Understand what protocols and chains your holders are active on.

Stage three: Strategy. Design outreach and engagement strategies for each segment. New holders get onboarding content. Active holders get feature updates and governance participation opportunities. Dormant holders get reactivation incentives. Exiting holders get product feedback requests through community channels.

Stage four: Measurement. Track on-chain metrics over time to measure the effectiveness of your GTM strategy. Are new holder acquisitions increasing? Is dormant holder reactivation working? Is governance participation growing? The on-chain data is your analytics dashboard. It is more transparent and more reliable than any traditional analytics platform.

Conclusion

Web3 go-to-market strategy is fundamentally different from traditional GTM because the user identity model is different. You cannot email your token holders. You cannot run targeted ads at them. You cannot look them up in a CRM. But you have something traditional marketers do not: a complete, public, verifiable record of every transaction your holders have ever made.

The framework is to use on-chain data to understand behavior, segment holders into cohorts, and design engagement strategies that respect privacy while driving growth. The tools are public — block explorers, Dune Analytics, The Graph, token APIs. The channels are community platforms, token-gated experiences, and on-chain incentive programs. The measurement is on-chain and transparent.

This is not traditional marketing. It is a new discipline that combines data analysis, community building, and incentive design — and on-chain wallet intelligence is the foundation of the data analysis layer. The projects that master it will build the most engaged, most committed, most resilient token holder bases in web3.

Orkid is building infrastructure that supports web3 go-to-market analysis. You can learn more at orkidlabs.xyz. The concepts described in this article are based on public documentation and widely available on-chain analytics tools.

Frequently Asked Questions

What is a web3 go-to-market strategy?

A web3 go-to-market strategy is a plan for launching and growing a token-based product or protocol. It encompasses user acquisition, liquidity provisioning, community building, token distribution, and partnership development. Unlike traditional web2 strategies, it must account for on-chain incentives, token economics, and decentralized governance.

How do token projects get users?

Token projects acquire users through a combination of community building, incentive programs, airdrops, liquidity mining, and integrations with existing DeFi protocols. On-chain data helps identify potential users by analyzing wallet behavior and token holdings. Successful projects combine organic community growth with targeted incentive campaigns.

What is token liquidity?

Token liquidity is the ease with which a token can be bought or sold without significantly impacting its price. High liquidity means large trades can be executed with minimal slippage, while low liquidity leads to volatile prices and poor execution. Liquidity is established through liquidity pools, market makers, and exchange listings.

How do you market a crypto project?

Marketing a crypto project involves community engagement on platforms like Discord and X, content creation, airdrop campaigns, token-gated experiences, and on-chain messaging to targeted wallet segments. Unlike traditional marketing, web3 marketing leverages token incentives and on-chain data to reach and retain users. Transparency and credibility are critical in the crypto community.

Further Reading

• Dune Analytics Documentation
• The Graph Documentation
• Etherscan Token Holders
• Guild.xyz Documentation
• Lens Protocol Documentation

Written by Jacob Cavazos