AlphaCOLLAB runs on GenesisL1 mainnet and has had no external audit. Use small amounts.Security notes

COLLAB

COLLAB documentation

COLLAB lets labs, research groups, universities, institutes, companies and non-profits run a DAO on GenesisL1 with nothing but smart contracts and a static website. This is its documentation: how COLLAB works, how to use it, how to run a COLLAB site, and how it is built. This page explains COLLAB in one minute, says which part of the documentation is for whom, and lists every page.

Version
COLLAB 2.2.0
Updated
Pages
58

DAO members

Use a DAO on GenesisL1: create one, propose and vote, run its treasury, tokens, data and models.

All 7 pages of Using COLLAB

Operators

Install and run a COLLAB site on your own server: the installer, the admin page, the prerender job and upgrades.

All 15 pages of Running a site

Developers

Read, test and extend COLLAB: the contracts, reading them from the chain, the web app and the release tooling.

All 13 pages of Developers

Warning. COLLAB 2.2 is an alpha that runs on GenesisL1 mainnet, with real L1: it is tested in the real environment, not on a test network. Its contracts, server kit and website were reviewed during development, with AI assistance and apart from the implementation work, but there has been no external audit. Use small amounts. Security at a glance explains what that means.

COLLAB in one minute

  • A DAO is six contracts that nobody owns. COLLAB's factory creates them in one transaction on GenesisL1, chain 29: a treasury, a governor, a share token, a call policy, a profile and a key vault. None of them has an admin key or an upgrade path, the creator's and COLLAB's authors' included.
  • Members decide with shares, the way GenesisL1 governance works. A deposit opens the vote; members vote Yes, No, No with veto or Abstain; quorum and thresholds decide. Your own vote always overrides your delegate's.
  • Every proposal has a type that limits what it can do. Changes to the rules, the members or the constitution, signatures, raw transactions and other sensitive calls must pass the stricter critical rules. A passed proposal waits out a timelock, then anyone can execute it.
  • Each DAO has a permanent identity. Its name and its web address, such as /dao/open-proteomics-collective, never change; its logo and description live in its own contract storage and are rewritten in place when they change.
  • The treasury holds what research needs: L1, tokens, NFTs, sealed CIPNFT data and GL1F models. A DAO can issue its own token with DeSciFi liquidity in a single vote.
  • The website is static. Your browser reads the chain directly and your wallet signs every transaction. A COLLAB server adds HTTPS, an admin page for its operator, prerendered pages and a price snapshot; it never holds a wallet key or funds.

All pages

Overview

  1. How COLLAB worksThe factory and each DAO's six contracts, the shared protocol contracts and lenses, the static site and your wallet, what a server adds, and trust.
  2. Key conceptsEvery core idea of COLLAB in a few sentences: the DAO, shares, proposals and their rules, the people, identity and tokens, each with its page.
  3. A tour of the siteThe portal: sidebar and network card, search and its / shortcut, the alpha strip and cookie notice, phones, and every page with its address.

Using COLLAB

  1. Wallets, networks and settingsConnecting a browser wallet on chain 29, accounts, RPC endpoints and the custom endpoint check, the explorer, the display currency, theme and stored data.
  2. Create a DAOThe creation wizard step by step: every field with its limits and defaults, the fee review, what a failed creation costs, and drafts.
  3. Name, web address, logo and descriptionA DAO's permanent title and web address, its on-chain logo and description: formats, limits, editing in place, costs, and the shared-name flag.
  4. Proposals and votingThe life of a proposal: deposits, the vote and how it is counted, delegation and the holding period, the timelock, execution and the review.
  5. The 13 proposal typesAll 13 proposal types: what each may do, when it uses the critical rules, its builders in the composer, examples, and the rules across types.
  6. Governance rules and presetsThe wizard's three presets, every governance setting and its range, standard and critical rules, the deposit flags, and how a DAO changes them.
  7. The constitution and announcementsThe versioned constitution: version 1 at creation, amendments by critical vote, the version history and comparisons, and announcements with their limits.

