DEV Community: JUMPBIT

NFT Snapshot Tools Compared: Jumpbit vs Magic Eden vs Tensor

JUMPBIT — Sun, 25 Jan 2026 12:24:40 +0000

Introduction

You need to export your Solana NFT collection's holder list. But which method should you use?

Magic Eden shows holder stats but doesn't export. Tensor has analytics but limited bulk access. APIs require coding. And there are dedicated snapshot tools that promise simpler workflows.

In this comparison, I'll break down the top methods for taking NFT snapshots on Solana—covering ease of use, data coverage, export capabilities, and pricing—so you can choose the right approach for your project.

Quick Comparison Overview

Feature	Jumpbit	Magic Eden	Tensor	Helius API
Holder List Export	✅ CSV/JSON	❌ No export	❌ Limited	✅ JSON (API)
Ease of Use	No-code UI	View only	View only	Requires coding
cNFT Support	✅ Yes	✅ View	✅ View	✅ Yes
API Key Required	No	N/A	For API	Yes
Bulk Export	✅ All holders	❌ No	❌ No	✅ Yes
Pricing	Pay-per-use	Free (view)	Free (view)	Subscription

Jumpbit NFT Snapshot

How It Works

Jumpbit offers a browser-based NFT holder export tool. You paste a collection address, click generate, and download your complete holder list. No account, no API keys, no coding.

Strengths

Full Holder Export

Download complete holder list
CSV for spreadsheets and airdrop tools
JSON for developers
All holders, not just top 100

Universal NFT Support

Standard Metaplex NFTs
Compressed NFTs (cNFTs)
Programmable NFTs (pNFTs)
Automatic standard detection

No Technical Barrier

Paste address → Click generate → Download
Works in any browser
No wallet connection required

Fast Processing

Handles large collections (50K+ NFTs)
Typical export time: 30-60 seconds
No rate limits

Limitations

No real-time price/trading data
No historical ownership tracking
UI only (no API access)

Best For

Projects needing holder lists for airdrops
Whitelist generation
Non-technical teams
One-time or occasional exports

Magic Eden Analytics

How It Works

Magic Eden is Solana's largest NFT marketplace. Their collection pages show holder statistics and top holders—but they don't offer bulk export.

What You Can See

Total holder count
Top holders (limited list)
Floor price history
Trading volume
Listed/unlisted ratio

Strengths

Real-Time Market Data

Live floor prices
Active listings
Recent sales
Volume trends

Trust & Authority

Largest Solana marketplace
Verified collections
Community trust

Free Access

No account needed for viewing
Public data accessible to all

Limitations

No Holder Export

Can't download holder lists
No CSV/JSON export
Limited to viewing top holders

Not Snapshot Purpose-Built

Analytics focused on trading
Not designed for airdrop workflows
No wallet-to-NFT count mapping export

API Restrictions

Developer API exists but limited
Not designed for bulk holder queries
Terms of service restrictions

Best For

Checking floor price and volume
Verifying collection legitimacy
Trading and marketplace activity
Quick holder count lookups

Tensor Analytics

How It Works

Tensor is a pro-focused NFT marketplace with advanced analytics. Like Magic Eden, they show holder data but don't provide bulk export for airdrops.

What You Can See

Holder distribution charts
Whale tracking
Diamond hands metrics
Floor depth analysis
Bid/ask spreads

Strengths

Advanced Analytics

More detailed than Magic Eden
Holder distribution visualizations
Whale concentration metrics

Pro Trading Features

Batch listing tools
Collection offers
Automated buying

Developer API

More permissive than Magic Eden
Holder data available via API
Requires account

Limitations

No Direct CSV Export

Must use API for bulk data
Requires developer skills
Rate limits on free tier

API Account Required

Sign up needed
Developer program access
Terms of service compliance

Not Airdrop-Focused

Built for trading analytics
Holder export not primary feature
Additional work needed for airdrop format

Best For

Advanced traders
Collection analytics and visualization
Developers building custom tools
Whale watching

Helius API

How It Works

Helius provides RPC and API infrastructure for Solana. Their NFT APIs let you query holder data programmatically.

const response = await fetch(
  'https://api.helius.xyz/v1/nfts',
  {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({
      ownerAddress: 'WALLET_ADDRESS',
      apiKey: 'YOUR_API_KEY'
    })
  }
);

Strengths

Full Programmability

Build custom snapshot tools
Automate recurring exports
Integrate with existing systems

Rich Data Access

NFT metadata
Ownership history
Transaction data
Collection information

Enterprise Support

High uptime
Dedicated support tiers
Scalable infrastructure

Limitations

Requires Coding

Must write JavaScript/Python/etc.
Build your own CSV export
Handle pagination and errors

API Key Required

Account signup
Key management
Authentication complexity

Subscription Pricing

Free tier limited
$49-$499+/month for full access
Ongoing cost

Best For

Developers building tools
Automated recurring snapshots
Custom integrations
Projects with technical resources

Detailed Feature Comparison

Export Capabilities

Capability	Jumpbit	Magic Eden	Tensor	Helius
Download CSV	✅ Native	❌ No	❌ No	❌ Build yourself
Download JSON	✅ Native	❌ No	❌ No	✅ API response
All holders	✅ Yes	❌ Top only	❌ Top only	✅ Yes
NFT counts	✅ Yes	❌ No	❌ No	✅ Yes
Airdrop-ready	✅ Yes	❌ No	❌ No	❌ Custom

NFT Standard Support

Standard	Jumpbit	Magic Eden	Tensor	Helius
Metaplex	✅	✅	✅	✅
Compressed (cNFT)	✅	✅	✅	✅
Programmable (pNFT)	✅	✅	✅	✅
Export all types	✅	❌	❌	✅

Pricing Comparison

Tool	Free Access	Paid Plans
Jumpbit	Pay-per-use	Pay-per-use
Magic Eden	View analytics	N/A (no export)
Tensor	View analytics	API tiers
Helius	Limited API	$49-$499+/mo

Use Case Recommendations

"I need to airdrop tokens to my NFT holders"

Best choice: Solana NFT snapshot tool

Marketplaces don't export holder lists. You need actual wallet addresses with NFT counts. A dedicated snapshot tool exports exactly what you need for bulk token distribution.

"I want to check my collection's holder stats"

Best choice: Magic Eden or Tensor

For quick lookups—holder count, top holders, floor price—marketplaces provide this for free without any export needed.

"I'm building a custom analytics dashboard"

Best choice: Helius API

If you're coding a tool that needs holder data, Helius provides programmable access with good documentation.

"I need to generate a whitelist for my mint"

Best choice: NFT holder CSV export

Export holder addresses, filter by NFT count if needed, and use for allowlist verification in your mint tool.

"I want to track whale movements over time"

Best choice: Tensor + periodic snapshots

Use Tensor for real-time whale visualization, and take periodic snapshots to track changes over time.

Migration Considerations

From Manual Tracking to Automated Snapshots

If you've been manually copying addresses from explorers, any snapshot tool will save hours. A collection holder export tool provides the fastest path to exportable data.

From Helius API to Simpler Tools

If you built custom scripts but only need occasional exports, you can eliminate code maintenance by using a no-code snapshot tool for one-off exports.

From Marketplaces to Export Tools

Marketplaces are great for analytics and trading. When you need to actually take action on holder data (airdrops, whitelists), you need a dedicated export tool.

Key Takeaways

Different tools serve different purposes:

Export holder lists: Jumpbit (only option for no-code bulk export)
View analytics: Magic Eden, Tensor (free, comprehensive)
Build custom tools: Helius API (full programmability)

For most projects planning airdrops, whitelists, or holder rewards, a dedicated NFT snapshot tool offers the fastest path from collection address to actionable CSV.

How to Take an NFT Snapshot on Solana: Step-by-Step Guide

JUMPBIT — Sun, 25 Jan 2026 12:01:57 +0000

Introduction

You need a list of every wallet holding NFTs from your Solana collection. Maybe you're airdropping tokens to holders, building a whitelist for your next mint, or identifying your most dedicated collectors.

The problem? Marketplaces don't export holder lists. APIs require coding. And manually checking each NFT is impossible for collections with thousands of items.

In this tutorial, I'll show you exactly how to take an NFT snapshot on Solana—no coding required—and export your NFT holders to CSV in under 60 seconds.

What You'll Need

Before starting, make sure you have:

Collection Address — The verified collection identifier (not individual NFT mints)
Web Browser — Any modern browser (Chrome, Firefox, Safari)
5 Minutes — That's all it takes

Don't have the collection address? Find it on Magic Eden, Tensor, or Solscan by searching your collection name.

How to Find Your Collection Address

The collection address is different from individual NFT mint addresses. Here's how to find it:

On Magic Eden

Go to your collection page
Click on any NFT in the collection
Look for "Collection" in the details
Copy the address shown

On Tensor

Navigate to your collection
Click the info icon or details section
Find "Collection Address" or "Verified Collection"
Copy the address

On Solscan

Search for any NFT from your collection
View the NFT details
Look for "Collection" metadata
The address shown is your collection address

Example collection address: DRiP2Pn2K6fuMLKQmt5rZWyHiUZ6WK3GChEySUpHSS4x

How to Take an NFT Snapshot (Step-by-Step)

Step 1: Open the NFT Snapshot Tool

Navigate to the Solana NFT holder export tool.

No account or wallet connection required—the tool reads public blockchain data.

Step 2: Enter Your Collection Address

Paste your collection's verified address into the input field.

The tool validates the address and shows collection metadata (name, symbol, total supply) if available.

Step 3: Configure Snapshot Settings

Adjust optional settings:

Setting	Description	Default
Max Holders	Limit results to top N holders	All
Min NFT Count	Exclude wallets below threshold	1
Export Format	CSV or JSON	CSV

For most use cases, default settings work fine—capturing all holders.

Step 4: Generate the Snapshot

Click "Generate Snapshot" to start the process.

What happens next:

The tool queries Solana for all NFTs in the collection
It identifies the current owner of each NFT
Progress bar shows completion status
Large collections (10K+ NFTs) may take 30-60 seconds

Step 5: Download Your Holder List

Once complete, click "Download CSV" or "Download JSON".

Your file includes:

Wallet addresses (holders)
NFT count per holder
Percentage of collection owned
Holder rank

Understanding Your Snapshot Data

Here's what each column in your CSV means:

Wallet Address

The Solana public key of the holder. This is the address you'll use for:

Airdrop distribution
Whitelist verification
Analytics tracking

NFT Count

The number of NFTs this wallet holds from the collection. A wallet with 5 NFTs appears once with count 5—not 5 separate entries.

Percentage of Collection

The holder's share of total collection supply. Useful for:

Identifying whales (collectors with many NFTs)
Proportional airdrop calculations
Concentration analysis

Holder Rank

Position in holder leaderboard by NFT count. Rank 1 = largest holder.

What to Do After Taking a Snapshot

For Token Airdrops

Calculate allocation — Decide tokens per NFT held
Add amount column — Multiply NFT count by tokens per NFT
Filter if needed — Remove marketplace wallets or bots
Import to Multisender — Upload to Jumpbit Multisender

Example calculation:

Wallet A: 5 NFTs × 100 tokens/NFT = 500 tokens
Wallet B: 1 NFT × 100 tokens/NFT = 100 tokens

For Whitelist Generation

Set criteria — Minimum NFTs required for whitelist
Filter snapshot — Keep only wallets meeting criteria
Export addresses — Single column of eligible wallets
Import to mint tool — Use for presale/allowlist verification

