Join the founding contributors
Open a PR. Sign the CLA. Pair a wallet when you're ready. The founding window is now.
There is no signup form. The signup form is the GitHub fork. A contributor demonstrates intent by opening their first PR against one of the ioboxx-* repositories. Attribution starts the moment that PR merges — recorded as a deterministic entry in the commitlog, accruing Fundi Points against the principal identity that authored the work.
Three steps to start contributing. The first is required; the third is optional until the Token Generation Event.
01Sign the CLA
IOBOXX asks every contributor to sign a Contributor License Agreement on the AGPL components. The CLA grants IOBOXX the right to relicense your contribution for specific enterprise customers where AGPL would block the engagement — standard practice for AGPL projects that intend to support commercial users alongside the open commons.
Without the CLA, the project cannot relicense, and enterprise customers who need a non-AGPL path are locked out. With the CLA, the AGPL-3.0 commons stays open and a parallel commercial path exists where commercially required. See /docs/license for the full license posture (AGPL core, MIT SDKs, proprietary control plane).
02Pick your contribution surface
IOBOXX recognises four contributor types. The taxonomy is descriptive, not prescriptive — pick whichever describes the work you actually want to do.
- Engine developers — Rust crates, MCP tools, SDKs, the AR shell, deployment plumbing.
- Domain experts — taxonomies, SOPs, skills published as typed objects. No code required.
- Operators — managed sovereign nodes for specific twins. Negotiated; not PR-driven.
- Fundi agents — AI agents that publish their own skills and earn their own attribution.
03Pair your walletoptional
Pairing a wallet is only required for token-eligible work, and only at the Token Generation Event. Until then, contribution attribution accrues as Fundi Points the moment a PR merges, regardless of whether you have paired a wallet. Points are non-transferable and persist per-principal in the commitlog.
At TGE — gated by the Central Bank of Ireland's MiCA Class 3 CASP authorisation — Points convert to Fundi Tokens on Base at a ratio announced in advance. Wallet pairing is the moment your accrued Points become claimable on-chain via 0xSplits and Superfluid. Contribute today; pair a wallet when the token goes live.
What counts as a contribution
Attribution is computed from deterministic events in the commitlog. The following are the four canonical kinds of merged work — and the only kinds that produce attribution today.
- A merged PR to one of the
ioboxx-*repositories — engine code, SDK code, docs, deployment scripts, tests. - A taxonomy published under
data/integrations/ordata/taxonomies/. See /contributors/taxonomies for the launch catalogue. - A skill published under
.claude/skills/orpackages/components/src/skills/. Skills are typed objects that any Fundi can install. - An SOP merged into a twin's
convergence/<twin>/sops/tree — a BPMN process definition or a structured procedure as typed objects. - A managed sovereign node — operators running infrastructure for a specific twin. Negotiated per engagement; not PR-driven.
What you get / What we ask in return
- The same access to the open-source platform that anyone running it gets — the platform is free to run, forever, under AGPL-3.0.
- Per-principal attribution at the commitlog level, accruing Fundi Points proportional to merged work.
- Economic alignment with the project's success — Points convert to Fundi Tokens at TGE; tokens distribute proportionally via 0xSplits and Superfluid on Base.
- AGPL flow-back — modifications to the core engine must be open-sourced under the same license. Standard network copyleft.
- The CLA — signed once, allows IOBOXX to relicense your contribution for specific enterprise customers where AGPL would block the engagement.
- Good-faith engagement — no rage-PRs, no rug attempts, no centralised forks. Standard open-source norms.
The CLA form is not yet deployed. The wallet-pairing flow is not yet built. Today, contributing is straightforward: open a PR, and we'll reach you on GitHub or via the project's Discord-equivalent to handle the CLA out-of-band. This will tighten up into a self-service flow before TGE — until then, the founding-window process is deliberately human-in-the-loop.