--- title: "Transparency: treasury, grants, reports | ZooBC Foundation" description: "How the ZooBC Foundation handles treasury, disclosure and reporting. Every published binary is anchored on-chain; every grant is public with its outcomes." url: https://zoobc.foundation/transparency/ language: en publisher: ZooBC Foundation retrieved: 2026-10-19 --- 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. On-chain releases anchored [26](https://zoobc.network/verify) SHA-256 of every published artefact, written to consensus — live count, resets when the testnet is rebuilt Genesis allocation cap 10% of total supply — a hard chain rule, never exceeded Grants awarded 0 programme opening; every award will appear in the directory ## 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](https://zoobc.network/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](https://zoobc.foundation/grants/) with recipient, amount, category, milestone status. - **Governance changelog.** Every foundation decision recorded on the [Governance page](https://zoobc.foundation/governance/), 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](https://zoobc.foundation/bounty/). 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](https://zoobc.foundation/news/) 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. Genesis allocation slices The genesis allocation is capped at 10% of total supply and divided into seven named slices. Four of them fund Foundation programmes, which is why the Foundation keeps the record here rather than pointing elsewhere for it. 1. **Public supporter sale.** Offered openly at published prices. Anyone can take part, and whatever is left unsold is never minted. 2. **Legacy v1 supporters and private.** The people who backed the first ZooBC between 2019 and 2021. Honouring them in the new genesis is a commitment, stated rather than hidden. 3. **Ecosystem grants.** Funding for wallets, tooling, integrations, and applications that make the network useful to more people — awarded through the [grants programme](https://zoobc.foundation/grants/). 4. **Bug bounties and security.** Paid for finding what is broken before it matters. Security work is rewarded, not assumed. Terms will appear on the [Security page](https://zoobc.foundation/security/). 5. **Community and ambassadors.** For the people who explain, translate, moderate, and grow the network in the open. Paths are listed on the [People page](https://zoobc.foundation/people/). 6. **Testnet contributor rewards.** Active testers, bug reporters, and documentation contributors earn allocations they can claim at mainnet. 7. **Foundation reserve.** The Foundation's own operating reserve, disclosed as its own slice instead of being folded into anything else. Each slice is capped at genesis and, per protocol rule, whatever is not allocated at genesis is **never minted** — it stays in the coinbase pool for nodes to earn over the emission curve. Per-slice figures are not published here yet. They will be stated as fixed numbers once the allocation closes; until then, quoting a provisional split would be worse than quoting none. [Supply, emission & sale terms →](https://zoobc.com/tokenomics/) Verify a download Trust the chain, not the page that served it. [Open /verify →](https://zoobc.network/verify) Why on-chain votes matter here The Foundation's own decisions are made on-chain, using the same voting rail node owners use for protocol changes. See the [Governance](https://zoobc.foundation/governance/) page for how the electorate differs between the two surfaces. ## 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. [Email info@zoobc.foundation](mailto:info@zoobc.foundation) [Security disclosure →](https://zoobc.foundation/security/) --- Source: https://zoobc.foundation/transparency/ All pages: https://zoobc.foundation/llms.txt Full text: https://zoobc.foundation/llms-full.txt