ObolNetwork · slugmann321 · Jan 27, 2025 · Jan 22, 2025 · Jan 22, 2025
diff --git a/docs/gov/governance/collective.md b/docs/gov/governance/collective.md
@@ -51,4 +51,10 @@ The Obol Association, via its governance administrators, will facilitate adminis
 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.
+- If it is not, the Association may, at its discretion, remove the proposal for resubmission or implement it with guardrails, coupled with an explanation.
+
+## Vision for Fully On-Chain Governance
+
+Once Collective’s governance develops and is deemed as sufficiently mature by the Obol Association, the implementations of passed proposals will follow full on-chain execution, where possible. Instead of the Collective’s reliance on the Obol Association for implementation, passed proposals will be moved to a queue to prepare for execution. The queue action will send the proposal to a Timelock contract, which starts a countdown until the proposal can be executed. 
+
+Executing a proposal will run its function calls on-chain. Each proposal can be associated with one or more function calls. These calls will perform actions such as transferring assets from the treasury, updating the Governor's parameters, or calling another smart contract.
diff --git a/docs/gov/governance/delegate-guide.md b/docs/gov/governance/delegate-guide.md
@@ -19,39 +19,7 @@ These tools or their uses may change over time as governance evolves. For exampl
 
 Please see the toolkit on the forum [here](https://community.obol.org/t/governance-toolkit/207).
 
-## Delegates’ Guide to the RAF
+## Delegates’ Role in the RAF
+The role of Delegates in the RAF is to allocate votes to projects that have made substantial positive impact on the Obol Collective’s Decentralized Operator Ecosystem. Vote allocation is proportional to the Delegates’ delegated power. To determine the funding amounts, the [quadratic funding](https://qf.gitcoin.co/) mechanism is used, to ensure a balanced and equitable distribution of influence.
 
-### How to vote in the RAF:
-
-1. Visit the  RAF portal at http://raf.obol.org. You will see information about the current or upcoming RAF round.
-
-![RAF Portal Homepage](/img/RAFPortalExplainer1.png)
-
-2. Click the “projects” tab on the top of the page. Here you see the projects applying to the current RAF round and that have been approved. 
-
-![RAF Portal Projects Page](/img/RAFPortalExplainer2.png)
-
-3. Add projects to your Ballot after reviewing their impact. (To examine a project, click anywhere on the project card to open the project details page.) Then, click on ‘View Ballot’ to visit the Ballot Page.
-
-![RAF Portal Project Selection](/img/RAFPortalExplainer3.png)
-
-4. The Ballot Page shows the projects you have chosen. Enter the desired number of votes for each project, based on your total vote allocation. Click “submit ballot” and sign the transaction.
-
-![RAF Ballot Review](/img/RAFPortalExplainer4.png)
-
-5. Once the RAF round is over, you will be able to see the results by clicking on the "stats" button at the top of the portal. 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, 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.
-
-![RAF Round Stats](/img/RAFPortalExplainer5.png)
-
-### 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.
+Visit read [the delegate guide](https://community.obol.org/t/delegate-guidelines-raf1/229) on the forum.
diff --git a/docs/gov/governance/raf.md b/docs/gov/governance/raf.md
@@ -11,7 +11,7 @@ Voting and funding distributions occur over a series of **Obol Retroactive Fund
 
 ## Overview of the Obol RAF:
 
-- Any Obol Collective project can make an application.
+- Any project that meets the RAF round’s criteria 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.
@@ -26,11 +26,11 @@ The scope of the round’s impact and the amount of funding to be allocated is d
 
 ### 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.
+Projects are invited to create an application on the [RAF App](http://raf.obol.org/). 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.
 
 Once a RAF round is opened, 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.
+1. **Create an Application:** Fill out the application form using the [RAF App](http://raf.obol.org/).
 2. **Describe Impact:** Specify the category of the project and its impact.
 
 ### Step 3: Application Review
@@ -64,4 +64,8 @@ The overall reward amount for the round is divided among the winning projects ba
 
 ### **Step 8: Community retrospective**
 
-After each round, The Obol Association will conduct a retrospective and gather community feedback.
+After each round, The Obol Association will conduct a retrospective and gather community feedback.
+
+## Guides for each Round
+
+RAF1: see the [RAF1 guide](https://community.obol.org/t/guide-for-raf-round-1-raf1/227) in the forum. 
diff --git a/docs/gov/governance/token-house.md b/docs/gov/governance/token-house.md
@@ -5,7 +5,7 @@ description: The Token House
 
 # The Token House
 
-In the Token House, OBOL Token holders are responsible for submitting, deliberating, and voting on various Obol Collective governance proposals. They may do so by directly voting with their OBOL Tokens (by delegating the voting power of their OBOL tokens to their own address) or by delegating their OBOL Token voting power to an eligible third party. Addresses with delegated OBOL voting power are called “Delegates”.
+In the Token House, OBOL Token holders are responsible for submitting, deliberating, and voting on various Obol Collective governance proposals.
 
 ## Overview of the Obol Token House
 
@@ -34,6 +34,22 @@ All governance proposals must fall within one of the following categories:
 - Work agreements
 - Veto on the Obol RAF operations
 
+The different requirements for submission and approval of each Proposal Type are summarized below. If a specific template is not specified below, proposals should follow this standard proposal template.
+
+All Ecosystem grant applications are processed by the Association.
+
+Below are listed types of Token House Proposals. Each has a two-week review period plus one week voting window, with an approval threshold of 51%.
+
+| Proposal Type | Description | Submission Requirements              |
+|:------------:|:---------:|:------------------|
+|Ecosystem grants|The Obol Association’s treasury may be used to support development of the Collective and/or growth of the ecosystem via the proposal template.|Forum proposal + On-Chain Voting|
+|Token inflation adjustment|Changes to the OBOL Token Contract or its supply.|Forum proposal + On-Chain Voting|
+|Treasury Appropriations|The amount of OBOL Tokens the Obol Association may spend or distribute annually|Proposal initiated by the Association + On-Chain Voting|
+|Work agreements|Formal arrangements between the Obol Association and contributors, teams, or organizations tasked with advancing specific initiatives or responsibilities within the ecosystem|Forum proposal  + On-Chain Voting|
+|Veto on the Obol RAF operations|The veto mechanism serves as a safeguard against decisions or actions within the RAF operations that are misaligned with the mission of decentralization, transparency, or the collective interests of the community.|Forum proposal + On-Chain Voting|
+|Protocol upgrades|Scheduled changes to the on-chain smart contracts comprising the protocol or governance contracts.|Forum proposal + On-Chain Voting|
+
+
 ### Weeks 1-2: Feedback and Review
 
 All proposal types should be posted to the Obol Forum for review. Proposal authors are expected to respond to feedback from Obol Collective members and Delegates.

diff --git a/versioned_docs/version-v1.2.0/gov/governance/collective.md b/versioned_docs/version-v1.2.0/gov/governance/collective.md
@@ -51,4 +51,10 @@ The Obol Association, via its governance administrators, will facilitate adminis
 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.
+- If it is not, the Association may, at its discretion, remove the proposal for resubmission or implement it with guardrails, coupled with an explanation.
+
+## Vision for Fully On-Chain Governance
+
+Once Collective’s governance develops and is deemed as sufficiently mature by the Obol Association, the implementations of passed proposals will follow full on-chain execution, where possible. Instead of the Collective’s reliance on the Obol Association for implementation, passed proposals will be moved to a queue to prepare for execution. The queue action will send the proposal to a Timelock contract, which starts a countdown until the proposal can be executed. 
+
+Executing a proposal will run its function calls on-chain. Each proposal can be associated with one or more function calls. These calls will perform actions such as transferring assets from the treasury, updating the Governor's parameters, or calling another smart contract.
diff --git a/versioned_docs/version-v1.2.0/gov/governance/delegate-guide.md b/versioned_docs/version-v1.2.0/gov/governance/delegate-guide.md
@@ -19,39 +19,7 @@ These tools or their uses may change over time as governance evolves. For exampl
 
 Please see the toolkit on the forum [here](https://community.obol.org/t/governance-toolkit/207).
 
-## Delegates’ Guide to the RAF
+## Delegates’ Role in the RAF
+The role of Delegates in the RAF is to allocate votes to projects that have made substantial positive impact on the Obol Collective’s Decentralized Operator Ecosystem. Vote allocation is proportional to the Delegates’ delegated power. To determine the funding amounts, the [quadratic funding](https://qf.gitcoin.co/) mechanism is used, to ensure a balanced and equitable distribution of influence.
 
-### How to vote in the RAF:
-
-1. Visit the  RAF portal at http://raf.obol.org. You will see information about the current or upcoming RAF round.
-
-![RAF Portal Homepage](/img/RAFPortalExplainer1.png)
-
-2. Click the “projects” tab on the top of the page. Here you see the projects applying to the current RAF round and that have been approved. 
-
-![RAF Portal Projects Page](/img/RAFPortalExplainer2.png)
-
-3. Add projects to your Ballot after reviewing their impact. (To examine a project, click anywhere on the project card to open the project details page.) Then, click on ‘View Ballot’ to visit the Ballot Page.
-
-![RAF Portal Project Selection](/img/RAFPortalExplainer3.png)
-
-4. The Ballot Page shows the projects you have chosen. Enter the desired number of votes for each project, based on your total vote allocation. Click “submit ballot” and sign the transaction.
-
-![RAF Ballot Review](/img/RAFPortalExplainer4.png)
-
-5. Once the RAF round is over, you will be able to see the results by clicking on the "stats" button at the top of the portal. 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, 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.
-
-![RAF Round Stats](/img/RAFPortalExplainer5.png)
-
-### 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.
+Visit read [the delegate guide](https://community.obol.org/t/delegate-guidelines-raf1/229) on the forum.
diff --git a/versioned_docs/version-v1.2.0/gov/governance/raf.md b/versioned_docs/version-v1.2.0/gov/governance/raf.md
@@ -11,7 +11,7 @@ Voting and funding distributions occur over a series of **Obol Retroactive Fund
 
 ## Overview of the Obol RAF:
 
-- Any Obol Collective project can make an application.
+- Any project that meets the RAF round’s criteria 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.
@@ -26,11 +26,11 @@ The scope of the round’s impact and the amount of funding to be allocated is d
 
 ### 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.
+Projects are invited to create an application on the [RAF App](http://raf.obol.org/). 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.
 
 Once a RAF round is opened, 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.
+1. **Create an Application:** Fill out the application form using the [RAF App](http://raf.obol.org/).
 2. **Describe Impact:** Specify the category of the project and its impact.
 
 ### Step 3: Application Review
@@ -64,4 +64,8 @@ The overall reward amount for the round is divided among the winning projects ba
 
 ### **Step 8: Community retrospective**
 
-After each round, The Obol Association will conduct a retrospective and gather community feedback.
+After each round, The Obol Association will conduct a retrospective and gather community feedback.
+
+## Guides for each Round
+
+RAF1: see the [RAF1 guide](https://community.obol.org/t/guide-for-raf-round-1-raf1/227) in the forum.