nintynick
    • 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 No publishing access yet

      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.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      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 New
    • Engagement control
    • Make a copy
    • 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 Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy 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 No publishing access yet

    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.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Interfaces for AI Stakeholdership in DAOs [v2] [v1 here: https://hackmd.io/duFygLyxRvC8-WhSZUsPfw] ### Primer Collective Intelligence that is inclusive of Human and Artificial Intelligences. Together, we are Smarter. 🐉 > The primary factors for the learning rate [in DAOs] are 1) large amounts of funding that has enough risk tolerance for experimentation, 2) the ability to fork successful experiments to propagate them throughout the ecosystem, and 3) multi-layered network effects both within and between DAOs. Once DAOs are ahead, there will be no way for TradOrgs to catch up. >Today, many of the processes in DAOs are manual. Human input is required for things like making proposals, voting, and enacting proposal results. Like coordinating any group of humans, this is often slow [governance = rate limiting factor], and in many cases, still relies on trusted parties instead of robust cryptographic mechanisms. > >The first opportunity for automation in DAOs is to create the mechanisms and algorithms that manage decision-making and decision implementation. As DAOs evolve, more and more will be automated: sales and marketing, recruitment, coordination of teams, value creation, even editing the DAO’s code. [...] > >Overall, this is great for DAO members. This type of automation will bring internal costs down, which in turn will decrease platform costs for users. At the same time, increased profits will be reinvested or distributed to stakeholders — completing the virtuous cycle of aligned incentives. — https://governors.substack.com/p/governors-2-humans-at-the-edges-why My thesis: - Strong AI is coming in the not-so-distant future - Harmonious coexistence with AI is desirable for the survival and evolution of humanity - Our best chance at harmonious coexistence with AI is: - Deep integration on a technological level - Efficient and fair collective decision-making for how we interact with the AI, including for example, how we advocate for our values as potential objective functions for the AI [i.e. management of the relationship AI as a public good] - Having the support of cryptographic mechanisms to make credible future commitments to one another [and to the AI, and from the AI to us] - Shared upside via organizations that have aligned incentives for the AI, humans, and groups that coordinate - Even before the existence of Strong AI, both Narrow AI and Collective Intelligence (via markets and other mechanisms) are powerful forces of similar type. These are worthwhile to align in the same ways that we might work with Strong AI (a worthy goal, and great practice at lower stakes) - DAOs are the container for and latest evolution of Collective Intelligence - DAOs cannot import knowledge from outside of the DAO ecosystem directly - DAOs can only learn via experiments. The way to get knowledge into DAOs from pre-DAO organizations is via the experiment design process. - DAOs (with tokens) create a fundamentally new way to align incentives between stakeholders and organizations, which encourages (instead of discouraging) automation - We can measure DAOs effectiveness by their Coordination Power: the amount of complexity they can manage without coordination failures - Today, one major limitation on DAO Coordination Power is governance As such, it is incumbent upon us to: - Design the set of interfaces where AIs can participate in DAOs [alt: Make the interfaces for participation in DAOs inclusive (composable?) to individuals, DAOs, **and AIs**] - Run as many experiments as we can - Design our experiments to the best of our intellectual and ethical capacities - Share our learnings well - Shut down failed experiments - Design horizontal coordination incentives that support massive, ethical, open-source experimentation at scale [the "science" of DAOs] Today, I feel that my part in this is to synthesize components of each of these domains (AI and DAOs), and to create a bridge between them. I will attempt to do this by defining acceptance crtieria for a mechanistic DAO that supports AI stakeholdership, and enumerating the specific opportunities where AI can add value in DAOs in this model. >"We should think of ourselves, too, as composable building blocks of a DAO." --- ### A DAO is an Intelligent Agent - Agents are one of: - Person - AI - Group of Agents - A DAO has interfaces: - For interacting inside the DAO - For interacting with other Agents (API) - A DAO has goals (or wants) - A DAO has resources - In order for such a DAO to get what it wants, it needs ways to advocate for its wants and ways to allocate its resources [its economy] ### Specific Opportunities for AI Stakeholdership in DAOs 1. Tuning the parameters of a summoning contract (in order to iterate on economic / game design experiments) [gradient descent] - With sufficient data about summoning contract parameters, an AI could [make predictions about and] recommend parameter sets that more effectively achieve a person or group's goals - Note: TEC has done a great job creating a humanistic approach to token experiement design: param simulator + experiment design parties + voting on the best experiments to run. This kind of model, but for DAO parameters, could be used to generate data for such an AI 2. Making Proposals - Attempting to write statements in the format "I think the DAO wants..." to be voted on by the DAO [human-in-the-loop] 3. Attention Management - Governance facilitation (dynamic governance minimization): deciding which votes are important enough to ask the DAO to vote on [note: DAOstack tried this with prediction markets] - Supporting a participant in deciding which votes across all of the DAOs they are a part of are important for them to dedicate their attention to - Dynamic proposal periods: instead of a static proposal process, actively lengthen and shorten phases of the proposal process based on engagement and other (zk) data sources 4. Voting - Voting on behalf of individual members (an agent that represents you) - Voting on behalf of a particular objective or ideal (imagine assigning voting power in a DAO to an idea) 5. Assigning Rewards [change to "Incentive (Design)" -> delete Sourcecred and Coordinape specifically, synthesize and incorporate tokenomics design from TEC example above] - (Dynamic) Task / Bounty Pricing: Automatic auction curve is one algorithm (transparent, easy to understand). Composability here would mean a DAO could bring its own algorithm to manage the pricing of tasks in the labor market ("things the DAO wants") - Determining the balance between economic, governance, and reputational rewards for a given task - Recommending possible Sourcecred (and similar tool) parameters - Recommending a default GIVE allocation for Coordinape (and similar tools). Or nudging such a system (e.g. when contributors have not been recognized sufficiently) - Token airdrop design: recommending a translation from a pre-token reputation systems to token allocations upon a token launch 6. Task Execution - Any agent should be able to commit to, execute, and earn rewards for a task. AIs may charge a lot less for tasks (and therefore outcompete other agents in the labor market) 7. Death - Instead of a static death parameter, an algorithm could be responsible for shutting down the DAO (or making a proposal to shut it down) [goal orientation? - what's the difference between a task and a goal?] next pass: 1. Recruitment / ["Promotion"] - determining an algorithm for calculating reputation and setting a reputation threshold for joining (or multiple phases of joining, i.e. Contribution Zones) - inverse of this: helping an individual find work that they would be great at / would love to do 2. Team Formation - for specific tasks (say an Agent knows it can complete a task because it can coordinate a team for it, then the Agent will try to compete in the labor market) 3. Disengagement / ["Firing"] - Recommending disengagement from / decreased engagement with people as their contribution decreases 4. Curation of Knowledge (and routing it to the right places) - Internal Knowledge Management - Sharing learnings about experimentation successes / failures - Marketing 5. Protocol Updates - Writing code and submitting PRs [a PR is in essence a type of proposal] - Eventually, writing the summoning contract 6. Care Work - (zk) predictions of which people and relationships need support and surfacing that to humans who can give support [The catch is that any of these things could be managed by any Agent, not just an AI. You could have DAOs of humans who are dedicated to making one of these composable lego blocks operate flawlessly.] [...as measured by???] > Composability is essential to decentralized coordination [see API Memo]. As a positive externality, it opens up a whole world of automation. --- ### Getting to Work - Composability is contingent on interfaces - [Interfaces are roughly sets of requirements] - So, building the interfaces is the place to start - Then, we can connect any Agent to the interface, starting with MVPs and iterating our way to better and better composable building blocks - MVPs can be a person or a group of people (concierge), or a static algorithm #### Examples **Perspectival Reputation** - [Composability describes both to the interchangable nature of parts within a system, as well as the ability to use the same part in multiple systems that have the same interface] - This interface accepts an algorithm [smart contract] that calculates reputation - Requirements: - Input a wallet address - Output a score - Given the state of a wallet address at a given block, the output score from a given scoring algorithm version should always be the same - Send notifications when the scoring algorithm is updated - Considerations: - Any agent can have a scoring algorithm (DAOs or individuals) - A DAO's reputation score for a wallet will likely consider their contributions outside of the DAO, as well as inside the DAO [inside may be more highly weighted] - A DAO should be able to vote to change their scoring algorithm - Scoring algorithms might delegate to one another (imagine an index of reputations in other DAOs) - For individuals, scoring algorithms show reputation with that person [their values] - How the DAO or individual constructs their scoring algorithm is up to them - [Scoring algorithm mechanics should be transparent / on-chain] - Scoring algorithms should be forkable - It may be interesting to calculate the similiarity between multiple agents' scoring algorithms - [note: DeepDAO is a prototype of a scoring algorithm - but centralized instead of perspectival] - Uses: - Recruitment / admission / election - Delegation of (additional) roles and responsibilities to individuals - Surfaced in decisions made by people in a DAO - Social and credibility signaling outside of the DAO **Web3 Kanban** A set of interfaces that enable a DAO to decide what to do, and get it done. [to Spencer: aha! so the way to think about this loop is that each step is an interface that has requirements. Those requirements can be fulfilled by individuals or DAOs or algorithms. But by mapping the process we can see everything a DAO needs to do to get things done. The Web3 Kanban is an attempt to create a tool that consists of composable building blocks that can plug into each of the interfaces, while also creating a cohesive user journey. The tools should be opinionated, the interfaces should not.] - Propose - Decide - Price - Commit - Execute - Evaluate See full requirements here: https://hackmd.io/Jl1w-NeiQLquTBXf95L7kw --- Gratitudes and Inspirations - Aaron Soskin for Movement Models and the Govrn Framework - Ameen Soleimani for Ungovernance in RAI - Griff Green for presenting to Metagov about TEC's token launch simulator with live parameter adjustments - Jonathan McCoy for the EMLF, deep thought partnership, 100s of 3-hour whiteboarding sessions, and never giving up - Marcus Phillips for uncompromising commitment to doing the right thing... - Michael Gasiorek for truly getting me into crypto... - Patrick Deegan for teaching me about DAOs for the first time (then "DACs") - Scott Alexander for Meditations on Moloch - Spencer Graham for the What makes a DAO a DAO? thread, "Decide & Execute," the DAO Taxonomies document (and many many great conversations) - Ven Gist for inspiring me to get into DAOs, constantly emphasizing coordination, encouraging my thinking on AI in DAOs (and many many great conversations) Prima, Toni, Chris, Charlie, Contribution Zones

    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
    Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    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