The Thanos Stack offers a variety of configurable parameters that can be customized to better suit specific operational goals or use cases. While the default settings provided by Optimism are the result of extensive testing and are considered the most stable, making adjustments may be necessary in certain scenarios. However, it's crucial to proceed with caution, as excessive or improper modifications could potentially impact the stability of the network.

<aside> 💡

To estimate operational costs, we've created a worksheet that allows you to adjust parameters impacting fees. Use this tool to refine your network's needs before deployment. Access the worksheet here: Thanos Stack Operation Fee Adjustment Spreadsheet

</aside>

1. Configurable FPS Parameters from the Downloaded Config File

Fig. Generate and download Network config file

Parameters to Consider

After downloading the config file during the "Configure env" step, you will find several parameters. Modifying any of these parameters will update the config values accordingly. For detailed explanations of these parameters, refer to the [Link].

Warning: Risks of Modifying FPS Parameters

1. System Stability:
   • Reducing values like faultGameMaxDepth or faultGameSplitDepth could compromise the fault proof system’s ability to process complex disputes, leading to incomplete resolutions.
2. Fairness of Disputes:
   • Shortening time-related parameters such as faultGameClockExtension, faultGameMaxClockDuration, or faultGameWithdrawalDelay might not provide participants enough time to respond or complete disputes, leading to unfair outcomes.
   • Excessively long durations may cause unnecessary delays in resolution, thereby extending the withdrawal period.
   • Inadequate review periods, such as lowering preimageOracleChallengePeriod, could increase the risk of errors or malicious actions going undetected.
3. Operational Efficiency:
   • Adjustments to preimageOracleMinProposalSize could lead to inefficiencies by allowing trivial submissions or premature actions that are not thoroughly validated.
   • Longer delays in finality and maturity settings (disputeGameFinalityDelaySeconds, proofMaturityDelaySeconds) could reduce the system’s throughput and slow down operations.

2. Adjustment of Initial Bond(DisputeGameFactory_setInitBond)

Fig. Safe Wallet sending ‘new transaction’.

After deploying the DisputeGameFactory contract, you need to configure the initBonds value. Follow the steps here to set the initial bond for each DisputeGameFactory you create.

Initial Bond Risks.

• Setting an insufficiently high InitialBond may enable malicious actors to engage in disputes with low stakes, increasing spam or frivolous activities within the system.
• Conversely, an excessively high InitialBond could discourage legitimate participants from entering disputes, thereby reducing system fairness and efficiency.