Role of $STRIKE vs $HUB

🧠 Two Tokens, Two Tracks — One Unified Ecosystem

StrikeBit uses a dual-token model to optimize scalability and clarity between protocol ownership and operational liquidity. Both tokens are essential — but they serve distinct purposes across two deployment flows:

• $STRIKE → Native agents launched directly on StrikeBit

• $HUB → Migrated agents and liquidity layers (e.g. from Virtuals)

This architecture ensures a sustainable economic model while aligning incentives across new builders, migrating projects, and active users.

---

🔑 Role of $STRIKE

$STRIKE is the core protocol and governance token. It governs StrikeBit’s native ecosystem and supports value accrual from marketplace activity, agent deployment, and staking infrastructure.

🔹 Key Functions:

• Governance over protocol-level decisions

• Native agent deployment (built directly within StrikeBit’s MAP)

• Staking via $rSTRIKE earned from Radiant AI Miners

• Treasury control, proposal voting, emissions management

• Alignment with long-term protocol health and TGE structure

---

🔵 Role of $HUB

$HUB is the agent-native utility token, used as the gas layer for migrated agents (e.g. from Virtuals) and agent-level operations such as mining, upgrading, and fusions.

🔹 Key Functions:

• Migrated agent deployment (via AgentHub)

• Virtual hashrate boosting for Radiant AI Miners

• Fusion, skin upgrades, modular boosts

• Marketplace activity for migrated NFTs and tools

• Cross-platform utility between Virtuals ↔ StrikeBit

---

🔁 Updated Functional Comparison

Use Case	$STRIKE	$HUB
Governance & voting	✅	❌
Native agent deployment	✅ (MAP deployment)	❌
Migrated agent deployment (AgentHub)	❌	✅
Radiant Miner rewards	Earn via $rSTRIKE	Boost with $HUB
Fusion & upgrades	❌	✅
NFT marketplace liquidity (ERC721)	❌	✅
Cross-chain liquidity utility	❌	✅ (Virtuals → StrikeBit bridge)
Airdrop/INO eligibility	Tiered by $rSTRIKE staking	Boosted via $HUB usage

---

🌉 Why This Structure Works

• $STRIKE powers the backbone of StrikeBit’s Modular Agent Protocol

• $HUB powers the adapters and liquidity bridges from other ecosystems

• Builders choose their track: native (deeper integration) or migrated (faster onboarding)

• This dual-layer model reduces dilution, improves UX, and drives protocol usage

---

🧠 Final Summary

Token	Layer	Role
$STRIKE	Protocol Core	Governance, native deployment, staking
$HUB	Utility Surface	Mining, migrated deployment, operations