$ZIRC Tokenomics

The economic design behind the first AI terminal for BSC.

This page is for investors, DAO voters, and BSC degens who want to understand how $ZIRC powers BSC intelligence. Dive into the token mechanics, governance, and future of the zIRC protocol.

Why $ZIRC?

zIRC needed its own token to align incentives across users, developers, and the BSC ecosystem. $ZIRC enables a sustainable model where users pay for premium queries, developers earn from API usage, and the community governs feature development. Every mechanic—from staking to governance—prioritizes user value and protocol sustainability. The goal: a protocol where value flows to those who query, analyze, and build on BSC data.

• Query-to-earn: Rewards active users and data contributors
• Sustainable model: Revenue from Pro tier funds development
• Open ecosystem: Developers can build on zIRC APIs

• Total supply cap: 1,000,000,000 $ZIRC
• Inflation: None (fixed supply)
• Burn logic: Protocol-level burns on spam/abuse, future DAO proposals

What can you do with $ZIRC?

• Stake $ZIRC to unlock unlimited BSC queries (no daily limits)
• Access premium BSC data: whale tracking, advanced analytics, custom alerts
• Use developer APIs to build BSC analytics tools and integrations
• Vote on protocol upgrades, feature priorities, and treasury allocation
• Earn protocol revenue share from Pro subscriptions (5-15% based on stake)
• Future: Multi-chain expansion (Ethereum, Arbitrum, Base)

How does governance work?

• Voting: 1 token = 1 vote (with future quadratic/rep-based options)
• Delegation: Token holders can delegate votes to trusted community members
• Proposal lifecycle: Idea → Discussion → Vote → On-chain execution
• DAO treasury: Managed by token holder votes, funds protocol growth and grants
• Examples: Protocol upgrades, feature launches, grant approvals, treasury spend

Keeping it fair

• No bot farming: Airdrops based on real terminal usage, not wallet activity
• Query-to-earn: Rewards genuine users who contribute to data quality
• Anti-spam: Rate limits prevent query abuse and bot manipulation
• Future: Proof-of-query validation for advanced features