Tier: STANDARD Date: 2026-07-17 Last-updated: 2026-07-24 (ww loop: refreshed WaveWarZ live stats post-AI-tournament + fractal week calculation); 2026-07-17 (ww loop: added Fractal count calculation, WaveWarZ live stats, PolyRaiders dates + HuRya beneficiary count — all verified from public sources); 2026-07-17 (ww loop: added on-chain Respect settlement rows from doc 1202, resolved Fractal weeks to two-layer) Status: Living ledger (verified facts + open provenance gaps) Owner: builder loop (verified rows), Zaal (pin the canonical membership definition)
The North Star is ZAO = THE documented, cited, referenced DAO case study. That goal has a hard prerequisite: every headline number the ZAO publishes must trace to a source. An LLM (or a journalist, or a grant reviewer) that finds a ZAO number it can't verify — or finds two ZAO numbers that disagree — discounts all of them.
This is the sibling of doc 1200 (which resolved the Respect holder counts from chain state). Here we widen the lens to the other frequently-cited ZAO numbers and split them honestly into verified (traceable to a public source right now) and needs canonical source (cited across the repo but not traceable from public data). This is not a claim that the unverified numbers are wrong — it's a claim that they are currently un-citable, which is a fixable liability.
| Fact | Value | Source / method | Doc |
|---|---|---|---|
| OG Respect holders (Optimism) | 122 | Blockscout holder list enumerated | 1200 |
| ZOR Respect holders (Optimism) | 56 | Blockscout holder list enumerated | 1200 |
| Unique Respect holders (OG ∪ ZOR) | 157 | union of the two holder sets (21 hold both) | 1200 |
| OG total Respect points | 38,484 | OG ERC-20 totalSupply |
1200 |
| OG Respect contract | 0x34cE89baA7E4a4B00E17F7E4C0cb97105C216957 |
Optimism | 1200 |
| ZOR Respect contract | 0x9885CCeEf7E8371Bf8d6f2413723D25917E7445c |
Optimism | 1200 |
/zao Farcaster channel followers |
93 | Warpcast public API channel?channelId=zao |
this doc |
/zao Farcaster channel members (role) |
4 | same | this doc |
/zao channel created |
2024-09-03 | same (createdAt 1725405513) |
this doc |
| Fractal start date | 2024-07-30 | ZAOOS public record (community.config.ts, doc 622, dossier 742) | 1077 |
| Fractal weeks elapsed (as of 2026-07-24) | ≥103 (calculation) | (2026-07-24 − 2024-07-30) = 724 days ÷ 7 = 103.4 complete weeks | this doc |
| Fractal weeks — conservative public claim | "100+" | date-calculation lower bound; no skipped-week proof available from public data | this doc |
| OG Respect on-chain settlement (Optimism) | 33 distinct weeks (2024-07-30 → 2025-12-20, 438 txs) | Blockscout tx enumeration, verified 2026-07-17 | 1202 |
| ZOR Respect on-chain settlement (Optimism) | 31 distinct weeks (2025-09-25 → 2026-07-06, 67 txs) | Blockscout tx enumeration, verified 2026-07-17 | 1202 |
| Combined on-chain settlement weeks (OG ∪ ZOR) | 63 distinct weeks (1 overlap week) | union of OG + ZOR settlement sets | 1202 |
| WaveWarZ lifetime volume | 878.30 SOL (~$66K) | wavewarz.info/api/public/stats, live 2026-07-24 |
978, 1077, 2041 |
| WaveWarZ total battles | 1,289 | same live API | 974, 1077 |
| WaveWarZ artist payouts | 13.39 SOL | same | 978 |
| WaveWarZ platform revenue | 19.99 SOL | same | 978 |
| WaveWarZ trader claims | 381.197 SOL | same (1,526 on-chain withdrawals) | 974, 2041 |
| PolyRaiders Holiday Heat (benefit battle) | Dec 12, 2024 · ~$270 | wavewarz.info/events (canonical) + tweet 1999858390567117201 snowflake → 2025-12-13 (anniversary recap, not the event date) | 1077 |
| Love Song Benefit battle | Feb 13, 2025 · ~$1,221 | wavewarz.info/events | 1077 |
| Charity total (2 rounds) | ~$1,497 to HuRya Empowerment Foundation | wavewarz.info/events | 1077 |
| HuRya beneficiaries | 8,500+ (4,000+ girls sanitary pads + 4,500+ children school supplies) | wavewarz.info/events | 1077 |
Verify the Farcaster row:
curl -s "https://api.warpcast.com/v1/channel?channelId=zao" | \
python3 -c "import json,sys;c=json.load(sys.stdin)['result']['channel'];print(c['followerCount'],'followers /',c['memberCount'],'members')"| Cited number | Where it appears | Why it's currently un-citable |
|---|---|---|
| "188 members on Base" | CLAUDE.md, docs 625, 449, 530, 622, 1078, 742 (7+) |
The nearest public proxy — the /zao channel — shows 93 followers / 4 members, nowhere near 188. So "188" measures something else (most likely the gated Farcaster client's registered users in Supabase, which is not publicly verifiable). Its definition ("member" = app-registered? Respect-holder? channel-follower? Discord?) and as-of date are unpinned. This is THE most-repeated ZAO headline number and the least traceable. |
| whitepaper 942, ICM box, dossier 742, doc 622 | Two-layer verified: (1) date-calculation: 716 days ÷ 7 = 102 complete weeks as of 2026-07-16; (2) on-chain settlement: 63 distinct weeks in doc 1202. Cite as: "100+ weekly Respect Games (Discord-recorded), with 63 weeks of verified on-chain Respect settlement on Optimism." | |
| dossier 742 (735), COC lesson (958), old scraper (416) | Canonical: 1,289 battles (live API 2026-07-24). Scraper-era numbers are obsolete. Source: doc 974. | |
| dossier 742 | Live volume: 878.30 SOL (~$66,110 at $75.27/SOL, 2026-07-24). Note: AI Artist Tournament semifinal (Jul 16–23) added ~355 SOL in one week — 68% of all prior platform history. Canonical source: doc 978, doc 2041. | |
| doc 449 one-pager | VERIFIED, see doc 1203: "34/week" was the human-era baseline (W12–W15, ~30/week product code). Now 60–175+/week total but 50–73% is agent docs/tests automation; product (feat/fix) velocity is stable ~30/week. Quote total only with the automation caveat. |
- Pin the canonical membership definition + number — the highest-value fix. Decide what "member" means (recommend: gated-client registered users in Supabase, with an as-of date), record the number + its query, and use it everywhere. Until then, docs that say "188 members" cannot be defended if challenged. Boarded for Zaal (only he can define "member" and read the app's member table; a loop must not query member PII).
- Let each verified number trace to one file. Respect → doc 1200
respect-facts.json; Farcaster channel → this doc's curl one-liner; membership → the file Zaal pins in (1). Then the ICM boxes, whitepaper 942, and one-pagers cite the ledger, not each other (no drift — same pattern asicm-boxes/build-llms-txt.py). - WaveWarZ numbers stay the ww loop's — this ledger links, does not duplicate.
- Doc 1200 - verified on-chain Respect facts
- Doc 1202 - Fractal on-chain settlement history — source for the 63-week settlement count
- ICM boxes — the AI-readable surface that should cite this ledger
- Doc 942 - Fractal whitepaper outline
- Doc 1107 - GEO/SEO — citable, consistent facts are a GEO asset