ZAOfractal
Search cmd K

08 - ORDAO / OREC / frapps / Optimystics

The software layer that runs every modern fractal community. Built by Optimystics - GitHub org with ~16 repos, mostly GPL-3.0 - and led by Tadas Vaitiekunas (sim31 on GitHub).

ORDAO - the system

ORDAO = Optimistic Respect-based DAO. It is the governance framework that wraps the Respect Game’s output (peer rankings) and turns it into on-chain decisions.

Its core innovation is being optimistic: instead of demanding a 50% quorum (which produces voter apathy in any large community), ORDAO trusts a proactive minority to propose and gives the rest of the community a challenge window to veto.

OREC - the contract

OREC = Optimistic Respect-based Executive Contract. A Solidity contract that runs three phases per proposal:

  1. Voting period. Anyone votes yes or no, weighted by Respect. Low quorum (e.g. 5%) - the design assumption is that most members will not vote, and that is OK.
  2. Veto period. A time-delayed challenge window where only NO votes count, vetoes carry 2x weight. A coalition with just 1/3 of yes-weight can veto.
  3. Execution. If a proposal survives both periods, anyone can call execute() to enact it on-chain.

The passing formula:

noWeight * 2 < yesWeight  AND  yesWeight >= minWeight

This is consent-based governance, not majority-based. It trusts the active minority while giving the broader community real blocking power.

The Optimystics repo ecosystem

RepoPurpose
ordao (Optimystics/ordao)Core monorepo - OREC contracts, orclient, ornode, ortypes, GUI, console
sim31/ordaoUpstream dev repo, Tadas’s working tree (254+ commits, last push Apr 2 2026)
orclient (npm: @ordao/orclient)TypeScript SDK. Current version 1.4.4, published 2026-04-02. Built on ethers v6 + zod
ornodeNode/Express + MongoDB backend. Stores off-chain proposal content
frappsThe “fractal apps” deployment platform. Each fractal gets a subdomain (e.g. zao.frapps.xyz, eden-fractal.frapps.xyz)
orfrappsNewer (April 2026) production-deployment + multi-instance CLI
FractalgramCustomized Telegram Web A client (GPL-3.0) - automates polls, breakout rooms, on-chain submission. Last activity Feb 11, 2026
Respect.GamesAsync-first Respect Game web app at respect.games (beta). MIT-licensed (unlike GPL-3.0 Fractalgram)
CignalsCompetition app for ranking live performances. Alpha-tested at Eden Fractal events 53/55/56 (“Fractal DJ” music ranking)
Cagendas, OPTOPICS, Respect Trees, RetroPollsOther Optimystics tools for meeting structure and async governance

orclient SDK functions

The SDK that fractal-app frontends call. Key functions:

FunctionWhat it does
proposeBreakoutResult(...)Submit a Respect Game session’s rankings as an OREC proposal
vote(propId, vote)Cast a yes or no vote on a proposal
execute(propId)Execute a proposal that survived voting + veto
getRespectOf(address)Read a member’s Respect balance

License + stack note

ORDAO tooling is GPL-3.0. ZAO OS is MIT. Using orclient as an npm dependency (linking) is fine and is what ZAO OS does.

A second consideration: orclient uses ethers v6, ZAO OS uses viem/wagmi. The integration pattern that solved this for ZAO is viem for reads, orclient for writes - the SDKs do not conflict at runtime because they call different methods.

frapps subdomains - active deployments

SubdomainFractal
zao.frapps.xyzZAO Fractal (Optimism) - LIVE
eden-fractal.frapps.xyzEden Fractal (Base) - LIVE
of.frapps.xyzOptimism Fractal (paused since Jan 2026)

ZAO’s OREC

ZAO Fractal’s OREC contract on Optimism: OREC0xcB05…e532optimism. As of May 21, 2026 it had recorded 242+ transactions since genesis. It reads the OG Respect token for vote weights and owns the ZOR Respect token to mint it.

Known operational issue: ZAO’s OREC has been driven by only two wallets to date (zaal.eth and civilmonkey.eth). All on-chain submissions have flowed through these two signers. Opening up direct member-submission is on ZAO’s roadmap (see ZAO research Doc 703, Recommendation #1).

Where to learn more

Sources

View source on GitHub →