Any grid-connected project that meets FTDAO's verification criteria can participate, regardless of source or geography. The network is designed to work the same way in Texas, Kenya, or Ireland.
Every project in the network follows the same four-step path.
The project submits site details, ownership documentation, and a metering/verification plan.
FTDAO holders vote via Snapshot on whether the project meets the network's verification criteria.
If approved, the project's token is deployed through the FTDAO factory contract — Solana by default, other chains where liquidity calls for it.
FTDAO receives an allocation of the newly issued project token, sized by governance vote, compensating the protocol for verification and standardization.
Once onboarded, a project reports production data through a submission form. Review runs in two stages before anything is published.
Data plus supporting documentation — a meter export or utility statement.
Held privately until it clears review.
Cross-checks figures against documentation, flags inconsistencies.
A human makes the final call — the AI agent narrows review, it does not publish.
A planned architectural evolution — not live today. Designed for projects, like AI data centers, whose underlying telemetry is commercially sensitive on its own terms.
A project's private hardware telemetry — rack power draw, GPU utilization, meter readings — never leaves its own systems. A local prover node computes the output metric off-chain and generates a zero-knowledge proof (a zk-SNARK) that the computation was correct, without exposing the underlying data.
This is grounded in 2025 academic research proposing the same approach for verifiable carbon emissions reporting across cloud data centre supply chains — see the whitepaper for the full citation and risk disclosure.
Read Section 6.4 in fullPrivate telemetry — solar, EV fleets, data centers, flaring reduction.
Computes verified output off-chain, generates a zk-SNARK proof.
Mints per verified unit, burns on offset or settlement.
Captures a micro-fee on minting and settlement.
Alongside energy source, a project can be tagged by what its output is oriented toward.
Flags a project whose output is committed, or intended, to serve AI/data-center demand. It's a demand-side tag, not a fourth energy source — the project is still fundamentally renewable, baseload, or another qualifying source.
Mining and mineral-extraction projects feeding the same supply chain don't fit the MWh-based verification model as-is. Flagged as a design question, not a currently supported tag.
AI and data center power demand is a global story, and Africa is one of its fastest-growing chapters — power availability, not connectivity, is now the leading constraint on new capacity across the continent. FTDAO's onboarding process is built to work the same way for a solar project in Nairobi as for a compute-linked facility in Northern Virginia.
As of this writing, no project has completed onboarding. The categories, figures, and pipelines above describe how the network is designed to work, not a claim that they are operating on live projects today. See the whitepaper for full current-status disclosure.