Gardens v2

• Name: Gardens v2
• URL: https://app.gardens.fund/
• Category: modular governance framework / conviction-voting public-goods infrastructure / multi-pool treasury coordination stack
• Tags: ethereum-ecosystem
• Summary: Gardens v2 is a reusable conviction-voting wrapper, not a new base protocol. It packages pool types, vote-weight rules, and threshold tuning around outside execution layers like Allo and Safe. The useful question is who gets to define those pool boundaries and defaults.
• What it does:
  • Lets communities create governance pools inside a broader ecosystem/community structure rather than governing only through one global treasury contract
  • Supports funding pools for discrete token allocations, signaling pools for non-executable or externally executed sentiment signaling, and documentation for streaming-style funding built around continuous allocation concepts
  • Supports multiple voting-weight systems including fixed, capped, unlimited/token-weighted, and quadratic models so communities can change how stake translates into influence
  • Uses conviction voting so support accumulates over time rather than relying only on one-shot proposal snapshots
  • Exposes configurable conviction parameters such as conviction growth, minimum conviction, spending limit, and fixed minimum threshold that determine how quickly proposals gain force and how hard they are to pass
  • Runs across multiple EVM networks and depends on adjacent infrastructure including Allo Protocol v2 and Safe, which is a reminder that Gardens is an orchestration layer rather than a self-contained protocol
  • Publishes an open-source app and contracts stack so communities can launch or adapt the framework rather than only consuming a hosted grants product
• Key claims:
  • Gardens decomposes governance into operator-chosen pools, weight systems, and parameter sets. That is the whole note.
  • Multiple pool types and voting models matter because they move authority upstream into pool design: who defines the boundary, who can propose, and what counts as support.
  • Conviction growth, spending limits, and the fixed minimum threshold are the real choke points. The framework slows flash majorities, but it also gives designers a lot of power over what can ever pass.
  • The Allo and Safe dependencies keep the stack honest. Gardens is governance packaging around outside execution and treasury layers, not a self-contained protocol center.
  • Keep the note on reusable conviction-voting orchestration, not on broad public-goods-software similarity spray.
• Whitepaper: No canonical standalone Gardens v2 whitepaper surfaced in this pass. The strongest primary materials were the official docs and the official gardens-v2 repository README; see ../whitepapers/gardens-v2-primary-sources-2026-05-09.md.
• Sources:
  • https://docs.gardens.fund/
  • https://docs.gardens.fund/conviction-voting/conviction-101.md
  • https://docs.gardens.fund/conviction-voting/conviction-pool-types.md
  • https://docs.gardens.fund/conviction-voting/conviction-parameters.md
  • https://docs.gardens.fund/proposals/streaming-proposals.md
  • https://github.com/1Hive/gardens-v2
  • https://raw.githubusercontent.com/1Hive/gardens-v2/main/README.md

Internal linkages

• Historical lineage: 1hive

• Closest constitutional and mechanism-family peer: commons-stack

• Pool-and-strategy substrate underneath much of the funding stack: allo-protocol

• Last reviewed: 2026-06-17 UTC