HackMD
  • Prime
    Prime  Full-text search on all paid plans
    Search anywhere and reach everything in a Workspace with Prime plan.
    Got it
    • Prime  Full-text search on all paid plans
      Prime  Full-text search on all paid plans
      Search anywhere and reach everything in a Workspace with Prime plan.
      Got it
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
    Menu Sharing Help
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    --- ###### tags: `Haus Party Live` --- # HAUS Party LIVE! Notes (3/3/2022) Join us for 🎉 Haus Party Live 🎉 every Thursday at 2pm EST on the [DAOhaus Discord](https://discord.gg/daohaus) ## Guests and Topics - Felipe, vengist, dekan, vanilladelphia - Spengrah (Spencer): Anticapture - Community Members from the Audience ## Anticapture Framework - **Anticapture** is a framework that gives language and a mental landscape to processes through which groups can spread power wider and "remain resistent to capture" - If power is shared then it is harder for a central agent to take over an organization - [Spencer's Anticapture Framework on Mirror](https://t.co/NSK0sZNwQW) - What is a DAO? Where do we draw the line? - What is Anticapture? - One component of a DAO -- *antifragile*, *anticapture* are things decentralization can help us with - *nintynick* coined the term in a conversation about the framework ## Anticapture Background - Came about in the last six or seven months when DAO conversations started exploding and started seeings lots of DAOs that are defined by tokens (as well as other projects calling themselves DAOs without having a strong argument that they were DAOs) - Investigating the question about "What is a DAO?" while working to figure out *why* they aren't DAOs -- "More of a feeling than any other intellectual exercise I'd gone through" - This investigation took several directions and led to notion that taking action is what's important for groups of people that are working - These groups are *taking actions together* - 🌱 "It's a little bit easier to talk about verbs instead of nouns or things that are action oriented rather than the organization that's doing the action itself." 🌱 - Easier to reference and think around the actions instead of the *organization* doing these actions - As soon as you start questioning whether an organization is a DAO the folks become defensive and difficult to have a meaningful conversation - Notion of actions unlocked a thread - Foundation of any group getting together and doing anything: - 1) They are taking action - 2) They are taking actions that use, leverage, or impact *shared resources* (belong to the organization and not just an aggregate of individual resources) - In a DAO, shared resources are anything in the treasury, but also governance mechanisms because DAOs are self-owning ### Actions Framework - 🌱 "*Networks of people* that are taking actions that impact their shared resources." 🌱 - **Actions have 4 phases** and are cyclical and also recursive (each phase comprises other actions and phases of actions within itself): - In a network of people, all individuals are taking actions that bubble up and aggregate into organization actions that are being taken - **Four Phases of Actions**: - 1) *Propose* - put options on the table for what the action will be - 2) *Decide* - decide what action to take, but this decision isn't the end stage - 3) *Execute* - actual rollout of the action - 4) *Evaluate* - after execution, there is some degree of feedback where the organization measures, and this leads into *the next action* - Key distinction between *decision* and *execution* ### Levels of Capture - When we're talking about Anticapture, what is it that we're referring to that isn't being captured? The treasury? The organization? The governance? - All of the above -- all shared resources - **Capture resistance** is important because this means that it's less risky for an individual to take their own money shared with other folks - Lowering this risk means we get more people willing to do this and increase the amount of shared resources - Can do exponentially more when *you do things together* -- increasing returns to capital and other resources when pooling together and collaborating - If stuck within captureable organizations then the risk of entering into mutual engagements with others is far higher and therefore we'd see less of the overall benefits - The more capture resistant an organization is (from perspective of members) then the easier it is to trust each other without additional context - Trust is a big issue, and so addressing issues of trust allows for increased coordination - 🌱 "If something is capture resistant then you can operate together with other people without having to trust them." 🌱 - **Higher the capture probability -> higher trust required for coordination** - Capture can happen in lots of ways -- [a 51% attack](https://www.investopedia.com/terms/1/51-attack.asp) is one way, but can also be captured by code exploits ### OODA (Observe, Orient, Decide, Act) Loop - Similarities and differences to OODA Loop? - Feedback at each step in the loop so can break out of it if something requires it - At a higher level, there are differences in the Anticapture phrases and the OODA Loop - Anticapture phases are more observational - Different frameworks for different purposes - Anticapture is more about identifying where an organizations operations can break down or where they need to be strengthened ### Fractal Nature of Actions - In every motion there is the cybernetic process we have to learn as large groups of people, and each of these contain opportunities for capture - Several wargames to think about capture scenarios - *Fractal and recursive nature of actions* came from conversation with [Tracheopteryx](https://twitter.com/tracheopteryx) - Hope that the Anticapture framework can become a shared vernacular and understanding where folks can discuss topics with a shared language - Evolve to a community-driven framework with potentially a "Wiki style" with bi-directional links - Creating a Wiki that's hosted on Radical that folks can fork and read there and establish a shared vernacular and shared language that we all can reference as we engage in a larger conversation ## The Execute Phase - **Question**: How does the need for consensus relate to the decision making processes? - Anticapture creates the linguistic tools to describe this in a non-prescriptive way - Focusing on **first principles** so that folks can build things that make sense without having the framework proscribed *to* them - Most important phase for capture resistance: if someone has unilateral power to execute it doesn't even matter if there was discussion in the *Decide* phase - Execute phase is most vulnerable to capture for this reason, so it is critical that executive power is decentralized, distributed, and autonomous (can't be changed by an outside actor) - Distribution of power (decentralization) is one of the most impactful ways to resist capture threats *from within* the organization - Accountability is another approach - Delegation can happen provided that there is a degree of accountability - Consensus can be more splintered as long as there is accountability - Levels and layers of capture risk - If someone has all the executive power, then there is already a huge degree of capture - Even if this is distributed, there could then be a potential risk where influentional folks are able to influence and capture (in either Decide or Evaluate Phases) - Domains of influence with regard to *who* can *do what* - One reason DAOs have taken off because governance and finance (treasury) are two very high consequence domains in executive power and smart contracts automate to remove need for trusting single actors with these processes ### The Evaluate Stage - Potential attack vector that takes less forcefulness to do - If able to understand *how* a community comes to understand where consensus will happen and if it's good or bad - This can occur even in DAOs where folks have force of reputation or charisma and can drive the agenda even without abusing smart contracts - 🌱 "The evaluate stage is the propaganda stage." 🌱 - Layers of capture risk: Executive power is the most impactful and we protect against this by *distributing executive power* but can still have people *influencing* others for their own agendas and capture what's going on that way (in Decide or Evaluate phases) - *Question*: What defines the people who are able to make a decision for a DAO? What happens if half the DAO disagrees -- who decides what decisions should and shouldn't be made? - Depends on the DAO protocol and which stage the decision making is happening - Usually this degree of split is an exception in DAOs - If someone makes a decision and then onboards others onto the decision, who decides what direction the DAO takes? - Nobody and everyone -- there isn't a single person who can say who has power - We need to aggregate all of our signals into one - One way that this can happen in Moloch DAOs: things are discussed in prior stages and there is often a high degree of consensus even before proposals - If there is a 50/50 split on a proposal, there are a few things that can happen: - Put the proposal to the DAO: Every person in the DAO can vote with their weight - If there's a huge split (such as 50/50) then there could potentially be Rage Quitting and a fork where they create another DAO aligned with their values ## Permission and Permissionlessness and Governance - Moloch DAOs have a reasonably unique feature in that they're *permissioned* and the question of *who gets to decide things* is a lot easier in a permissioned DAO - There are tradeoffs here -- lots of great things about being *permissionless* participation environment, but a tradeoff is that the game theory becomes more difficult to reason about since you're in an adversarial environment - For example, one person onboarding others to swing sentiment toward their favorable outcome is possible in a *permissionless DAO* and this is then a capture vector that those types of DAOs need to be aware of - *Question*: How could a C-Corp structure work as a DAO? - DAOs are flexible, and ultimately are a tool for serving the needs of the community - Yeeter platform as an example: - Folks are joining a DAO through some kind of a Stake and then getting Loot (non voting share) - Allows for Shareholders (Board of Directors -- managing proposals) and also can incorporate Loot (via a Snapshot, for example) - [LexDAO GitHub](https://github.com/lexdao) has resources that can be helpful here - *Question*: Are DAOs Democracies? - Ultimately up to whoever set up the DAO -- could go highly democratic such as "one person one vote" and DAOs can have different intents such as being product focused or process focused - Comparing DAOs to governments where there are lots of different government structures. How do DAOs relate to democracy? - Can you have a system that is democratic some time but also reverts to non-democratic when the stakes change? Are there ways to change governmental structure? - This itself could be an exciting topic for discussion - There is a perception that DAOs are *plutocratic*, but it's open to interpretation - For DAOs with token voting: Whoever has the most tokens has the most power, and tokens be purchased, but this is often a two body structure: - Typically has multi-sig signers vs. token holders - DAOs are even better than democracy because they're composable ## Current Events - Anytime someone has a token or an NFT they feel like they're in a DAO which is interesting if the community is forming for a purpose, but what happens when there is an NFT reveal and everyone is upset that it didn't meet their expectations? - Is there something here? Should folks have exit rights after reveal? Was there malice behind this or was it incompetence? - This is a form of capture even if it was unintentional - In one sense it's "buyer beware," but could also provide an exit opportunity for buyers who don't like what is delivered - **Asset capture vs. ideological capture** - Rage Quit refund policy (for NFT reveals) - Ukrainian token drop: - Hinting at a token drop where there could have been the first *state sponsored DAO* but then they changed their mind and moved away from the token drop. What happens if people want a refund? Is this a form of capture? - Element of reputational risk, but this is reasonable when your existence is at risk - 🌱 "This space has created a culture of distributed power -- a DAO culture -- but unless we embed that culture and those concepts and that philosophy into the structure and technology of what we're using, then that culture will be captured by other people who swarm in and call things 'DAOs' that aren't really DAOs and do other things to rug other people or capture organizations." 🌱 - Imperative that we get better and more explicit about how we're distributing power in a structural way and not just a cultural way - Having a mission that is anticapture is critical, as are the linguistic tools for different stakeholders - There is a lot of cultural and intellectual values, but we need to *ensure that these are ingrained in the tools* where we don't need to completely rely on each other

    Import from clipboard

    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 lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    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

    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

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    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

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    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. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        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
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

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

        Syncing

        Push failed

        Push successfully