Documentation

One public hub for product context, integrations, and support articles.

FundLoop documentation should explain the product honestly: what exists today, what the network is growing toward, and where to look next when you need workflow-level detail.

Support articles

Use the article list to browse current help content. As the support library grows, this hub remains the public entry point instead of splitting product guidance across separate mini-sites.

About FundLoop

FundLoop is building operating logic for a network economy that shares value back out.

The public docs should do more than answer support questions. They should also explain the economic model, why monthly structure matters, and how public discovery, founder operations, and identity-aware workflows fit together.

Mutual prosperity, made operational

FundLoop exists to help projects, participants, and operators move beyond vague community language and into repeatable operational flows.

Product before mythology

The public story should map back to real routes in the app today: discovery, onboarding, project contribution operations, reconciliation, and emerging reporting.

Using FundLoop

The current product has three practical entry paths.

Participants discover projects and build signal, founders manage contribution operations and route setup, and operators verify the payment and reporting pipeline that supports the monthly cycle.

Participation path

Start on the public participation funnel, continue into onboarding, and then move toward workspace-level results visibility over time.

Founder path

Use the founder funnel to understand the commitment model, then move into onboarding and project-side contribution operations.

Support path

Use documentation and FAQ first, then contact support when the issue depends on a real account, route, or payment workflow.

Protocol and integrations

FundLoop is documenting a future-facing integration surface without pretending it is finished today.

The longer-term target includes public protocol docs, MCP-friendly workflows, and agent/operator integrations. Right now, the truthful public guidance is to use the documentation hub as the source of product and workflow context while the formal external surface matures.

Product-aware integrations

The most useful external touchpoints will reflect real FundLoop domains such as identity, contribution cycles, payments, reporting, and observability rather than a generic CRUD API pitch.

Agent and MCP direction

The target architecture expects an MCP-accessible layer for founders, project members, and operators, but that work is still ahead of the current public docs surface.

Getting Started

How FundLoop Works

Understand the mechanics of the 1% pledge and citizen salary

Last updated September 20, 2026

FundLoop creates a regenerative economic loop by connecting projects that contribute a portion of their revenue with users who receive compensation for being active, verified participants. This section explains how the flow of value works, who is involved, and how distributions are calculated.

The 1% Pledge

Projects that join FundLoop commit to contributing 1% of their revenue each month to the ecosystem. This can include:

  • Product revenue
  • Grant funding
  • Token inflows or treasury activity

These contributions are reported monthly and fund two main outputs:

  • **Citizen salaries** for verified active users
  • **Public goods** and shared services across the ecosystem

Citizen Salary Distribution

Each month, FundLoop distributes contributed funds through a two-pass system:

1. Project Allocation Pass

- Each project nominates users and assigns them fractional values (from 0 to 1) based on their level of engagement.

- The user receives the highest assigned amount from any one project they are nominated by.

- Any overlapping contributions are returned to a communal pool.

2. Ecosystem Allocation Pass

- Remaining funds in the communal pool are distributed equally to all eligible users, using a square root multiplier based on how many different projects they engaged with during the month.

- Only users who are validated through Cubid and have engaged with at least two projects are eligible.

This structure rewards both deep and broad engagement, while ensuring no double-counting of value across projects.

User Validation and Eligibility

Only verified humans are eligible for citizen salaries. Validation is handled via Cubid, which allows users to link credentials like:

  • Phone or email
  • Social accounts (e.g., GitHub, Twitter)
  • Gitcoin Passport or wallet-based credentials

Users must meet a minimum validation threshold and demonstrate ongoing activity to qualify for payouts.

Benefits for Projects

Projects benefit by:

  • Gaining access to a pool of real, verified users
  • Incentivizing consistent usage through direct payouts
  • Demonstrating alignment with a broader regenerative economy
  • Building trust through transparent contribution and nomination patterns

Summary

FundLoop works by turning small recurring contributions into a sustainable funding system for human participation and public infrastructure. The more consistently projects contribute and users engage, the more the loop grows—and the more value it generates for everyone involved.

For more on how to get started, see the [Project Onboarding](/docs/project-onboarding) and [User Guide](/docs/user-guide) documentation.