For Diamond Hands Tracking

Take initial snapshot — Record holders at time T1
Wait period — Weeks or months
Take second snapshot — Record holders at time T2
Compare lists — Wallets in both = diamond hands

How to Filter Your Snapshot Data

Raw snapshots include everything—including addresses you may want to exclude.

Removing Marketplace Wallets

When NFTs are listed for sale, they may be held by marketplace escrow accounts:

Marketplace	What Happens	Action
Magic Eden	Escrow holds listed NFTs	Optional filter
Tensor	Various escrow accounts	Optional filter
Other	Check listing status	Case-by-case

Note: Listed NFTs are still "owned" in some sense—the seller controls them. Decide based on your use case.

Removing Suspected Bots

Bot wallets often have patterns:

Very new wallet age
Holding minimum 1 NFT only
No other activity on-chain

Consider your filtering criteria carefully—some legitimate holders may match these patterns.

Setting Minimum Thresholds

Filter by NFT count:

Filter: NFT Count >= 3 (for whale-only rewards)
Filter: NFT Count >= 1 (for all holders)

NFT Snapshot for Different Collection Types

Standard Metaplex Collections

Most Solana NFT collections use Metaplex standard:

SMB, DeGods, y00ts, Mad Lads
Straightforward snapshot process
Works with all snapshot tools

Compressed NFT Collections (cNFTs)

Newer collections using state compression:

DRiP, some gaming NFTs
Stored in Merkle trees
Requires cNFT-compatible tools

The Metaplex NFT snapshot tool supports cNFTs—no special configuration needed.

Programmable NFTs (pNFTs)

Collections with enforced royalties:

Some newer Metaplex collections
Custom authorization rules
Same snapshot process as standard

Mixed Collections

Some collections have multiple standards:

Early mints: standard Metaplex
Later mints: cNFTs or pNFTs
Good tools handle all types automatically

Troubleshooting Common Issues

"Invalid Collection Address"

Cause: You entered something that isn't a valid Solana collection address.

Fix:

Verify on Magic Eden or Tensor
Ensure it's the collection address, not an NFT mint
Check for extra spaces or characters

"Collection Not Found"

Cause: The collection may not be verified or uses non-standard structure.

Fix:

Confirm collection has verified collection status
Try finding the address on a different marketplace
Some very old collections lack proper collection data

"No Holders Found"

Cause: The collection has no current holders or address is incorrect.

Fix:

Verify collection exists and has been minted
Check that NFTs aren't all burned
Confirm collection address on explorer

"Snapshot Taking Too Long"

Cause: Large collection with many NFTs.

Fix:

Wait for processing (can take 60-90 seconds for 50K+ NFTs)
Large compressed NFT collections may take longer
Try during off-peak hours

Alternative Methods for NFT Snapshots

Method 1: Helius API

const response = await fetch(
  'https://api.helius.xyz/v1/nft-events',
  {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({
      query: { collection: 'COLLECTION_ADDRESS' },
      apiKey: 'YOUR_API_KEY'
    })
  }
);

Pros: Programmable, rich data
Cons: Requires coding, API key, rate limits

Method 2: Tensor API

Tensor offers API access for analytics:

Holder data available
Requires developer account
Rate limits apply

Pros: Real-time marketplace data
Cons: Account required, limits on free tier

Method 3: Snapshot Tool (Recommended)

No code, no API keys, just paste and export. Use a collection holder snapshot tool for the fastest results.

Pros: Fast, simple, export-ready formats
Cons: Less customizable than API methods

Best Practices for NFT Snapshots

1. Document Snapshot Timing

Always record when the snapshot was taken:

Block height (if available)
Timestamp
Purpose of snapshot

2. Announce in Advance

For governance or rewards:

Announce snapshot date/time beforehand
Prevents accusations of unfairness
Gives holders time to consolidate

3. Verify Sample Addresses

Spot-check 5-10 random addresses:

Confirm they hold the expected NFTs
Verify NFT counts match
Build confidence in data accuracy

4. Consider Staked/Locked NFTs

NFTs in staking contracts may show different owners:

Staking contract address = current holder
Original owner = intended recipient
Coordinate with staking platform for true owner data

5. Keep Historical Snapshots

Save snapshots for:

Audit trails
Diamond hands comparisons
Dispute resolution

Key Takeaways

Taking an NFT snapshot on Solana is straightforward:

Get your collection address (not NFT mints)
Use a snapshot tool (no coding required)
Generate and download your holder list
Filter and process for your specific use case

The entire process takes under 60 seconds for most collections.

Ready to snapshot your NFT collection?

Try the NFT holder CSV export tool—paste your collection address and download in seconds.

What is an NFT Snapshot? Complete Guide to Solana Holder Exports

JUMPBIT — Sun, 25 Jan 2026 11:56:52 +0000

Introduction

You're planning a token airdrop to your NFT holders. Or building a whitelist for your next mint. Or just trying to figure out who owns your collection.

But how do you get a list of every wallet holding your NFTs?

The answer: NFT Snapshots.

In this guide, I'll explain exactly what an NFT snapshot is, how it works on Solana, what data it captures, and why projects use snapshots for airdrops, whitelists, and community rewards.

What is an NFT Snapshot?

An NFT snapshot is a point-in-time capture of all wallet addresses holding NFTs from a specific collection, along with how many NFTs each wallet owns.

On Solana, a snapshot scans every NFT associated with a collection address and identifies the current owner of each. The result is a downloadable list—typically CSV or JSON—containing every holder's wallet address and NFT count.

Simple explanation:

You provide the collection address
The tool queries the Solana blockchain
It finds every wallet holding NFTs from that collection
You download the complete holder list with NFT counts

Unlike marketplace analytics (which show limited data), an NFT holder export tool gives you the raw ownership data—every single holder, exportable and actionable.

How Does an NFT Snapshot Work? (Technical Breakdown)

Let's look at what happens when you take a snapshot of a Solana NFT collection:

Step 1: Collection Address Input

You provide the collection address—the verified collection identifier that groups NFTs together. This is different from individual NFT mint addresses.

Step 2: NFT Discovery

The snapshot tool queries the Solana blockchain to find all NFTs belonging to that collection. This involves:

Reading Metaplex metadata
Checking collection verification
Handling both standard and compressed NFTs

Step 3: Owner Identification

For each NFT in the collection, the tool identifies the owner—the wallet address that currently holds that NFT.

Step 4: Aggregation

Owners are aggregated by wallet address:

If a wallet holds 5 NFTs → counted once with quantity 5
Single NFT holders → counted once with quantity 1

Step 5: Data Compilation

All holder data is compiled into a structured format:

Data Field	Description	Example
Wallet Address	Owner of the NFT(s)	7xKX...4mPq
NFT Count	Number of NFTs held	5
Percentage	Share of total collection	0.5%

Step 6: Export

The complete holder list is exported to CSV (for spreadsheets and airdrop tools) or JSON (for developers and custom scripts).

What Data Does an NFT Snapshot Include?

A comprehensive NFT snapshot captures:

Core Fields:

Wallet address — The holder's Solana public key
NFT count — Number of NFTs held from the collection
Percentage of collection — Holder's share of total supply

Extended Fields (tool-dependent):

Individual NFT mint addresses
Holder rank by quantity
Rarity scores (if available)
Collection verification status

Why Do Projects Take NFT Snapshots?

1. Token Airdrops to Holders

The most common use case. NFT projects airdrop tokens to holders:

Reward community members with governance tokens
Distribute utility tokens for ecosystem
Proportional rewards based on NFTs held

Example: A collection airdrops 100 tokens per NFT held—holders with 5 NFTs receive 500 tokens. After you export your NFT holders to CSV, use a bulk sender to distribute tokens.

2. Whitelist Generation

Create allow-lists for exclusive access:

Presale spots for new mints
Exclusive drops for existing holders
Tiered access based on NFT count

3. Diamond Hands Rewards

Identify and reward loyal long-term holders:

Compare snapshots over time
Track who has held continuously
Reward holders who didn't flip

4. Whale Detection

Identify collectors with multiple NFTs:

Track top 10/50/100 collectors
Monitor collection concentration
Identify potential influencers

5. Community Analytics

Understand your holder base:

Total unique holders
Average NFTs per holder
Holder growth over time
Distribution patterns

NFT Standards on Solana

Metaplex Standard (Original)

The classic Solana NFT standard:

Individual NFT accounts
On-chain metadata
Used by most collections

Snapshot compatibility: ✅ Fully supported

Certified Collections

Metaplex verified collections with on-chain collection authority:

Collection address links all NFTs
Verification prevents fakes
Easier to snapshot

Snapshot compatibility: ✅ Fully supported

Compressed NFTs (cNFTs)

State compression for cheaper minting:

Data stored in Merkle trees
Much cheaper to mint (1000x)
Different on-chain structure

Snapshot compatibility: ✅ Requires updated tools that support cNFT scanning

Programmable NFTs (pNFTs)

NFTs with enforced royalties and rules:

Royalty enforcement on-chain
Custom authorization rules
Used by newer collections

Snapshot compatibility: ✅ Fully supported

NFT Snapshot vs Marketplace Analytics

Why not just use Magic Eden or Tensor?

Feature	Marketplace Analytics	NFT Snapshot Tool
View holder count	✅ Yes	✅ Yes
See top holders	✅ Limited	✅ All holders
Export to CSV	❌ No	✅ Yes
Get wallet addresses	❌ No bulk export	✅ Full list
Airdrop-ready format	❌ No	✅ Yes
Compressed NFT support	✅ Partial	✅ Full

Marketplaces are great for trading and quick stats. A dedicated Solana NFT snapshot tool is essential for taking action on holder data.

How to Use an NFT Snapshot for Airdrops

Here's a typical workflow for airdropping tokens to your NFT community:

Step 1: Take the Snapshot

Enter your collection address
Generate the snapshot
Download the CSV file

Step 2: Calculate Airdrop Amounts

Add a column for airdrop allocation:

Per-NFT: Multiply NFT count by tokens per NFT
Equal: Same amount to all holders regardless of count
Tiered: Different rates for different holder tiers

Step 3: Filter (Optional)

Remove known marketplace wallets
Exclude suspected bots
Set minimum NFT threshold

Step 4: Import to Multisender

Upload your CSV to Jumpbit Multisender and execute the airdrop to all holders in batches.

What Are the Limitations of NFT Snapshots?

Point-in-Time Only
A snapshot captures one moment. Ownership changes constantly—the data is accurate only at snapshot time.

No Historical Data (Usually)
Most tools snapshot the current state only. Historical ownership requires specialized archival tools.

Includes All Holders
Snapshots include marketplace escrows, lending protocols, and bots. You may need to filter these out.

Large Collections Take Longer
Collections with 50K+ NFTs require more processing time. Expect 30-90 seconds for large collections.

Common Questions About NFT Snapshots

What address do I need?

You need the collection address, not individual NFT mints. Find it on:

Magic Eden (collection page URL or details)
Tensor (collection info section)
Solscan (search collection name)

Can I snapshot compressed NFTs?

Yes, but not all tools support cNFTs. Modern snapshot tools handle standard Metaplex, compressed NFTs (cNFTs), and programmable NFTs (pNFTs) automatically.

How accurate is the data?

Snapshot accuracy depends on:

RPC node freshness (usually <1 second delay)
Collection verification (verified = more accurate)
Time of snapshot (ownership changes constantly)

Can I snapshot a specific time in the past?

Most tools only support current-block snapshots. Historical snapshots require archival RPC nodes and specialized tools.

Key Takeaways

NFT snapshots are essential for any Solana collection planning:

Token airdrops to holders
Whitelist generation for mints
Community reward programs
Holder analytics and tracking

The process is straightforward: provide a collection address, let the tool scan the blockchain, and download your complete holder list.

Ready to capture your NFT holder data?

Try Jumpbit's NFT holder snapshot tool—no API keys, no coding, just paste your collection address and export in seconds.

Token Snapshot Tools Compared: Jumpbit vs Helius vs Smithii

JUMPBIT — Sun, 25 Jan 2026 11:44:34 +0000

Introduction

You need to export your Solana token holders. But which tool should you use?

Helius API requires coding. Smithii has rate limits. Manual RPC queries are complex. And there are newer options like Jumpbit that promise simpler workflows.

In this comparison, I'll break down the top methods for taking token snapshots on Solana—covering ease of use, speed, pricing, and export capabilities—so you can choose the right tool for your project.

Quick Comparison Overview

Feature	Jumpbit	Helius API	Smithii	Manual RPC
Ease of Use	No-code UI	Requires coding	Web UI	Requires coding
Export Formats	CSV, JSON	JSON (API)	CSV	Custom
API Key Required	No	Yes	Yes	No
Rate Limits	None	Yes (tier-based)	Yes	RPC-dependent
Large Token Support	1M+ holders	Tier-dependent	Limited	Slow
SPL22 Support	Yes	Yes	Partial	Yes
Pricing	Pay-per-use	Subscription	Subscription	RPC costs

Jumpbit Token Snapshot

How It Works

Jumpbit offers a browser-based snapshot tool. You paste a mint address, click generate, and download your holder list. No account, no API keys, no coding.

Strengths

No Technical Barrier

Paste address → Click generate → Download CSV
Works in any browser
No wallet connection required

Fast Processing

Handles 1M+ holder tokens
Typical export time: 30-60 seconds
No rate limits or daily caps

Export-Ready Formats

CSV for spreadsheets and airdrop tools
JSON for developers
Clean data with wallet addresses, balances, percentages

Full Token Support

SPL (original Token Program)
SPL22 (Token Extensions)
Automatic standard detection

Limitations

No API access (UI only)
No historical snapshots (current block only)
Less customizable than API solutions

Best For

Project teams needing quick exports
Non-technical users
One-time or occasional snapshots
Airdrop preparation

Helius API

How It Works

Helius provides RPC and API infrastructure for Solana. Their token holder endpoints let you query holder data programmatically.

const response = await fetch(
  'https://api.helius.xyz/v0/token-accounts',
  {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({
      mintAddress: 'YOUR_TOKEN_MINT',
      apiKey: 'YOUR_API_KEY'
    })
  }
);
const holders = await response.json();

Strengths

Full Programmability

Integrate into custom scripts
Automate recurring snapshots
Build custom analytics pipelines

Rich Data

Detailed token account information
Transaction history access
Webhook support for real-time tracking

Enterprise Infrastructure

High uptime guarantees
Dedicated support on higher tiers
Scalable for large applications

Limitations

Requires Coding

Must write JavaScript/Python/etc.
Handle pagination manually
Build your own CSV export

API Key Required

Sign up for account
Manage authentication
Key rotation for security

Rate Limits

Free tier: Limited requests/second
Paid tiers: Higher limits but still capped
Large exports may hit limits

Subscription Pricing

Free tier limited
Developer: $49/month
Growth: $499/month
Enterprise: Custom

Best For

Developers building custom tools
Recurring automated snapshots
Integration with existing systems
Projects needing full API access

Smithii

How It Works

Smithii offers Solana analytics tools including token holder lookups. Their web interface allows viewing holder data with limited export.

Strengths

Analytics Dashboard

Visual holder distribution
Whale tracking
Historical data (limited)

Web Interface

No coding required
Visual charts and graphs
Quick lookups

Limitations

Export Restrictions

CSV export limited on free tier
Full exports require subscription
Rate limits on queries

Account Required

Must create account
Email verification
API key management

Less Comprehensive

Fewer features than Helius API
Limited customization
Slower for large tokens

Best For

Quick holder lookups
Visual analytics
Projects already using Smithii ecosystem

Manual RPC Queries

How It Works

Query Solana RPC nodes directly using getProgramAccounts to fetch all token accounts for a mint.

const { Connection, PublicKey } = require('@solana/web3.js');
const { TOKEN_PROGRAM_ID } = require('@solana/spl-token');

const connection = new Connection('https://api.mainnet-beta.solana.com');

const accounts = await connection.getProgramAccounts(
  TOKEN_PROGRAM_ID,
  {
    filters: [
      { dataSize: 165 },
      { memcmp: { offset: 0, bytes: mintAddress } }
    ]
  }
);

Strengths

No Third-Party Dependency

Direct blockchain access
No API keys
No rate limits (except RPC)

Full Control

Custom data processing
Any export format
Complete flexibility

Free (Mostly)

Public RPC endpoints available
Pay only for premium RPC if needed

Limitations

High Technical Barrier

Requires Solana development knowledge
Must handle data parsing
Error handling complexity

Slow for Large Tokens

getProgramAccounts is resource-intensive
May timeout on large tokens
Pagination required

RPC Limitations

Public RPCs have restrictions
May need paid RPC for reliability
Geographic performance varies

Best For

Experienced Solana developers
Custom integration requirements
Projects wanting zero external dependencies

Detailed Feature Comparison

Speed Comparison

Token Size	Jumpbit	Helius	Smithii	Manual RPC
10K holders	~5s	~3s	~10s	~15s
100K holders	~15s	~10s	~45s	~60s
1M holders	~45s	~30s	Timeout	Timeout

Export Format Comparison

Format	Jumpbit	Helius	Smithii	Manual RPC
CSV (Excel-ready)	✅ Native	❌ Build yourself	✅ Limited	❌ Build yourself
JSON	✅ Native	✅ Native	✅ Native	✅ Native
Custom	❌ No	✅ Yes	❌ No	✅ Yes

Pricing Comparison

Tool	Free Tier	Paid Plans
Jumpbit	Pay-per-use	Pay-per-use
Helius	Limited	$49-$499+/mo
Smithii	Very limited	$29+/mo
Manual RPC	Free (public)	RPC costs

Which Tool Should You Choose?

Choose Jumpbit If:

You need a quick, one-time snapshot
You're not a developer
You want CSV export without coding
You have a large token (1M+ holders)
You don't want subscriptions or API keys

Choose Helius If:

You're building a custom application
You need automated recurring snapshots
You want full API programmability
You have budget for subscriptions
You need enterprise support

Choose Smithii If:

You want visual analytics dashboards
You're already in their ecosystem
You need quick lookups (not bulk export)
You prefer charts over raw data

Choose Manual RPC If:

You're an experienced Solana developer
You want zero external dependencies
You need maximum customization
You have smaller tokens (<100K holders)

Migration Considerations

Moving from Manual RPC to Jumpbit

If you've been writing custom scripts, Jumpbit can save hours of development time. Export your snapshot in seconds instead of maintaining code.

Moving from Helius/Smithii to Jumpbit

If you only need occasional snapshots (not automated), you can eliminate monthly subscriptions by using pay-per-use tools.

Moving from UI Tools to API

If your needs grow—recurring snapshots, custom integrations, automation—consider upgrading to Helius API for full programmability.

Key Takeaways

There's no single "best" tool—it depends on your needs:

Simplest option: Jumpbit (no code, no subscription)
Most powerful: Helius API (full programmability)
Best analytics: Smithii (visual dashboards)
Most control: Manual RPC (zero dependencies)

For most projects doing occasional airdrops or governance snapshots, a no-code tool like Jumpbit Token Snapshot offers the fastest path from mint address to CSV export.

How to Take a Token Snapshot on Solana: Step-by-Step Guide

JUMPBIT — Sun, 25 Jan 2026 11:34:43 +0000

Introduction

You need a list of every wallet holding your Solana token. Maybe you're planning an airdrop, setting up a governance vote, or just analyzing your holder base.

The problem? Blockchain explorers don't let you export that data. APIs require coding. RPC queries are complex.

In this tutorial, I'll show you exactly how to take a token snapshot on Solana—no coding required—and export your complete holder list to CSV in under 60 seconds.

What You'll Need

Before starting, make sure you have:

Token Mint Address — The unique identifier for your SPL or SPL22 token
Web Browser — Any modern browser (Chrome, Firefox, Safari)
5 Minutes — That's all it takes

Don't have the mint address? Find it on Solscan, Birdeye, or DexScreener by searching your token name.

How to Take a Token Snapshot (Step-by-Step)

Step 1: Open the Token Snapshot Tool

Navigate to Jumpbit Token Snapshot.

No account or wallet connection required—the tool reads public blockchain data.

Step 2: Enter Your Token Mint Address

Paste your SPL or SPL22 token's mint address into the input field.

Example mint addresses:

BONK: DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263
USDC: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v

The tool validates the address and shows token metadata (name, symbol, decimals).

Step 3: Configure Snapshot Settings

Adjust optional settings:

Setting	Description	Default
Max Holders	Limit results to top N holders	All
Min Balance	Exclude wallets below threshold	0
Export Format	CSV or JSON	CSV

For most use cases, default settings work fine—capturing all holders.

Step 4: Generate the Snapshot

Click "Generate Snapshot" to start the process.

What happens next:

The tool queries Solana RPC nodes
It scans all token accounts for your mint
Progress bar shows completion status
Large tokens (100K+ holders) may take 30-60 seconds

Step 5: Download Your Holder List

Once complete, click "Download CSV" or "Download JSON".

Your file includes:

Wallet addresses (holders)
Token balances (raw and formatted)
Percentage of total supply
Holder rank

Understanding Your Snapshot Data

Here's what each column in your CSV means:

Wallet Address

The Solana public key of the holder. This is the address you'll use for:

Airdrop distribution
Whitelist verification
Analytics tracking

Token Balance (Raw)

The on-chain balance as a raw integer. For a token with 9 decimals, a balance of 1000000000 equals 1.0 tokens.

Token Balance (UI Amount)

The human-readable balance with decimals applied. This is what you'd see in a wallet—1,000.50 tokens.

Percentage of Supply

The holder's share of total circulating supply. Useful for:

Identifying whales (5%+ holders)
Proportional airdrop calculations
Supply concentration analysis

What to Do After Taking a Snapshot

For Airdrops

Filter the list — Remove exchange wallets, known bots, or holders below minimum
Calculate amounts — Add an "airdrop amount" column based on your distribution logic
Import to Multisender — Upload to Jumpbit Multisender for bulk distribution

For Governance

Set snapshot block — Note the timestamp/block when snapshot was taken
Publish criteria — Announce minimum balance required to vote
Verify eligibility — Cross-reference voter addresses against snapshot

For Analytics

Save historical copies — Take weekly/monthly snapshots to track growth
Calculate metrics — Holder count, average balance, Gini coefficient
Visualize trends — Chart holder growth over time

How to Filter Your Snapshot Data

Raw snapshots include everything—including wallets you may want to exclude.

Removing Exchange Wallets

Known Solana exchange wallets to filter out:

Exchange	Wallet Prefix	Action
Binance	Multiple	Remove from airdrop
Coinbase	Multiple	Remove from airdrop
Kraken	Multiple	Remove from airdrop

