Page cover

EquityOS

EquityOS bridges token communities to real-world ownership.

It provides a compliant path for projects to graduate from meme → brand → business by mapping on-chain participation to cap table events (equity, revenue-share, or SAFEs) with verifiable attestations and governance control.

Status: design complete, integrations in progress. This page outlines scope, flows, and guardrails.


What EquityOS solves

  • From vibes to vehicles — most community tokens lack a legal wrapper and can’t share upside beyond price action.

  • From spreadsheets to state — cap tables, grants, lockups and cliffs live off-chain, unverified, and error-prone.

  • From promises to proofs — contributors and early believers need enforceable, auditable claims.

EquityOS introduces programmable corporate actions that sync legal docs, cap tables, and on-chain proofs — without breaking compliance.


Modes of use

  1. NewCo Formation

    • Spin up a legal entity (jurisdiction configurable) and seed an Equity Pool for community/contributors.

    • Token ↔ equity policy set by governance.

  2. Brand Partnership / Rev-Share

    • Keep entity separate; issue revenue-share claims or royalty rights to aligned holders (dividend-like flows) without issuing stock.

  3. SAFE / Warrant Track

    • Route select contributors/investors through SAFE/warrants mapped to on-chain attestations, vesting, and KYC gates.

All modes share the same attestation & audit layer; only the legal instrument differs.


How it works (end-to-end)

  1. Activate via GovernOS

    • DAO passes a binding proposal “Enable EquityOS” with:

      • Mode (NewCo / Rev-Share / SAFE)

      • Jurisdiction & entity type (templates available)

      • Equity/claim pool size (e.g., 5–20%)

      • Eligibility snapshot (block height, roles, or quests)

      • Vesting (cliff, schedule), lockups, and transferability rules

  2. Set policy & documents

    • Upload standardized legal templates (company formation, plan rules, grant agreements).

    • Hashes anchored on-chain; docs stored on decentralized storage (e.g., IPFS/Arweave) and mirrored.

  3. Identity & KYC (gated, read-only)

    • Eligible addresses receive an Attestation Request (non-custodial).

    • Users complete KYC/AML with an integrated provider; issuance proceeds only after pass.

    • Result: a Verifiable Credential (VC) bound to the address (or to a custody address, if chosen).

  4. Issue claim tokens (ECTs)

    • Mint Equity Claim Tokens (ECTs) or Rev-Share Claim Tokens (RCTs) to eligible addresses.

    • Default: non-transferable (soulbound) until converted; transferability governed by policy.

    • Vesting/lockups enforced by smart contracts; cliffs respected.

  5. Conversion / Payout

    • NewCo: upon board/admin approval, ECTs convert into book-entry shares on the official cap table; on-chain proof references the updated register.

    • Rev-Share: RCTs receive automated payouts (stablecoins/$DOGE) per revenue event.

    • SAFE/Warrant: exercise conditions tracked; conversions logged with on-chain proofs.

  6. Ongoing corporate actions

    • Top-ups, buybacks, cancellations, secondary approvals, and clawbacks (per plan rules) executed via GovernOS templates with full audit history.


Architecture highlights

  • Attestation Registry — binds legal identity → wallet via VC; stores hashes of signed docs.

  • Corporate Action Executor — pre-audited methods for issue/convert/cancel/top-up/buyback.

  • Payout Router — distributes revenue/dividends to RCTs; supports $DOGE, $LAIKA, stables.

  • Cap Table Sync — writes authoritative share movements to the off-chain register and anchors state (hash) on-chain.

  • Policy Engine — enforces vesting, cliffs, lockups, transfer rules.


Default parameters (governance-tunable)

  • Equity/Claim Pool: 5–20% (project-defined).

  • Eligibility: address snapshot; role-based (veTOKEN/veLAIKA thresholds), or quest completion.

  • Vesting: e.g., 12-month cliff, 36-month vest (monthly).

  • Transferability: ECT/RCT default non-transferable; allowlists possible post-vesting.

  • KYC scope: full (equity), light (rev-share), or exempt for tiny grants where permitted.

  • Disclosure: auto-generated grant notices & consent receipts to each recipient.

Active defaults visible in-app; changes require a DAO vote.


Roles & responsibilities

  • DAO / Board — sets policy, approves corporate actions, monitors issuance.

  • Operators — upload docs, coordinate KYC, manage payouts (no custody of user funds).

  • Contributors / Holders — complete KYC (if required), accept grants, monitor vesting/payouts in-app.

  • Auditors (optional) — read-only access to registry & cap table hashes for reviews.


Safety, compliance & plain-language notes

  • EquityOS is infrastructure, not legal advice. Projects must ensure jurisdictional compliance.

  • Equity claims (ECTs) and rev-share claims (RCTs) may be securities in some regions; defaults are non-transferable unless governance explicitly enables allowed routes.

  • KYC/AML is required for equity issuance in most jurisdictions; Rev-Share may still require checks.

  • All payouts and conversions are programmatic; corporate records are mirrored and cryptographically anchored.

  • Recipients should review grant terms and tax implications before accepting.


Why it matters

Community tokens can now own what they build — not only culturally, but legally and economically.

EquityOS gives DAOs and founders a credible path to reward conviction, retain top contributors, and align long-term value with the people who make the brand real.