sacha
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Introducing Gardens: a framework for effective on-chain governance > I'm still waiting for the perfect on-chain way to do everything. I don't think one token, one vote is the way to go. This is very prone to governance takeover by whales and so on... We're going to find something. -- 0xMaki > 8/ The dream here is for the everyday person to earn their wages, and store their capital, in cryptonetworks. > > But that requires limiting how extractive a large player can be with their capital. > > Mechanism design needs more work here. https://twitter.com/cburniske/status/1391401785584234499 *n.b. I have liberally stolen many of these thoughts from all sorts of hard-to-find 1hive resources; special thanks goes to Burrratta, many of the best sentences, including the introduction, are adapted from his forum posts.* -------- When governance power is determined purely by capital, decision making is centralised, and the rich get richer. Those who aren't whales are poorly represented in governance decisions, and there is no way to hold important stakeholders accountable to the desires of the broader community, or the past expectations they have bought into. On the flip side, attracting capital is critical to the success and sustainability of tokenized communities. Decisions backed by skin-in-the-game are key to ensuring that those who don’t have any interest in the long-term success of a community can't unduly influence how resources are allocated, and/or which policies are enacted. So how do we balance these opposing forces, and create a more effective and aligned community? Enter *Gardens.* ## Gardens Gardens is an initiative by 1hive to create a template for public communities to coordinate shared resources in a bottom-up fashion (essentially taking the best lessons learnt from the 1hive community and allowing any DAO to implement them in a plug-and-play fashion). A Garden has three main pillars: 1. A novel voting system (Conviction voting) 2. A decentralised social contract (Community Covenant) 3. A dispute resolution protocol (Celeste) Taken together, they fulfill the promise of effective community-driven on-chain governance, not tomorrow, but today. ## Conviction voting (to allocate funds) https://twitter.com/Square1_pod/status/1386714507460837378 *Conviction voting is the heart of a Garden.* It allows folks to signal their preferences continuously rather than forcing them to “make a decision.” From the perspective of a community member, the UX is simplified to just showing up and supporting things you care about. To quote a passage from [Jeff Emmett's wonderful introductory post](https://medium.com/giveth/conviction-voting-a-novel-continuous-decision-making-alternative-to-governance-aa746cfb9475): > **Conviction Voting offers a novel decision making process that funds proposals based on the aggregated preference of community members, expressed continuously.** > > In other words, voters are always asserting their preference for which proposals they would like to see approved, rather than casting votes in a single time-boxed session. > > A member can change their preference at any time, but the longer they keep their preference for the same proposal, the “stronger” their conviction gets. > > This added conviction gives long standing community members with consistent preferences more influence than short term participants merely trying to influence a vote. > >**Conviction Voting sidesteps sybil attacks, provides collusion resistance, and mitigates many of the attack vectors of time-boxed voting mechanisms**. Under conviction voting, **the majority doesn’t need to achieve consensus on everything.** As such, we get real [proportional representation](https://en.wikipedia.org/wiki/Proportional_representation#Advantages_and_disadvantages). Community members can propose and support things they care about without fear that a whale will vote them down. In fact, there is no down voting. **People with large stakes and strong opinions can’t suppress the community.** > *Footnote:* Rather than relying entirely on majority rule decision making, resource allocation decisions are regulated by staking on proposals to accumulate conviction over time. This allows resources to be allocated fairly, while minimizing the political and divisive process of coming to consensus on a single course of action. **Proposals simply need enough support to pass -- the fewer funds they ask for, the less support required.** This means there's a real sense in which everyone has a voice. The only thing token holders have to think about is whether or not they support something. *That’s it.* Under this framework, **many divergent initiatives can be proposed and run in parallel**. This allows the DAO to explore, experiment, and innovate quickly and seamlessly. If an experiment works, a larger proposal can then be submitted. One underrated benefit of this is that it allows the DAO to grow as a [headless brand](https://otherinter.net/web3/headless-brands/), iterating through cycles of [divergence and convergence](https://otherinter.net/web3/market-protocol-fit/), and continuously reflecting the preferences and interests of token holders (a true living organisation!). In sum, by giving small token holders the agency to contribute, **conviction voting helps lay the foundation for a fiercely loyal community**, solving the problems associated with governance attacks, low participation, and the overall inability to effectively prioritise and decide when there are many potential options all competing for consideration at once. ## Community Covenant (to encode values) The second pillar of a Garden is the community covenant. You can think of it as a constitution or **decentralised social contract** of sorts. https://twitter.com/starkness/status/463873319809212416 > *Footnote:* Covenants are the bridge between a Garden organisation and Celeste (the dispute resolution mechanism). On a practical level, a covenant is a document, stored on [IPFS](), which explains what a DAO is about in plain english. It establishes values, rules and customs. And is used to protect the DAO from malicious actors *without* sacrificing the agency of its members. The key idea here is that a covenant allows an organisation's actions to be governed by a subjective set of rules; rules which are either impossible to encode into smart contracts, or which would otherwise result in a complicated and slow-moving organization. Take [1Hive's Covenant](https://ipfs.eth.aragon.network/ipfs/QmfWppqC55Xc7PU48vei2XvVAuH76z2rNFF7JMUhjVM5xV), for example: > 1Hive is a community of activists seeking to build a future that is more free, fair, open, and humane. > > 1Hive is also an economic protocol, similar to Bitcoin or Ethereum, where a digital currency, Honey, is issued and distributed programmatically. Unlike Bitcoin or Ethereum, the 1Hive protocol does not narrowly define the set of activities that are valuable but instead relies on community members to guide the distribution process by creating and staking on Honey distribution proposals. > > The goal of the 1Hive protocol is to foster a healthy community economy by allocating a steady stream of Honey towards development, maintenance, and improvement of the common goods that bring the most value to the 1Hive community... Anyone interacting with the 1Hive protocol has to abide by this covenant. In particular, any proposal which violates the spirit of the covenant can be challenged and taken to Celeste (a decentralised court). In a sentence, a covenant allows a DAO to adhere to an agreement specifying its values, as well as outline subjective rules for what types of proposals are allowed. This unlocks the ability for much more nuanced and complex governance. ## Celeste (to protect values) The third pillar of Gardens, Celeste, serves as **the interface for a DAO's shared values, beliefs and hopes**. It provides a way to resolve subjective disputes, and to peacefully enforce the covenant. More technically, **Celeste is a [BrightID](https://www.brightid.org/) integrated fork of Aragon Court** -- the integration with BrightID allows for placing limits on how much stake an individual can add to the system. While we'll save the details for a dedicated follow-up post, I think it's worth mentioning here that Celeste is invoked only if and when an action is challenged (i.e. only in exceptional circumstances). Once Celeste is invoked, a decentralised (and randomly selected) group of BrightID verified humans -- called keepers -- is drafted to rule on the dispute (they are tasked with deciding whether or not the disputed action is compatible with that community's covenant). > *Footnote*: Well-reasoned [cryptoeconomic incentives](https://1hive.gitbook.io/celeste/keepers/dispute-lifecycle) ensure that the keepers converge to the most reasonable outcome for the dispute. If the keepers decide the proposal is compatible, on-chain execution continues. If they decide it is not, the proposal is blocked. By allowing even small token holders to challenge proposals that aren’t in line with the values of the community, Celeste provides a trustless way to uphold a DAO's core values. > *Footnote:* Celeste acts as a check on the power of *all* individuals – even highly-trusted community members. In doing so, it protects the long-term integrity of the DAO. > *Footnote:* It's important to note that Celeste can be used to rule on disputes arising over *any* human readable english document that allows for the possibility for subjective outcomes, not just a Covenant. For example, you could use it to decide on whether work, as outlined in a funding proposal, was actually completed or not. ## Conclusion https://twitter.com/0xMiel/status/1382641538551980033 Gardens provides a beautiful foundation for public communities to coordinate around shared resources in a bottom-up fashion. By combining three of the most important pieces of decentralized software ever written -- Conviction voting, Community Covenants (Aragon Agreements), and Celeste (a BrightID integrated Aragon Court), we are able to fulfill the promise of effective community-driven on-chain governance, not tomorrow, but today. With these building blocks we now have essentially limitless abilities for completely decentralised, and completely autonomous organisations. **P.S.** If you'd like to be one of the first to grow a Garden, please either DM me on [twitter](https://twitter.com/0xMiel) or fill out this [typeform](). I suspect the Gardens model applies equally well to communities thinking of launching they're own DAO + token, as it does to existing DAOs looking to improve the interface between their core contributors and wider community. In particular, if you're sitting on a large treasury and wondering how to [bridge the gap](https://gardens.substack.com/p/daos-and-the-pitfalls-of-progressive) between community and core devs, please get in touch. I'd love to help you experiment with a tiny part of it. In [the words](https://twitter.com/tobyshorin/status/1388940489781485568 ) of Toby Shorin: > The real flippening is when corporate dictatorships and internal command economies are ideologically defeated and replaced with cooperatively managed economic mini-democracies I believe Gardens is a key part of this puzzle. ## Resources - [Gardens overview - original idea](https://forum.1hive.org/t/gardens-overview/32) - [Gardens based media publications](https://forum.1hive.org/t/buzz-gardens-based-media-publications/36) - [Gardens + NFTs](https://forum.1hive.org/t/gallery-gardens-nfts/35) - [Rethinking incentives for open-source](https://forum.1hive.org/t/harberger-commons-rethinking-incentives-for-open-source/37) - [Celeste launch + next steps](https://forum.1hive.org/t/celeste-launch-and-next-steps/3446) - [1Hive conviction voting app](https://github.com/1Hive/conviction-voting-app) - [Gardens repo](https://github.com/1Hive/gardens) - [A brief history of Conviction voting](https://michaelzargham.medium.com/a-brief-history-of-conviction-voting-ad4ca4eb4aee) - [What is 1Hive?](https://forum.1hive.org/t/together-we-thrive/1278) ------ ## Notes on the multisig problem Governance by plutocracy is simply not a sustainable way of running a DAO. In particular, without additional checks in place, there's the ever-present risk that a whale, or a special interest group, will at some point cause the DAO to take actions that are not in its best interest (or in line with the values of its community). So far, most DAOs have skirted around this problem by relying on a multisig to officially sign off on proposals (as a sort of insurance layer against a malicious proposal being passed). In other words, while the community can vote on proposals, these votes are not binding; a small set of trusted community members have to sign off on them. If the multisig doesn’t sign, the system cannot move. However, while a multisig does act as a check on the power of whales, it doesn't solve the concentration of power problem: it merely shifts it away from large tokenholders towards a small group of trusted community members. There is nothing, apart from perhaps reputation, actually stopping the multisig from either executing an action that the community does not agree on, or vetoing an action that the community has advanced. And even if we assume that this group is honest and will continue to remain so, as the value they secure with their keys increases they become more and more vulnerable as individuals to attacks from others (the law included). In sum, multisig governance increases the risk born by both multisig holders and token holders, and leads to a somewhat fragile, and rather centralised DAO. ## Notes on the funding allocation problem The process of allocating funds in DAOs today feels very slow and cumbersome, typically requiring a series of yes/no votes evaluated independently. As a result, most DAOs suffer from a number of important challenges like 51% attacks, low participation, and an overall inability to effectively prioritise and decide when there are many potential options all competing for consideration at once.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully