Tokenomics & Fee Usage
How FoxTrace Token Fees Power the Engine
FoxTrace is compute and data intensive. Fees are used to fund API credits, indexing, and infrastructure so scans stay fast, reliable, and available when you need them.
⚡
What will fees be used for
Deep scans can fan out across thousands of nodes and transaction pages. That means real API usage, not just UI. Fees keep the analysis engine online and scalable.
⛽
API Credits
Primary Cost
Indexing and transfer history queries require paid credits on high-speed providers.
🧠
Compute & Indexing
Heavy Workloads
Aggregation, graph traversal, caching, and path reconstruction.
🛡️
Reliability
Always-On
Rate limits, retries, and redundancy to prevent timeouts during peak usage.
🔥
Buybacks / Burns / Trending Bots
Advertising
Some fees will go toward buybacks, burns, and getting trending on various platforms.
Fee Allocation
A transparent breakdown of where fees go.
API Credits (Indexing / History)
50%
Funds high-speed data providers so scans return quickly and consistently.
Infrastructure (Servers / WebSockets)
20%
Keeps the platform online, responsive, and able to handle high concurrency.
Development & Security
10%
Continuous improvements, bug fixes, and hardening against abuse.
Buybacks / Burns / Dex / Trending Bots
20%
Buybacks are secondary to funding the API credits required to keep FoxTrace running.
Tip: When using the Deep Scan, keep the number of hops below 5.
How Fees Are Used During Scans
FoxTrace fees map directly to what you run. Lightweight scans cost less. Deep scans cost more because they hit more endpoints and traverse larger graphs.
Direct Scan
Light
- ✓Single wallet transfer history
- ✓Aggregated by counterparty
- ✓Direction + threshold + lookback filters
Best for quick funding checks and flow summaries.
Deep Hop Scan
Intensive
- ✓Multi-hop traversal (BFS graph search)
- ✓Edges per wallet + tx pages per wallet
- ✓Max nodes safety cap (prevents runaway scans)
Best for finding indirect links and hidden bridges.
Large Wallet Indexing
Heavy
- ✓High-volume transfer parsing
- ✓Caching + dedupe + retry logic
- ✓Performance safeguards for stability
Best for whales, exchanges, and high-activity wallets.
Fair Use and Abuse Protection
Limits exist to keep the platform healthy for everyone and prevent expensive runaway traversals.
Max Nodes Safety Cap
Hard limit on how many wallet nodes a deep scan can visit.
Edges per Wallet
Controls network expansion so scans stay focused and fast.
Transaction Pages per Wallet
Limits how much history is pulled per node to manage API usage.
Lookback Windows
Reduces noise, increases relevance, and lowers scan cost.
Tokenomics FAQ
Quick answers about why fees exist and how they are used.
Ready to run a trace?
Start with a Direct Scan, then go deeper only when you need to.
