Transparency
Transparency is the product, not an appendix.
Foundations exist to be checkable. This page describes how the ZooBC Foundation approaches treasury, disclosure, and reporting — and where you can independently verify each claim today.
Treasury approach
The Foundation's operating reserve — the "Foundation reserve" slice below — is one line item on a public genesis allocation. It is not a discretionary pool that grows over time from opaque sources. The slice is fixed at genesis and will be drawn down against published programmes.
Where the money came from, and where it goes. The network's founder financed the first ZooBC personally between 2019 and 2021, and has funded the C++ rebuild since June 2025 from the same source. Proceeds of the genesis supporter sale fund the Foundation, the setup of the network's supporting infrastructure, and partial repayment of that personal funding. Stating this plainly is the point: a foundation that is vague about who paid for its existence has already failed its first disclosure.
How every published binary is verifiable
ZooBC has an on-chain release registry: a release authority writes the SHA-256 hash of every published artefact (binary, page, wallet, CLI) as a transaction to the chain. When you download something from the network, you can drag the file into /verify and it checks the file's hash against consensus rather than against the website that served it. That is a strictly stronger guarantee than "trust our download page" — a compromised web server cannot forge a hash that the entire network has agreed on.
The commitment is the mechanism, not the number: nothing the Foundation publishes is announced before it is anchored. The registry currently holds 26 anchored releases. That figure is read live from the chain and returns to zero whenever the testnet is rebuilt — a low count means a fresh chain, not an abandoned practice.
Reporting commitment
The Foundation commits to:
- Annual transparency report. Programmes funded, decisions made, treasury movements, board and staff changes.
- Quarterly grants update. Applications received, reviewed, approved, and closed with outcomes. Applicant names appear only with consent; grant recipients are public by default because they are receiving public funds.
- Live grants directory. Every awarded grant appears immediately on the Grants page with recipient, amount, category, milestone status.
- Governance changelog. Every foundation decision recorded on the Governance page, mirrored from the on-chain vote.
- Bug bounty ledger. Every confirmed testnet finding, who reported it, how it was judged and what it was worth, on the bug bounty page. A programme that pays quietly gets the reports it deserves.
- Post-incorporation. Articles of association, board minutes summary, and audit findings when applicable.
Cadence starts on incorporation. Interim reports and grant announcements are published as they happen — the site's news archive is the running log.
What is not yet available
Because the Foundation has not yet incorporated and initial funding rounds have not yet closed, several pieces of a mature transparency page are not yet honest to publish. Rather than fabricate them, the following are explicitly not shown until they exist:
- Multisig treasury address(es) — will be published at incorporation.
- Audit firm and audit findings — no audit commissioned yet; will be commissioned once treasury is capitalised.
- Historical spend — nothing to spend yet.
- Named institutional partners — announced as they sign, not before.
Found something the Foundation should disclose?
If you believe a fact on this site is inaccurate, or that something material is missing, tell us plainly. The whole point of a transparency page is to be corrected.