-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update fraud-detector doc for Anchorage #1380
Open
mmontour1306
wants to merge
1
commit into
develop
Choose a base branch
from
mm/fraud-detector-doc
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,9 @@ | |
description: Learn how to help detect operator fraud | ||
--- | ||
|
||
# Checking Boba Mainnet for Fraud | ||
# Checking Boba Mainnet for Fraud (pre-Anchorage) | ||
|
||
This page applies to the Boba network prior to the Anchorage update in April 2024. The block derivation process in the new system provides stronger inherent guarantees of cross-chain consistency, as described at https://specs.optimism.io/protocol/derivation.html in the Optimism Bedrock documentation. The following information is preserved as a historical reference. | ||
|
||
## Basics | ||
|
||
|
@@ -16,7 +18,7 @@ The central idea is that if two (or more) geths injects the same transactions, t | |
|
||
## What do when you discover a state root mismatch | ||
|
||
Congratulations! The security of the L2 depends on community monitoring of the operator's actions. If you have discovered a state root mismatch, please file a GitHub issue (https://github.com/bobanetwork/boba/issues). We should have a good response/clarification for you quickly. In the future, with the Boba governance token, additional mechanisms will be released to incentivize and reward community monitoring of Boba. | ||
(section removed; not applicable to Anchorage) | ||
|
||
## Running the Fraud Detector, the Verifier, and the Data Transport Layer (DTL) from local images | ||
|
||
|
@@ -25,8 +27,8 @@ Congratulations! The security of the L2 depends on community monitoring of the o | |
**Open a terminal window**. First, clone the project and install needed dependencies: | ||
|
||
```bash | ||
$ git clone [email protected]:bobanetwork/boba.git | ||
$ cd boba | ||
$ git clone [email protected]:bobanetwork/boba_legacy.git | ||
$ cd boba_legacy | ||
$ yarn install | ||
$ yarn build | ||
$ cd ops | ||
|
@@ -63,7 +65,7 @@ $ docker compose up | |
Finally, **Open another terminal window** and upload the `addresses.json` to the `data transport layer` service. | ||
|
||
```bash | ||
$ cd boba/boba_community/fraud-detector | ||
$ cd boba_legacy/boba_community/fraud-detector | ||
$ curl -H "Content-Type: application/json" -T state-dumps/mainnet/addresses.json http://localhost:8080/addresses.json | ||
``` | ||
|
||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we think it makes sense to mention Anchorage in the legacy repo?
What we've done for other pages which are outdated but linked to from the doc is to either delete the link, or, add an intermediary landing page which mentions that the old doc is pre-anchorage. In this case I would kind of think simply deleting the link might make the most sense?