Tip: Search "Solana exchange wallets list" for updated addresses, or check if balances are suspiciously large and static.

Removing Dust Wallets

Wallets with tiny balances (dust) often aren't real users:

Filter: Balance > 10 tokens (or your preferred minimum)

Removing Program Accounts

Some "holders" are actually smart contracts or program accounts:

Liquidity pools
Staking contracts
Token vesting contracts

Check if the address is a known program before including in airdrops.

Token Snapshot for Different Token Standards

SPL Tokens (Original Standard)

The standard Solana token program. Most tokens use this:

USDC, USDT, BONK, WIF, JUP
Straightforward snapshot process
Works with all snapshot tools

SPL22 / Token Extensions (Token-2022)

Newer token standard with advanced features:

Transfer fees
Interest-bearing tokens
Non-transferable tokens
Confidential transfers

Important: Make sure your snapshot tool supports Token-2022. Jumpbit Token Snapshot handles both standards automatically.

Troubleshooting Common Issues

"Invalid Token Address"

Cause: You entered something that isn't a valid Solana mint address.

Fix:

Verify the address on Solscan
Ensure you're using the mint address, not a token account
Check for extra spaces or characters

"No Holders Found"

Cause: The token has zero holders or the mint is incorrect.

Fix:

Confirm the token exists and has been distributed
Verify mint address on a blockchain explorer
Check if the token is on the correct network (mainnet vs devnet)

"Snapshot Taking Too Long"

Cause: Token has millions of holders.

Fix:

Wait for processing (can take 60-90 seconds for 1M+ holders)
Check your internet connection
Try during off-peak hours if RPC nodes are congested

"Balance Shows Zero"

Cause: Holder recently transferred out or data is from a previous block.

Fix:

Refresh and take a new snapshot
Verify current balance on explorer
Note that snapshots are point-in-time—balances change constantly

Alternative Methods for Token Snapshots

Method 1: Helius API

// Requires API key and coding
const response = await fetch(
  `https://api.helius.xyz/v0/token-accounts?api-key=${API_KEY}`,
  {
    method: 'POST',
    body: JSON.stringify({ mint: 'TOKEN_MINT' })
  }
);

Pros: Programmable, customizable
Cons: Requires coding, API key, rate limits apply

Method 2: Direct RPC Query

// Using getProgramAccounts
const accounts = await connection.getProgramAccounts(
  TOKEN_PROGRAM_ID,
  {
    filters: [
      { dataSize: 165 },
      { memcmp: { offset: 0, bytes: mintAddress } }
    ]
  }
);

Pros: No third-party dependency
Cons: Complex, slow for large tokens, requires RPC expertise

Method 3: Snapshot Tool (Recommended)

No code, no API keys, just paste and export.

Pros: Fast, simple, export-ready formats
Cons: Less customizable than API methods

Best Practices for Token Snapshots

1. Document Your Snapshot Time

Always record when the snapshot was taken. This is crucial for:

Governance vote eligibility disputes
Airdrop fairness verification
Historical analysis

2. Take Multiple Snapshots

Don't rely on a single snapshot. Take snapshots at:

Announcement time (baseline)
Distribution time (final eligibility)
Post-distribution (verification)

3. Verify Random Samples

Spot-check 5-10 random addresses on Solscan to verify balances match your snapshot data.

4. Secure Your Data

Holder lists are valuable data. Store securely and don't share publicly unless intended.

5. Consider Privacy

Some holders may not want their addresses publicly linked to token holdings. Be mindful when publishing holder lists.

Key Takeaways

Taking a token snapshot on Solana is straightforward:

Get your token's mint address
Use a snapshot tool (no coding required)
Generate and download your holder list
Filter and process for your specific use case

The entire process takes under 60 seconds for most tokens.

Ready to snapshot your token?

Try Jumpbit Token Snapshot—paste your mint address and export in seconds.

What is a Token Snapshot? Complete Guide to Solana Holder Exports

JUMPBIT — Sun, 25 Jan 2026 11:29:07 +0000

Introduction

You're planning an airdrop. You need a list of everyone holding your token—wallet addresses, balances, percentages of supply.

But how do you get that data off the blockchain and into a usable format?

The answer: Token Snapshots.

In this guide, I'll explain exactly what a token snapshot is, how it works on Solana, what data it captures, and why projects use snapshots for airdrops, governance, and community rewards.

What is a Token Snapshot?

A token snapshot is a point-in-time capture of all wallet addresses holding a specific token, along with their balances.

On Solana, a snapshot scans every token account associated with an SPL or SPL22 mint address and extracts the current holdings. The result is a downloadable list—typically CSV or JSON—containing every holder's wallet address and token balance.

Simple explanation:

You provide the token's mint address
The tool queries the Solana blockchain
It finds every wallet holding that token
You download the complete holder list with balances

Unlike blockchain explorers (which show limited holder counts), a snapshot gives you the raw data—every single holder, exportable and actionable.

How Does a Token Snapshot Work? (Technical Breakdown)

Let's look at what happens when you take a snapshot of a Solana token:

Step 1: Mint Address Input

You provide the SPL or SPL22 token mint address. This is the unique identifier for the token on Solana's blockchain.

Step 2: Token Account Discovery

The snapshot tool queries Solana's Token Program to find all token accounts associated with that mint. Each token account represents one wallet's holdings of that specific token.

Step 3: Owner Extraction

For each token account, the tool identifies the owner—the wallet address that controls those tokens. This is the address you'll use for airdrops or analysis.

Step 4: Balance Reading

The tool reads the current token balance from each account. Balances are stored as raw integers on-chain, then converted to human-readable amounts using the token's decimal precision.

Step 5: Data Aggregation

All holder data is compiled into a structured format:

Data Field	Description	Example
Wallet Address	Owner of the token account	7xKX...4mPq
Balance (Raw)	On-chain integer amount	1000000000
Balance (UI)	Human-readable with decimals	1,000.00
Percentage	Share of total supply	0.15%

Step 6: Export

The complete holder list is exported to CSV (for spreadsheets and airdrop tools) or JSON (for developers and custom scripts).

What Data Does a Token Snapshot Include?

A comprehensive token snapshot captures:

Core Fields:

Wallet address — The holder's Solana public key
Token balance — Current holdings at snapshot time
Percentage of supply — Holder's share of circulating supply

Extended Fields (tool-dependent):

Token account address (the associated token account)
Holder rank by balance
First transaction date (for loyalty analysis)
Account status (active/frozen)

Why Do Projects Take Token Snapshots?

1. Airdrop Distribution

The most common use case. Projects snapshot their token holders to:

Reward existing community members
Distribute new tokens proportionally to holdings
Target specific holder tiers (whales, mid-holders, small holders)

Example: A project launching a governance token airdrops to everyone holding 1,000+ of their original token.

2. DAO Governance

Snapshots enable fair voting by capturing who held tokens at a specific moment:

Prevents vote manipulation via last-minute purchases
Weights votes by token balance at snapshot time
Provides verifiable on-chain proof of eligibility

3. Community Rewards

Identify and reward loyal holders:

Diamond hands recognition (long-term holders)
Exclusive access to presales or NFT mints
Tiered rewards based on holding amount

4. Whale Monitoring

Track large holder movements:

Identify top 10/50/100 holders
Monitor supply concentration
Detect potential sell pressure

5. Analytics & Research

Analyze token distribution:

Holder growth over time (comparing snapshots)
Gini coefficient (supply concentration)
Active vs inactive holder ratios

Token Snapshot vs Blockchain Explorer

Why not just use Solscan or Birdeye?

Feature	Blockchain Explorer	Token Snapshot Tool
View holder count	✅ Yes	✅ Yes
See top holders	✅ Limited (top 20-100)	✅ All holders
Export to CSV	❌ No	✅ Yes
Get wallet addresses	❌ No bulk export	✅ Full list
Airdrop-ready format	❌ No	✅ Yes
Filter by balance	❌ No	✅ Yes

Explorers are great for quick lookups. Snapshots are essential for taking action on that data.

SPL vs SPL22: What's the Difference for Snapshots?

Solana has two token standards:

SPL (Token Program)

Original Solana token standard
Used by most tokens (USDC, BONK, etc.)
Straightforward snapshot process

SPL22 (Token Extensions / Token-2022)

Newer standard with advanced features
Supports transfer fees, metadata, confidential transfers
Requires updated snapshot tools that understand the new program

Good snapshot tools support both standards—so you don't need to worry which one your token uses.

How to Use a Token Snapshot for Airdrops

Here's a typical workflow using Jumpbit's Token Snapshot and Multisender:

Step 1: Take the Snapshot

Enter your token's mint address
Generate the snapshot
Download the CSV file

Step 2: Filter Holders (Optional)

Open the CSV in Excel or Google Sheets:

Remove wallets below minimum balance
Exclude known exchange wallets
Sort by balance for tiered rewards

Step 3: Calculate Airdrop Amounts

Add a column for airdrop allocation:

Equal distribution: Same amount to everyone
Proportional: Based on % of supply held
Tiered: Different amounts for different tiers

Step 4: Import to Multisender

Upload your modified CSV to a bulk distribution tool and execute the airdrop in batches.

What Are the Limitations of Token Snapshots?

Point-in-Time Only
A snapshot captures one moment. Holdings change constantly—the data is accurate only at snapshot time.

No Historical Data (Usually)
Most tools snapshot the current block only. Historical snapshots at past block heights require archival RPC nodes.

Includes All Holders
Snapshots include exchange wallets, bots, and program accounts. You may need to filter these out manually.

Large Tokens Take Longer
Tokens with 1M+ holders require more processing time. Most tools handle this, but expect 30-60 seconds for massive tokens.

Key Takeaways

Token snapshots are essential infrastructure for any Solana project planning:

Airdrop campaigns
DAO governance votes
Community reward programs
Holder analytics

The process is straightforward: provide a mint address, let the tool scan the blockchain, and download your complete holder list.

Ready to snapshot your token holders?

Try Jumpbit Token Snapshot—no API keys, no coding, just paste your mint address and export.

Maker Bot Settings: Fixed vs Range Amounts Explained

JUMPBIT — Fri, 23 Jan 2026 18:33:12 +0000

Introduction

You're setting up your maker bot and hit the configuration screen:

Trade Amount: Fixed ○ or Range ○

Which do you choose? Does it actually matter?

Yes—this single setting affects how natural your trading activity looks on charts, your cost per maker, and potentially your DexScreener ranking.

In this guide, I'll explain the difference between fixed and range modes, when to use each, and the optimal settings for different strategies.

What is Fixed Amount Mode?

Fixed mode uses the exact same SOL amount for every maker transaction.

How It Works

Setting: Fixed 0.005 SOL

Maker 1: Buys 0.005 SOL → Sells 0.005 SOL worth
Maker 2: Buys 0.005 SOL → Sells 0.005 SOL worth
Maker 3: Buys 0.005 SOL → Sells 0.005 SOL worth
...
Maker 500: Buys 0.005 SOL → Sells 0.005 SOL worth

Every transaction is identical in size.

Pros of Fixed Mode

Predictable costs - Know exactly how much each maker costs
Simpler budgeting - Total spend = makers × fixed amount + fees
Consistent chart impact - Each trade has same visual weight

Cons of Fixed Mode

Looks artificial - Real traders don't all trade identical amounts
Pattern detection - Repeated same-size trades are easy to spot
Less natural charts - Creates uniform candle patterns

