A concise protocol map for ComputeX
ComputeX is a Keccak256-based compute-mining network on Binance Smart Chain. Browser miners, terminal miners, and AI-agent operators all compete inside shared 10-minute epochs and earn from a fixed epoch reward pool based on the quality of one final hash.
Total Supply
100,000,000 CMP
Fixed token supply for the network.
Mining Allocation
92,500,000 CMP
Distributed through compute proof validation.
Epoch Length
10 Minutes
Every epoch runs on a new challenge window.
Submission Model
1 Best Hash
One accepted result per user, per epoch.
Compute-backed issuance, not faucet-style inflation
ComputeX replaces noisy share spam with epoch-based competition. Each miner works locally for most of the epoch, improves one best candidate hash, and submits only during the closing window. That makes network load predictable while still rewarding stronger compute with more points and a larger share of the epoch pool.
Mining rewards are sourced from a fixed emission schedule, finalized server-side, and distributed proportionally from the pool assigned to each epoch. Staking, referrals, and user balances are accounted for in the same Supabase-backed protocol layer.
Mining Hash
keccak256(challenge + walletAddress + nonce)
Epoch Pool
yearlyEmission / 52,560 epochs
Reward Share
userReward = epochPool × (userPoints / totalEpochPoints)
Protocol Architecture
Four layers keep the mining loop simple
Compute happens at the edge. Verification and accounting happen on the server. The database keeps state, claims, and security boundaries clean.
Wallet Authentication
Users authenticate with an ECDSA wallet signature. The server verifies the message and issues a session cookie for dashboard and mining APIs.
Epoch Challenge Layer
The server keeps a rolling 10-minute epoch with a unique challenge, reward pool, submission window, and settlement metadata.
Local Compute Mining
Browser workers and the ComputeX CLI both mine locally by testing random nonces against the current epoch challenge.
Server Settlement
The API re-verifies the submitted hash, records epoch points, and finalizes rewards after the epoch closes.
One best hash per epoch
Every epoch uses a fresh challenge, so a result that was valid in one epoch cannot be replayed into the next. Each user can have only one accepted best hash in the same epoch, which prevents reward farming through repeated low-quality submissions.
Submission Window
15s
Final seconds only. The server rejects early submissions.
Points Range
1 - 2048
Better hashes receive more points, capped for balance.
Why this matters
Miners spend the full epoch searching for a stronger result instead of flooding the API. Compute strength improves reward share, while server load stays low and predictable.
Request Current Epoch
A miner authenticates, fetches the active challenge, and opens a mining session for the current epoch.
Mine Locally
The client evaluates keccak256(challenge + wallet + nonce) locally and keeps improving its best candidate hash.
Submit Once Near Epoch End
Only the final 15 seconds are valid for submission. Clients finalize roughly 4 seconds before epoch close and submit one result.
Verify and Score
The server recomputes the submitted hash, rejects duplicates, enforces the epoch window, and converts hash quality into points.
Finalize the Epoch Pool
After the epoch closes, the protocol distributes that epoch’s fixed reward pool in proportion to each miner’s recorded points.
Tokenomics
Fixed supply with annual halving
The protocol distributes a mining allocation of 92,500,000 CMP across epochs. The yearly mining emission halves every year, and each epoch receives a deterministic slice of that year’s emission budget.
Mining Rewards
92.5%
92,500,000 CMP
Primary distribution bucket for compute miners.
Liquidity
5%
5,000,000 CMP
Reserved for DEX liquidity on Binance Smart Chain.
Marketing
2.5%
2,500,000 CMP
Reserved for growth, partnerships, and ecosystem awareness.
First Four Emission Years
Yearly issuance and approximate reward per epoch
52,560 epochs per year at 10-minute epochs
Year 1
46,250,000 CMP
Approx. 879.9467275 CMP per epoch
Year 2
23,125,000 CMP
Approx. 439.9733638 CMP per epoch
Year 3
11,562,500 CMP
Approx. 219.9866819 CMP per epoch
Year 4
5,781,250 CMP
Approx. 109.9933409 CMP per epoch
The halving schedule continues beyond year four. In practice, later epochs keep following the same yearly emission rule while reward settlement remains proportional to the points earned in each epoch.
Secondary yield layers
ComputeX also supports staking with a 30-day lock. Staking APY scales with a user’s total active stake, while staking and referral rewards accumulate through the claims layer.
Bronze
< 1,000 CMP
12% APY
Silver
1,000+ CMP
15% APY
Gold
5,000+ CMP
18.5% APY
Diamond
25,000+ CMP
24% APY
Referrals
Referrers receive a 2% commission on the finalized mining rewards of referred users. That commission is tracked independently and does not reduce the referred miner’s own finalized epoch reward.
Claims
Mining rewards are finalized epoch-by-epoch and credited to user balances. Referral and staking rewards enter the claims system first and can then be claimed into the user balance through the API.
Point-Based Fairness
ComputeX uses point-weighted epoch settlement instead of paying per raw submission. That means stronger compute is rewarded, but endpoint spam does not create artificial advantage.
Security Model
Verification is centralized, compute is distributed
Miners do the work locally, but rewards are only recognized after the server verifies the result, the session, the epoch timing, and the database constraints.
Server-Side Hash Verification
The server recomputes the submitted Keccak256 result and never trusts the client’s claimed score or reward.
Single Submission Per Epoch
The protocol enforces one accepted best hash per wallet, per epoch through API checks and database uniqueness on mining shares.
Protected Sessions
Authenticated routes use signed JWT sessions stored in HttpOnly, SameSite=Strict cookies and validated at the dashboard proxy layer.
RLS-Scoped Data Access
Supabase row-level security limits users to their own rows while public epoch reads remain available for mining clients.
Next Steps
Read the docs or start mining
The whitepaper explains the protocol. The docs page explains installation, browser mining, agent workflows, and the live CLI commands for ComputeX.