Gardens DAO

Based on the 1hive model, Gardens is a framework for a new kind of DAO - a composable, sufficiently decentralized, and self-improving system, limited only by your community's collective imagination.

Veneto Gardens

• The type of Garden that 1hive uses. It comes with a powerful dynamic issuance policy - the details of which you can fine tune - although you are free to choose a more conventional supply policy should you so wish.
• When a community launches this type of Garden, they also create a community token. This token is used to grant voting power to vote on proposals that allocate shared resources from the Common Pool.
• Note that common pool funds may consist of the governance token, or any ERC-20 token

The key features are:

• A configurable amount of community tokens is minted and sent to the common pool.
• A pre-distribution of initial tokens can be made by the garden summoner to accounts within the related community.
• If you choose to go with a Dynamic Issuance Policy, then this can be configured to mint and burn the community tokens relative to a specified threshold of tokens in the common pool.
• If you choose to hold governance tokens in the Common Pool, then a configurable amount of these tokens is minted and sent to it.

Boboli Gardens

• Under this type of Garden, you have more flexibility in the sense that you are importing an existing token that may already have its own supply policy and rules associated with it. Once imported, this token is used to attribute voting power over the Garden's shared resources.
• One key difference between this type of garden and a Veneto garden is the incentive contract. The incentive contract can be used to reward users who choose to import their existing ERC20 token into the Garden in order to gain governance rights within that Garden (in simple terms, it provides a way to incentivise voting).

The community creating the Garden is encouraged to:

• Allocate a portion of their treasury to the Garden common pool.
• Send tokens to the incentive contract (not too little and not too much) in order to reward users who choose to import the original token in exchange for governance rights in the Garden.

Honeyswap Liquidity

When you create your Garden, you will need to provide the initial liquidity for your new token on Honeyswap.  The minimum liquidity requirement is $100 of HNY paired with $100 of your new GDN token.

The logic behind this requirement is as follows:

• It acts as a spam filter. Since we are putting in time and effort to help every Garden creator set up and manage a Garden, we want to make sure Garden creators are somewhat serious / at least have some skin in the game.
• If you are using Gardens to create a token, you will need some initial liquidity somewhere to allow for both trading and price discovery. Providing it on Honeyswap helps strengthen the relationship between your community and ours (more on this below).
• If you intend to recalibrate your proposal and challenge deposit amounts (which are paid for in your Garden's token) relative to a specific dollar amount, your Garden uses Honeyswap as an oracle. Without at least some liquidity on Honeyswap, accurate recalibration is not possible.
• The only case in which this requirement isn't strictly needed for your Garden to function properly is if you are importing your own token that already has liquidity somewhere else, and you don't wish to recalibrate your proposal and challenge deposit amounts according to a set dollar amount. In this case, you can think of it as a small gesture of solidarity that serves to align both our communities.

For some context, Honeyswap is a Uniswap v2 fork managed by the 1hive community that uses part of the protocol fee to buy back HNY and return it to the common pool.

Sources:

• https://1hive.gitbook.io/gardens/
• https://defillama.com/protocol/gardens-dao