ZEROBASE (ZBT) Price

ZEROBASE is a proving network that makes off-chain computation results verifiable; ZBT is the network's native utility token. Its goal is not to put all computation and raw data on-chain, but to perform sensitive computations in a protected off-chain environment and then provide verifiable results to the chain or other users. In its design, trusted execution environments (TEEs) isolate runtime environments and handle sensitive computation, while remote attestation proves that nodes are running in the intended trusted environment; zero-knowledge proofs (ZKPs) allow verifiers to confirm that results comply with rules without obtaining all underlying data. Accordingly, ZBT is positioned as a tool for network services and participation incentives, not as project equity, debt, income rights, or asset claims.

ZEROBASE divides work in its proving network into routing and proof-generation stages. HUB nodes assign users' zero-knowledge-proof tasks to available Proving nodes and contribute bandwidth; Proving nodes execute within TEEs and generate zero-knowledge proofs. This division first sends tasks to computation nodes able to provide service, then has the computation layer produce verifiable proofs. The participation requirements and reward bases for the two node types differ. According to the official economic description, HUB nodes require no collateral and periodically receive small amounts of ZBT based on routing performance, traffic contribution, and uptime; Proving nodes must provide at least US$1 million in stablecoin collateral, and their rewards may be ZBT or stablecoins, depending on the quantity and quality of completed proving tasks. Rewards are not generated automatically merely by holding ZBT.

The role of zero-knowledge proofs in ZEROBASE is to turn “a computation has been completed according to the rules” into a verifiable proof, without requiring verifiers to inspect all sensitive inputs or strategy details. TEEs first provide an isolated environment for sensitive off-chain computation, and node remote attestation proves the integrity of the runtime environment; ZKPs then allow external verification to check the result. This combination addresses the fact that off-chain computation is often more efficient but difficult to independently verify: verifiers receive a proof or a limited-disclosure state, rather than raw data. For example, the system can prove that a risk metric falls within a given range without disclosing the complete strategy. What can be verified is the content included in the proving circuit or proof statement; this does not mean that all off-chain behavior is automatically disclosed or verified.

ZBT has a fixed total supply of 1 billion tokens, which the official materials define as non-inflationary; a fixed total supply does not mean all tokens are tradable at the same time. Changes in circulation mainly come from unlocking and release across categories: 2% for liquidity and 15% for the ecosystem fund are fully unlocked at TGE; airdrops and early mining account for 8%, with 5% unlocked at TGE and the remaining 3% planned for release in the following month. The other major categories have different schedules: the team and advisors account for 20%, locked for 1 year and then released linearly over 48 months; investors account for 11.25%, locked for 1 year and then released linearly over 24 months; node staking accounts for 43.75%, released linearly starting one month after TGE. Thus, the fixed cap answers how many ZBT can exist at most, while the amount available for circulation at a given time also depends on these release arrangements.

According to official materials, network revenue may come from routing, proof generation, bandwidth sharing, and capital-management strategies related to node collateral. Revenue first enters the protocol revenue module; a fixed 20% is reserved for the ZEROBASE Foundation for research, infrastructure maintenance, and ecosystem expansion, while the remainder mainly goes to the DAO treasury. This 20% ratio may be adjusted through community voting. ZBT holders in the DAO treasury can vote on whether to conduct buybacks and on their size and frequency; only after governance approval may the treasury buy back ZBT and permanently burn it. This mechanism is a supply-adjustment design that may be implemented and requires governance approval, and it cannot be used to infer that burns or price outcomes will necessarily occur.