AI data center demand is the single fastest-growing driver of new electricity investment worldwide. A project whose output is committed to compute demand can carry FTDAO's compute-linked tag — without disclosing the operational data that makes competitors nervous.
Power availability, not chip supply, is the binding constraint on AI infrastructure — globally, and increasingly in emerging markets.
A data center's rack power draw, GPU utilization, and workload telemetry can reveal customer volumes, training schedules, and capacity utilization — information no operator wants sitting in public, even to prove a legitimate clean-power claim.
FTDAO's planned ZK-dMRV layer lets an operator prove a specific claim — for example, hourly Scope 2 matching — without publishing the telemetry behind it. This is grounded in 2025 academic research proposing the same approach for cloud data centre supply chains.
Read Section 6.4 in fullRack power meters, GPU utilization logs — stays on the operator's own infrastructure.
Computes verified MWh matched off-chain, generates a zk-SNARK proof.
Minted per verified MWh, burned when a claim is settled.
Illustrative claims this category is designed around — none of these are live today.
A verified claim that compute demand was matched with clean generation on an hourly basis, not just annually.
Proof that a power purchase agreement between a generator and a data center is being honored, without exposing commercial terms.
An immutable record a customer or regulator can check, without the operator disclosing workload-level data.
Africa's data center market is growing 14–24% a year, and power availability — not connectivity — is now the leading constraint on new capacity there. A compute-linked project in Kenya or Egypt faces the same structural opportunity as one in Texas or Virginia, under the same verification standard.
No compute-linked project has completed onboarding as of this writing, and the ZK-dMRV layer referenced above is a roadmap item, not a live system. See whitepaper Sections 2.4 and 6.4 for the full market context and architecture.