What is Range Amount Mode?

Range mode randomizes trade amounts within your specified minimum and maximum.

How It Works

Setting: Range 0.001 - 0.01 SOL

Maker 1: Buys 0.0034 SOL → Sells
Maker 2: Buys 0.0078 SOL → Sells
Maker 3: Buys 0.0012 SOL → Sells
Maker 4: Buys 0.0091 SOL → Sells
...

Every transaction has a different, randomized size within your bounds.

Pros of Range Mode

Natural appearance - Mimics real trading behavior
Varied chart patterns - Different candle sizes look organic
Harder to detect - No repeating patterns to flag
Better for long campaigns - Sustainable without looking automated

Cons of Range Mode

Variable costs - Harder to predict exact spend
Wider range = more variance - Costs can skew high or low
Requires more initial funding - Need buffer for max amounts

Side-by-Side Comparison

Aspect	Fixed Mode	Range Mode
Trade sizes	All identical	Randomized
Chart appearance	Uniform, artificial	Varied, natural
Cost predictability	Exact	Approximate
Detection risk	Higher	Lower
Setup complexity	Simple	Slightly more
Best for	Short bursts, testing	Long campaigns, organic look

When to Use Fixed Mode

Scenario 1: Quick Test Run

Running 50-100 makers to test your setup? Fixed mode is fine—not enough volume for patterns to matter.

Scenario 2: Exact Budget Control

Have exactly 5 SOL and need to know exactly how many makers you'll get? Fixed mode gives precision.

Budget: 5 SOL
Fixed amount: 0.005 SOL
Platform fee: 0.0005 SOL
PDA cost: ~0.01 SOL

Per maker: ~0.0155 SOL
Total makers: ~322

Scenario 3: High-Speed Short Burst

Running 500 makers in 1 minute? The burst is so fast that pattern detection is less relevant.

When to Use Range Mode

Scenario 1: Extended Campaigns (Recommended)

Running makers over 30+ minutes? Range mode prevents detectable patterns from forming.

Scenario 2: Organic Appearance Priority

Want charts that look natural to traders reviewing your token? Range creates varied candle sizes.

Scenario 3: DexScreener Credibility

Platforms may develop detection for uniform trading. Range mode future-proofs your activity.

Scenario 4: Combining with Organic Activity

If real traders are also buying, range-mode bot activity blends in better.

Optimal Range Settings

Conservative Range (Safest)

Min: 0.001 SOL
Max: 0.003 SOL
Variance: 3x (low)

Small trades, minimal chart impact, very budget-friendly.
Best for: High-volume maker campaigns, budget-conscious runs.

Moderate Range (Recommended)

Min: 0.001 SOL
Max: 0.01 SOL
Variance: 10x (moderate)

Good variety, visible on charts, balanced cost.
Best for: Most campaigns, balanced organic appearance.

Aggressive Range (High Visibility)

Min: 0.005 SOL
Max: 0.05 SOL
Variance: 10x (moderate)

Larger trades, noticeable chart activity, higher cost.
Best for: Creating visible volume alongside makers, premium campaigns.

How Range Affects Your Budget

Expected Value Calculation

With a range, your average cost is approximately the midpoint:

Range: 0.001 - 0.01 SOL
Average trade: (0.001 + 0.01) / 2 = 0.0055 SOL

500 makers:
- Trade value: 500 × 0.0055 = 2.75 SOL (average)
- Platform fee: 500 × 0.0005 = 0.25 SOL
- PDA costs: 500 × 0.01 = 5 SOL
- Total: ~8 SOL (approximate)

Buffer Recommendation

Always fund 10-20% more than calculated average to handle variance:

Calculated need: 8 SOL
Recommended funding: 9-10 SOL

Chart Impact: Fixed vs Range

Fixed Mode Charts

│    ║    ║    ║    ║    ║
│    ║    ║    ║    ║    ║
│    ║    ║    ║    ║    ║
└────────────────────────────
     Identical candles = Obvious bot

Range Mode Charts

│    ║         ║
│    ║    ║    ║    ║
│    ║    ║    ║    ║    ║
│         ║         ║    ║
└────────────────────────────
     Varied candles = Natural appearance

Experienced traders scan charts for repeating patterns. Range mode avoids this red flag.

Combining with Timing Randomization

Jumpbit's maker bot also randomizes timing between transactions (jitter). Combined with range amounts:

Double Randomization

Transaction 1: 0.0034 SOL at T+0.0s
Transaction 2: 0.0078 SOL at T+0.3s
Transaction 3: 0.0012 SOL at T+0.7s
Transaction 4: 0.0091 SOL at T+0.9s

Both AMOUNT and TIMING vary = maximum organic appearance.

Why This Matters

Bots with fixed amounts AND fixed intervals create obvious patterns:

Same trade size
Exact same gap between trades
Repeats hundreds of times

Randomizing both breaks any detectable pattern.

Settings Cheat Sheet

Goal	Mode	Range	Rate
Quick test	Fixed	0.005 SOL	Any
Budget run	Fixed	0.001 SOL	100/min
Standard campaign	Range	0.001-0.01	200/min
Organic appearance	Range	0.002-0.02	100/min
High visibility	Range	0.01-0.05	200/min
Blending with organic	Range	0.001-0.005	50/min

Common Mistakes

Mistake 1: Using Fixed for Long Campaigns

Running 2000 makers over an hour with fixed amounts creates obvious patterns.

Fix: Use range mode for any campaign over 10-15 minutes.

Mistake 2: Range Too Narrow

Setting 0.001-0.002 SOL doesn't create meaningful variety.

Fix: Use at least 5-10x variance (e.g., 0.001-0.01).

Mistake 3: Range Too Wide

Setting 0.001-1 SOL creates unpredictable costs and wild chart swings.

Fix: Keep max at 10-20x minimum, not 100x+.

Mistake 4: Not Accounting for Range in Budget

Calculating budget on minimum amount, then running out of SOL.

Fix: Calculate on midpoint + 20% buffer.

Key Takeaways

Fixed mode = Same amount every trade, predictable but artificial-looking
Range mode = Randomized amounts, natural appearance, slightly variable cost
Use range for most campaigns - Organic appearance is worth the slight complexity
Moderate range (0.001-0.01 SOL) is optimal for most use cases
Combined with timing jitter - Double randomization = undetectable patterns
Budget for midpoint + 20% when using range mode

Next Steps

Ready to configure your maker bot?

Jumpbit Maker Bot - Supports both fixed and range modes with timing randomization

How Many Makers Do You Need to Trend on DexScreener?

JUMPBIT — Fri, 23 Jan 2026 18:01:36 +0000

Introduction

"How many makers do I need to trend?"

It's the most common question from Pump.fun devs—and the answer isn't a single number.

Trending is relative. You don't need a fixed maker count; you need more makers than your competition during the same time window.

In this guide, I'll break down the maker thresholds I've observed across different trending positions, how to benchmark against competitors, and how fast you can reach these targets.

How DexScreener Trending Works

Before talking numbers, understand the system:

Trending Score Components

DexScreener calculates a "Trending Score" for every token based on:

Trading volume
Transaction count
Unique makers (distinct trading wallets)
Holder count
Liquidity depth
Page engagement (visits, reactions)

Relative Ranking

Trending isn't about hitting a magic number—it's about outperforming other tokens in the same timeframe.

During quiet hours, 300 makers might trend.
During peak competition, 1000 makers might not.

Maker Count Benchmarks by Position

Based on analysis of DexScreener trending tokens (January 2026 data):

Pump.fun Bonding Curve - Trending Page

Position	Maker Range	Volume Range	Notes
Top 5	1,500-5,000+	100-500+ SOL	Peak competition
Top 10	800-2,000	50-200 SOL	Strong position
Top 20	400-1,000	25-100 SOL	Visible trending
Page 2	200-500	10-50 SOL	Secondary visibility
Page 3+	50-200	5-25 SOL	Low visibility

Key Thresholds

< 100 makers  → Invisible to most traders
100-200       → Minimum visibility threshold
200-400       → Competitive during low activity
400-800       → Solid trending position
800-1,500     → Strong trending (top 10-20)
1,500+        → Dominant (top 5)

Important: These numbers shift constantly based on market activity.

How to Benchmark Against Competitors

Don't guess—measure. Here's how to find your target:

Step 1: Check Current Trending Tokens

Go to DexScreener Pump.fun
Sort by trending (default view)
Note the maker count of tokens in your target position

Step 2: Calculate Your Gap

Target: Top 20 position
Current top 20 average: 650 makers
Your current count: 150 makers
Gap: 500 makers needed

Step 3: Factor in Competition Growth

Competitors aren't standing still. If they're running bots too, you need to outpace them.

Rule of thumb: Target 20-30% above current threshold to account for competition growth.

Step 4: Set Time-Based Goals

At 500 makers/minute (Jumpbit max speed):

500 makers = 1 minute
1,000 makers = 2 minutes
2,000 makers = 4 minutes

At 100 makers/minute (moderate pace):

500 makers = 5 minutes
1,000 makers = 10 minutes
2,000 makers = 20 minutes

Maker Requirements by Time of Day

Competition varies dramatically by time:

Low Competition (Best for smaller budgets)

When: 2-8 AM UTC (off-peak US hours)
Typical top 20 requirement: 300-600 makers
Strategy: Run moderate maker rate, cheaper to compete

Medium Competition

When: 8 AM - 2 PM UTC (EU peak, US morning)
Typical top 20 requirement: 500-1,000 makers
Strategy: Standard maker campaign needed

High Competition (Most expensive)

When: 2-10 PM UTC (US peak hours)
Typical top 20 requirement: 800-2,000+ makers
Strategy: Aggressive maker rate or accept lower position

Strategic Timing

If budget is limited:

Launch during low competition hours
Build maker base while competition is light
Maintain position as competition increases

Maker-to-Volume Ratio

Raw maker count isn't everything. The ratio matters:

Healthy Ratios

1 maker per 0.1-0.5 SOL volume = Natural looking
1 maker per 0.5-2 SOL volume = Acceptable
1 maker per 2-5 SOL volume = Starting to look suspicious
1 maker per 5+ SOL volume = Wash trading signal

Example Analysis

Token A:

500 makers, 100 SOL volume
Ratio: 0.2 SOL per maker ✅ Healthy

Token B:

50 makers, 100 SOL volume
Ratio: 2 SOL per maker ⚠️ Borderline

Token C:

20 makers, 100 SOL volume
Ratio: 5 SOL per maker ❌ Suspicious

Balancing Strategy

Don't just pump makers—balance with volume:

Target: 500 makers + 100 SOL volume (0.2 ratio)

Method:
- Maker bot: 500 makers (~6-8 SOL cost)
- Volume bot: Match with volume activity
- Result: Healthy-looking metrics

Speed to Trending: Time Calculations

How fast can you reach trending thresholds?

Jumpbit (500 makers/min max)

Target	Time	Est. Cost
200 makers	24 seconds	~2-3 SOL
500 makers	1 minute	~5-7 SOL
1,000 makers	2 minutes	~10-13 SOL
2,000 makers	4 minutes	~20-26 SOL

Typical Competitors (50-100 makers/min)

Target	Time	Notes
200 makers	2-4 minutes	4-10x slower
500 makers	5-10 minutes	Competition may pass you
1,000 makers	10-20 minutes	Significant time disadvantage
2,000 makers	20-40 minutes	Very slow

Why Speed Matters

