Cowrie Research

1hive

3 min read

1Hive

  • Name: 1Hive
  • URL: https://1hive.org/
  • Category: conviction-voting DAO / commons-funding mechanism source / public-goods governance framework
  • Tags: ethereum-ecosystem
  • Summary: 1Hive is an operating treasury experiment and the main live conviction-voting lineage note in the corpus. The point is Honey issuance into a common pool, continuous allocation through conviction voting, and later export of that design into Gardens. The useful question is where power really sits: issuance policy, replenishment rules, threshold tuning, and the boundary between social norms and onchain enforcement.
  • What it does:
    • Issues a community currency called Honey and routes newly issued Honey into a shared Common Pool
    • Lets Honey holders stake support behind funding proposals so capital allocation happens through conviction voting rather than one-off snapshot elections
    • Organizes work through self-organizing swarms around projects and work areas, making social coordination part of the operating model rather than a side channel
    • Developed the Gardens lineage that later feeds into Gardens v2 as a reusable governance framework derived from the 1Hive model, allowing other communities to launch token-governed public-goods systems
    • In Gardens, separates funding decisions from constitutional / parameter changes by pairing Conviction Voting with Decision Voting, a Covenant, and Celeste dispute resolution
    • In the current Gardens v2 stack, expands the model into modular governance pools with multiple vote-weight systems and multi-network deployments
  • Key claims:
    • The official DAO explainer and FAQ make the core 1Hive mechanism explicit: Honey issuance accumulates into a common pool and Honey holders direct that pool through conviction voting. This is analytically more important than the community-token surface because it shows a built-in treasury replenishment loop
    • The forum explainer on conviction-voting thresholds is a major corpus signal because it makes parameter governance legible. Alpha, beta, rho, and related settings determine how hard it is for proposals to pass, so treasury power sits partly with whoever defines those constants
    • 1Hive is useful because it operationalized commons governance rather than only theorizing it. The swarms, forum process, token issuance, and parameter tuning sit in one live system
    • The Gardens docs show 1Hive’s biggest downstream contribution: exporting the model into a framework where funding, meta-governance, constitutional text, and disputes are intentionally separated into different modules
    • Celeste and the Covenant matter because they reveal an important design claim: token voting alone is insufficient for subjective conflicts, so community values need both textual expression and a dispute venue
    • The v2 materials show a further move from one DAO instance toward governance infrastructure. Modular pools, alternative vote-weight systems, and multi-network deployment turn 1Hive from a case study into a reusable coordination stack
    • As a comparison class, 1Hive is especially useful beside Commons Stack and Token Engineering Commons because it shows what happens when commons-funding ideas leave the architecture diagram and become an operating treasury with adjustable thresholds and real social overhead
  • Whitepaper: No canonical standalone 1Hive whitepaper surfaced in this pass. The strongest primary materials were the official DAO / FAQ pages, Gardens documentation, the official conviction-voting parameter explainer, and the official repositories; see ../whitepapers/1hive-primary-sources-2026-05-09.md.
  • Sources:

Internal linkages

  • Closest constitutional peer in the same commons-funding family: commons-stack

  • Strong downstream productization of the lineage into reusable infrastructure: gardens-v2

  • Broader reusable funding-control substrate from a different design tradition: allo-protocol

  • Last reviewed: 2026-06-03 UTC

Graph View

Backlinks