Question 1

What is STRIKE?

Accepted Answer

STRIKE is the protocol and governance token of StrikeBit AI, serving the project's native deployment path: AI agents created directly within StrikeBit's Modular Agent Protocol (MAP) use this track. It performs the roles listed in the documentation, including protocol-level proposal voting, treasury control, issuance management, and native agent deployment. Here, “governance” describes the token's role in protocol-level matters; it does not mean that simply holding STRIKE automatically confers ownership of an agent, fixed returns, or rights to all platform activity. Specific exercisable rights still depend on the governance, staking, and application rules actually deployed by the project.

Question 2

What do native agents mean in the context of STRIKE?

Accepted Answer

Native agents are agents created and deployed directly in StrikeBit's MAP, rather than agents migrated from other ecosystems. STRIKE is assigned to this native deployment path, linking it to deployment within MAP and protocol-level governance. The practical significance of this classification is to distinguish the deployment origin and subsequent operational layer: projects likewise called AI agents are placed on the STRIKE track by the documentation if built directly within StrikeBit, while migrated projects are placed on the HUB track. It does not mean that all agents use the same token or have identical functions.

Question 3

What does STRIKE's governance role include?

Accepted Answer

STRIKE's governance role applies to protocol-level decisions. The project documentation lists proposal voting, treasury control, and issuance management among its scope; these matters affect how the protocol is configured and evolves, rather than directly controlling the day-to-day operations of each individual agent transaction by transaction. The documentation also links STRIKE to long-term protocol health, native agent deployment, and the staking track associated with rSTRIKE. “A token is designed for a function” should be distinguished from “any holder can necessarily use it now or necessarily receive returns”: participation conditions, voting implementation, and reward arrangements are subject to the actual contracts and product rules at the time.

Question 4

How are rSTRIKE and STRIKE related?

Accepted Answer

rSTRIKE is a participation token designed by StrikeBit and differs from tradable STRIKE: it is non-transferable, non-tradable, and non-liquid. The project associates it with participation and reward paths for Radiant AI Miner holders, long-term participants, and community contributors. The project documentation explicitly labels “burn 1 STRIKE to mint 1 rSTRIKE” as coming soon, so this conversion cannot be treated as a live feature. The documentation also describes rSTRIKE as redeemable for STRIKE after a 60-day cooldown period; early redemption carries a 5:1 burn penalty. The cooldown period and penalty make rSTRIKE's participation path different from STRIKE, which can be traded on the market at any time.

Question 5

What is the difference between STRIKE and HUB?

Accepted Answer

The two correspond to two different StrikeBit tracks. STRIKE sits at the protocol core, for governance and deploying native agents within MAP; HUB sits at the utility and operational layer, serving migrated agents, such as agents migrated through AgentHub and their associated operations. According to the project documentation, HUB can be used for migrated-agent deployment, virtual computing-power acceleration for Radiant AI Miner, fusion, appearance upgrades, and marketplace activity for migrated NFTs and tools; STRIKE does not perform these migrated operational-layer roles. This division is intended to separate workflows for native building and external migration, and does not support an inference that the two tokens can be exchanged at a fixed ratio.

STRIKE (STRIKE) Price