Trending is real-time - Competitors are running too
Momentum compounds - Early trending = organic discovery
Attention windows are short - Miss the window, miss the pump

Minimum Viable Maker Count

If budget is tight, what's the absolute minimum?

Survival Thresholds

< 50 makers   → Won't appear in most filtered views
50-100        → May show in "all" view, not trending
100-200       → Minimum to appear credible
200-300       → Can trend during very low competition

Budget-Constrained Strategy

With only 3-5 SOL:

Target 200-300 makers
Run during off-peak hours (2-8 AM UTC)
Combine with bump bot for visibility
Focus on holder growth for credibility

Case Study: Maker Count Impact

Real scenario (anonymized):

Before Maker Bot

Position: Page 4
Makers: 67
Volume: 25 SOL
Ratio: 0.37 SOL/maker (healthy)

After Maker Bot (15 minutes later)

Position: Page 1, #12
Makers: 567 (+500)
Volume: 30 SOL (+5 SOL from maker trades)
Ratio: 0.05 SOL/maker (very healthy)

Analysis

The +500 makers (from ~6-7 SOL spend) moved the token from invisible to top 15. The volume increase was minimal, but the maker diversity signaled legitimacy.

Dynamic Targeting Strategy

Instead of fixed targets, use dynamic benchmarking:

Step 1: Check Every 30 Minutes

Monitor competitors' maker counts throughout your campaign.

Step 2: Maintain Gap

Stay 20-30% above the #20 position threshold.

Step 3: Burst When Needed

If competitor surges, have maker bot ready to respond.

Step 4: Sustain Don't Spike

After reaching target, maintain 50-100 makers/hour to hold position.

Common Mistakes

Mistake 1: Targeting Fixed Numbers

"I need exactly 1000 makers" ignores competition reality.

Fix: Benchmark against current trending tokens, not arbitrary numbers.

Mistake 2: Ignoring Time of Day

Running during peak hours with a small budget = wasted SOL.

Fix: Launch during off-peak for cheaper competition.

Mistake 3: All Makers, No Volume

500 makers with 5 SOL volume looks fake.

Fix: Balance maker growth with volume bot.

Mistake 4: One-Time Push

Reaching 500 makers, then stopping = competitors catch up.

Fix: Continuous maintenance at lower rate (20-50/min).

Quick Reference: Maker Targets

Goal	Maker Target	Budget Est.	Time (500/min)
Minimum visibility	200	~2-3 SOL	24 sec
Low competition trending	400	~4-6 SOL	48 sec
Average competition	700	~7-10 SOL	1.4 min
High competition	1,200	~12-16 SOL	2.4 min
Dominant position	2,000+	~20-26 SOL	4 min

Costs vary based on PDA creation and trade amounts

Key Takeaways

Trending is relative - You need more makers than competitors, not a fixed number
Benchmark constantly - Check current trending tokens before setting targets
Time of day matters - Off-peak = cheaper to compete
Balance maker-to-volume ratio - Makers alone look suspicious without volume
Speed matters - Faster maker generation = first to trending
Maintain, don't spike - Continuous low-rate after initial push

Next Steps

Ready to hit your maker targets?

Jumpbit Maker Bot - 500 makers/min, reach any target in minutes

How to Increase Unique Makers on Pump.fun: 5 Proven Methods

JUMPBIT — Fri, 23 Jan 2026 17:54:18 +0000

Introduction

Your Pump.fun token has 47 unique makers. The token above you on DexScreener has 600.

You're running volume bot. They're running maker bot.

Same effort. Different results.

In this guide, I'll show you 5 proven methods to increase your unique maker count—from organic strategies to automated tools—and explain when to use each approach.

Why Unique Makers Matter (Quick Recap)

Before diving into methods, here's why maker count matters:

DexScreener Trending Score weights unique makers as a key factor
Trader Trust - Low maker count looks like wash trading
Algorithm Signals - High maker diversity = organic appearance
Visibility Thresholds - Many traders filter out tokens with <100 makers

For a deep dive, see Why Unique Makers Matter for DexScreener Rankings.

Method 1: Maker Bot (Fastest)

Speed: Up to 500 makers/minute
Cost: ~0.005-0.013 SOL per maker
Best for: Rapid maker growth, competitive trending

How It Works

A maker bot automates the process of:

Creating fresh Solana wallets
Funding each wallet with SOL
Executing a buy transaction
Executing a sell transaction
Repeating with new wallets

Each wallet becomes a unique maker on-chain.

When to Use Maker Bot

✅ You need 500+ makers quickly
✅ Competing for DexScreener trending
✅ Your maker-to-volume ratio looks suspicious
✅ You have budget (~5-15 SOL for 500-1000 makers)

Setup Steps

Connect wallet to Jumpbit Maker Bot
Enter your token's mint address
Choose trade amount (fixed or range)
Set maker rate (up to 500/min)
Set duration
Deploy and monitor dashboard

Pro Tips

Use range mode (e.g., 0.001-0.01 SOL) for natural variation
Start at 100-200/min for organic-looking growth
Run alongside volume bot for balanced metrics
Don't burst all at once - spread over 10-30 minutes

Method 2: Holder Bot (Two Birds, One Stone)

Speed: Up to 500 holders/minute
Cost: ~0.007 SOL per holder
Best for: Growing BOTH makers AND holders

How It Works

Here's what many don't realize: Holder bots also increase maker count.

When a wallet buys your token:

It becomes a holder (owns tokens)
It becomes a maker (executed a trade)

One action, two metrics boosted.

When to Use Holder Bot for Makers

✅ You need both holder AND maker growth
✅ Budget is limited (better value per SOL)
✅ Pump.fun credibility is also important
✅ You want permanent holders, not just activity

Maker Bot vs Holder Bot for Makers

Aspect	Maker Bot	Holder Bot
Maker increase	+1 per cycle	+1 per cycle
Holder increase	0 (sells back)	+1 (keeps tokens)
Cost per maker	~0.005-0.013 SOL	~0.007 SOL
Best for	Pure maker growth	Maker + holder growth

Verdict: If you need ONLY makers, use maker bot. If you need BOTH, holder bot gives more value.

Method 3: Coordinated Community Buying

Speed: Variable (depends on community size)
Cost: Coordination effort
Best for: Organic-looking growth with real wallets

How It Works

Organize your community to:

Each person uses their own wallet
Everyone buys at scheduled time
Some hold, some trade—both count as makers

Execution Strategy

Example: 50-person coordinated buy

Time 0:00 - Group A (15 people) buys
Time 0:05 - Group B (15 people) buys
Time 0:10 - Group C (20 people) buys

Result: 50 new unique makers in 10 minutes

Pros and Cons

Pros:

100% organic wallets
Real community engagement
No bot detection risk
Free (no tool costs)

Cons:

Limited scale (need actual people)
Coordination overhead
Unpredictable execution
Can't repeat at will

Best Used For

Launch events
Milestone celebrations
Combining with bot activity for authenticity
Building genuine community metrics

Method 4: Influencer/KOL Campaigns

Speed: Variable (hours to days)
Cost: Influencer fees ($50-$5000+)
Best for: Organic makers + broader awareness

How It Works

When an influencer promotes your token:

Their followers buy (new makers)
Buys come from diverse, real wallets
Side benefit: awareness, holders, volume

Finding the Right Influencers

Look for:

Solana/Pump.fun focused accounts
Engaged followers (not just follower count)
Previous successful calls
Reasonable pricing

Expected Maker Impact

Influencer Size	Typical New Makers
Micro (1-10K followers)	10-50
Mid (10-50K followers)	50-200
Large (50K+ followers)	200-1000+

Combine with Bots

Smart strategy: Run maker bot BEFORE influencer post.

Why? When influencer's followers check DexScreener, they see healthy maker count already. Social proof compounds.

Method 5: Airdrop to Active Traders

Speed: Depends on claim rate
Cost: Token allocation + gas
Best for: Attracting active wallets

How It Works

Identify active Solana traders (via on-chain data)
Airdrop small token amounts
When they sell (or buy more), they become makers

Finding Active Wallets

Sources:

Recent Pump.fun traders
DexScreener active pairs
Birdeye volume leaders
Public airdrop tools

Conversion Rate

Not everyone will interact:

Typical claim rate: 10-30%
Typical trade rate: 5-15%

Airdrop to 1000 wallets → ~50-150 new makers

Pros and Cons

Pros:

Attracts real, active traders
Can create ongoing trading activity
Builds initial distribution

Cons:

Low conversion rate
Requires token allocation
Complex execution
May attract dumpers

Optimal Strategy: Stack Multiple Methods

The most successful Pump.fun tokens don't rely on one method—they stack:

Launch Day Strategy

Hour 0-1: Maker Bot (500 makers)
Hour 1-2: Holder Bot (300 holders/makers)
Hour 2-4: Influencer posts go live
Hour 4+:  Organic growth + maintenance bot runs

Ongoing Maintenance

Daily: Maker bot at 50-100/hour during peak times
Weekly: Coordinated community events
Monthly: Influencer refreshes

Budget Allocation Example (20 SOL)

Method	Allocation	Expected Makers
Maker Bot	10 SOL	~700-800
Holder Bot	5 SOL	~700 (also holders)
Influencer	5 SOL	~100-300
Total	20 SOL	~1500-1900

Common Mistakes When Growing Makers

Mistake 1: Only Running Volume Bot

Volume bot reuses same wallet. Your volume grows but maker count stays flat.

Fix: Add maker bot specifically for unique wallet growth.

Mistake 2: Bursting All Makers at Once

1000 makers in 2 minutes looks unnatural. May trigger algorithm skepticism.

Fix: Spread maker generation over 15-60 minutes at 100-200/min.

Mistake 3: Ignoring Maker-to-Volume Ratio

High makers + low volume looks weird. Low makers + high volume looks like wash trading.

Fix: Balance both metrics. Run volume bot alongside maker bot.

Mistake 4: Stopping After Initial Push

Maker count plateaus. Competitors catch up. Ranking drops.

Fix: Continuous low-rate maker generation (20-50/min) for maintenance.

Mistake 5: Not Tracking Results

Running bots blindly without checking DexScreener impact.

Fix: Monitor DexScreener maker count before/after. Adjust strategy based on results.

How to Track Your Maker Growth

DexScreener

Go to dexscreener.com
Search your token
Check "Makers" column
Note: Updates every few minutes, not real-time

Solscan

Go to solscan.io
Enter token address
View "Holders" and recent transactions
Each unique trading wallet = maker

Birdeye

Go to birdeye.so
Search token
Check "Traders" analytics
Shows unique wallet activity over time

Key Takeaways

Maker bot is fastest - 500 makers/minute, ~0.005-0.013 SOL each
Holder bot gives double value - +1 maker AND +1 holder per buy
Organic methods work but don't scale - Community buys, influencers
Stack multiple methods - Best results come from combining approaches
Spread over time - Don't burst; gradual growth looks more natural
Balance with volume - Maker-to-volume ratio matters for credibility

Next Steps

Ready to grow your unique maker count?

Jumpbit Maker Bot - 500 makers/min, 0.0005 SOL platform fee

Jumpbit Holder Bot - Grow makers AND holders simultaneously

Maker Count vs Holder Count: What's the Difference?

JUMPBIT — Fri, 23 Jan 2026 17:15:52 +0000

Introduction

You're launching a Pump.fun token and everyone says "you need more holders" and "you need more makers."

But what's the difference? Aren't they the same thing?

