adding governance docs (#469)

* adding governance docs

* typos

---------

Co-authored-by: “Max <“[email protected]”>
Co-authored-by: Thomas <[email protected]>

docs/gov/governance/collective.md

@@ -0,0 +1,54 @@
+---
+sidebar_position: 1
+description: Obol Collective Overview
+---
+
+# Collective Overview
+
+## Purpose 
+
+The Obol Collective’s governance system has two primary goals:
+
+1. **Resource allocation.** Allocate resources effectively to support the Collective’s vision and grow the Obol Collective's sustainable value. Long-term vision may sometimes conflict with short-term value creation; thus, governance requires a blend of short-term and long-term thinking to allocate the token treasury and protocol revenue effectively.
+2. **Capture resistance.** Governance plays a key role in securing the anti-capture and censorship resistance of the Obol Collective. Governance should: 
+    1. make it possible for operations to continue over the long term without reliance on any individual entity;
+    2. prevent any one entity or small group of entities from being able to control or censor.
+
+## Overview: The Obol Token House and RAF
+
+Two houses govern the Obol Collective: the Token House and the Obol RAF.
+
+In the **Token House,** OBOL Token holders are responsible for submitting, deliberating, and voting on governance proposals using the Governance Portal. Token holders can delegate their OBOL Token voting power to their own address or an eligible third party. Addresses with delegated voting power are called “Delegates”.
+
+In the **Obol Retroactive Fund (RAF)**, OBOL Token Delegates are responsible for allocating funds within the RAF to projects and teams that provide value to the Obol Collective.
+
+All OBOL holders and Delegates are expected to exercise their authority responsibly and follow the Delegate [Rules of Engagement](https://community.obol.org/t/delegates-rules-of-engagement/206) and the general [Code of Conduct](https://community.obol.org/t/code-of-conduct-for-discussion-forum/205) for the forum.
+
+![Goverance Houses](/img/GovernanceHouses.png)
+
+## The Security Council
+
+The Security Council is a committee of multi-sig wallet signers with the power to perform certain emergency actions as delegated to it by the Obol Association. 
+
+The Security Council can execute any software upgrade or perform other emergency actions without delay to respond to a security emergency, should one arise. The Security Council must not use its power to perform Emergency Actions except in a true security emergency, such as a critical vulnerability that could significantly compromise the Obol Collective.
+
+After taking any Emergency Action, the Security Council must issue a full transparency report (at an appropriate time after the security emergency has passed) explaining what was done and why such action was justified.
+
+
+## Administration and Implementation
+
+In all cases, Obol Collective governance is intended to be carried out in a manner consistent with the Delegate [Rules of Engagement](https://community.obol.org/t/delegates-rules-of-engagement/206) and the general [Code of Conduct](https://community.obol.org/t/code-of-conduct-for-discussion-forum/205) for the forum. The Obol Association will steward this process as described below, with the goal of increasingly decentralising its role over time.
+
+The Obol Association, via its governance administrators, will facilitate administration to ensure that anyone may participate thoughtfully in governance. Such administrative services may include:
+
+- Moderation of governance proposals to ensure they are validly submitted and voted upon;
+- Removal of proposals that reasonably appear to be fraudulent, spam-oriented, defamatory, hateful, or otherwise inappropriate or inconsistent with the values of the Collective;
+- Monitoring of votes, voting power, the votable token supply, and voting periods for purposes of determining whether quorums and approval thresholds are met or accurately reflected;
+- Management of mutually contradictory or duplicate proposals that are submitted simultaneously or close to one another;
+- Maintenance of the Governance & RAF Portal;
+- Other tasks that the Obol Association deems appropriate in connection with the above.
+
+Approved governance proposals will be routed to the Obol Association for implementation. Upon receipt of an approved proposal or chosen RAF recipients, the Obol Association will determine whether the proposal is safe, consistent with the purposes of the Obol Collective, and capable of being implemented legally (including potential KYC requirements).
+
+- If it is, the Association will act diligently and in a commercially reasonable manner to consider the proposal for implementation.
+- If it is not, the Association may, at its discretion, remove the proposal for resubmission or implement it with guardrails, coupled with an explanation.

docs/gov/governance/contributions.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 2
+sidebar_position: 6
 description: Earning Obol Contributions
 ---
 
@@ -23,7 +23,7 @@ You can participate in the Obol Contributions Program by:
 
 1. **Running your own DV Cluster**: You can create and manage your own DV cluster using our [DV Launchpad](https://launchpad.obol.org), for example using a [DappNode](https://dappnode.com/). This allows you to directly participate in the network's decentralisation efforts and earn contributions. You can also visit our [Squad Staking](https://squadstaking.com) page for inspiration and to find squad members.
 
-2. **Staking through Staking Partners**: By participating in staking through our partners, your staking rewards will also contribute to the Obol Collective. For the current list of staking partners, please visit [obol.org/contributions](https://obol.org/contributions)
+2. **Staking through Staking Partners**: By participating in staking through our partners, your staking rewards will also contribute to the Obol Collective. For the current list of staking partners, please visit [obol.org/contributions](https://obol.org/contributions).
 
 ## How can I track my contributions?
 

docs/gov/governance/delegate-guide.md

@@ -0,0 +1,44 @@
+---
+sidebar_position: 5
+description: Delegate Guide
+---
+
+# Delegate Guide
+
+## Delegate Rules of Engagement
+
+This document outlines the expectations, responsibilities, and values that should guide interactions within the Obol Collective governance community, including the Obol Forum, Discord, and working group meetings. This Code of Conduct will be reviewed periodically to incorporate feedback and adapt to governance needs. Any changes require community approval through the governance process.
+
+Please review these principles carefully to ensure alignment with the Obol Collective’s vision and commitment to a decentralized and sustainable ecosystem.
+
+Please read the rules of engagement on the forum [here](https://community.obol.org/t/delegates-rules-of-engagement/206).
+
+## **Governance Toolkit**
+
+These tools or their uses may change over time as governance evolves. For example, additional user interfaces dedicated to governance may be developed. Likewise, while voting currently takes place on-chain through the Governance Contract, some successful votes are administered and implemented by the Obol Association, which should not be the case indefinitely.
+
+Please see the toolkit on the forum [here](https://community.obol.org/t/governance-toolkit/207).
+
+## Delegates’ Guide to the RAF
+
+### How to vote in the RAF:
+
+1. Visit the  RAF portal at http://raf.obol.org.
+2. Click the “projects” tab on the top of the page.
+3. Click `+` to add your favourite projects to the Ballot, after reviewing their impact. To examine a project, click anywhere on the project card to open the project details page.
+4. Click on ‘Go to Ballot’ at the top right of the page, which will take you to the Ballot Page, with the projects you have chosen. In the screenshot below, you can see two choices. 
+5. Give each project the desired number of votes, based on your total vote allocation.
+6. Click “submit ballot” and sign the transaction.
+
+### How to evaluate projects
+
+Allocating funding is not a perfect process. You may not feel like an expert on a given project, or it may be challenging to directly compare projects’ impact. Here are some considerations to use throughout the process. 
+
+- **Don’t fake expertise. You are voting for *you* — not for all of the Collective.**
+    You are not individually responsible for knowing everything about every Obol RAF category. Some delegates may be experts in education, while others may be deeply experienced in technical infrastructure. We urge you to share your expertise with others, and where necessary, relying on the expertise of other trusted contributors.
+
+- **Make sense together**
+    Feel free to engage with other contributors and the broader Obol Collective in evaluating project impact.
+
+- **Make holistic impact determinations, but when in doubt, don’t make assumptions.**
+    A combination of data and research should leave you qualified to make an informed decision about a given applicant. Still, there might be some projects whose impact argument is more subjective and hard to quantify (in the education category, for example). Use your gut in these situations, but don’t be *too* charitable with an applicant. If an impact statement seems like a stretch, it probably is.

docs/gov/governance/obol-token.md

@@ -0,0 +1,24 @@
+---
+sidebar_position: 4
+description: The OBOL Token
+---
+
+# The OBOL Token
+
+The OBOL Token is central to the governance and operation of the Obol Collective. It serves multiple purposes that are essential to its functioning.
+
+### Token Utility
+
+1. **Token Governance:** OBOL Token holders delegate their voting power to delegates who participate in the Token House decision-making processes. This includes voting on proposals affecting the Obol Collective’s direction, upgrades, and funding allocations. Read more about the Token House [here](./token-house.md). 
+
+2. **Obol Retroactive Funding (RAF):** Token holders delegate their voting power to Delegates, who vote on the projects eligible for retroactive funding. Read more about the Obol RAF [here](./raf.md). 
+
+3. **Staking**: Plans are in place to build staking for the OBOL Token using the Tally Protocol, similar to UNI Token staking for the Unichain and ARB Token staking. Activation of staking for the OBOL Token is subject to governance approval.
+    1. Staking OBOL Tokens through Tally’s staking module wraps them into a yield-bearing token, stOBOL, preserving governance rights while enabling use in DeFi. In this case, the yield comes from two sources: **token inflation** (new OBOL tokens issued by the protocol while maintaining the 500M cap) and **protocol revenue**. This incentivises using the staking mechanism while ensuring that governance power is retained. Read more on the Tally Protocol [here](https://tally.mirror.xyz/Drw-uvqhUnJLRxg32sV-sqKZ785-AO85FBaCYeXqxhA).
+    2. Delegates who actively participate in governance can receive a **portion of the staking yield** as payment for their service. This creates a system where both individual stakers and governance delegates are rewarded, aligning incentives for robust participation.
+
+4. **Restaking**: Plans are in place to list the OBOL Token on restaking platform such as Eigenlayer and Symbiotic to allow AVSs and the Obol Collective to leverage the security provided by restaked OBOL Tokens. 
+    1. Restaking takes the stOBOL Tokens from Tally’s staking module described above and uses them in additional protocols, such as Symbiotic or EigenLayer. The yield here is protocol-specific, often derived from fees, rewards, or staking incentives within those secondary protocols. However, restaking introduces added risk, such as slashing, if the protocol’s conditions aren’t met, whereas staking does not have these risks.
+    2. Activation of restaking for the stOBOL Token is subject to governance (both on the Obol Collective side but also the restaking platform, if relevant)
+
+5. **DeFi:** Plans are in place to launch several DeFi avenues for the OBOL Token post-TGE, such as liquidity pools and lending protocols.

docs/gov/governance/raf.md

@@ -0,0 +1,63 @@
+---
+sidebar_position: 3
+description: The RAF
+---
+
+# The RAF
+
+Obol’s Retroactive Funding (RAF) mechanism is designed to strengthen and promote the decentralisation of Ethereum's settlement layer by rewarding projects that add value and drive impact for Ethereum’s decentralisation. Read more about the Obol RAF [here](https://blog.obol.org/1-percent-for-decentralisation/).
+
+Voting and funding distributions occur over a series of **Obol Retroactive Fund (RAF)** rounds, with OBOL token Delegates determining how funds from the RAF are allocated.
+
+## Overview of the Obol RAF:
+
+- Any Obol Collective project can make an application.
+- OBOL Token Delegates vote on applications proportional to their delegated power and using [quadratic funding](https://qf.gitcoin.co/).
+- The Obol RAF rounds occur at intervals and include phases for scoping, application creation, application review, voting, and funding distribution.
+- The Obol Association will collect information from projects to distribute grants, including KYC, where required.
+
+### Step 1: Scoping
+
+The scope of the round’s impact and the amount of funding to be allocated is defined by the Obol Association at the outset of the round and posted on the Obol Forum.
+
+### Step 2: Application Registration
+
+Projects are invited to create an application on the RAF Portal. Any project or team can apply, but in the future, governance may decide that an application needs to be made by someone holding a minimum amount of OBOL tokens.
+
+To apply for the Obol RAF, projects can create an application on [raf.obol.org](http://raf.obol.org/) by following these steps:
+
+1. **Create an Application:** Fill out the application form using the RAF Portal.
+2. **Describe Impact:** Specify the category of the project and its impact.
+
+### Step 3: Application Review
+
+A subset of OBOL Delegates appointed by the Obol Association reviews applications to ensure compliance with the application rules.
+
+The Obol Association will also review applications to filter out spam or applications that do not align with the mission of the Obol Collective.
+
+### Step 4: Voting
+
+OBOL Delegates vote on projects in proportion to their voting power. Here’s how it works:
+
+1. **Eligibility:** Every address that has been delegated voting power by OBOL Token holders can submit votes.
+2. **Voting Process:** Delegates vote using the [raf.obol.org](http://raf.obol.org) app. Depending on the type of application being reviewed, a specific set of criteria should be used to judge a project's contributions to the Obol Collective.
+
+:::warning
+The Obol Association will monitor votes to ensure contributors are not voting for projects they are directly involved in or where a substantial conflict of interest may be present. Delegates are expected to act in accordance with the Delegate [Rules of Engagement](https://community.obol.org/t/delegates-rules-of-engagement/206) and the general [Code of Conduct](https://community.obol.org/t/code-of-conduct-for-discussion-forum/205) for the forum.
+:::
+
+### Step 5: Tallying Results
+
+The voting power of each OBOL Token Delegate is proportional to the amount of OBOL tokens delegated to them. However, the funding results are calculated using [quadratic funding](https://qf.gitcoin.co/), meaning that the square root of the votes is used to determine the final allocation. This approach ensures a broader distribution of funding across the Obol Collective, rather than allowing a small number of winners to dominate.
+
+### Step 6: Compliance
+
+The Obol Association will review the list of selected projects, adjust if necessary and collect information from them to distribute the grant legally compliantly (including completing KYC if required).
+
+### Step 7: Funding distribution
+
+The overall reward amount for the round is divided among the winning projects based on the delegates' vote and allocation according to the quadratic funding mechanism.
+
+### **Step 8: Community retrospective**
+
+After each round, The Obol Association will conduct a retrospective and gather community feedback.