Skip to content

Commit 4c78801

Browse files
committed
Update fault-proof explainer with warning about create-game subcommand and provide guidance for op-challenger usage
1 parent a5814a3 commit 4c78801

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

pages/stack/fault-proofs/explainer.mdx

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -86,11 +86,17 @@ Due to the permissionless structure where many different actors can participate
8686
Users can complete the full withdrawal cycle without depending on any privileged action.
8787
The Guardian role can override the system by pausing withdrawals, blacklisting games, or reverting to a permissioned system.
8888
As a result, the trust assumption is reduced to requiring only that the Guardian role does not act to intervene, inline with the stage 1 requirements.
89+
8990
### Since the roles of proposer and challenger will be open to everyone, are guides available outlining the best practices for running them?
9091

9192
It's not expected that normal users run `op-proposer` to regularly propose output roots.
92-
Users would generally just propose a single output root if they need to withdraw and the chain operator isn't proposing outputs for them via direct calls to the `DisputeGameFactory` via Etherscan or using the [`create-game`](https://github.com/ethereum-optimism/optimism/tree/develop/op-challenger#create-game) subcommand of `op-challenger`.
93-
Documentation for `op-challenger` is forthcoming.
93+
Users would generally just propose a single output root if they need to withdraw and the chain operator isn't proposing outputs for them via direct calls to the `DisputeGameFactory` via Etherscan.
94+
95+
<Callout type="warning">
96+
The [`create-game`](https://github.com/ethereum-optimism/optimism/tree/develop/op-challenger#create-game) subcommand of `op-challenger` is **for testing purposes only** and should not be used in production environments. It is not intended as a replacement for proper `op-proposer` infrastructure.
97+
</Callout>
98+
99+
For detailed guidance on running `op-challenger`, see the [OP-Challenger explainer](/stack/fault-proofs/challenger) and [how to configure challenger for your chain](/operators/chain-operators/tools/op-challenger).
94100

95101
### How much ETH should a chain operator put aside to operate the Fault Proof System?
96102

0 commit comments

Comments
 (0)