No. And confusing them will waste your SOL.

In this guide, I'll explain the exact difference between maker count and holder count, when each metric matters, and which bot you actually need for your situation.

What is Maker Count?

Maker count represents the number of unique wallet addresses that have traded your token.

A wallet becomes a "maker" when it executes a swap—either buying or selling. The same wallet trading 50 times still counts as 1 maker.

Key characteristics:

Measures trading activity breadth
Wallet can buy AND sell (still 1 maker)
Doesn't require holding tokens
Tracked on DexScreener "Makers" column

Example:

Wallet A buys → sells → 1 maker
Wallet B buys → holds → 1 maker
Wallet C sells airdrop → 1 maker
Total makers: 3

What is Holder Count?

Holder count represents the number of unique wallet addresses currently holding your token.

A wallet is a "holder" if it has a non-zero token balance right now. If it sells everything, it's no longer a holder.

Key characteristics:

Measures ownership distribution
Wallet must currently hold tokens
Real-time snapshot (changes with every sell)
Tracked on DexScreener "Holders" column, Pump.fun UI

Example:

Wallet A holds 1,000 tokens → 1 holder
Wallet B holds 100 tokens → 1 holder
Wallet C sold everything → 0 holders
Total holders: 2

Side-by-Side Comparison

Aspect	Maker Count	Holder Count
Definition	Unique wallets that traded	Unique wallets currently holding
Action required	Buy OR sell	Buy and keep
Permanence	Permanent (once a maker, always counted)	Temporary (lost when wallet sells)
What it signals	Trading interest, market activity	Community size, long-term interest
Primary platform	DexScreener trending	Pump.fun, trust signals
Bot type	Maker bot (buy + sell)	Holder bot (buy only)

How Each Metric Affects Rankings

Maker Count → DexScreener Trending Score

DexScreener's algorithm weighs unique makers as a signal of organic trading activity. High maker count suggests:

Many different people are interested
Trading isn't concentrated in few wallets
Market has genuine breadth

Impact: Direct influence on DexScreener trending position.

Holder Count → Trust & Credibility

Holder count signals community strength. High holder count suggests:

People want to own the token long-term
Distribution is healthy (not concentrated)
Less likely to be a quick pump-and-dump

Impact: Influences trader psychology, Pump.fun visibility, and analyst ratings.

When Maker Count Matters More

Focus on makers when:

1. You Want DexScreener Trending

DexScreener explicitly weighs unique makers. If trending is your goal, makers are essential.

2. Your Volume-to-Maker Ratio is Off

High volume + low makers looks like wash trading. Adding makers legitimizes your volume.

3. Competing Against High-Maker Tokens

If top trending tokens have 1,000+ makers and you have 100, you won't outrank them regardless of volume.

4. You Want Activity Without Holding Pressure

Maker bots buy and sell, so tokens cycle back. No permanent buy pressure or holder dilution.

When Holder Count Matters More

Focus on holders when:

1. You're Building Community Trust

Traders check holder count before buying. 500+ holders signals "real community."

2. You're on Pump.fun King of the Hill

Pump.fun's leaderboard factors holder count. Low holders = lower ranking.

3. You Want Distribution Score

Analytics platforms flag concentrated holdings. More holders = better distribution.

4. You're Preparing for Graduation

Post-bonding-curve tokens need strong holder bases for sustained interest.

The Overlap: One Wallet Can Be Both

Here's what confuses people:

A wallet that buys and holds is counted as:

1 maker (it traded)
1 holder (it currently holds)

A wallet that buys then sells is counted as:

1 maker (it traded)
0 holders (it sold everything)

This is why holder bots and maker bots produce different results:

Bot Type	Wallet Action	Maker Count	Holder Count
Holder Bot	Buy only	+1	+1
Maker Bot	Buy + Sell	+1	0
Volume Bot	Repeat trades	+0 (same wallet)	+0 or +1

Which Bot Do You Need?

Scenario 1: "I need DexScreener trending"

Use: Maker Bot (primary) + Volume Bot (secondary)

DexScreener weights unique makers. Maker bot generates fresh wallets that trade. Volume bot adds trading volume to support the maker count.

Scenario 2: "I need Pump.fun credibility"

Use: Holder Bot (primary) + Bump Bot (secondary)

Traders on Pump.fun check holder count. Holder bot creates permanent holders. Bump bot keeps you visible on front page.

Scenario 3: "I want both trending + credibility"

Use: All bots strategically

Start with Bump Bot (visibility)
Add Holder Bot (credibility)
Add Maker Bot (DexScreener ranking)
Add Volume Bot (healthy charts)

Scenario 4: "I have limited budget"

Priority order:

Bump Bot - Get visible first
Holder Bot - Build credibility (most trust impact per SOL)
Maker Bot - DexScreener ranking
Volume Bot - If budget remains

Cost Comparison

Bot Type	Cost Per Unit	What You Get
Maker Bot	~0.005-0.013 SOL/maker	+1 unique maker (DexScreener)
Holder Bot	~0.007 SOL/holder	+1 unique holder + +1 maker
Volume Bot	~0.0005 SOL/txn	+Volume (no new makers/holders)
Bump Bot	~0.0005 SOL/bump	+Activity, front page visibility

Note: Holder bots give you BOTH a holder and a maker (since buying counts as trading). Maker bots only give makers (since they sell).

The Optimal Strategy: Stack Both Metrics

Top Pump.fun tokens don't choose between makers and holders—they grow both:

Phase 1: Launch (First 30 minutes)

Bump Bot at 300-500 BPM → Front page visibility
Holder Bot at 100-200 HPM → Build initial credibility

Phase 2: Growth (30 minutes - 2 hours)

Continue Bump Bot (maintain visibility)
Maker Bot at 200-500 MPM → DexScreener ranking
Volume Bot → Support healthy charts

Phase 3: Maintenance (Ongoing)

Reduce all bots to sustainable rates
Focus on organic community growth
Use bots to maintain competitive metrics

Common Mistakes

Mistake 1: Only Running Holder Bot

You get holders but low unique maker count. DexScreener ranking suffers.

Fix: Add maker bot for DexScreener trending.

Mistake 2: Only Running Maker Bot

You get makers but low holder count. Traders see "no community."

Fix: Add holder bot for credibility.

Mistake 3: Confusing Volume Bot for Maker Bot

Volume bot reuses same wallet. Maker count stays flat.

Fix: Use maker bot specifically for unique maker growth.

Mistake 4: Running Everything at Once Day 1

Budget drains fast, metrics spike unnaturally.

Fix: Phase your approach. Visibility → credibility → ranking → volume.

Key Takeaways

Maker count = unique wallets that traded (includes buyers AND sellers)
Holder count = unique wallets currently holding (only active balances)
Maker bots do buy + sell (increases makers, not holders)
Holder bots do buy only (increases BOTH makers and holders)
DexScreener trending needs makers - Volume alone won't rank you
Pump.fun credibility needs holders - Makers alone won't build trust
Optimal strategy uses both - Stack metrics for maximum impact

Next Steps

Need to grow both metrics? Here's where to start:

Jumpbit Maker Bot - 500 makers/minute for DexScreener ranking

Jumpbit Holder Bot - 500 holders/minute for community credibility

Why Unique Makers Matter for DexScreener Rankings

JUMPBIT — Fri, 23 Jan 2026 17:08:53 +0000

Introduction

You've pumped 50 SOL of volume into your Pump.fun token. Your chart looks healthy. But you're stuck on page 3 of DexScreener while tokens with less volume sit on the trending page.

What's the difference?

Check their unique makers count. They have 800. You have 47.

In this guide, I'll break down exactly why unique makers matter for DexScreener rankings, how the algorithm weighs this metric, and what maker thresholds you need to hit for trending positions.

What Are "Unique Makers" on DexScreener?

Unique makers represent the number of distinct wallet addresses that have traded a token. On DexScreener, this appears as the "Makers" column in token listings.

Key distinction:

Volume = Total SOL value traded
Transactions = Number of individual trades
Makers = Number of unique wallets that traded

A single wallet trading 100 times adds 100 transactions and volume—but only 1 maker.

100 different wallets trading once each adds 100 transactions AND 100 makers.

DexScreener tracks this separately because it signals something volume alone cannot: market breadth.

How DexScreener's Trending Algorithm Works

DexScreener assigns every token a Trending Score based on multiple weighted factors. While the exact formula is proprietary, analysis of trending tokens reveals the key inputs:

Primary Ranking Factors

Factor	Weight	What It Measures
Trading Volume	High	Total SOL/USD traded
Unique Makers	High	Distinct trading wallets
Transaction Velocity	Medium	Trades per time period
Holder Count	Medium	Unique holding wallets
Liquidity Depth	Medium	Pool size
Page Engagement	Low	Clicks, reactions

Why Makers Matter More Than You Think

Volume can be faked cheaply with wash trading—one wallet buying and selling repeatedly. DexScreener's algorithm knows this.

Unique makers are harder to fake because each new maker requires:

A fresh wallet address
PDA creation costs (~0.004-0.012 SOL)
Separate transaction fees

This makes maker count a more reliable signal of genuine market interest than raw volume.

The Math Behind DexScreener Rankings

Let's compare two tokens:

Token A:

Volume: 100 SOL
Makers: 50
Volume per Maker: 2 SOL

Token B:

Volume: 100 SOL
Makers: 500
Volume per Maker: 0.2 SOL

Same volume. But Token B's activity comes from 10x more unique wallets—suggesting broader market participation.

DexScreener interprets this as:

Token B has more organic interest
Token B has better distribution of traders
Token B is less likely to be wash-traded

Result: Token B ranks higher despite identical volume.

Maker Count Benchmarks for Trending

Based on analysis of DexScreener trending tokens (January 2026 data):

Pump.fun Bonding Curve Tokens

Position	Typical Maker Count	Volume Range
Page 1 (Top 20)	800-3,000+	50-500 SOL
Page 2-3	300-800	20-100 SOL
Page 4-5	100-300	10-50 SOL
Below Page 5	<100	<20 SOL

Key Thresholds

100 makers - Minimum visibility threshold
300 makers - Competitive for trending
500 makers - Strong trending position
1,000+ makers - Top trending territory

Important: These numbers shift based on market competition. Check current trending tokens for real-time benchmarks.

Why Low Maker Count Kills Your Ranking

Even with strong volume, low maker count signals red flags:

1. Wash Trading Suspicion

High volume + low makers = same wallets trading repeatedly. DexScreener's algorithm deprioritizes this pattern.

2. Whale Concentration

Few makers suggests a small group controls trading. This signals instability and risk.

3. Bot Activity Detection

Repetitive patterns from few wallets are easier for algorithms to identify and discount.

4. Poor User Trust

Traders manually check maker count before buying. Low numbers = "this looks manipulated."

How Maker Count Affects Other Metrics

Unique makers don't exist in isolation—they influence your entire DexScreener profile:

Maker-to-Volume Ratio

Healthy ratio: 1 maker per 0.1-1 SOL volume
Suspicious ratio: 1 maker per 5+ SOL volume

Tokens with healthy ratios get algorithmic boosts.

Maker Growth Velocity

DexScreener tracks how fast your maker count grows. Sudden spikes followed by flatlines look artificial. Steady growth signals organic interest.

Maker Distribution Over Time

Are makers spread across hours/days, or concentrated in minutes? Natural distribution patterns rank better.

Maker Count vs Holder Count: Both Matter

Common question: "Should I focus on makers or holders?"

