Allo logo

AutoPGF

AutoPGF

TL;DR:

AutoPGF removes the friction of governance-heavy funding by automating the distribution of public goods capital. Funds flow continuously or periodically to projects based on objective or semi-objective inputs—like usage metrics, votes, or external data feeds.


Instead of holding rounds or reviews, AutoPGF uses code and signals to determine where funds go. It’s inspired by the idea that funding infrastructure can be autonomous—responding to community needs and activity without manual intervention.


This can take several forms:

  • Protocol-native PGF: where a percentage of fees or inflation is automatically routed to public goods
  • Signal-based streaming: where votes, contributions, or metrics determine how funds flow in real time
  • Trigger-based allocations: where certain thresholds or conditions unlock new distributions


AutoPGF is ideal for ecosystems that want reliable, recurring support for public goods—without the overhead of managing each allocation by hand.

Best For

  • Protocols with consistent revenue streams
  • Ecosystems seeking hands-off public goods funding
  • Builders designing automated treasury flows
  • DAOs with limited bandwidth for managing grants

Good At

  1. Reducing governance and review overhead
  2. Providing consistent support to long-term contributors
  3. Aligning funding with transparent, trackable inputs
  4. Enabling predictable, rule-based capital flows

Dependencies / Requirements

  • A source of funds (protocol revenue, treasury, inflation)
  • A signal system (e.g. votes, metrics, oracles)
  • Smart contracts to automate distribution logic
  • Optional: safeguards or feedback loops for recalibration

Not Good At

  • One-time or high-touch funding needs
  • New, untested contributors without past data
  • Creative or experimental projects that don’t map to clean metrics
  • Communities with low consensus on what signals should matter

Who Should Use It?

  • Protocol DAOs seeking sustainable, no-drama public goods funding
  • Ecosystems with robust onchain activity and measurable metrics
  • Treasury managers who want to “set and forget” part of their public goods allocation
  • Builders aiming for automated legitimacy and continuity

Example Use Cases

  • A protocol routes 1% of all transaction fees into an AutoPGF system, which streams funds to the top-used open-source tools in the ecosystem
  • A DAO streams capital to contributors based on GitHub commits and onchain usage statistics, rebalanced monthly
  • An ecosystem uses AutoPGF to support infrastructure projects whose health is monitored via oracles and usage signals