DecentralizeSDGs
    • 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 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

    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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    #Decentralized SDG Impact ## Case 4: TEC Praise System (Team 11) #### Data Repository: https://github.com/CommonsBuild/IH-intervention ## Data ![](https://i.imgur.com/R3SY8cx.png) ![](https://i.imgur.com/DEwp6g4.png) ![](https://i.imgur.com/bK3NWgO.png) #### Reflection questions: * Descripe the tools & process you used: Want to raise the question if Excel though data visualization may sufficient in standard tools such as PowerBI or Tableu to have clarity on distribution that is easily digestible and not overengineered. * Any challenges / difficulties (i.e. dataset issues, definitions): Unstructured data as there was no established categorization at the oneset. Quantification was conducted without a clear methdology. * Is there any raw data missing that might be interesting to analyze? DAO's are digital architecture that are intended to incubate and nourish resilient communities. The design of DAO architecture and its value allocation system can act as an enabling environment for equitable inclusion that optimizes the sustainable development of that community and the greater communities in which it interacts. The TEC follows the principles of Elinor Ostrom and thus rewards systems should have Ostrom best practice in the design. In an updated TEC Praise data strategy the following data points would have provided a more granular view of the Praise system in support of a fair, equitable and consistent distribution. - Working Group Identification - Category of work (i.e. Comms, Development, Design, etc.) - Deliverable and project identifier - Supporting Praise (validated by others) - Qualitative aspects it supports (i.e. Culture, Motivation, Inspiration, etc.) - Priority and weight of Praise - Spend limits of Praise giver - Budget of allocated Praise pool - Users provided targets (goals and areas for improvement that allows personalized areas for personsal growth) * Which datapoints do you think are relevant to measuring system health? Allowing for qualitative measurement in a quantitative manner that is viewed by the community as fair, equitable, consistent and representative of the community values that it supports sits at the core of any successful rewards system. As Praise is ultimately calculated into Impact Hours that have financial implications it should be viewed as a community resource and therefore Ostrom's principles on how that scare community resource is managed should be applied. The value of Praise should be consistent. This could be supported by an ontology and an accompanying methodology that measures that aspects that the community values in a manner that is equitable and inclusive. ## Taxonomy considerations for token engineering rewards systems in labor DAOs ![](https://i.imgur.com/KEyFjJJ.png) ## Evaluation of TEC Praise on Elinor Ostrom's Principles - **Clearly defined boundaries** - Praise resource (xDAI) available to Praise appropriators was not defined at the onset. Post hoc vs. ex ante. - Who had access to appropriate Praise resources was neither based on eligibility criteria or delegated formally by community through an established process. Self appointment vs. due process - Specified community of benefit (targeted rationale) for Praise allocation undefined. - **Congruence between appropriation and provision rules and local conditions** - Guidance note on Praise that would be validated by TEC community - Methodology of Praise - Guidance Note Categorization of Praise - Guidance Note Quantification of Praise - Data Strategy - **Collective choice arrangements** - TEC Priase was retroactively modified through collective choice (Snapshot vote) which allowed for post hoc choice but not ex ante community driven policy - **Monitoring** - Compliance with rules that can be monitored at low cost and performed by members of the community in transparent ways requires that the rules are clear. Here the monitoring mechanism is strong from a transparency perspective but the rules upon what is being monitored are not firmly established, thus compliance is assessed against what standards. - **Graduated sanctions** - Similar to monitoring the issue of graudated sanctions requires that there are clear rules upon which can be broken. However, as Praise had not set criteria it would be hard to escalate to a graduated sanctions mechanism unless there was some egregious behavior that would break general principles (self-dealing, fraud, collusion, etc.). - **Conflict resolution mechanisms** - The Praise system implementation in the TEC Hatch did result in some community dispute. The resolution of this dispute was not channeled through Celeste as similar to graduated sanctions and monitoring there were no written rules upon which resolution could be based. Instead a vote was taken through Snapshot that did not adjudicate the dispute but mediated a consenus oriented solution. This has benefits for post-hoc solution but does not address the ex-ante prevention of conflict. - **Minimal recognition of rights to organize** - In this regards there is much praise for TEC Praise as it is very individual based. However, this right of autonomous organization comes with it the obligation that the other Principles of Elinor Ostrom establish so we - **Nested enterprises** - Praise was fully decentralized and not in nested enterprise which would have aligned more with established working group structures, community inititatives, etc. ## Risk Assessment - Unsustainable appropriation of community resource Ostom's non-compliance - Misalignment of Praise with community desired outcomes - Reward system incentivizes low value activities - Game theory negative feedback loop on dissent and discourse - Prone to collusion hacks and other self-interested misappropriation ## Theory of Change - General process ![](https://i.imgur.com/uhiMcSE.png) ## Schematic Depiction of Theory of Change Implementation ![](https://i.imgur.com/Vszb9oC.png) ## Data Driven Praise System Considerations - Measurements in TE Commons - Deliverables - Submission Targets - Activity Time - Value Contribution & Validation - Community Prioritization & Weights - Risk Matrix - Ethos Alignment Indicators - SourceCred Compatable ![](https://i.imgur.com/vP0qmjs.png) ## Considerations for Safeguarded Mission Rewards Align with Ostrom's Principles - Defined budget of Praise, sub-categorized by Working Group or other community decided category structure - Community endorsed Praise policy with methodology for Praise giver selection, Praise appropriation and allocation, compliance monitoring, and evaluation of results. - Appointment of Praise allocators and quantifiers through participatory community mechanisms (i.e. nominations, vote, etc.) - Rights and obligations of delegated Praise appropriators, quantifiers, recipients defined

    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