Feat/r0.8 gov

[sajanrajdev]

• Remove the Security mutltisig as default for the authority owner: Owner should be the deployer since it is required for wiring up governance in the same run
• Adds the multisigs where missing
• Removes deployemt outputs for Sepolia exceptt for the Timelocks and adds the mainnet Timelocks
• Adds the option to skip Timelocks wiring in case exisitng timelocks are reused

Summary by CodeRabbit

• New Features

  • Introduced a conditional check for Timelock configuration, enhancing flexibility in setup.
  • Updated multisig addresses for improved security and operational efficiency.
  • Added a new parameter for authority ownership, allowing better control over deployment.
  • Introduced a toggle for manual Timelock configuration, providing more customization options.

• Refactor

  • Enhanced security and operational control in deployment setup through various parameter updates and new additions.

[coderabbitai[bot]]

Walkthrough

The recent updates enhance security and operational control in blockchain contract deployment. A new conditional check manages timelock configuration, while refined multisig addresses bolster security. An authority ownership parameter is introduced for improved operational control.

Changes

Files	Summary
.../eBTCDeployScript.js .../eBTCDeploymentParams.mainnet.js	Conditional check added for timelock configuration control. Multisig addresses updated, authority ownership parameter added, manual Timelock configuration toggle introduced.
.../eBTCDeploymentParams.sepolia.js	Updated authorityOwner, collateral, securityMultisig, cdpTechOpsMultisig values. Added SKIP_TIMELOCK_CONFIG.

Poem

🌟 In the land of code and vast digital seas,
🐰 A rabbit worked hard with the greatest of ease.
"To secure and to manage," it said with a hop,
🛠️ Adjusting the locks, not a single one to drop.
🗝️ With timelocks and multisigs, updates galore,
Ensuring the blockchain was safe, evermore.
🎉 "Let's celebrate changes, both big and small,
For together, we hop higher and never fall!" 🚀

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

---

Tips

### Chat There are 3 ways to chat with CodeRabbit: - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit-tests for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit tests for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit tests.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - The JSON schema for the configuration file is available [here](https://coderabbit.ai/integrations/coderabbit-overrides.v2.json). - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json` ### CodeRabbit Discord Community Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback.

[getrecon-bot]

Job ID	360416d2-f2cf-49cf-84aa-4b5bbd98d3e2
Command	yarn && git submodule init && git submodule update && solc-select use 0.8.17 && cd packages/contracts/ && yarn echidna --test-mode assertion --test-limit 300000
Instance ID	i-045e355f441da9af3
Instance Type	c5.2xlarge
Status	Started
Elapsed

[getrecon-bot]

Job ID	360416d2-f2cf-49cf-84aa-4b5bbd98d3e2
Command	yarn && git submodule init && git submodule update && solc-select use 0.8.17 && cd packages/contracts/ && yarn echidna --test-mode assertion --test-limit 300000
Instance ID	i-045e355f441da9af3
Instance Type	c5.2xlarge
Status	Running
Elapsed	49 seconds

[getrecon-bot]

Job ID	360416d2-f2cf-49cf-84aa-4b5bbd98d3e2
Command	yarn && git submodule init && git submodule update && solc-select use 0.8.17 && cd packages/contracts/ && yarn echidna --test-mode assertion --test-limit 300000
Instance ID	i-045e355f441da9af3
Instance Type	c5.2xlarge
Status	Running
Elapsed	50 seconds

[getrecon-bot]

Job ID	360416d2-f2cf-49cf-84aa-4b5bbd98d3e2
Command	yarn && git submodule init && git submodule update && solc-select use 0.8.17 && cd packages/contracts/ && yarn echidna --test-mode assertion --test-limit 300000
Instance ID	i-045e355f441da9af3
Instance Type	c5.2xlarge
Status	Error
Elapsed	1 minute 11 seconds