What is the Token House?
What is the Token House?
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 UpgradesDelegates 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 AllocationDelegates participate in resource allocation decisions, including:
- Approving the Collective Intent, missions, and budget
- Approving Governance Fund proposals
How do I vote with my tokens?
How do I vote with my tokens?
Unlock Your Voting PowerOP 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
What is the Citizens' House?
What is the Citizens' House?
Unlock Your Voting PowerOP 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
How do I become a Citizen?
How do I become a Citizen?
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 UpgradesCitizens 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 AllocationCitizens participate in resource allocation decisions, including:- Approving the Collective Intent, missions, and budget
How do the Token House and the Citizens' House work together?
How do the Token House and the Citizens' House work together?
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. You can track cycles on the governance calendar.
What is expected of voters?
What is expected of voters?
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
- Activity: The social standard for being an active delegate is participating in 70% of all votes.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
What is Retro Funding?
What is Retro Funding?
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
How does identity work within the Optimism ecosystem?
How does identity work within the Optimism ecosystem?
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 Contracts
EAS Contracts
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 addressesThe Ethereum Attestation Service is deployed on these addresses:
How to read and write attestationsYou can read and write attestations in several ways:
| Network | Attestation Contract | Schema Registry Contract |
|---|---|---|
| OP Sepolia | 0x4200000000000000000000000000000000000021 | 0x4200000000000000000000000000000000000020 |
| OP Mainnet | 0x4200000000000000000000000000000000000021 | 0x4200000000000000000000000000000000000020 |
- EAS scan user interface (OP Mainnet)
- EAS scan user interface (OP Sepolia)
- JavaScript SDK
- Access directly onchain (if you need to attest from a smart contract)
Schemas
Schemas
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.
Organization metadataUsed to associate metadata to an organization. Re-issued each time there is a change to metadata
Project metadataUsed to associate metadata to a project. Re-issued each time there is a change to metadata.
Retro funding applicationUsed to identify a project’s application to a specific Retro Funding Round. This attestation is used for Retro Funding Round 6 and beyond.
Retro funding application approval/rejectionUsed to identify which Retro Funding applications have been approved or rejected.
Retro funding rewardsUsed to identify the reward amount each approved project received in a Retro Funding round
Retro funding votersThese attestations are voting Badges issued for Retro Round 5 and beyond. They are different from the previous schema to include new fields like votingGroup, used to assign voters to sub-categories in the round.
MetaGov contribution
Foundation mission request completed
Retro funding governance contribution
Governance contributionIssued to those who held governance roles in the Collective, such as Grants Council members.
Retro funding badgeholdersThese 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.
Project identifierUsed 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).
General schemas
- **Gitcoin Passport V1 scores schema UID:**
0x6ab5d34260fca0cfcf0e76e96d439cace6aa7c3c019d7c4580ed52c6845e9c89 - Superchain Faucet schema UID:
0x98ef220cd2f94de79fbc343ef982bfa8f5b315dec6a08f413680ecb7085624d7
| 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” |
| 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 |
| 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 |
| 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. |
| 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” |
| 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 approvedIssued 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
CitizensCitizen 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 address0xE4553b743E74dA3424Ac51f8C1E586fd43aE226F| 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. |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 applicationUsed 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. |
| 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 |
| 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:**
0xebbf697d5d3ca4b53579917ffc3597fb8d1a85b8c6ca10ec10039709903b9277. Important: Remember to verify the attester address is0x621477dBA416E12df7FF0d48E14c4D20DC85D7D9 - **RetroPGF 3 Application schema UID:**
0x76e98cce95f3ba992c2ee25cef25f756495147608a3da3aa2e5ca43109fe77cc - **RetroPGF 3 Lists schema UID:**
0x3e3e2172aebb902cf7aa6e1820809c5b469af139e7a4265442b1c22b97c6b2a5 - Season 4 Co-grant participant schema UID:
0x401a80196f3805c57b00482ae2b575a9f270562b6b6de7711af9837f08fa0faf. Important: Remember to verify the attester address is0x3C7820f2874b665AC7471f84f5cbd6E12871F4cCor0x2a0eB7cAE52B68e94FF6ab0bFcf0dF8EeEB624be - **Optimist Profile schema UID:**
0xac4c92fc5c7babed88f78a917cdbcdc1c496a8f4ab2d5b2ec29402736b2cf929
Dashboards Trackers, and Addresses
Dashboards Trackers, and Addresses
Here you’ll find the Superchain Health Dashboard, below are relevant OP trackers, reports, and addresses.Governing Documentation
- Operating Manual
- Working Constitution of the Optimism Collective
- Standard Rollup Charter
- Law of Chains
- Decentralization Milestone Working Model
- Decision Diagram Working Model
- Optimist Expectations
- These can be found here on the governance forum.
- These can be found here on retrofunding.optimism.io.
- 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.
- You can find a link to the Governance Calendar here.
What is the Optimism Foundation?
What is the Optimism Foundation?
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.
- 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.