At a glance
- $COMPUTE can lose some or all of its value, and you may be unable to sell it when you want.
- GPUs have finite working lives. Rental income and reinvestment depend on demand, costs, and continued operation.
- Projections and the 60% holder allocation do not promise a personal return.
- USDG payouts, credit usage, and settlement depend on policy rules, funding, and external services.
Understanding these risks
ComputeWorks provides these disclosures for the website and holder-benefit program. Read them with the Terms of Service. They describe material risks but cannot identify every possible loss or failure. Only participate if you understand the program and can bear the loss of the full amount you commit.
Trading may be available before hardware rentals or holder benefits are enabled. Planned features, example balances, and testnet demonstrations are not evidence of a funded entitlement or a production service. A working website or smart contract does not establish that an independent audit or regulatory approval has occurred.
Token price and liquidity
The market price of $COMPUTE can move sharply and fall to zero. Hardware purchases or rental earnings do not guarantee its price or a buyer for it. Markets may have limited liquidity, large spreads, slippage, restrictions, or no active trading at all.
Fees, network costs, and taxes can reduce what you receive. Holding $COMPUTE should not be treated as a bank deposit or a promise that your acquisition cost will be repaid.
Hardware and operating income
GPUs can become obsolete, wear out, fail, or cost more to operate than they earn. Demand, rental rates, utilization, power, cooling, hosting, maintenance, insurance, and counterparties affect net earnings. Customers or providers may delay payment or fail to pay.
Supplier availability, pricing, delivery, installation, and review can delay procurement. Hardware may need replacement before the fleet expands. Reinvestment creates acquisition funding; it does not ensure growth forever or continued income if trading stops.
Any prefunded build-period subsidy or revenue advance relies on limited reserves and the applicable program rules. It may stop when its funded period or commitment ends. Reserve funding is not evidence of rental demand or a guarantee that future hardware revenue will replace the support.
Illustrations are assumptions
The calculator’s default $1 million in daily trading volume is a scenario input, not actual volume or a forecast. Hardware prices and monthly earnings are rounded assumptions. Constant volume, rental rates, and purchase timing can make an illustration differ significantly from real operations.
The projection starts from the model’s stated starting point, reinvests according to the selected allocation, and purchases whole hardware batches. Real procurement, downtime, and changing economics can produce fewer GPUs and lower earnings.
A 60% holder allocation means 60% of modeled net rental earnings goes to the pool. Your share depends on eligibility, balances over time, other eligible holders, actual earnings, and the applicable policy. It is not a 60% yield.
Credits, USDG, and settlement
Credits depend on funded entitlements and settlement. An estimate or acquisition target is not a withdrawable balance. Verification, challenges, minimums, network costs, pauses, and service failures can delay distribution.
Hourly credits are provisional until their earning period finalizes. A period that finalizes lower, for example after a challenge, reduces unused provisional credits. Instant sales of provisional credits depend on the instant payout pool: its daily limits, its USDG balance, and pauses can leave part of a sale unpaid until the period finalizes.
Cash-out at the initial 90% of face value consumes the entire selected credit balance and pays USDG, rather than redeeming it for the same number of dollars. Model pricing and availability affect how much inference credits buy. A credit cannot be spent and cashed out twice.
USDG carries market, issuer, custody, contract, network, liquidity, and redemption risks. A USDG amount does not guarantee the same value in dollars or access to an off-ramp. Read the credit and cash-out terms.
The holder ledger and payout services must reconcile credits, usage, and on-chain payments correctly. Inference billing holds, exhausted operational funding, or an interrupted payout process can block access even when a balance is displayed. Credits not expiring does not guarantee uninterrupted access or recovery if an operator or provider fails.
Operational and administrative control
The program depends on people and providers to acquire and run hardware, reconcile revenue, calculate entitlements, and publish settlement records. A smart contract does not independently verify that a GPU is operating or that every off-chain calculation is correct.
Administrator and guardian roles can affect policy scheduling, challenges, and pauses. These controls help respond to incidents but introduce governance, key-management, and availability risks. At launch, each of the program's Safes is controlled by a single signer; a second required signer is planned later. Until then, the loss or compromise of that one key affects the funds and controls those Safes hold. Provider failure or operator insolvency can interrupt operations.
Token ownership does not, by itself, establish legal title to individual GPUs, a security interest over hardware, or control over ComputeWorks’s bank accounts or operations. Recovery in a wind-down depends on applicable law, actual asset ownership, financing obligations, and creditor claims. There may be no recovery for holders.
Team allocations and decisions about procurement, hosting, expenses, and providers can create conflicts of interest. Operators and providers may make decisions that reduce net earnings or delay distributions. Policy controls do not eliminate these commercial risks.
Wallet and software risks
Contracts, wallets, infrastructure, and integrations can contain vulnerabilities or fail. Transactions can be delayed, reorganized, rejected, or irreversible. Compromised keys, malicious approvals, wrong addresses, or unsupported networks can cause permanent loss.
$COMPUTE is launched and traded through Pons, whose contracts and administration are operated by a third party. Pons has stated that audits of its V2 contracts were still in progress. ComputeWorks cannot change or pause Pons contracts, and a failure or change there can affect trading, fees, and the funding of the program.
The leaderboard and the compute reimbursement manifests publish how many credits each wallet has loaded onto its OpenRouter key. Shortened addresses are not anonymous accounts. Blockchain activity can be linked with other information. Consider that visibility before using a wallet you also use elsewhere.
Regulation and tax
The legal treatment of tokens, revenue-linked benefits, credits, and digital-asset payouts depends on their structure and applicable law. Rules or regulatory action may affect access, trading, distributions, or operation.
Calling a benefit a credit does not, by itself, determine its legal classification. These disclosures do not represent regulatory approval or replace required registration, authorization, or customer protections.
Trading, receiving credits, using benefits, or receiving USDG may create tax or reporting obligations. Obtain advice suited to your circumstances. Questions about this document can be sent to [email protected].