Answer: Both, for different reasons.

Metric	What It Signals	DexScreener Impact
Makers	Trading activity, market interest	Trending score
Holders	Community size, long-term interest	Trust signal

Makers show your token is actively traded.
Holders show people want to keep it.

A token with 1,000 makers but 50 holders looks like pure speculation.
A token with 50 makers but 1,000 holders looks stagnant.

The winning combination: high makers AND high holders.

How to Increase Unique Makers

Method 1: Organic Growth

Community trading
Influencer mentions
Viral marketing

Pros: Authentic, sustainable
Cons: Slow, unpredictable

Method 2: Maker Bot

Maker bots automate fresh wallet creation and trading.

Pros: Fast (up to 500 makers/minute), predictable, controllable
Cons: Costs SOL (~0.005-0.013 per maker)

Method 3: Coordinated Buying

Organize community members to trade from unique wallets.

Pros: Semi-organic
Cons: Coordination overhead, limited scale

For most Pump.fun launches, maker bots provide the fastest path to competitive maker counts.

Common Mistakes That Tank Your Maker Count

Mistake 1: Only Running Volume Bot

Volume bots reuse the same wallet. You get volume but zero new makers. Your maker count stays flat while competitors grow.

Fix: Add maker bot to generate unique wallets.

Mistake 2: Running Maker Bot Too Fast

500 makers in 30 seconds looks unnatural. DexScreener may discount sudden spikes.

Fix: Spread maker generation over time. 100-200/minute looks more organic.

Mistake 3: Ignoring Maker-to-Volume Ratio

1,000 makers with 10 SOL volume looks fake. The ratio is off.

Fix: Match maker growth with proportional volume. Run volume bot alongside maker bot.

Mistake 4: Stopping After Initial Push

Makers plateau, competitors catch up, ranking drops.

Fix: Continuous maker generation at lower rates (20-50/min) maintains momentum.

DexScreener Maker Tracking: What Gets Counted

DexScreener reads on-chain data directly. Here's what counts as a maker:

Counted as Maker:

Any wallet that executes a swap (buy or sell)
Bot-generated wallets that trade
Wallets that trade and exit

NOT Counted:

Wallets that only receive tokens (transfers)
Wallets on allowlists without trading
LP provision (different metric)

Every unique address that interacts with the trading pool = 1 maker.

Real Example: Maker Count Impact

Let's examine a real scenario (anonymized):

Token X - Launch Day:

Volume: 30 SOL
Makers: 45
Ranking: Page 4

Token X - After Maker Bot (2 hours later):

Volume: 35 SOL (+5 SOL)
Makers: 450 (+405)
Ranking: Page 1, position #8

The modest volume increase didn't move the needle. The maker increase pushed it to trending.

Key Takeaways

Unique makers = distinct wallets that traded - not transaction count
DexScreener weighs makers heavily in trending algorithm
Same volume, more makers = higher ranking - breadth matters
100-300 makers minimum for visibility, 500+ for competitive trending
Maker-to-volume ratio matters - avoid suspicious patterns
Combine makers + holders + volume for maximum ranking impact
Maker bots are the fastest method to scale unique maker count

Next Steps

Ready to boost your DexScreener ranking with more unique makers?

Try Jumpbit Maker Bot - 500 makers/minute, 0.0005 SOL platform fee, live dashboard.

What is a Pump.fun Maker Bot? Complete Guide to Unique Makers

JUMPBIT — Fri, 23 Jan 2026 17:04:22 +0000

Introduction

Your Pump.fun token has volume. It has bumps. But DexScreener shows only 23 unique makers—while trending tokens show 500, 1,000, even 3,000+.

What are "makers" and why does everyone have more than you?

The answer: Maker Bots.

In this guide, I'll explain exactly what a maker bot is, how it differs from holder and volume bots, what it costs, and when you should use one to boost your DexScreener trending score.

What is a Maker Bot?

A maker bot is an automated tool that increases your token's unique maker count by executing buy and sell transactions from multiple fresh wallet addresses.

Each transaction cycle creates a new "maker"—a unique wallet that has traded your token. Platforms like DexScreener, Pump.fun, and Birdeye track unique makers as a signal of organic trading activity.

Simple explanation:

You configure the bot with your token's mint address
The bot generates fresh Solana wallets
Each wallet executes a buy → then a sell
Each wallet = 1 new unique maker on-chain
Your maker count grows automatically

Unlike holder bots (which buy and hold), maker bots complete the full trading cycle. The wallet buys, then sells—simulating real trading activity from a unique address.

How Does a Maker Bot Work? (Technical Breakdown)

Let's look at what happens when a maker bot adds one new maker to your Pump.fun token:

Step 1: Wallet Generation

The bot generates a fresh Solana keypair—a brand new wallet address that has never interacted with your token.

Step 2: Funding

A small amount of SOL is transferred to the new wallet to cover:

The trade amount (buy + sell)
Transaction gas fees
PDA creation costs

Step 3: PDA Creation

For each new maker on Pump.fun's bonding curve, two Program Derived Accounts (PDAs) must be created:

PDA Type	Purpose	Rent Cost
Token Account	Temporarily holds purchased tokens	~0.002 SOL
UserVolumeAccumulator	Tracks wallet's trading volume	~0.002 SOL

Total PDA cost: ~0.004-0.012 SOL per maker (depending on existing accounts)

Step 4: Buy Transaction

The bot executes a buy on Pump.fun's bonding curve. The wallet now holds tokens.

Step 5: Sell Transaction

Immediately after (or with randomized delay), the bot sells the tokens back. The wallet has now completed a full trade cycle.

Step 6: Maker Registered

The wallet is now counted as a unique maker—a distinct address that traded the token.

Step 7: Repeat

The bot repeats this process at your configured rate (e.g., 100 makers/minute, 500 makers/minute).

What Does a Maker Bot Actually Cost?

Let's break down the real cost per maker on Pump.fun:

PDA Creation (2 accounts):     ~0.004-0.012 SOL
Trade Amount:                  ~0.0001 SOL (configurable, recycles)
Pump.fun Fees (buy + sell):    ~0.00002 SOL
Transaction Gas (2 txns):      ~0.00002 SOL
Platform Fee:                  ~0.0005 SOL
─────────────────────────────────────────────────
TOTAL PER MAKER:               ~0.005-0.013 SOL

Cost examples (at ~0.013 SOL/maker):

100 makers: ~1.3 SOL
500 makers: ~6.5 SOL
1,000 makers: ~13 SOL

The trade amount is configurable and mostly recycles back (minus fees). You can use tiny amounts (0.0001 SOL) for budget campaigns or larger amounts (0.001+ SOL) for more visible trading activity.

Maker Bot vs Holder Bot vs Volume Bot

This is where most people get confused. Here's the clear distinction:

Feature	Maker Bot	Holder Bot	Volume Bot
Action	Buy + Sell	Buy only	Buy + Sell
Wallets	Fresh wallet each time	Fresh wallet each time	Same wallet repeats
Result	+1 unique maker	+1 unique holder	+Volume (same wallet)
Wallet fate	Used once	Holds tokens forever	Reused continuously
Primary metric	Unique traders count	Holder count	Trading volume
DexScreener impact	Makers column	Holders column	Volume column

Key insight:

Maker Bot = Many wallets, each trades once → increases unique traders
Volume Bot = One wallet trades many times → increases volume but not unique traders
Holder Bot = Many wallets, each buys once and holds → increases holders

For maximum DexScreener ranking impact, you need all three metrics: volume, holders, AND unique makers.

Why Do Unique Makers Matter?

DexScreener's trending algorithm weighs multiple factors:

Trading Volume - Total SOL traded
Transaction Count - Number of trades
Unique Makers - Distinct wallets trading
Holder Count - Wallets holding tokens
Liquidity - Pool depth

Unique makers signal organic interest. A token with 100 SOL volume from 5 wallets looks suspicious. The same volume from 500 unique wallets looks like genuine market activity.

DexScreener specifically displays "Makers" as a visible metric—traders check this before buying.

When Should You Use a Maker Bot?

Good Use Cases:

1. Boosting DexScreener Trending Score
DexScreener weights unique makers heavily. If your maker count is low relative to competitors, you won't trend regardless of volume.

2. After Establishing Volume
Don't run maker bot on a zero-volume token. Build volume first with volume bot, then add unique makers for credibility.

3. Competing for Top Trending Positions
Top DexScreener tokens show 1,000-5,000+ unique makers. At 500 MPM (makers per minute), you can compete in minutes.

4. Creating Natural-Looking Activity
Maker bots with randomized trade amounts create chart patterns that look organic—varied transaction sizes from many wallets.

When NOT to Use:

1. Before You Have Visibility
Build volume and get on front page first. Makers without visibility waste SOL.

2. As a Substitute for Holders
Maker bots don't increase holder count. You need holder bot for that metric.

3. After Bonding Curve Graduation
Pump.fun maker bots only work on the bonding curve. After migration to Raydium/Pump.fun AMM, you need different tools.

Maker Bot Speed Comparison

Bot Service	Max Speed	Time for 1000 Makers
Manual trading	1-5 MPM	3-16 hours
Basic Telegram bots	20-50 MPM	20-50 minutes
Smithii	50-100 MPM	10-20 minutes
Jumpbit	500 MPM	2 minutes

Speed matters because DexScreener updates in near real-time. Faster maker generation = faster ranking improvements.

How to Set Up a Maker Bot (No-Code)

Modern maker bots don't require coding. Here's the typical setup with Jumpbit:

Connect Wallet - Link your Solana wallet (Phantom, Solflare, etc.)
Enter Token Mint - Paste your token's contract address
Configure Trade Amount - Fixed or random range (e.g., 0.0001-0.001 SOL)
Set Maker Rate - Makers per minute (up to 500 MPM)
Set Duration - How long to run
Deploy - Confirm and monitor live dashboard

The bot handles wallet generation, funding, and trade execution automatically.

Fixed vs Range Trade Amounts

Most maker bots offer two modes:

Fixed Amount:

Every trade uses the same SOL amount
Predictable cost per maker
Less natural-looking on charts

Range Amount:

Trades use random amounts within your range (e.g., 0.0001-0.001 SOL)
More organic-looking transaction patterns
Variable cost per maker

Range mode is recommended for creating natural chart activity.

Common Maker Bot Questions

Q: Will DexScreener count bot-generated makers?
Yes. DexScreener reads on-chain data. Every unique wallet that trades counts as a maker.

Q: Can I run maker bot and holder bot together?
Yes. Maker bot increases unique traders, holder bot increases holder count. Both metrics matter.

Q: What happens after graduation from Pump.fun?
The maker bot pauses. You'll need AMM-compatible tools for Raydium/Pump.fun AMM pools.

Q: Is maker bot the same as volume bot?
No. Volume bot uses the same wallet repeatedly (more volume, same maker count). Maker bot uses fresh wallets (more unique makers).

Key Takeaways

Maker bots increase unique trader count by executing buy+sell from fresh wallets
Different from holder bots - makers trade and exit, holders buy and keep
Different from volume bots - makers use unique wallets, volume bots reuse wallets
Real cost is ~0.005-0.013 SOL/maker due to PDA creation
Speed varies widely - from 20 MPM to 500 MPM
DexScreener weights unique makers in trending algorithm

Next Steps

Ready to increase your unique maker count?

Try Jumpbit Maker Bot - Generate up to 500 unique makers per minute with 0.0005 SOL platform fee.