PA/vPA Operations Treasury
      • 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
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners 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
    • 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 Help
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
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners 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
    What is a Trustee? === ### A Trustee Onboarding Page :::info A **trustee** of the side-treasury ecosystem is responsible for contributing to monthly reporting to Catalyst, managing a key to the multi-sig treasury wallet, approving charters of Governing Bodies to further distribute governance alongside approving of community submissions for revisions to side-treasury governance, and facilitating communication with any governing bodies that they represent. ::: ## Accountability Trustees show accountability by - Updating the community via written or oral reports to the Board of Trustees on a regular basis. - This can be as simple as sharing the efforts and deliverables of a Working Group or Committee with other trustees in a monthly async meeting. - These reports are used to assemble the monthly Catalyst Coordinator report for the proposal funding that funds the side-treasury. ## Security and Alignment Trustees are each given a key to the multisig Roundtable wallet. Every treasury transaction that has been referred to the trustees from Working Group accountability models, or from a community vote for a claim against the treasury, requires a consensus vote by the trustees to release the funds. This is done by - Check the claim or funding request for evidence of following prescribed treasury processes of review and discussion. - Check that the claim or funding request has been "approved" by the community. - Discuss with other trustees whether the funding request or claim meets criteria described in the following sections of the Governance Framework: - [4.0 Purpose](/Zq6KbmZVSoSbP7iNmWoRCQ) - [5.0 Scope](/wHmECtv5TFqVnH8dCbkHNw) - [6.0 Objectives](/0H3HNj-mTGiWOMnz4VcK4w) - [7.0 Principles](/FTugLcJ4TuCz0z4vN4hVyg) - Vote to establish consensus on whether all of the above thresholds have been met. - Collaborate with the rest of the Board of Trustees to "Turn the Keys" and release funding. :::danger Note that the community should have already submitted one or more reviews using the **[Review Criteria](https://hackmd.io/@PA-vPATreasury/Bk-NHxPHi)** which should have addressed these points, but the final responsibility for the accuracy of that analysis rests with the Board of Trustees. ::: Trustees also achieve Security and Alignment by considering and approving the charters of Working Groups and Committees that form under this Governance Framework. They do this by: - Reviewing the submitted charter and checking that it has used the proper [Charter Template](https://hackmd.io/@PA-vPATreasury/B1Eicv0Qs). - Checking that the charter meets the requirements set forth in the [Governing Bodies Policies](/XY7-3dwHTamw3FyOCWW2Rw). - Checking that there has been adequate discussion of the charter by the community and that any concerns raised have been addressed. - If the above items are satisfactory, the Board of Trustees should vote to establish consensus on the approval and acceptance of the charter. - If accepted, the current version of the charter should be added to the [Governing Bodies](/wQm0zkflSNmmrRCwolZQsA) master list. ## Liveness :::info **Liveness** here refers to the treasury community providing feedback and updates to all side-treasury documentation, processes and roles. All side-treasury documentation exists in a format that allows for an "always on" commenting and feedback function that collects real-time suggestions from the treasury community. ::: Trustees encourage and enable liveness in the side-treasury ecosystem by meeting regularly to go over any suggested changes to side-treasury governance and the discussions surrounding them. These are typically submitted as comments on documentation, feedback received via messaging channels, or via formal submissions called Treasury Improvement Proposals (TIPs, modeled on Cardano CIP_001). To establish a path forward for any suggestion, Trustees should: - gather information and resources to inform any decisions regarding a suggested revision. This could be a task assigned to the community, or to a working group or committee chartered under the side-treasury. - Present a formal version of the revision to the community for the purpose of discussion and voting. - hold a special meeting of the Board of Trustees to gather trustee consensus on proposed revisions, and to announce when and where the revision will be applied. - Familiarize themselves with section **[9.0 Revisions](/LuYNF9g9QEKmQ_cGywIUJg)** of the Governance Framework. ## Reciprocity All trustees should act as liaisons between their respective working groups or committees and the Board of Trustees. This means sharing information freely when asked, and preparing written or oral reports if requested. In this way, all governing bodies of the side-treasury should be able to stay up-to-date on the balance of effort and funding occurring among all other bodies. Trustees should - encourage decisionmaking and responsibility arising from areas outside of their own groups - submit reports when requested from other trustees - stay up to date on all deliverables and tasks arising from their group or committee, including all task forces organized under a working group ## Guiding Principles Trustees should familiarize themselves with the **[Qualities of Distributed Leadership](/7lEf9w6WRXeaNaT8TJnAZA)**, specifically the principles outlined within: - **Foster Self-organization** - Each group the trustee's represent is a source of dynamic ideas and leadership. Trustees should encourage others to develop their own processes, tasks and collaborations. - **Promote Emergence** - Trustees should strengthen connection between themselves and others, rather than multiply connections. - Trustees should also ask good questions and provide space and time to listen. - As well, Trustees should embrace learning and adapting, from their own groups as well as other's. Act - Learn - Fail - Do Better is the standard, not perfection. - **Embrace Change** - Mentor others and share responsibility, and if you spot critical functions in your group, encourage others to learn and duplicate these functions. - **Hold Dynamic Tension** - Where there is disagreement try to adopt "and-both" thinking and empower both sides of the issue to fully present themselves for consideration. ## A Sustainable Behavior Model Even successfully sharing the responsibilities above, there is no doubt that trustees have plenty to do to help steward successful outcomes for the side-treasury community and the larger ecosystems they participate in. Trustees should recognize: - That part of the responsibility to health of a community or system is *health to the individual*. Take care of yourself first. - That the pace of Catalyst can be unnatural and overwhelming. Don't let these rhythms impose themselves artificially on you or others. Take time to rest and take breaks when needed, and respect this need of others. - That dedicated time for reflecting, revisioning and orienting is positive and should be encouraged. Adaptive systems need rest, too. #### Back to Board of Trustees [⬅️](https://hackmd.io/@PA-vPATreasury/SynfeL8Xo/https%3A%2F%2Fhackmd.io%2F%40PA-vPATreasury%2FrkgLLECms)

    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