diff --git a/app-developers/tools/data/oracles.mdx b/app-developers/tools/data/oracles.mdx index 91b200abd..77250a0c6 100644 --- a/app-developers/tools/data/oracles.mdx +++ b/app-developers/tools/data/oracles.mdx @@ -136,7 +136,6 @@ Developer teams who want to feature products/tools on this page must meet the fo 3. **actively maintained developer tool** that aligns with OP's commitment to a magical developer experience (e.g., easy-to-use, easy-to-integrate, great DevX, highly-rated by community, etc.) For teams that are supporting but still establishing a user base, we encourage you to share your tool on the [community oracles page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/oracles.md). -You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and sign up to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/?utm_source=op-docs&utm_medium=docs). ## Next steps diff --git a/app-developers/tools/infrastructure/block-explorers.mdx b/app-developers/tools/infrastructure/block-explorers.mdx index 9e749888f..555de841b 100644 --- a/app-developers/tools/infrastructure/block-explorers.mdx +++ b/app-developers/tools/infrastructure/block-explorers.mdx @@ -88,9 +88,6 @@ Developer teams who want to feature products/tools on this page must meet the fo 2. **established user base** and OP ecosystem engagement such as governance participation, [Community Discord](https://discord.gg/optimism) or [Superchain Developer Discord](https://guild.xyz/superchain-devs) participation, etc.; and 3. **actively maintained developer tool** that aligns with OP's commitment to a magical developer experience (e.g., easy-to-use, easy-to-integrate, great DevX, highly rated by the community, etc.) -For teams that are supporting but still establishing a user base, we encourage you to share your tool on the [community block explorers page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/block-explorers.md). -You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and sign up to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/?utm_source=op-docs&utm_medium=docs). - ## Next Steps * Please visit the [community block explorers page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/block-explorers.md) for a listing of third-party block explorers used by the Optimism developer community. diff --git a/app-developers/tools/testing/faucets.mdx b/app-developers/tools/testing/faucets.mdx index f1462a241..9c7f34cc8 100644 --- a/app-developers/tools/testing/faucets.mdx +++ b/app-developers/tools/testing/faucets.mdx @@ -54,9 +54,6 @@ Developer teams who want to feature products/tools on this page must meet the fo 2. **established user base** and OP ecosystem engagement such as governance participation, [Community Discord](https://discord.gg/optimism) or [Superchain Developer Discord](https://guild.xyz/superchain-devs) participation, etc.; and 3. **actively maintained developer tool** that aligns with OP's commitment to a magical developer experience (e.g., easy-to-use, easy-to-integrate, great DevX, highly rated by the community, etc.) -For teams that are supporting but still establishing a user base, we encourage you to share your tool on the [community faucets page](https://github.com/ethereum-optimism/developers/blob/main/community/tools/faucets.md). -You can also promote your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and sign up to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/?utm_source=op-docs&utm_medium=docs). - ## Next steps * If you're new to onchain development, check out [Optimism Unleashed](https://cryptozombies.io/en/optimism) by CryptoZombies and [Superchain Builder NFT](https://web.archive.org/web/20231218203510/https://blog.thirdweb.com/guides/optimism-superchain-faucet-nft/) by ThirdWeb. diff --git a/app-developers/tools/wallets/account-abstraction.mdx b/app-developers/tools/wallets/account-abstraction.mdx index 9e6db8b49..abc95c23a 100644 --- a/app-developers/tools/wallets/account-abstraction.mdx +++ b/app-developers/tools/wallets/account-abstraction.mdx @@ -65,5 +65,3 @@ Developer teams who want to feature products/tools on this page must meet the fo 1. **ongoing partnership** with Optimism whether formal agreement, RPGF, RFP, collaborated on specific initiatives, etc.; 2. **established user base** and OP ecosystem engagement such as governance participation, [Community Discord](https://discord.gg/optimism) or [Superchain Developer Discord](https://guild.xyz/superchain-devs) participation, etc.; and 3. **actively maintained developer tool** that aligns with OP's commitment to a magical developer experience (e.g., easy-to-use, easy-to-integrate, great DevX, highly rated by the community, etc.) - -For teams that are supporting but still establishing a user base, we encourage you to share your tool in the [developer forum](https://github.com/ethereum-optimism/developers/discussions/categories/show-and-tell) and sign up to share your tool at the next [demo day](https://community.optimism.io/docs/contribute/demo-day/?utm_source=op-docs&utm_medium=docs). diff --git a/chain-operators/reference/standard-configuration.mdx b/chain-operators/reference/standard-configuration.mdx index 385a3e5bd..f145143c8 100644 --- a/chain-operators/reference/standard-configuration.mdx +++ b/chain-operators/reference/standard-configuration.mdx @@ -100,9 +100,6 @@ The [Superchain Registry](/superchain/superchain-registry) is the authoritative 4. **Seek guidance:** Consult the [developer support](https://github.com/ethereum-optimism/developers/discussions) team for clarifications on standardization. -5. **Contribute to the ecosystem:** - Engage with the [Optimism Collective](https://community.optimism.io/?utm_source=op-docs&utm_medium=docs) to share feedback and propose improvements. - ## References * [OP Stack Specifications](https://specs.optimism.io/protocol/configurability.html?utm_source=op-docs&utm_medium=docs) diff --git a/chain-operators/tutorials/l1-contract-upgrades/upgrade-op-contracts-1-3-1-8.mdx b/chain-operators/tutorials/l1-contract-upgrades/upgrade-op-contracts-1-3-1-8.mdx index 735dc16a9..8d38441d8 100644 --- a/chain-operators/tutorials/l1-contract-upgrades/upgrade-op-contracts-1-3-1-8.mdx +++ b/chain-operators/tutorials/l1-contract-upgrades/upgrade-op-contracts-1-3-1-8.mdx @@ -209,6 +209,5 @@ Now you have the calldata that can be executed onchain to perform the L1 contrac ## Additional Resources -* [Optimism Documentation](https://community.optimism.io/docs/) * [superchain-ops Repository](https://github.com/ethereum-optimism/superchain-ops) * [Optimism Monorepo](https://github.com/ethereum-optimism/optimism) diff --git a/connect/contribute/docs-contribute.mdx b/connect/contribute/docs-contribute.mdx index 9241cef55..57bdb5b0e 100644 --- a/connect/contribute/docs-contribute.mdx +++ b/connect/contribute/docs-contribute.mdx @@ -5,11 +5,6 @@ description: Learn about the different ways you can contribute to Optimism Docs. Optimism Docs (docs.optimism.io) is an open-source project, and we welcome your contributions. Here's how you can help grow and support the Optimism Collective. - - We recently migrated our technical docs from community.optimism.io --> docs.optimism.io. - So, if you contributed to either repo in 2023, don't forget to claim your [POAP token](#claim-your-gitpoap)! - - ## Ways to contribute * [Edit existing content](#how-to-work-on-docsoptimismio): make tweaks to existing content using the ✏️ **Edit this page on GitHub** or ❤️ **Share general feedback** links on the right-side of any page. diff --git a/connect/contribute/stack-contribute.mdx b/connect/contribute/stack-contribute.mdx index e5d8a429b..ca1607bcb 100644 --- a/connect/contribute/stack-contribute.mdx +++ b/connect/contribute/stack-contribute.mdx @@ -12,7 +12,6 @@ Every contribution makes a difference — no contribution is too small. If you'r ## Component contributions The OP Stack is a decentralized development stack and is constantly evolving as new layers and modules are developed. Anyone can contribute components that can be considered part of the OP Stack as long as those components fit the stack's [design principles and goals](/op-stack/protocol/design-principles). -To start contributing components to the stack, check out some of these [useful ideas](https://github.com/ethereum-optimism/ecosystem-contributions) and get to building! And don't forget that projects can also receive grants from the Collective via [RetroPGF](https://community.optimism.io/docs/citizen-house/how-retro-funding-works/?utm_source=op-docs&utm_medium=docs). ## Codebase contributions diff --git a/docs.json b/docs.json index 50f76c8d0..8de1165d6 100644 --- a/docs.json +++ b/docs.json @@ -347,11 +347,11 @@ }, { "source": "/identity/optimist-profile", - "destination": "https://community.optimism.io/identity/overview" + "destination": "/governance/gov-faq" }, { "source": "/chain/identity/optimist-profile", - "destination": "https://community.optimism.io/identity/overview" + "destination": "/governance/gov-faq" }, { "source": "/app-developers/tools/overview", @@ -2194,6 +2194,20 @@ } ] }, + { + "tab": "How Optimism Evolves", + "groups": [ + { + "group": "How Optimism Evolves", + "pages": [ + "governance/protocol-upgrades", + "governance/capital-allocation", + "governance/evolution-and-experimentation", + "governance/gov-faq" + ] + } + ] + }, { "tab": "Notices", "groups": [ @@ -2246,11 +2260,6 @@ ], "global": { "anchors": [ - { - "anchor": "Community Hub", - "href": "https://community.optimism.io/", - "icon": "users" - }, { "anchor": "Status", "href": "https://status.optimism.io", diff --git a/governance/capital-allocation.mdx b/governance/capital-allocation.mdx new file mode 100644 index 000000000..793f63e74 --- /dev/null +++ b/governance/capital-allocation.mdx @@ -0,0 +1,74 @@ +--- +title: Capital Allocation +description: Learn how Optimism allocates capital for long-term success. +--- + +## How does Optimism ensure long-term success? + +Optimism strives to create a sustainable ecosystem flywheel. In this flywheel, revenue contributed by OP Chains to the Optimism Collective funds open-source development and drives ecosystem growth, which strengthens the OP Stack and attracts more end-users, apps, integration partners, and chains. + +In implementing this flywheel, Optimism uses a public decision making process designed to prevent short-term profit seeking at the expense of the platform, while ensuring organizations contributing the OP Stack remain accountable to tokenholders and customers. This process includes a capital allocation model, designed to avoid many of the common failure modes of corporate governance, aiming to ensure the product always remains at the cutting edge. + +For more details, please see the Operating Manual. + +![capital alloction](/public/img/governance/capital-allocation.png) + + ## How does Optimism generate revenue? + +OP Chains in the Superchain earn transaction fees whenever users send transactions onchain, including for payments, trading, identity, and other applications. Each chain also pays costs to publish its activity to Ethereum for security. + +OP Chains contribute a portion of their revenue to Optimism. This treasury is used to drive growth, provide shared infrastructure, and fund open source contributions that benefit the Superchain. + +Superchain member chains contribute the greater of: + +- 15% of net transaction fee profit (transaction fees earned on L2 - costs paid to Ethereum L1), or +- 2.5% of gross transaction fees + +OP Mainnet contributes 100% of its revenue to this shared treasury. + +You can find more information about revenue in the [here](governance/capital-allocation.mdx). + +You can also find the list of wallets across L1 and OP Mainnet where the Optimism Collective Revenue earned sits [here](https://docs.google.com/spreadsheets/d/1f-uIW_PzlGQ_XFAmsf9FYiUf0N9l_nePwDVrw0D5MXY/edit?gid=155717474#gid=155717474), on the right-hand side of the Collective Contribution page. + +- OP Treasury Address for Foundation Allocated Budget: `0x2A82Ae142b2e62Cb7D10b55E323ACB1Cab663a26` + - This address hold the remaining OP tokens allocated to the Foundation, which the Foundation requires governance approval to access (via annual FND budget proposals). +- OP Treasury Address for Foundation Approved Budget: `0x2501c477D0A35545a387Aa4A3EEe4292A9a8B3F0` + - This is the Foundation's OP Treasury which is available for the Foundation to utilize as the Foundation's budget granted through the initial token allocation. Transactions from this wallet are typically internal operational movements per the Foundation's needs. + - Additional token may be moved from `0x2…a26` to `0x2…3F0` based on governance approval of budgets. +- OP Foundation Grants Wallet: `0x19793c7824Be70ec58BB673CA42D2779d12581BE` + - This Foundation wallet is used to make private OP grants. This is topped up from the OP Treasury Foundation Approved Budget wallet `0x2…B3F0` as needed. +- OP Foundation Locked Grants Wallet: `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F` + - This Foundation wallet is used to hold OP for one year lockups. This is topped up from the OP Foundation Grants Wallet `0x1...81BE` as needed. + +## How is the treasury managed? + +The treasury is currently stewarded by the Foundation, but is subject to oversight by key stakeholder groups, via Optimism's public decision making process. Specifically, tokenholders, chains, apps, and users are asked to oversee annual budgets, which enable the Foundation to deploy the treasury into initiatives aimed at generated the sustainable flywheel described above. + +Foundation Budget Reports can be found [here](https://gov.optimism.io/c/updates-and-announcements/foundation-budgets/) on the governance forum. + +The OP Token Unlock (Estimated) sheet can be found [here](https://docs.google.com/spreadsheets/d/1qVMhLmmch3s6XSbiBe8hgD4ntMkPIOhc1WrhsYsQc7M/edit?usp=sharing). + +You can find more information via the Operating Manual [here](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md). + +## What is Optimism's commitment to Open Source Software? + +Optimism has always been committed to funding open-source software. OP Labs, a core contributor to the OP Stack, is registered as a public benefit corporation with a mission to enhance and enshrine access to public goods. The OP Stack is MIT licensed and Optimism dedicates a significant portion of its treasury to funding public goods and open-source software. + +Optimism operates various grant programs to incentivize and reward open-source contributions. Grant programs can be found via [atlas.optimism.io](http://atlas.optimism.io). + +## What can I do with the OP Token? + +The OP token was created in May of 2022, with an initial supply of 4,294,967,296 OP tokens. The token was launched as a governance token to enable tokenholders to weigh in on technical and economic decisions that impact Optimism, such as protocol upgrades and capital allocation. The Optimism Foundation estimates the total supply of circulating OP tokens to increase as detailed in [this sheet](https://docs.google.com/spreadsheets/d/1qVMhLmmch3s6XSbiBe8hgD4ntMkPIOhc1WrhsYsQc7M/). + +Tokenholders can use OP to vote on: + +- Protocol Upgrades +- Token Allocations +- Adjusting Inflation +- Removing the Director of the Optimism Foundation +- Dissolutions +- Elections (and representative removal) +- Protecting the rights of tokenholders by consenting to any changes to the founding documents of the Optimism Foundation, if those changes would materially reduce their rights. +- Ratification of Governing Documents + +You can find full details of what Tokenholders can vote with the Operating Manual [here](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md). You can sign up to vote with your tokens [here](https://vote.optimism.io/delegates). \ No newline at end of file diff --git a/governance/evolution-and-experimentation.mdx b/governance/evolution-and-experimentation.mdx new file mode 100644 index 000000000..0a971b125 --- /dev/null +++ b/governance/evolution-and-experimentation.mdx @@ -0,0 +1,59 @@ +--- +title: Evolution & Experimentation +description: Learn about Optimism's commitment to iterative improvement and experimentation. +--- + +## Evolution + +In our pursuit to design a new type of organization, Optimism's public decision making process has undergone significant evolution since its inception, reflecting Optimism's commitment to iterative improvement and experimentation. +Below is a summary of some of the key things we learned along the way. + +### Key Stakeholders + +- We've run multiple experiments to understand who our most engaged stakeholders are and how they participate in our public decision making process. +- **Tokenholders:** Anyone who holds OP can vote + - We've also run multiple delegation experiments aimed at getting if specific types of tokenholders (protocols, chains, and individual community members) more involved. Our main learning has been that tokenholders need strong incentive alignment to invest time in decision making processes and they want to be involved in low effort, high impact ways. + - While our system allows for delegation - whereby tokenholders can assign their votes to someone else to cast on their behalf - over time we've come to believe that delegation disrupts the incentives of token-weighted voting and that voting directly should be heavily encouraged. + - Tokenholders are asked to make decisions that would benefit from investor protections +- **Users, Apps, and Chains:** You must qualify to be a Citizen + - Citizenship started with a small initial group and expanded via a Web of Trust model. This model suffered from in-group dynamics (which were replicated here), resulting in many Citizens that were impacted by the decisions being made. + - We later ran targeted experiments to evaluate how community members, chains, and past grant recipients voted, ultimately resulting in our key stakeholder model. Our stakeholder models ensures chains, apps, and end-users are able to influence the decisions that impact them. + - Citizens are asked to make decisions that would benefit from consumer protections +- We've realized that input from different stakeholders is needed depending on the type of decision being made: + - **Preferences**: There is no absolute "right" answer and all stakeholders should have a say + - **Prediction**: There is a correct answer, which is only revealed in the future. Experts are best suited to make these decisions. + - When “experts” are needed, these decisions are made by Councils and Boards - such as the Developer Advisory Board and Security Council. These Councils and Boards are still ultimately accountable to key stakeholders. + - **Measurement**: This is best done objectively, by a computer, when possible, or by experts. + +### High Impact Inputs + +- Different decisions impact each stakeholder group in unique ways. Our approach has evolved from “everyone decides everything” to one that only asks stakeholders to make decisions that directly impact them. +- In many cases, a stakeholder doesn't need to make a decision directly, but should still have the ability to veto - or reject - a decision that disadvantages their stakeholder group. +- Stakeholders will also be able to express preferences and influence strategy via non-voting processes. +- We've outlined the different decisions here: Figma + +### The Core Set of Decisions + +- Governance minimization is a foundational principle of Optimism's collective decision making process. Our evolution has been one of continuously simplifying process, reducing structure, and further refining scope. +- We've learned over time that several decisions that used to be made publicly, actually benefit from more centralized decision making (CoCC, CFC, BB.) +- We believe the set of decisions that should be made collectively are those that: + - Reduce platform risk for customers and users of the protocol + - Prevent short-term profit seeking at the long-term expense of the platform +- Optimism has always been committed to supporting public goods, but the way we support public goods has evolved greatly over time. We started with a fully public grant making process, which gradually evolved to be more metrics-driven and programmatic approach, requiring less human input. We expect this to be a continued area of evolution and innovation. +- Our Decentralization Milestones outlines the remaining steps we hope to take to refine and further decentralize our public decision making process. + +## Experimentation + +Underpinning the learnings outlined above is a culture of experimentation. In our early days, our [iterative approach](https://gov.optimism.io/t/the-path-to-open-metagovernance/7728) sometimes involved a less-scientific, trial-and-error approach. Over time, we've realized a more rigorous, data-driven approach - leveraging controlled trials where possible - allows us to truly understand what works and what doesn't. + +A sample of our Research & Experiments findings are summarized in the table below. We often collaborate with academics, industry experts, and independent researchers. + +| **Topic** | **Research question** | **Methods** | **Key Takeaways** | **Write-up** | +| --- | --- | --- | --- | --- | +| **Airdrops** | Do airdrops drive prosocial behaviors like delegation? Do they increase retention among new users? | Regression discontinuity design (RDD) | Increased delegation esp among small wallets; Baseline reward increases retention but high activity bonuses decrease retention | - [Did OP Airdrop 2 Increase Governance Engagement?](https://gov.optimism.io/t/did-op-airdrop-2-increase-governance-engagement/7270)
- [Did OP Airdrop 5 Increase User Retention Rates? A Regression Discontinuity Analysis](https://gov.optimism.io/t/did-op-airdrop-5-increase-user-retention-rates-a-regression-discontinuity-analysis/9610) | +| **Citizenship** | How do we identify key stakeholders (eg, end users, app devs, or partner chains) and give them decision-making rights? | Voting data analysis, surveys, qualitative interviews | Experts no “better” at values questions but better at assessing impact; Guest voters don’t vote differently to existing set; 3 clear personas | - [Citizenship Learnings 2024](https://gov.optimism.io/t/citizenship-learnings-2024/9563) | +| **Deliberation** | How does participating in a deliberative process with direct policy implications change individual attitudes and behaviors? | Randomized experiment, instrumental variable regression | Deliberation increases knowledge and trust; No reduction in polarization when outcome is binding | - [When Is Deliberation Useful for Optimism Governance?](https://gov.optimism.io/t/when-is-deliberation-useful-for-optimism-governance/9142) | +| **Futarchy** | Do projects selected via Futarchy see greater increase in TVL than projects selected by existing Grants Council? | Time-series analysis, RDD, analysis of telegram, survey, and trading data | Futarchy grants produced more Superchain TVL after 3 months than Grants Council picks; Predictions notably overpriced; 400+ forecasters participated | - [Futarchy v1 Preliminary Findings](https://gov.optimism.io/t/futarchy-v1-preliminary-findings/10062) | +| **Public Goods Funding** | What voting designs lead to impactful grant allocation decisions? Does algorithmic/ metrics-based voting improve outcomes? | Voting data analysis, synthetic control method, surveys, qualitative feedback | Humans are bad at quantification and bias toward even distributions rather than reflecting value; Experts with context make better decisions for OSS; Individual bias about impact vs need is inevitable | - [Retro Funding 4: Learnings and Reflections](https://gov.optimism.io/t/retro-funding-4-learnings-and-reflections/9271)
- [Season 7 Retro Funding - Early Evidence on Developer Tooling Impact](https://gov.optimism.io/t/season-7-retro-funding-early-evidence-on-developer-tooling-impact/10162) | +| **Voter mobilization** | Do appeals to civic duty, economic self-interest, collective security, or decision authority increase tokenholder turnout? | Randomized multi-wave experiment | Economic and security (tangible stakes) were most effective in driving turnout; Repeated reminders are necessary to sustain increase in participation; catchy visuals and follow-ups important | - “What Drives Turnout in Digital Governance? Evidence from a Multi-stage Voter Mobilization Experiment among 34,328 Tokenholders” (Draft available upon request: eliza@optimism.io) + diff --git a/governance/gov-faq.mdx b/governance/gov-faq.mdx new file mode 100644 index 000000000..57d27c4ef --- /dev/null +++ b/governance/gov-faq.mdx @@ -0,0 +1,466 @@ +--- +title: FAQs +description: Frequently Asked Questions about how Optimism evolves. +--- + + + + + All OP tokenholders, a key stakeholder group, are represented in governance via the Token House. The Token House uses token-weighted voting, giving influence proportional to OP token holdings. Tokenholders may vote themselves or assign their voting power to a “delegate.” The primary role of tokenholders is to express their financial interest in the evolution of the Superchain and to hold proposers accountable. Tokenholders may vote on: + + **Protocol Upgrades** + + Delegates have the power to veto decisions about protocol upgrades made by the Developer Advisory Board (DAB). This veto power serves as a critical check on technical changes, with the aim of ensuring they align with the interests of those who rely on the protocol. + + **Capital Allocation** + + Delegates participate in resource allocation decisions, including: + + - Approving the Collective Intent, missions, and budget + - Approving Governance Fund proposals + + **Representative Elections** + + Delegates elect members to the Councils and Boards and/or approve any alternative selection mechanisms + + **Ratification** + + Delegates may ratify core governing documents. + + For a full description of the voting mechanics for each of these proposal types, please refer to the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md). In future phases, the Token House may gain additional governance powers. + + + + + **Unlock Your Voting Power** + + OP token holders are able to vote on some of the most important decisions for the Collective. This empowers one of the Collective's key stakeholders to have a say in the development of the system. + + You can either vote yourself with your OP tokens, or you can delegate the voting power of your OP tokens to someone else to make decisions on your behalf. + + Get started at [vote.optimism.io/delegates](http://vote.optimism.io/delegates) + + + + **Unlock Your Voting Power** + + OP token holders are able to vote on some of the most important decisions for the Collective. This empowers one of the Collective's key stakeholders to have a say in the development of the system. + + You can either vote yourself with your OP tokens, or you can delegate the voting power of your OP tokens to someone else to make decisions on your behalf. + + Get started at [vote.optimism.io/delegates](http://vote.optimism.io/delegates) + + + + Users, Apps, and Chains, key stakeholder groups, are represented in governance via the Citizens' House. The Citizens' House uses a `1 member, 1 vote` model, so all members have the same level of influence. The primary role of Citizens is to express their preferences in the evolution of the Superchain and to hold proposers accountable. Citizens may vote on: + + **Protocol Upgrades** + + Citizens have the power to veto decisions about protocol upgrades made by the Developer Advisory Board (DAB). This veto power serves as a critical check on technical changes, ensuring they align with the interests of those who rely on the protocol. + + **Resource Allocation** + + Citizens participate in resource allocation decisions, including: + + - Approving the Collective Intent, missions, and budget + + **Representative Elections** + + Citizens elect representatives to the Developer Advisory Board, ensuring it remains accountable to their interests. + + **Ratification** + + Citizens may ratify core governing documents. + + For a full description of the voting mechanics for each of these proposal types, please refer to the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md). In future phases, the Citizens' House may gain additional governance powers. + + + + The Token House and the Citizens' House together represent all key stakeholders of the Superchain: tokenholders, chains, apps, and end-users. Both houses vote on proposals when the interests of all stakeholders should be represented in a particular decision. Each house has a distinct voting mechanism which, when combined together, creates a system of checks and balances aimed at balancing competing interests. + + Voting happens on a regular schedule via three-week voting cycles. Regular voting Cycles begin on Thursday at 19:00p GMT (12p PST) and end on Wednesday at 19:00 GMT (12p PST). Protocol Upgrades may go through an accelerated process. You can view full details [here](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md). You can track cycles on [the governance calendar](https://calendar.google.com/calendar/u/0/r?cid=Y180aHVpNzBpdG0wODllN3Q4cTUwaGVoMWtub0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t). + + + + + Key stakeholders of the Superchain can protect their interests by participating in Optimism's public decision making process (governance). This process allows stakeholders to influence the future of the Superchain with limited day-to-day involvement. + + Key stakeholders will be asked to: + + - **Vote:** 1-2 times per year + - **Provide input:** 3-4 times per year + - **Veto:** only as needed + + Email notifications will be sent to all stakeholders whenever any of the above actions is possible. Stakeholders can also monitor activity directly at [vote.optimism.io](http://vote.optimism.io) or [atlas.optimism.io](http://atlas.optimism.io) + + **Token House Voters** + + 1. **Activity:** The social standard for being an active delegate is participating in 70% of all votes. + 2. **No self-dealing:** Voters are prohibited from approving and voting on their own proposals. Voters may not vote solely for their own candidacy in an election. In the case of approval/ranked choice elections, optimists may vote for themselves, so long as they also cast votes for the remaining elected positions. + 3. **Conflicts of Interest:** Any actual or reasonably anticipated conflicts of interest must be disclosed in writing and prominently displayed ahead of any voting (i.e. when approving proposal drafts, when running for an elected position, when making public recommendations). + + These guidelines help ensure that the Token House remains active and resistant to capture or manipulation. + + **Citizens House Voters** + + To maintain the integrity of the Citizens' House, several important rules govern participation: + + 1. **No Double Representation**: If you are an admin of a Citizen project or organization, you may not also join the Citizens' House as a Superchain user. + 2. **Organization Priority**: An organization and a project under that organization can never both get votes in the Citizens' House. If both are eligible, membership defaults to the organization. + 3. **No Multiple Accounts**: It is forbidden to create multiple accounts to attempt to get multiple votes in the Citizens' House as a Superchain user. In Season 8, Citizens will be manually reviewed for possible Sybil activity by the Optimism Foundation. + 4. **Seasonal Recalculation**: The eligibility criteria for being a member of the Citizens' House will be recalculated every Season and may change—being a Citizen now doesn't guarantee future Citizens' House membership. + + These rules help ensure that the Citizens' House remains balanced, representative, and resistant to capture or manipulation. + + You can view the Code of Conduct [here](https://gov.optimism.io/t/code-of-conduct/5751). + + + + + Funding public goods is core to Optimism's values and vision for a healthy ecosystem. Retroactive Public Goods Funding (Retro Funding) is an experimental grant program to reward public goods that have created impact in the Optimism ecosystem. Learn more at atlas.optimism.io + + + +This guide covers [Ethereum Attestation Service ("EAS")](https://attest.sh/), an open-source public good that is included as a predeploy in the OP Stack. It also covers EAS contract addresses, how to read and write attestations, and indexing. + + + + This guide covers Ethereum Attestation Service ("EAS"), an open-source public good that is included as a predeploy in the OP Stack. It also covers EAS contract addresses, how to read and write attestations, and indexing. + + **EAS contract addresses** + + The [Ethereum Attestation Service](https://docs.attest.sh/docs/welcome) is deployed on these addresses: + + | **Network** | **Attestation Contract** | **Schema Registry Contract** | + | --- | --- | --- | + | OP Sepolia | [0x4200000000000000000000000000000000000021](https://sepolia-optimism.etherscan.io/address/0x4200000000000000000000000000000000000021) | [0x4200000000000000000000000000000000000020](https://sepolia-optimism.etherscan.io/address/0x4200000000000000000000000000000000000020) | + | OP Mainnet | [0x4200000000000000000000000000000000000021](https://optimistic.etherscan.io/address/0x4200000000000000000000000000000000000021) | [0x4200000000000000000000000000000000000020](https://optimistic.etherscan.io/address/0x4200000000000000000000000000000000000020) | + + **How to read and write attestations** + + You can read and write attestations in several ways: + + - [EAS scan user interface (OP Mainnet)](https://optimism.easscan.org/) + - [EAS scan user interface (OP Sepolia)](https://optimism-sepolia.easscan.org/) + - [JavaScript SDK](https://docs.attest.sh/docs/developer-tools/eas-sdk) + - [Access directly onchain](https://github.com/ethereum-attestation-service/eas-contracts/blob/master/contracts/EAS.sol) (if you need to attest from a smart contract) + + **Indexing** + + Indexing is available via: + + - [GraphQL endpoint](https://docs.attest.sh/docs/developer-tools/api) + - [Ponder graph](https://github.com/ethereum-attestation-service/eas-ponder-graph) + - [Open source indexer](https://github.com/ethereum-attestation-service/eas-indexing-service) + + + + + + Schemas define the structure and type of data that can be included in an attestation. + + Below you will find a list of relevant schemas that are being used on OP Mainnet. Schemas are built using the [Ethereum Attestation Service](https://docs.attest.sh/docs/welcome). + + ## General schemas + + - [**Gitcoin Passport V1 scores schema UID](https://optimism.easscan.org/schema/view/0x6ab5d34260fca0cfcf0e76e96d439cace6aa7c3c019d7c4580ed52c6845e9c89):** `0x6ab5d34260fca0cfcf0e76e96d439cace6aa7c3c019d7c4580ed52c6845e9c89` + - [**Superchain Faucet schema UID**](https://optimism.easscan.org/schema/view/0x98ef220cd2f94de79fbc343ef982bfa8f5b315dec6a08f413680ecb7085624d7): `0x98ef220cd2f94de79fbc343ef982bfa8f5b315dec6a08f413680ecb7085624d7` + + **Schemas related to project creation and Retro funding application** + + [**Project and organization identifier**](https://optimism.easscan.org/schema/view/0xff0b916851c1c5507406cfcaa60e5d549c91b7f642eb74e33b88143cae4b47d0) + + Used as the unique identifier for projects and organizations created on or after 23 August 2024. For projects created earlier, please see the archived section at the bottom of this page. + + | **Schema UID** | **`0xff0b916851c1c5507406cfcaa60e5d549c91b7f642eb74e33b88143cae4b47d0`** | + | --- | --- | + | Issuer | Attestations issued as part of Retro Funding sign up are issued by `0xF6872D315CC2E1AfF6abae5dd814fd54755fE97C` | + | farcasterID | The Farcaster id of the individual who created the project or organization | + | type | "Project" or "Organization" | + + [**Organization metadata**](https://optimism.easscan.org/schema/view/0xc2b376d1a140287b1fa1519747baae1317cf37e0d27289b86f85aa7cebfd649f) + + Used to associate metadata to an organization. Re-issued each time there is a change to metadata + + | **Schema UID** | **`0xc2b376d1a140287b1fa1519747baae1317cf37e0d27289b86f85aa7cebfd649f`** | + | --- | --- | + | Issuer | Attestations issued as part of Retro Funding sign up are issued by `0xF6872D315CC2E1AfF6abae5dd814fd54755fE97C` | + | Recipient | Null | + | RefUID | The attestation UID of the organization this metadata relates to | + | farcasterID | The Farcaster id of the individual who published the organization metadata | + | name | The name of the organization | + | projects | The array of projects that belong to this organization | + | parentOrgUID | The attestation UID of this organization's parent, in case it has one | + | metadataType | How the metadata can be accessed. 1 for ipfs, 2 for http | + | metadataUrl | The storage location where the metadata can be retrieved | + + [**Project metadata**](https://optimism.easscan.org/schema/view/0xe035e3fe27a64c8d7291ae54c6e85676addcbc2d179224fe7fc1f7f05a8c6eac) + + Used to associate metadata to a project. Re-issued each time there is a change to metadata. + + | **Schema UID** | **`0xe035e3fe27a64c8d7291ae54c6e85676addcbc2d179224fe7fc1f7f05a8c6eac`** | + | --- | --- | + | Issuer | Attestations issued as part of Retro Funding sign up are issued by `0xF6872D315CC2E1AfF6abae5dd814fd54755fE97C` | + | Recipient | Null | + | projectRefUID | The attestation UID of the project this metadata relates to | + | farcasterID | The Farcaster id of the individual who published the project metadata | + | name | The name of the project | + | category | The category of the project | + | parentProject RefUID | The attestation UID of this project's parent project, in case it has a parent | + | metadataType | How the metadata can be accessed. 1 for ipfs, 2 for http | + | metadataUrl | The storage location where the metadata can be retrieved | + + [**Retro funding application**](https://optimism.easscan.org/schema/view/0x2169b74bfcb5d10a6616bbc8931dc1c56f8d1c305319a9eeca77623a991d4b80) + + Used to identify a project's application to a specific Retro Funding Round. This attestation is used for Retro Funding Round 6 and beyond. + + | **Schema UID** | **`0x2169b74bfcb5d10a6616bbc8931dc1c56f8d1c305319a9eeca77623a991d4b80`** | + | --- | --- | + | Issuer | Attestations issued as part of Retro Funding sign up are issued by: `0xF6872D315CC2E1AfF6abae5dd814fd54755fE97C` | + | Recipient | Null | + | round | The round number for which this application was submitted | + | metadataType | How the metadata can be accessed. 1 for ipfs, 2 for http | + | metadataUrl | The storage location where the metadata can be retrieved | + | farcasterID | The individual that submitted this application on behalf of the project. | + | metadataSnapshot RefUID | The project metadata at the time the application was submitted. | + + [**Retro funding application approval/rejection**](https://optimism.easscan.org/schema/view/0x683b1b399d47aabed79c9aa8f2674729021174b6e5cce1e20675eab404fc82d6) + + Used to identify which Retro Funding applications have been approved or rejected. + + | **Schema UID** | **`0x683b1b399d47aabed79c9aa8f2674729021174b6e5cce1e20675eab404fc82d6`** | + | --- | --- | + | Issuer | Currently, the Optimism Foundation issues these from the following address: `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F` | + | Recipient | Null | + | projectApplicationUID | The unique identifier of the projects Retro Funding application. | + | Status | The status of the Retro Funding application. | + | Reason | Identifier for the reason an application was rejected. 1 = "Duplicate Application", 2 = "Deceiving Badgeholders", 3 = "Spam", 4 = "Not meeting eligibility criteria" | + + [**Retro funding rewards**](https://optimism.easscan.org/schema/view/0x670ad6e6ffb842d37e050ea6d3a5ab308195c6f584cf2121076067e0d8adde18) + + Used to identify the reward amount each approved project received in a Retro Funding round + + | **Schema UID** | **`0x670ad6e6ffb842d37e050ea6d3a5ab308195c6f584cf2121076067e0d8adde18`** | + | --- | --- | + | Issuer | Currently, the Optimism Foundation issues these from one the following address: `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F` | + | Recipient | Null | + | refUID | The UID of the Retro Funding application | + | projectRefUID | The unique identifier of the project | + | round | The retro round for which the project was rewarded | + | OPamount | The amount of OP awarded to the project | + + ## Schemas related to token house grants + + [**Token house grant approved**](https://optimism.easscan.org/schema/view/0x8aef6b9adab6252367588ad337f304da1c060cc3190f01d7b72c7e512b9bfb38) + + Issued by the Grants Council when a project is approved for a grant. Does not indicate that the grant has been completed. + + | **Schema UID** | **`0x8aef6b9adab6252367588ad337f304da1c060cc3190f01d7b72c7e512b9bfb38`** | + | --- | --- | + | Issuer | Currently issued by the Grants Council lead. | + | Recipient | The address where the tokens will be delivered once the grant has been completed. | + | refUID | Currently null | + | projectRefUID | The unique identifier of the project that was approved for the grant. | + | UserIncentivesOP | The OP amount approved for user incentives. | + | BuildersOP | The OP amount approved for the builder. | + | Season | The season (number) in which the grant was approved | + | Intent | The intent (number) to which the mission belongs | + | Mission | The name of the mission (in words) under which this grant was made. | + | Approval date | The date the grant was approved, in the following format MM/DD/YYYY | + | MetadataUrl | Currently null | + + ## Schemas related to roles and contributions + + [**Citizens**](https://optimism.easscan.org/schema/view/0xc35634c4ca8a54dce0a2af61a9a9a5a3067398cb3916b133238c4f6ba721bc8a) + + Citizen attestations were first issued in Season 6 and are used to represent Citizenship separately from the ability to vote in a specific Retro Round. The resolver contract checks that the issuer is the Foundation with following address `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F` + + | **Schema UID** | **`0xc35634c4ca8a54dce0a2af61a9a9a5a3067398cb3916b133238c4f6ba721bc8a`** | + | --- | --- | + | RefUID | In case the Citizen is a chain or an app, the refUID field will reference the organization/project id of the chain or app. If null, the Citizen is an end-user | + | FarcasterID | The Citizen's unique identifier | + | SelectionMethod | A Code representing the method through which the Citizen was selected. Codes beginning with the number 1 refer to various flavours of Web of Trust selection. | + + [**Retro funding voters**](https://optimism.easscan.org/schema/view/0x41513aa7b99bfea09d389c74aacedaeb13c28fb748569e9e2400109cbe284ee5) + + These attestations are voting Badges issued for Retro Round 5 and beyond. They are different from the [previous schema](https://optimism.easscan.org/schema/view/0xfdcfdad2dbe7489e0ce56b260348b7f14e8365a8a325aef9834818c00d46b31b) to include new fields like votingGroup, used to assign voters to sub-categories in the round. + + | **Schema UID** | **`0x41513aa7b99bfea09d389c74aacedaeb13c28fb748569e9e2400109cbe284ee5`** | + | --- | --- | + | FarcasterID | The voter's unique identifier | + | Round | The round number for which this voting Badge was valid | + | voterType | Guest or Citizen | + | votingGroup | Used to assign voters to subcategories in case the Round has subcategories | + | selectionMethod | The method in which this voter was selected | + + [**MetaGov contribution**](https://optimism.easscan.org/schema/view/0x84260b9102b41041692558a4e0cba6b7e5f9b813be56402c3db820c06dd4a5f1) + + | **Schema UID** | **`0x84260b9102b41041692558a4e0cba6b7e5f9b813be56402c3db820c06dd4a5f1`** | + | --- | --- | + | Issuer | Currently, the Optimism Foundation issues these from one of the following addresses: `0x621477dBA416E12df7FF0d48E14c4D20DC85D7D9` or `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F`. | + | Recipient | The address of the individual who made the contribution | + | refUID | The UID of the project, in case this contribution is represented as a project | + | FarcasterID | The id of the individual who made the contribution, if known | + | Impact | This field is not currently being used | + | Season | The season in which the contribution was made | + | Decision Module | The decision module to which the contribution relates | + | Contribution Type | The type of contribution | + | MetadataUrl | This field is not currently being used | + + [**Foundation mission request completed**](https://optimism.easscan.org/schema/view/0x649cc6df5af7561b66384405a62682c44e2428584d2f17a202ac3ef4506e2457) + + | **Schema UID** | **`0x649cc6df5af7561b66384405a62682c44e2428584d2f17a202ac3ef4506e2457`** | + | --- | --- | + | Issuer | Currently, the Optimism Foundation issues these from one of the following addresses: `0x621477dBA416E12df7FF0d48E14c4D20DC85D7D9` or `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F`. | + | projectRefUID | The UID of the project that represents the work completed as part of the Foundation Mission Request | + | OP Amount | The OP Amount that was awarded for the completion of this Mission Request | + | Season | The season in which this Mission Request was completed | + + [**Retro funding governance contribution**](https://optimism.easscan.org/schema/view/0x3743be2afa818ee40304516c153427be55931f238d961af5d98653a93192cdb3) + + | **Schema UID** | **`0x3743be2afa818ee40304516c153427be55931f238d961af5d98653a93192cdb3`** | + | --- | --- | + | Issuer | Currently, the Optimism Foundation issues these from one of the following addresses: `0x621477dBA416E12df7FF0d48E14c4D20DC85D7D9` or `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F`. | + | Recipient | The address of the individual who made the contribution | + | Rpgf_round | The round number for which this contribution was made | + | RetroPGF_Contribution | The type of contribution made | + + [**Governance contribution**](https://optimism.easscan.org/schema/view/0xef874554718a2afc254b064e5ce9c58c9082fb9f770250499bf406fc112bd315) + + Issued to those who held governance roles in the Collective, such as Grants Council members. + + | **Schema UID** | **`0xef874554718a2afc254b064e5ce9c58c9082fb9f770250499bf406fc112bd315`** | + | --- | --- | + | Issuer | Currently, the Optimism Foundation issues these from one of the following addresses: `0x621477dBA416E12df7FF0d48E14c4D20DC85D7D9` or `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F`. | + | Issuer | Currently, the Optimism Foundation issues these from one of the following addresses: `0x621477dBA416E12df7FF0d48E14c4D20DC85D7D9` or `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F` | + | Recipient | The address of the individual who made the contribution | + | govSeason | The season the individual held the role | + | govRole | The role held by the individual | + + ## Archived schemas + + These schemas are no longer being actively issued, but capture valuable historical data. + + [**Retro funding application**](https://optimism.easscan.org/schema/view/0x88b62595c76fbcd261710d0930b5f1cc2e56758e155dea537f82bf0baadd9a32) + + Used to identify a project's application to a specific Retro Funding Round. This attestation was used for Retro Funding Rounds 4 and 5. + + | **Schema UID** | **`0x88b62595c76fbcd261710d0930b5f1cc2e56758e155dea537f82bf0baadd9a32`** | + | --- | --- | + | Issuer | Attestations issued as part of Retro Funding sign up are issued by: `0xF6872D315CC2E1AfF6abae5dd814fd54755fE97C` | + | Recipient | Null | + | round | The round number for which this application was submitted | + | projectRefUID | The unique identifier of the project that submitted this application | + | farcasterID | The individual that submitted this application on behalf of the project. | + | metadataSnapshot RefUID | The project metadata at the time the application was submitted. | + + [**Retro funding badgeholders**](https://optimism.easscan.org/schema/view/0xfdcfdad2dbe7489e0ce56b260348b7f14e8365a8a325aef9834818c00d46b31b) + + These attestations are considered "voting Badges" and allow an individual to vote in any given iteration of Retro Funding. They were used up to and including Retro Round 4. + + | **Schema UID** | **`0xfdcfdad2dbe7489e0ce56b260348b7f14e8365a8a325aef9834818c00d46b31b`** | + | --- | --- | + | Issuer | Currently, the Optimism Foundation issues these from one of the following addresses: `0x621477dBA416E12df7FF0d48E14c4D20DC85D7D9` or `0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F` | + | Recipient | The Badgeholder's address | + | rpgfRound | The round number for which this voting Badge was valid | + | referredBy | In early rounds, new Badges were issued by referral. This field captures the address of the referrer, if there was one | + | referredMethod | If this voting Badge was issued by referral, this field captures the referral method | + + [**Project identifier**](https://optimism.easscan.org/schema/view/0x7ae9f4adabd9214049df72f58eceffc48c4a69e920882f5b06a6c69a3157e5bd) + + Used as the unique identifier for projects created in the Collective before 23 August 2024. Attestations issued from this schema prior to 23 August 2024 are still used as the unique identifier for projects. New projects created after 23 August 2024 use the new entity identifier (see above). + + | **Schema UID** | **`0x7ae9f4adabd9214049df72f58eceffc48c4a69e920882f5b06a6c69a3157e5bd`** | + | --- | --- | + | Issuer | Attestations issued as part of Retro Funding sign up are issued by `0xF6872D315CC2E1AfF6abae5dd814fd54755fE97C` | + | Recipient | Null | + | farcasterID | The Farcaster id of the individual who created the project | + - [**RetroPGF 3 Approved Application schema UID](https://optimism.easscan.org/schema/view/0xebbf697d5d3ca4b53579917ffc3597fb8d1a85b8c6ca10ec10039709903b9277):**`0xebbf697d5d3ca4b53579917ffc3597fb8d1a85b8c6ca10ec10039709903b9277`. Important: Remember to verify the attester address is `0x621477dBA416E12df7FF0d48E14c4D20DC85D7D9` + - [**RetroPGF 3 Application schema UID](https://optimism.easscan.org/schema/view/0x76e98cce95f3ba992c2ee25cef25f756495147608a3da3aa2e5ca43109fe77cc):** `0x76e98cce95f3ba992c2ee25cef25f756495147608a3da3aa2e5ca43109fe77cc` + - [**RetroPGF 3 Lists schema UID](https://optimism.easscan.org/schema/view/0x3e3e2172aebb902cf7aa6e1820809c5b469af139e7a4265442b1c22b97c6b2a5):** `0x3e3e2172aebb902cf7aa6e1820809c5b469af139e7a4265442b1c22b97c6b2a5` + - [**Season 4 Co-grant participant schema UID**](https://optimism.easscan.org/schema/view/0x401a80196f3805c57b00482ae2b575a9f270562b6b6de7711af9837f08fa0faf): `0x401a80196f3805c57b00482ae2b575a9f270562b6b6de7711af9837f08fa0faf`. Important: Remember to verify the attester address is `0x3C7820f2874b665AC7471f84f5cbd6E12871F4cC` or `0x2a0eB7cAE52B68e94FF6ab0bFcf0dF8EeEB624be` + - [**Optimist Profile schema UID](https://optimism.easscan.org/schema/view/0xac4c92fc5c7babed88f78a917cdbcdc1c496a8f4ab2d5b2ec29402736b2cf929):** `0xac4c92fc5c7babed88f78a917cdbcdc1c496a8f4ab2d5b2ec29402736b2cf929` + + + + + + + + Here you'll find the [Superchain Health Dashboard](https://docs.google.com/spreadsheets/d/1f-uIW_PzlGQ_XFAmsf9FYiUf0N9l_nePwDVrw0D5MXY/edit?gid=584971628#gid=584971628), below are relevant OP trackers, reports, and addresses. + + Governing Documentation + + - [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md) + - [Working Constitution of the Optimism Collective](https://gov.optimism.io/t/working-constitution-of-the-optimism-collective/55) + - [Standard Rollup Charter](https://github.com/ethereum-optimism/OPerating-manual/blob/main/Standard%20Rollup%20Charter.md) + - [Law of Chains](https://gov.optimism.io/t/final-law-of-chains-v0-1/) + - [Decentralization Milestone Working Model](https://docs.google.com/spreadsheets/d/1IpL0oTd3AgNBu_eWdjP9EjbQfZjq-_Nd3yU1H2ke3vY/edit?gid=0#gid=0) + - [Decision Diagram Working Model](https://www.figma.com/board/iXqyKmLJeBeplKpJBHDI7G/PUBLIC%3A-Optimism-Decision-Diagram-Working-Model?node-id=0-1&node-type=canvas&t=QLiz1uM1DepwYyHy-0) + - [Optimist Expectations](https://gov.optimism.io/t/optimist-expectations/) + + **OP Trackers** + + - [Optimism GovFund Grants: Public Delivery Tracking](https://docs.google.com/spreadsheets/d/1Ul8iMTsOFUKUmqz6MK0zpgt8Ki8tFtoWKGlwXj-Op34/edit?gid=1179446718#gid=1179446718) + - [OP Token Unlock (Estimated)](https://docs.google.com/spreadsheets/d/1qVMhLmmch3s6XSbiBe8hgD4ntMkPIOhc1WrhsYsQc7M/edit?gid=470961921#gid=470961921) + + **Foundation Budget Reports** + + - These can be found [here](https://gov.optimism.io/c/updates-and-announcements/foundation-budgets/) on the governance forum. + + **Retroactive Public Goods Funding Round Results** + + - These can be found [here](https://retrofunding.optimism.io/round/results) on retrofunding.optimism.io. + + **Relevant Addresses** + + You can find the list of wallets across L1 and OP Mainnet where the Optimism Collective Revenue earned sits [here](https://docs.google.com/spreadsheets/d/1f-uIW_PzlGQ_XFAmsf9FYiUf0N9l_nePwDVrw0D5MXY/edit?gid=155717474#gid=155717474), on the right-hand side of the Collective Contribution page. + + - OP Treasury Address for Foundation Allocated Budget: 0x2A82Ae142b2e62Cb7D10b55E323ACB1Cab663a26 + - This address hold the remaining OP tokens allocated to the Foundation, which the Foundation requires governance approval to access (via annual FND budget proposals). + - OP Treasury Address for Foundation Approved Budget: 0x2501c477D0A35545a387Aa4A3EEe4292A9a8B3F0 + - This is the Foundation's OP Treasury which is available for the Foundation to utilize as the Foundation's budget granted through the initial token allocation. Transactions from this wallet are typically internal operational movements per the Foundation's needs. + - Additional token may be moved from 0x2…a26 to 0x2…3F0 based on governance approval of budgets. + - OP Foundation Grants Wallet: 0x19793c7824Be70ec58BB673CA42D2779d12581BE + - This Foundation wallet is used to make private OP grants. This is topped up from the OP Treasury Foundation Approved Budget wallet 0x2…B3F0 as needed. + - OP Foundation Locked Grants Wallet: 0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F + - This Foundation wallet is used to hold OP for one year lockups. This is topped up from the OP Foundation Grants Wallet 0x1...81BE as needed. + + **Optimism Governance Calendar** + + - You can find a link to the Governance Calendar [here](https://calendar.google.com/calendar/embed?src=c_fnmtguh6noo6qgbni2gperid4k%40group.calendar.google.com&ctz=Europe%2FBerlin). + + + + The Optimism Foundation is a Cayman Islands foundation company. It operates to support the establishment of the Optimism Collective, the development of the Optimism ecosystem, and the technology that powers it. + + Consistent with the Collective's Working Constitution, the Foundation strives to: + + - Support the Collective with a formal legal entity, allowing the Foundation to: + - Enter into contracts with third parties, such as service providers. + - Administer intellectual property rights. + - Make required governmental reports and filings. + + **How does the Foundation work?** + + The Optimism Foundation is governed by a Board of Directors and a Supervisor. + + The Board of Directors currently consists of: Abbey Titcomb, Mark Tyneway, Brian Avello, and Jing Wang. The Board's role is to manage the business and affairs of the Foundation. + + The Supervisor is the Cayman Islands firm, DS Limited. Its role is to oversee the Foundation's directors and ensure the observance of their legal obligations. + + The Foundation also employs officers, contractors and service providers to execute on its operational and administrative aims. + + **How is the Foundation held accountable?** + + As a Cayman Islands foundation company, the Foundation is legally accountable to its governing documentation, which sets up the Foundation to defer to the will of the Optimism Collective and its governance. + + There are two governance proposal types specifically targeted towards ensuring that the Foundation and its personnel are accountable to the will of the Collective: + + - **Director removal** - the ability of governance to have a member of the Foundation's Board of Directors removed from service. + - **Rights protections** - a blocking vote, which enables governance to veto any proposed change to the Foundation's governing documents that would materially reduce the rights of OP token holders. + + More information on each of the above proposal types is contained in the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual). + + + \ No newline at end of file diff --git a/governance/protocol-upgrades.mdx b/governance/protocol-upgrades.mdx new file mode 100644 index 000000000..9950d6477 --- /dev/null +++ b/governance/protocol-upgrades.mdx @@ -0,0 +1,40 @@ +--- +title: Protocol Upgrades +description: Learn how the OP Stack stay up to date with the latest innovations. +--- + +## How does the OP Stack stay up to date with the latest innovation? + +The OP Stack is Optimism's open-source software for deploying next-generation onchain products. The software is licensed under the MIT license, meaning it can be freely used and forked by all parties. The OP Stack has a vibrant core developer community who contribute to the stack, ensuring it reflects the features and values protocol users care about. + +The Superchain is an ecosystem of chains running on Optimism's OP Stack, featuring some of the world's largest enterprises. Superchain networks benefit from shared security, upgrades and services provided by Optimism. Each chain maintains peak performance with access to innovative new features developed anywhere on the stack, continually strengthening the entire Superchain ecosystem. Chains may also configure components of the OP Stack to fit their regulatory and business needs while still benefiting from shared infrastructure and innovation. Learn more about the best way to build on the OP Stack for your business [here](https://www.optimism.io/compare). + +## How are new features added to the OP Stack? + +OP Labs and external contributors determine the feature roadmap. Based on discussions, protocol upgrades are drafted, which go through the protocol upgrade process. + +## What is the protocol upgrade process? + +The protocol upgrade process is designed to make sure the OP Stack does not change against the interests of the businesses building on the platform. This is a key benefit of crypto systems compared to their centralized alternatives. Platform risk is a common risk of [Web 2 platforms](https://a16zcrypto.com/posts/article/when-is-decentralizing-on-a-blockchain-valuable/) and is a key consideration for the largest partners building on the OP Stack. + +![protocol-upgrade-process](/public/img/governance/protocol-upgrade-process.png) + +Protocol upgrades are drafted by OP Labs or other core contributors to the OP Stack. Before they are implemented, they are reviewed by an independent group of developers (the Developer Advisory Board) to ensure the upgrade is well justified. + +After a proposal has been reviewed by the Developer Advisory Board, it enters a 7 day veto period. This allows all impacted stakeholders, namely tokenholders, chains, apps, and end-users to override the DAB's decision if they believe an upgrade disadvantages their interests. This is how platform risk is reduced for key stakeholders of the OP Stack. + +If a proposal is veto'd, it enters an appeals and discussion phase and can be resubmitted. + +For full details about the protocol upgrade process, please see the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md). + +Overall - contributors, tokenholders, chains, apps, and end-users all have a voice. Checks and balances exist so that no single entity (including OP Labs or the Foundation) can unilaterally dictate the future of the OP Stack. + +Platform risk is reduced by distributing veto power across stakeholder groups while maintaining an efficient core developer process. This ensures upgrades happen quickly but can be vetoed if they harm key stakeholders. + +## How can my chain specifically influence the feature roadmap? + +Superchain members who contribute revenue back to the Collective are consulted by OP Labs and core developers about the feature roadmap to ensure their voices are heard. All development happens in the open and chains are encouraged to participate and share their perspectives within various research and development repositories. + +## How does Optimism help my chain achieve decentralization? + +Permissionless Fault Proof OP Chains that have their upgrade keys managed by the Optimism Security Council are classified as Stage 1 in [L2Beat's framework](https://l2beat.com/stages). This distributed group delivers the benefit of security scrutinized upgrades that are managed by Optimism. diff --git a/op-stack/protocol/design-principles.mdx b/op-stack/protocol/design-principles.mdx index d6b817d74..28112d84f 100644 --- a/op-stack/protocol/design-principles.mdx +++ b/op-stack/protocol/design-principles.mdx @@ -104,8 +104,3 @@ Extensible code should be designed with the mindset that others will want to bui In practice, this means that the code should be open source (under a permissive license), expose clean APIs, and generally be modular such that another developer can relatively easily extend the functionality of the code. Extensibility is a key design principle that unlocks the superpower of collaboration within the Optimism Collective ecosystem. -## Contributing to the OP Stack - -The OP Stack is a decentralized software stack that anyone can contribute to. -If you're interested in contributing to the OP Stack, check out [the Contributing section on our Community pages](https://community.optimism.io). -Of course, software that has an impact for the Optimism Collective is eligible to receive [Retroactive Public Goods Funding](https://app.optimism.io/retropgf?utm_source=op-docs&utm_medium=docs). Build for the OP Stack — get rewarded for writing great open source software. What's not to love? diff --git a/op-stack/protocol/network-upgrades.mdx b/op-stack/protocol/network-upgrades.mdx index 606ce277a..79421e727 100644 --- a/op-stack/protocol/network-upgrades.mdx +++ b/op-stack/protocol/network-upgrades.mdx @@ -72,8 +72,3 @@ then the software is deployed on production networks. * `Upgrade Activated` - -## More information - -* To check for the latest node software, see the [Software Releases](/operators/node-operators/releases). -* For more information on the governance process see the [governance documentation](https://community.optimism.io/docs/governance/?utm_source=op-docs\&utm_medium=docs). diff --git a/op-stack/protocol/smart-contracts.mdx b/op-stack/protocol/smart-contracts.mdx index 61952cf6f..8f933c8ac 100644 --- a/op-stack/protocol/smart-contracts.mdx +++ b/op-stack/protocol/smart-contracts.mdx @@ -670,7 +670,7 @@ The `SchemaRegistry` predeploy implements the global attestation schemas for the * **Deprecated:** no * **Proxied:** yes -The SchemaRegistry works alongside the Ethereum Attestation Service (EAS) to enable attestations. See [Build Decentralized Identity Apps with Attestations](https://community.optimism.io/identity/about-attestations?utm_source=op-docs\&utm_medium=docs) for more details on schemas and usage. +The SchemaRegistry works alongside the Ethereum Attestation Service (EAS) to enable attestations. ### EAS (Ethereum Attestation Service) @@ -714,8 +714,6 @@ Attestations made via EAS can be indexed through the following tools: * [Ponder Graph](https://github.com/ethereum-attestation-service/eas-ponder-graph) * [Open Source Indexer](https://github.com/ethereum-attestation-service/eas-indexing-service) -For more information on working with attestations, see [Build Decentralized Identity Apps with Attestations](https://community.optimism.io/identity/about-attestations?utm_source=op-docs\&utm_medium=docs). - ### BeaconBlockRoot The `BeaconBlockRoot` predeploy provides access to the L1 beacon block roots. diff --git a/op-stack/security/faq-sec-model.mdx b/op-stack/security/faq-sec-model.mdx index de0f26a77..7c312172d 100644 --- a/op-stack/security/faq-sec-model.mdx +++ b/op-stack/security/faq-sec-model.mdx @@ -4,7 +4,7 @@ description: Learn about the OP Stack security model and answers to common quest --- Many OP Stack chains, such as OP Mainnet, are a work in progress. -Constant, iterative improvement of the security mechanisms that safeguard OP Stack users is a top priority for the entire [Optimism Collective](https://community.optimism.io/docs/governance/?utm_source=op-docs&utm_medium=docs). +Constant, iterative improvement of the security mechanisms that safeguard OP Stack users is a top priority for the entire [Optimism Collective](governance/evolution-and-experimentation). The Optimism Collective strives to be clear and transparent about the security of OP Stack chains and the OP Stack as a whole. ## Bottom line diff --git a/public/img/governance/capital-allocation.png b/public/img/governance/capital-allocation.png new file mode 100644 index 000000000..0ba9360c2 Binary files /dev/null and b/public/img/governance/capital-allocation.png differ diff --git a/public/img/governance/protocol-upgrade-process.png b/public/img/governance/protocol-upgrade-process.png new file mode 100644 index 000000000..8be7a322c Binary files /dev/null and b/public/img/governance/protocol-upgrade-process.png differ diff --git a/reference/contribute/docs-contribute.mdx b/reference/contribute/docs-contribute.mdx index 554d6bc4d..d7c9fb4e2 100644 --- a/reference/contribute/docs-contribute.mdx +++ b/reference/contribute/docs-contribute.mdx @@ -5,11 +5,6 @@ description: Learn about the different ways you can contribute to Optimism Docs. Optimism Docs (docs.optimism.io) is an open-source project, and we welcome your contributions. Here's how you can help grow and support the Optimism Collective. - - We recently migrated our technical docs from community.optimism.io --> docs.optimism.io. - So, if you contributed to either repo in 2023, don't forget to claim your [POAP token](#claim-your-gitpoap)! - - ## Ways to contribute * [Edit existing content](#how-to-work-on-docsoptimismio): make tweaks to existing content using the ✏️ **Edit this page on GitHub** or ❤️ **Share general feedback** links on the right-side of any page. diff --git a/reference/contribute/stack-contribute.mdx b/reference/contribute/stack-contribute.mdx index e5f38b88c..356d365b8 100644 --- a/reference/contribute/stack-contribute.mdx +++ b/reference/contribute/stack-contribute.mdx @@ -12,7 +12,6 @@ Every contribution makes a difference — no contribution is too small. If you'r ## Component contributions The OP Stack is a decentralized development stack and is constantly evolving as new layers and modules are developed. Anyone can contribute components that can be considered part of the OP Stack as long as those components fit the stack's [design principles and goals](/stack/design-principles). -To start contributing components to the stack, check out some of these [useful ideas](https://github.com/ethereum-optimism/ecosystem-contributions) and get to building! And don't forget that projects can also receive grants from the Collective via [RetroPGF](https://community.optimism.io/docs/citizen-house/how-retro-funding-works/?utm_source=op-docs&utm_medium=docs). ## Codebase contributions