DAO Masons
      • 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
    • Engagement control
    • 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 Versions and GitHub Sync Note Insights Sharing URL Help
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
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
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    --- tags: Grant Ships --- # Grant Ships FAQ New to Grant Ships? See the [Overview Document](https://hackmd.io/06-DcdCuQmaBhKKjmlE-LQ) first. ## Reasoning **Q:** **Why not just have a grants council?** We wanted to emphasize a pluralistic approach and avoid centralization of power. Grant Ships unbundles the functions of a traditional, centralized grants-giving committee and distributes power and responsibility among 3 groups: Grant Ships, Referees, and the voting community. Together, these 3 groups have all the power and responsibility of a grants council but ensure a broader representation of perspectives and mitigate the risk of undue influence. However, because many of the relevant permissions and processes are explicitly defined, we offload the governance overhead that a grant-giving organization would normally be responsible for designing. Grant Ships are free to focus on transparently allocating funds. Referees make sure the rules are being followed. Members of Arbitrum DAO need only focus on voting on their favorite Grant Ships and checking power where needed. In essence, we aim to get the best of both worlds. We get the capture-resistance of a decentralized organization, as well as the efficiency and clarity of a traditional structure. Here is a diagram showing how this system could be built: [![Alt text](https://hackmd.io/_uploads/Bkg3a5FNn.png)](https://hackmd.io/_uploads/H1jJ2_NWT.png) While we're mostly agnostic about the tech that each Grant Ship uses, we believe that **Hats Protocol** is an ideal tool for creating the structural 'skeleton' for this system. **Q: This all seems complicated, why not do something simpler?** **A:** The more distributed and decentralized a system is, the more its rules must be explicitly defined. In centralized grant-giving solutions, the complexity is hidden in the internal political dynamics and decision-making processes of the responsible team. By providing this structure for a pluralistic approach, we relieve teams of managing a major portion of the complexity by systematizing it, and then allowing them to focus on the equally complex problem domain which is "How to Give Grants Effectively." ## Hats **Q: Why Hats Protocol?** **A:** Hats Protocol allows DAOs to create organizational structures that are capture resistant, transparent, and efficient. A Hats structure is a network of non-transferable ERC-1155 compatible tokens. They allow a DAO to build a 'tree-shaped' role and permission structure where each token can manage the tokens below it, but not above. Placing the 'Top Hat' on Arbitrum DAO ensures that the ultimate decision-making power is granted to the most decentralized player in this game. By offloading operational authority and responsibility, Arbitrum DAO needn't be burdened with every decision -- only revoking authority when needed. Hats also have the additional benefit of providing an easy map of all the key players involved. Referees, Grant Ships, and Grant Recipients could all be made visible in one live chart that sources purely from on-chain data. ## Details ### Grant Ships **Q: What is a Grant Ship?** **A:** A Grant Ship is a subDAO. It receives funds each season based on its past performance, with the expectation that it will distribute those funds as ecosystem grants. **Q: How are Grant Ships selected?** **A:** When the game first begins, teams can apply to become Grant Ships. A weighted token vote is held, and the top 6 teams are assigned to become Grant Ships. **Q: What powers do Grant Ships have?** **A:** Grant Ships have 2 main powers: Distribution & Disclosure. A Grant Ship receives funding and has permission to distribute the funds. It also can make official on-chain disclosures. **Q: What are the expectations of a Grant Ship?** **A:** Grant Ships can operate however they like but are expected to submit a complete Portfolio Report at the end of a funding season, disclose who they are funding (as the funding occurs), and disclose major internal decisions and announcements on-chain. **Q: What happens if a Grant Ship doesn't meet those expectations?** **A:** The Referee Team assigns the Grant Ship a "yellow flag" (rules violation) or "red flag" (bad faith) that adds context for the end-of-season Ship Ranking Vote. **Q: How does a Grant Ship receive funding?** **A:** In the first season, all Grant Ships receive an equal portion of funding from a Common Funding Pool. In the following seasons, the Grant Ship's portion of the Funding Pool is proportional to their performance in the previous season, relative to other active Grant Ships. **Q: How is Grant Ship's performance measured?** **A:** At the end of each season, each Grant Ship is required to submit a Portfolio Report. Portfolio Reports are ranked during the Ship Ranking Vote at the end of each season. **Q: Why isn't there a set governance structure for each Grant Ship?** **A:** We believe that optimal models for grant distribution have yet to be discovered. Only through experimentation and real-world tests can we begin to narrow in on what might be the best model for a decentralized grants committee. ### Referee Team **Q: What power does the Referee Team have?** **A:** The Referee Team is a group of elected individuals that collectively has permission to assign yellow and red flags to Grant Ships. They can also initiate the Ship Ranking Vote at the end of the season and finalize the results. **Q: What are yellow and red flags?** **A:** Yellow and red flags are attestations issued by the Referee team. They are included as context in a Ship's Portfolio Report. Yellow flags are for rules violations such as failure to meet a reporting requirement. Red flags are issued to teams that have 'abandoned the ship' or are deemed to be operating in bad faith. **Q: What are the responsibilities of the Referee Team?** **A:** The Referee Team is expected to take care of any non-automated administrative or on-chain actions required by the Rule Book. This includes initiating funds disbursal proposals at the beginning of the season and initiating the end-of-season Ship Ranking Vote. They should also note and document any inconsistencies or flaws in the Rule Book and submit them for public review at the end of the season. They are the arbiters and adjudicators of the Rule Book and are responsible for providing interpretations if clarity is lacking. **Q: How is the Referee Team selected and held accountable?** **A:** The Referee team is elected through a volunteer/nomination process followed by a Token Vote. Referees can be replaced at any time through an Arbitrum Token Vote. Referee Team attestations can be contested by any Grant Ship with a counter-attestation. ### Season Cycle ![](https://hackmd.io/_uploads/SJyIDnUNh.png) **Q: What is a Grant Season?** **A:** A Grant Season or Season for short, is a period of 3 months and is broken into 2 phases: the Allocation Phase and the Review Phase. **Q: What happens during the Allocation Phase?** **A:** This is the period where Grant Recipients are funded and begin producing results. This is also where most of the interaction between Grant Ships, Grant Recipients and the community occurs. **Q: What happens during the Review Phase?** **A:** This is the phase where Grant Ships submit their Portfolio Report for review by the community and Referees. A community vote is initiated and the results determine funding levels for the upcoming season. If a crew fails to receive a minimum threshold of support from the community, new crews are onboarded to that ship during this period. ### Reports & Voting **Q: What is included in a Portfolio Report?** **A:** The Portfolio Report should include expenses, funding allocations, and grant recipient progress. A template is provided and Referees review the report before initiating the token vote. Any yellow or red flags assigned by Referees are appended to this report. **Q: How does the Ship Ranking Vote work?** **A:** The Ship Ranking Vote is a weighted token vote that occurs at the end of each season, and is an opportunity for the Arbitrum community to rate and rank the performance of the active Grant Ships. The Portfolio Reports from each Grant Ship are first made available for review. Then, each ARB holder has the opportunity to 'weight' the performance of each Grant Ship. They receive votes equal to their token count and can assign them across the Grant Ships as they see fit. The vote total received by each ship is divided by the total number of votes received by all ships. This number determines the proportion of the total funding pool they receive in the upcoming season. Additionally, any new crew that have applied can receive votes at this time. If an active Grant Ship crew fails to receive a minimum threshold of support, they are evacuated from their ship and replaced with the highest-rated new crew. ### Other Questions **Q: How does the Common Funding Pool receive funds?** **A:** Presumably these funds are being supplied by Arbitrum DAO itself, so whatever process they use to disburse funds would need to be used to fill the pool. The pool could also be opened to receive funds from other sources looking to support Arbitrum Grants. Ideally, this Common Funding Pool would be refreshed each Season automatically. **Q: What if this rulebook has a flaw or needs to be updated?** **A:** During the course of a season, the Referee Team is responsible for adjudicating the rules. If they see an inconsistency or flaw, they have the purview to make adjustments on the fly to maintain the integrity of the game. These issues should be documented and submitted for review at the end of each season. Variables such as the number of Grant Ships, minimum vote thresholds, size of the Referee Team, and funding levels can be set depending on the needs and wants of the community when the game begins. **Q: When does the game end?** **A:** Ideally, a token vote is held to initiate this game and then it would run indefinitely, ended only by a separate successful token vote initiative.

    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