Whitepaper — FTDAO
FTDAO is a utility and coordination token Whitepaper v2.2 →
Documentation

The FTDAO Whitepaper

The full architecture, the market context, and every disclosed risk. Version 2.2 — July 2026.

Version history

VersionDateWhat changed
v1Sep 2023Original Fund Governance Token Strategic Whitepaper — pooled investment framing (retired).
v2.0Jul 2026Repositioned FTDAO as a utility and coordination token; introduced the Energy Project Network.
v2.1Jul 2026Globalized market context; added Africa data center coverage and critical minerals (Section 2.5).
v2.2Jul 2026Added the planned ZK-dMRV Reporting Token layer (Section 6.4) as an architectural evolution.

What's inside

Twelve sections, from market context to a full risk disclosure.

1Executive SummaryWhat FTDAO is, and what this revision changes.
2Market ContextEnergy investment, RWA tokenization, AI data centers, and critical minerals — globally, with an Africa focus.
3What FTDAO Is — and Is NotDAO structure, governance data, and the is/is-not distinction.
4Technical ArchitectureBSC, Solana, Wormhole NTT, and why not a dedicated chain.
5The 12-Month Stability VaultHow migrated tokens lock without losing governance weight.
6The Energy Project NetworkOnboarding, verification, and the planned ZK-dMRV reporting layer.
7Regional Data & TransparencyThird-party grid data displayed on fundtokens.io.
8Market AccessWhere FTDAO trades and what's coming next.
9Token Economy Design Self-AssessmentFTDAO evaluated against the TEDM framework.
10RoadmapFive phases, from Solana issuance to the ZK-dMRV pilot.
11Risks and Barriers to AdoptionEvery material risk, disclosed directly.
12SourcesFull citations for every figure in the document.

Where to start

Section 2 — Market context

Global energy investment, AI data center demand, and why Africa's critical minerals matter to the network's design.

Section 6 — The Energy Project Network

How a project joins today, and the planned zero-knowledge reporting layer for tomorrow.

Section 11 — Risks, disclosed

Technical, regulatory, and adoption risk, written plainly — including what the ZK layer does not solve.

Read the document that everything on this site is built from.