Treasury, tokens and members

  1. The treasuryWhat a DAO's treasury holds, how only passed proposals move it, the stricter rules when treasury spends are critical, signatures, modules and funding.
  2. Members and sharesShares and voting power, delegating, transferable shares and the holding period, issuing and burning shares, freezes, exclusions and the Members section.
  3. RepresentativesWhat representatives may do, how they are elected and removed, editing the logo and description directly, announcements and the tools in Settings.
  4. Issue and manage tokensIssuing an ERC-20 by vote and splitting its supply, member airdrops and claims, minting, pausing and the other token powers, and a DAO's Tokens section.

DeSciFi

  1. Swap on DeSciFiBuying and selling on DeSciFi: quotes and routes from the pools, price impact, slippage and deadlines, L1 and wL1, verification and the link check, errors.
  2. Pools, liquidity and locksDeSciFi's constant-product pools with fees kept apart, adding and removing liquidity, one-sided launch pools, LP locks, the pool page and the risks.
  3. The tokens list and token pagesThe /tokens list and token pages: how price, USD value, 24 h change, the 7-day line, liquidity, market cap and holders are computed, and what "—" means.

Science

  1. Sealed data with CIPNFTHow a DAO holds encrypted research data on CIPNFT: key stewards and key epochs, sealing, buying and selling, reveals, declassifying, and what cannot be undone.
  2. Models with GL1FHow a DAO owns GL1F Model NFTs: pricing inference, selling access and API keys, market listings, licences and internals, donations and the Models section.
  3. IntegrationsThe GL1F collections and CIPNFT contracts a DAO uses: defaults and your own, the checks, critical votes to change them, unlisted ones and outside admin keys.

Safety and costs

  1. Staying safePractical safety for COLLAB users: copycat DAOs, unverified tokens, phishing, wallet hygiene, checking what you sign, small amounts in the alpha, reporting.
  2. Costs and gasWhat using COLLAB costs: network fees with measured gas for common actions, GenesisL1's half-the-limit rule, large logos, deposits and protocol fees.
  3. Security at a glanceSecurity in brief for members: what COLLAB's contracts guarantee, what you still trust, which reviews were done, and why the alpha has no external audit yet.
  4. Known limitationsEvery known limitation of COLLAB 2.2 in one place, in plain words, each with what to do about it: alpha status, gas, names, governance, sealed data and more.
  5. Questions and answersShort answers for members and operators: voting, deposits, costs, names and web addresses, logos, safety, the alpha, privacy and the admin page.
  6. GlossaryShort definitions of the terms COLLAB uses, from Abstain to Web address, each with a link to the page that explains it.

Running a site

  1. Running a COLLAB siteWhat running a COLLAB site involves: the static site, what the server adds, what it never holds, its parts, and the path from upload to a working site.
  2. Before you install: server, DNS and namesWhat to prepare before the installer runs: the server, DNS for every name, the firewall, an existing nginx, the main host, the RPC and a funded wallet.
  3. Installing COLLAB on a serverThe complete install reference: upload and extract the archive, run server/install.sh, every option, its output, the files it writes and what to do next.
  4. The admin pageThe admin page at /admin: the admin token, sessions and sign-in limits, and what each tab shows: Status, Deploy, Publish, Check and Site settings.
  5. Deploy the protocol from /adminDeploying COLLAB's 20 contracts from the Deploy tab: the wallet and L1 needed, the plan, each transaction, resuming, verification and publishing.
  6. Publish, unpublish and checkPublishing a deployment to this site, from the Deploy tab or an existing record, what the server writes, unpublishing, and the Check tab.
  7. Site settingsEvery field of site.json on the admin page's Site settings tab: what it changes on the site, its exact label, its rules and examples.
  8. Static pages, data files and pricesThe prerender job on a COLLAB server: the pages, images, sitemap and /data/ files it writes, when it runs, its user and limits, prices, warnings and failures.
  9. Domains, redirects and certificatesThe main host and its aliases, the 301 redirects, the Let's Encrypt certificate and its renewals, adding or removing a name, unknown names and HSTS.
  10. Upgrades, rollbacks and backupsUpgrading a COLLAB server with the new release's installer, what it keeps, going back with an older release's installer, backups, restoring and moving servers.
  11. Status, logs and the collab commandWatching a COLLAB server: the collab command (status, logs, prerender, admin-token, apply), the journal, nginx's logs, check_site.py and healthy values.
  12. TroubleshootingSymptom, cause and fix for real problems on a COLLAB server: DNS, certificates, nginx, publishing, sign-in, the prerender job, RPCs, the policy, upgrades.
  13. Hosting without the server kitHosting COLLAB without the server kit: plain nginx or Caddy, Netlify or Cloudflare Pages, IPFS; config.js by hand, what you lose, and the ?v= caveat.
  14. Operator security checklistThe operator's security checklist for a COLLAB server: the admin token, patches, the firewall, backups, logs, certificates, and the server kit's threat model.
  15. Deploying COLLAB: referenceThe deploy reference: contracts with Foundry or the Deploy tab, the deployment record, config.js and the policy, static servers, prerendering and checks.

Developers

  1. Developer overviewWhere to start with COLLAB's code: the repository, the toolchain (Foundry, Python, no Node.js), memory notes, the project's rules and the licences.
  2. ArchitectureHow COLLAB is built: the contracts on GenesisL1, the static web app, the server kit with its admin service and prerender job, and the tooling.
  3. Local developmentRun COLLAB on your machine: Foundry and Python, a local chain with demo DAOs, the dev server, private sandboxes, test wallets and common pitfalls.
  4. Contracts guideEvery COLLAB contract and how they fit: the factory and its six clones, the singletons, DeSciFi, the lenses, the main flows, events and errors.
  5. Governance internalsHow DAOPolicy decides what a proposal may do: rules, roles and precedence, critical kinds, the 115 default rules, the treasury stance and validate().
  6. Reading COLLAB from the chainRead DAOs, slugs, profiles, proposals, pools and events straight from GenesisL1 with cast, within the nodes' gas and log limits.
  7. The web appThe rules and modules of COLLAB's static web app: layout, URLs, the portal shell, design system, core modules, views and builders.
  8. Data formatsThe schema, an example, size limits, writer and readers of config.js, site.json, deployment records, the deploy bundle and the /data and /og files.
  9. Admin API referenceEvery endpoint of the admin service behind /admin/api/: requests, responses, errors, sign-in, sessions and the cross-site checks.
  10. TestingHow COLLAB is tested: 331 Foundry tests in 92 suites, the browser suites, the server kit's tests, lint and the generated-file checks.
  11. Building a releaseWhat tools/build_release.py does step by step: checks, batched compile and tests, exports, versioned assets, docs, the reproducible tar.gz and its verification.
  12. Gas referenceMeasured gas of COLLAB's heavy transactions, the gas-limit formula, the 25M estimate cap and GenesisL1's rule that a failure pays half its limit.
  13. Contract API referenceEvery function, event and error of the COLLAB contracts and of the GenesisL1 contracts they use, generated from the ABIs.

Security and project

  1. SecurityWhat COLLAB's contracts guarantee, what you still trust, every security review with its findings and fixes, and the known limitations.
  2. Release notesWhat changed in each release of COLLAB, from 1.0.0 to 2.2.0: features, reviews, interface changes, upgrading and what is not done yet.
  3. Licence and third-party codeCOLLAB's MIT License and its copyright holder, what it covers, and the third-party code COLLAB ships or compiles in, each under its own licence.

Read it where you are

  • On a COLLAB site: /docs, with a search; each page at /docs/<page>.
  • On GitHub: the docs/ folder of the repository, where this page is the index.
  • As Markdown: every page at /docs/<page>.md of a COLLAB site, for reading offline or by language models.

This documentation describes COLLAB 2.2.0, contracts version "COLLAB DAO v2.2.0" on GenesisL1, chain 29. COLLAB is open source under the MIT License, copyright 2026 Decentralized Science Labs LLC.