From 16eb469c63d31c86c611d223d917026e5f9da3dd Mon Sep 17 00:00:00 2001 From: crStiv Date: Fri, 7 Feb 2025 18:45:09 +0100 Subject: [PATCH 1/6] Update CONTRIBUTING.md --- CONTRIBUTING.md | 223 +++++++++++++++++++++++++----------------------- 1 file changed, 117 insertions(+), 106 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b7e4cd152..ad3cf4833 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,113 +2,124 @@ Thanks for taking the time to contribute! ❤️ -Optimism's documentation is open-source, hosted on GitHub in the `ethereum-optimism/docs` repository which renders on the corresponding official website hosted at [docs.optimism.io](https://docs.optimism.io). This guide will give you an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR. Please note that contributions, pull requests, and issues should be written in English at this time. We will be running a dedicated project in the future to add language support to the technical docs, so please reach out via our [developer support channel](https://github.com/ethereum-optimism/developers/) if you are interested in helping with that project. - -The Optimism Documentation team reviews pull requests and either merges, requests changes, or comments and closes the pull request. You can open a documentation pull request by: - -- forking the `docs` repository and working locally, -- or, for smaller updates, clicking the `Edit this page` link on the right side of any documentation page to directly edit in GitHub. - -Contributing to the Optimism documentation implies 2 steps: - -1. Learn how to use [Nextra](#learn-how-to-use-nextra), the tool used to write and generate Optimism's documentation. - -2. [Submit a pull request](#send-pull-request) for review. - -## Learn How to Use Nextra - -Optimism's documentation is built with the React and Markdown-based [Nextra](https://nextra.site/docs) framework. We are using the docs theme (as opposed to the blog theme), which has specialized features. - -To start contributing to Optimism's documentation using Nextra, you need to understand the [files and branches architecture](#understand-file-architecture-and-branch-names) and use the proper [syntax to format content](#use-proper-formatting-and-syntax). Additionally, if you want to work locally from a repository fork, you should [set up the Nextra project](#set-up-the-project-and-test-locally) on your machine. - -### Understand File Architecture and Branch Names - -Optimism's documentation includes two major sections with each section living in a different folder. - -| Section name | Target content | Folder | -| ------------------| ----------------------------------------------------------------- | ----------------------------- | -| Pages | Where all the pages of the technical docs live | `/docs/pages/` | -| Public | Where all the images, icons, and illustrations for the tech docs live | `/docs/public/` | - -**Warning** -The `public` folder also stores the `robots.txt` and `sitemap.xml` files used for SEO. Please do not modify these pages. -The Optimism Documentation team will modify these pages, when necessary, after your PR is merged. - -### Use Proper Formatting and Syntax - -Nextra is MDX-based, meaning the content you write is [Markdown](https://daringfireball.net/projects/markdown/syntax) that accepts [React](https://reactjs.org/) components. - -The Optimism Documentation team has created a complete style guide for you to make the best out of the various options available: - -[Optimism Documentation Style Guide](/pages/connect/contribute/style-guide.mdx) - -### Set Up the Project and Test Locally - -To set up the Nextra project on your machine, perform the following steps from a terminal instance: - -1. Install pnpm [install pnpm](https://pnpm.io/installation). -2. First, run `pnpm i` to install the dependencies. -3. Then, run `pnpm dev` to start the development server and -4. Visit [localhost:3000](http://localhost:3000) in your browser to view the website. +## Table of Contents +- [Overview](#overview) +- [Getting Started](#getting-started) + - [Prerequisites](#prerequisites) + - [Development Setup](#development-setup) +- [Contributing Process](#contributing-process) + - [File Architecture](#file-architecture) + - [Content Guidelines](#content-guidelines) + - [Local Testing](#local-testing) +- [Pull Request Process](#pull-request-process) + - [Before Submitting](#before-submitting) + - [Submission Guidelines](#submission-guidelines) + - [Review Process](#review-process) +- [Code of Conduct](#code-of-conduct) +- [Additional Ways to Contribute](#additional-ways-to-contribute) + +## Overview + +Optimism's documentation is open-source and hosted on GitHub in the `ethereum-optimism/docs` repository. The documentation is rendered at [docs.optimism.io](https://docs.optimism.io). You can contribute either by: +- Forking the `docs` repository and working locally +- Using the "Edit this page" button on any documentation page for smaller updates + +All contributions, pull requests, and issues should be in English at this time. We will be running a dedicated project in the future to add language support to the technical docs, so please reach out via our [developer support channel](https://github.com/ethereum-optimism/developers/) if you are interested in helping with that project. + +## Getting Started + +### Prerequisites +- Basic knowledge of Git and GitHub +- Familiarity with Markdown +- Understanding of technical documentation principles +- Node.js and npm installed + +### Development Setup +1. Install [pnpm](https://pnpm.io/installation) +2. Run `pnpm i` to install dependencies +3. Run `pnpm dev` to start development server +4. Visit [localhost:3000](http://localhost:3000) You can now start changing content and see the website updated live each time you save a new file. 🤓 -## Send Pull Request - -**Important prerequisite** - -To prevent building issues upstream, you should build the content locally before submitting a pull request: stop or delete the terminal server if it's running, then run `pnpm dev`. - -- Use the information reported by the terminal to fix any issues (e.g., broken links). -- Run `pnpm fix` to automatically fix most linting issues (e.g., formatting and style guide). -- Run `pnpm spellcheck:lint` to test your content against the dictionary. Add new words to the dictionary by appending them to `words.txt`. -- Run `pnpm spellcheck:fix` to add new words to the dictionary automatically. -- Try another `pnpm dev` and repeat until no issues are reported ("client" and "server compiled successfully"). - - -Your pull request should usually target the `main` branch, though the Optimism Documentation team might sometimes ask you to target another branch. - -To submit your contribution for review: - -1. Create a new [pull request on GitHub](https://github.com/ethereum-optimism/docs/issues/new/choose). -2. Select a PR type from the list or choose **Open a blank issue** at the bottom of the page. -3. Complete the form as requested. For blank PR issues, please provide a clear title and accurate description/context. -4. Click the "Create pull request" button to create the pull request effectively. - ->If your pull request is not ready for review yet, choose the "[Create draft pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)"in the dropdown. The Optimism documentation team will review your pull request only when you mark it as "[Ready for review](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)". +## Contributing Process + +### File Architecture +Our documentation is organized into two main sections: + +| Section | Purpose | Location | +|---------|----------|----------| +| Pages | Technical documentation content | `/docs/pages/` | +| Public | Images, icons, and illustrations | `/docs/public/` | + +**Warning**: The `public` folder contains `robots.txt` and `sitemap.xml` for SEO purposes. These files are maintained by the Documentation team only. + +### Content Guidelines +We use [Nextra](https://nextra.site/docs), a React and MDX-based framework with the docs theme (as opposed to the blog theme). The content you write is [Markdown](https://daringfireball.net/projects/markdown/syntax) that accepts [React](https://reactjs.org/) components. + +Please refer to our comprehensive [Style Guide](/pages/connect/contribute/style-guide.mdx) for detailed formatting instructions. + +### Local Testing +Before submitting your changes: +1. Stop or delete the terminal server if it's running +2. Run `pnpm dev` to test builds +3. Execute `pnpm fix` for automatic linting +4. Run `pnpm spellcheck:lint` for spell checking + - Add new words to the dictionary by appending them to `words.txt` +5. Use `pnpm spellcheck:fix` to update dictionary +6. Try another `pnpm dev` and repeat until no issues are reported ("client" and "server compiled successfully") + +If you encounter build issues: +- Check terminal output for error messages +- Verify all links are working +- Ensure proper formatting according to the style guide +- Test locally before pushing changes + +## Pull Request Process + +### Before Submitting +- Ensure all local tests pass +- Fix any reported issues +- Verify content accuracy +- Test all links and references +- Target the `main` branch (unless otherwise specified) + +### Submission Guidelines +1. Create a [new pull request](https://github.com/ethereum-optimism/docs/issues/new/choose) +2. Choose appropriate PR type or use blank template +3. Provide clear title and accurate description +4. Add required labels: + - `documentation` (required for all PRs) + - Content-specific: `tutorial`, `faq`, `troubleshooting` + - Feature-specific: `oracle`, `rpc-provider`, `faucet`, `attestation` + - Issue-specific: `user feedback`, `bug` -5. Add GitHub labels for the pull request. Add `documentation` to all pull requests in this repo **AND** additional labels based on the type of update or request. - - `tutorial`, `faq`, or `troubleshooting` for specific content types, - - `oracle`, `rpc-provider`, `faucet`, or `attestation` for ecosystem offerings, - - `user feedback` for general feedback about one or more pages, or - - `bug` if something isn't working as expected. ->If label for type of update is not set, the Optimism Documentation team will set or update this for you
- -**Warning** -Approved pull requests are usually merged immediately into the `main` branch, automatically triggering a deployment on docs.optimism.io. Please add the `flag:merge-pending-release` label if the pull request content should only be released publicly in sync with a product release. - -That's it! 🥳 Once the pull request is [reviewed and approved](#review-and-management-of-pull-requests), the Optimism Documentation team will merge it, and the content will be live on [docs.optimism.io](http://docs.optimism.io) a few minutes later. 🚀 - -## Review and Management of Pull Requests - -The pull request review process and timeline are based on the availability of the Optimism Documentation team to handle community contributions. The workflow is as follows: - -1. The pull request is assigned to a member of the Documentation team. -2. At least 1 member of the Documentation team will review the pull request for: - - - accuracy, - - quality, - - alignment with the documentation scope. - -3. Reviewers will either approve, ask for changes, or reject the pull request. -4. Accepted pull requests will be merged and automatically deployed on [docs.optimism.io](https://docs.optimism.io) a few minutes later. - -## Other Ways to Support the Project -All types of contributions are encouraged and valued. -And if you like the project, but just don't have time to contribute, that's fine too. There are other easy ways to support the project and show your appreciation, which we would also be very happy about: -- Star the project -- Tweet about it -- Refer this project in your project's readme -- Mention the project at local meetups and tell your friends/colleagues - -The community looks forward to your contributions. 🎉 +> **Note**: If label type is not set, the Documentation team will set or update it for you. + +> **Important**: Add `flag:merge-pending-release` label if the PR content should only be released publicly in sync with a product release. + +> **Tip**: Use "[Create draft pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)" if your work is still in progress. + +### Review Process +1. Assignment to Documentation team member +2. Technical review for accuracy +3. Quality and scope alignment check +4. Minimum 1 reviewer approval required +5. Reviewers will either approve, request changes, or close the pull request with comments +6. Automatic deployment after merge to [docs.optimism.io](https://docs.optimism.io) + +## Code of Conduct +- Be respectful and inclusive +- Follow project guidelines +- Provide constructive feedback +- Maintain professional communication +- Report inappropriate behavior + +## Additional Ways to Contribute +Even without direct code contributions, you can support us by: +- ⭐ Starring the project +- 🐦 Sharing on social media +- 📝 Mentioning us in your projects +- 🗣️ Spreading the word in your community + +Thank you for contributing to Optimism Docs! 🎉 From a7ee5c40d43e192829e56fbbf0113001dbf64f81 Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Mon, 3 Mar 2025 10:11:02 -0800 Subject: [PATCH 2/6] empty commit --- pages/stack/smart-contracts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/smart-contracts.mdx b/pages/stack/smart-contracts.mdx index 35759d155..b470212c6 100644 --- a/pages/stack/smart-contracts.mdx +++ b/pages/stack/smart-contracts.mdx @@ -90,7 +90,7 @@ closer to satisfying the 1 week exit window requirement for Stage 1. * [Governance Post](https://gov.optimism.io/t/final-protocol-upgrade-8-guardian-security-council-threshold-and-l2-proxyadmin-ownership-changes-for-stage-1-decentralization/8157)
- **Changelog** + **Changelog** **Added:** * LivenessGuard: [1.0.0](https://github.com/ethereum-optimism/optimism/blob/9047beb54c66a5c572784efec8984f259302ec92/packages/contracts-bedrock/src/Safe/LivenessGuard.sol#L29) From 969b353db9f407e4569de3b3a81771fbbe990a18 Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Mon, 3 Mar 2025 10:14:14 -0800 Subject: [PATCH 3/6] empty commit again --- pages/stack/smart-contracts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/smart-contracts.mdx b/pages/stack/smart-contracts.mdx index b470212c6..9707f1250 100644 --- a/pages/stack/smart-contracts.mdx +++ b/pages/stack/smart-contracts.mdx @@ -90,7 +90,7 @@ closer to satisfying the 1 week exit window requirement for Stage 1. * [Governance Post](https://gov.optimism.io/t/final-protocol-upgrade-8-guardian-security-council-threshold-and-l2-proxyadmin-ownership-changes-for-stage-1-decentralization/8157)
- **Changelog** + **Changelog** **Added:** * LivenessGuard: [1.0.0](https://github.com/ethereum-optimism/optimism/blob/9047beb54c66a5c572784efec8984f259302ec92/packages/contracts-bedrock/src/Safe/LivenessGuard.sol#L29) From b196cab512e6431dda5d2ea26c17b383ee9d5f89 Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Mon, 3 Mar 2025 10:14:52 -0800 Subject: [PATCH 4/6] empty commit again and again --- pages/stack/smart-contracts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/stack/smart-contracts.mdx b/pages/stack/smart-contracts.mdx index 9707f1250..324ee435e 100644 --- a/pages/stack/smart-contracts.mdx +++ b/pages/stack/smart-contracts.mdx @@ -90,7 +90,7 @@ closer to satisfying the 1 week exit window requirement for Stage 1. * [Governance Post](https://gov.optimism.io/t/final-protocol-upgrade-8-guardian-security-council-threshold-and-l2-proxyadmin-ownership-changes-for-stage-1-decentralization/8157)
- **Changelog** + **Changelog** **Added:** * LivenessGuard: [1.0.0](https://github.com/ethereum-optimism/optimism/blob/9047beb54c66a5c572784efec8984f259302ec92/packages/contracts-bedrock/src/Safe/LivenessGuard.sol#L29) From 74cbd41304b7d4580944819d7d400b6e136f5679 Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Wed, 5 Mar 2025 10:00:34 -0800 Subject: [PATCH 5/6] Empty commit again --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ad3cf4833..2dd99a02b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -16,7 +16,7 @@ Thanks for taking the time to contribute! ❤️ - [Submission Guidelines](#submission-guidelines) - [Review Process](#review-process) - [Code of Conduct](#code-of-conduct) -- [Additional Ways to Contribute](#additional-ways-to-contribute) +- [Additional Ways to Contribute](#additional-ways-to-contribute) ## Overview From ab7671a57353cfbd5a999779918f27d3bd54e7bf Mon Sep 17 00:00:00 2001 From: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com> Date: Wed, 5 Mar 2025 10:03:49 -0800 Subject: [PATCH 6/6] Auto-fix: Update breadcrumbs, spelling dictionary and other automated fixes --- pages/stack/smart-contracts.mdx | 68 +++++++++++++++++---------------- words.txt | 1 + 2 files changed, 36 insertions(+), 33 deletions(-) diff --git a/pages/stack/smart-contracts.mdx b/pages/stack/smart-contracts.mdx index 9f367c0c8..7535d78f7 100644 --- a/pages/stack/smart-contracts.mdx +++ b/pages/stack/smart-contracts.mdx @@ -33,15 +33,18 @@ Contract releases have a component name of `op-contracts` and therefore are tagg smart contracts—only deploy from `op-contracts/vX.Y.Z` -#### op-contracts/v1.8.0 - Holocene contract changes +#### op-contracts/v1.8.0 - Holocene contract changes This release is suitable for the L1 contracts as part of the Holocene network upgrade. The Holocene network upgrade contains three changes: * Holocene block derivation: a set of changes that render the derivation pipeline stricter and simpler, but also improve worst-case scenarios for Fault Proofs and Interoperability. + * EIP-1559 configurability: The elasticity and denominator EIP-1559 parameters become configurable via the SystemConfig L1 contract, allowing gas target and gas limit to be independently configured. + * MIPS contract upgrade: Updates to support additional calls made by the new op-program version. * [Official - Holocene Contract Release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0) + * [Governance Post](https://gov.optimism.io/t/upgrade-proposal-11-holocene-network-upgrade/9313)
@@ -52,7 +55,7 @@ This release is suitable for the L1 contracts as part of the Holocene network up * SystemConfig: [2.3.0](https://github.com/ethereum-optimism/optimism/blob/op-contracts/v1.8.0/packages/contracts-bedrock/src/L1/SystemConfig.sol) * FaultDisputeGame: [1.3.1](https://github.com/ethereum-optimism/optimism/blob/op-contracts/v1.8.0/packages/contracts-bedrock/src/dispute/FaultDisputeGame.sol) * PermissionedDisputeGame: [1.3.1](https://github.com/ethereum-optimism/optimism/blob/op-contracts/v1.8.0/packages/contracts-bedrock/src/dispute/PermissionedDisputeGame.sol) - + **No change:** * AddressManager: [Latest (this has no version)](https://github.com/ethereum-optimism/optimism/blob/op-contracts/v1.2.0/packages/contracts-bedrock/src/legacy/AddressManager.sol) @@ -109,14 +112,14 @@ The upgrade was coupled with the Granite network upgrade to improve the stabilit The Safe Extensions protocol upgrade is intended to increase the security and decentralization of the Superchain by: -1. Increasing the Security Council Safe's signing threshold, from 4 to 10, out -of 13 owners. This meets the 75% threshold requirement for a Stage 1 rollup -outlined in [L2Beat's Stages framework](https://medium.com/l2beat/stages-update-security-council-requirements-4c79cea8ef52) -2. Reassigning the role of Guardian from the Foundation to a new Guardian Safe -with the Security Council Safe as its sole owner. This moves the Superchain -closer to satisfying the 1 week exit window requirement for Stage 1. - * Additionally the Foundation is appointed to the new DeputyGuardian role - which is able to act as Guardian through the Guardian Safe. This +1. Increasing the Security Council Safe's signing threshold, from 4 to 10, out + of 13 owners. This meets the 75% threshold requirement for a Stage 1 rollup + outlined in [L2Beat's Stages framework](https://medium.com/l2beat/stages-update-security-council-requirements-4c79cea8ef52) +2. Reassigning the role of Guardian from the Foundation to a new Guardian Safe + with the Security Council Safe as its sole owner. This moves the Superchain + closer to satisfying the 1 week exit window requirement for Stage 1. + * Additionally the Foundation is appointed to the new DeputyGuardian role + which is able to act as Guardian through the Guardian Safe. This appointment can be revoked by the Security Council Safe at any time. 3. Reassigning the owner of the L2ProxyAdmin contract from the Foundation to the Security Council. This ensures the Security Council Safe has a blocking @@ -126,7 +129,7 @@ closer to satisfying the 1 week exit window requirement for Stage 1. * [Governance Post](https://gov.optimism.io/t/final-protocol-upgrade-8-guardian-security-council-threshold-and-l2-proxyadmin-ownership-changes-for-stage-1-decentralization/8157)
- **Changelog** + **Changelog**\ **Added:** * LivenessGuard: [1.0.0](https://github.com/ethereum-optimism/optimism/blob/9047beb54c66a5c572784efec8984f259302ec92/packages/contracts-bedrock/src/Safe/LivenessGuard.sol#L29) @@ -389,32 +392,32 @@ optionally halt if using the wrong version. #### SystemConfig -The `SystemConfig` contract helps manage configuration of an OP Stack -network. Much of the network's configuration is stored on L1 and picked up by -L2 as part of the derivation of the L2 chain. The contract also contains +The `SystemConfig` contract helps manage configuration of an OP Stack +network. Much of the network's configuration is stored on L1 and picked up by +L2 as part of the derivation of the L2 chain. The contract also contains references to all other contract addresses for the chain. #### DisputeGameFactory -The `DisputeGameFactory` deploys instances of `FaultDisputeGame` and `PermissionedDisputeGame` -to resolve disputes about the OP Stack chain state at specific block numbers. +The `DisputeGameFactory` deploys instances of `FaultDisputeGame` and `PermissionedDisputeGame` +to resolve disputes about the OP Stack chain state at specific block numbers. It serves as the entry point for creating and managing dispute games. The factory uses the `AnchorStateRegistry` for initialization, and integrates the `DelayedWETH` contract to manage participant bonds. #### FaultDisputeGame -The `FaultDisputeGame` resolves disputes about the OP Stack chain state by -allowing participants to propose or challenge states. -It is deployed by the `DisputeGameFactory` and includes logic to finalize disputes. -The contract uses the `AnchorStateRegistry` to start from trusted states, -`MIPS` to execute fault proofs, the `PreimageOracle` to validate hash-based claims, +The `FaultDisputeGame` resolves disputes about the OP Stack chain state by +allowing participants to propose or challenge states. +It is deployed by the `DisputeGameFactory` and includes logic to finalize disputes. +The contract uses the `AnchorStateRegistry` to start from trusted states, +`MIPS` to execute fault proofs, the `PreimageOracle` to validate hash-based claims, and the `DelayedWETH` contract to handle bonds. #### PermissionedDisputeGame -The `PermissionedDisputeGame` is also deployed by the `DisputeGameFactory`, -and inherits logic and dependencies from `FaultDisputeGame` while adding role-based restrictions. +The `PermissionedDisputeGame` is also deployed by the `DisputeGameFactory`, +and inherits logic and dependencies from `FaultDisputeGame` while adding role-based restrictions. It restricts participation to specific roles, such as designated proposers or challengers. It is used when stricter access controls are required, as enforced by the Guardian. @@ -432,22 +435,21 @@ This mechanism ensures participants are financially committed and disputes are f #### MIPS -The `MIPS` contract provides an on-chain implementation of a big-endian MIPS32 R1 virtual machine, -designed to execute fault proofs for disputes by processing a standardized instruction set. +The `MIPS` contract provides an on-chain implementation of a big-endian MIPS32 R1 virtual machine, +designed to execute fault proofs for disputes by processing a standardized instruction set. This enables instances of `FaultDisputeGame` and `PermissionedDisputeGame` to resolve disputes - over state transitions accurately and consistently. - The process starts from the trusted anchor state provided by the `AnchorStateRegistry`, - ensuring that the dispute is based on a reliable foundation. - The `PreimageOracle` is then used to retrieve pre-images of hash-based claims, - validating the data used in the computation and ensuring its integrity. +over state transitions accurately and consistently. +The process starts from the trusted anchor state provided by the `AnchorStateRegistry`, +ensuring that the dispute is based on a reliable foundation. +The `PreimageOracle` is then used to retrieve pre-images of hash-based claims, +validating the data used in the computation and ensuring its integrity. #### PreimageOracle -The `PreimageOracle` maps hashes to their corresponding pre-images for secure and permissioned data retrieval. -It validates hash-based claims used in disputes, such as state transitions or computational steps. +The `PreimageOracle` maps hashes to their corresponding pre-images for secure and permissioned data retrieval. +It validates hash-based claims used in disputes, such as state transitions or computational steps. This ensures the integrity of fault proofs in `FaultDisputeGame` and `PermissionedDisputeGame` instances. - #### DEPRECATED - L2OutputOracle The `L2OutputOracle` contains an array of L2 state outputs, where each output is a diff --git a/words.txt b/words.txt index 326d37a04..25d6705da 100644 --- a/words.txt +++ b/words.txt @@ -115,6 +115,7 @@ ETHERBASE etherbase Ethernity Ethernow +ethpandaops ETHSTATS ethstats EVMTIMEOUT