1Hive is most valuable as an operational proving ground for conviction-voting-based treasury allocation, not merely as a community token on Gnosis/xDai.
The DAO overview and FAQ make the original 1Hive mechanism explicit: Honey issuance accumulates into a common pool, then Honey holders stake support behind proposals so funds can be allocated through conviction voting.
The forum threshold explainer is especially important because it shows where real power sits inside conviction voting: not just in token balances, but in the choice of decay, max-ratio, weight, and related threshold parameters.
The Gardens docs show that 1Hive did not keep its governance design local. It abstracted the model into a reusable framework with Conviction Voting for funding, Decision Voting for discrete rule changes, a Covenant for plain-language social rules, and Celeste for subjective dispute resolution.
The newer Gardens v2 materials show further evolution from a single common-pool template into modular governance pools, multiple vote-weight systems, and multi-network deployment. That shift matters because it turns 1Hive’s earlier public-goods governance design into more general coordination infrastructure.
Together, the sources make 1Hive a useful bridge between Commons Stack’s architectural ideas and later products that package public-goods governance as reusable software.
Specific source signals worth retaining
about.1hive.org/docs/dao: clearest concise statement that 1Hive uses Honey plus conviction voting to fund public goods and investments that grow the community economy.
about.1hive.org/faq: strongest plain-language statement that new Honey accumulates in the Common Pool and is distributed via a proposal-and-staking process.
Conviction-voting threshold explainer: strongest source on alpha / beta / rho parameterization and why threshold tuning is a governance surface rather than a neutral implementation detail.
Gardens GitBook ask responses: best compact explanation of the four-pillar model — Conviction Voting, Decision Voting, Covenant, and Celeste.
gardens-v2 README: strongest current signal that the framework evolved toward modular pools, alternative vote-weight systems, and broader governance infrastructure rather than only one DAO instance.
Why this entry belongs in the corpus
1Hive belongs because it is both a live historical instance of commons-based crypto governance and a mechanism source for later public-goods tooling.
It is especially useful next to Commons Stack and Token Engineering Commons because it shows how continuous funding, social rules, dispute resolution, and parameter governance interact in practice.
The reusable insight is that supposedly decentralized treasury allocation still concentrates real authority in issuance rules, common-pool replenishment, conviction-threshold tuning, and the institutions that interpret or enforce a community covenant.