docs(testnet-v6): update deployedContracts.json

[adu-web3]

Description

Since we have redeployed some new contracts for testnet v6, we should update deployedContracts.json with other possible updates to reflect the changes.

Summary by CodeRabbit

• New Features
  • Updated configurations for clientChain and exocore, enhancing functionality with new entries such as bootstrap, bootstrapLogic, and erc20Token.
• Bug Fixes
  • Corrected various address entries in clientChain and exocore, ensuring improved reliability and performance.

[coderabbitai]

Walkthrough

The changes involve updates to the script/deployedContracts.json file, specifically in the clientChain and exocore sections. Several existing entries have been modified with new addresses, and new entries have been added, including bootstrap, bootstrapLogic, and erc20Token in the clientChain, as well as exocoreProxyAdmin in the exocore section. The lzEndpoint entry remains unchanged.

Changes

File	Change Summary
script/deployedContracts.json	Updated multiple entries in the clientChain and exocore sections with new addresses and added new entries.

Poem

In the land of code where contracts play,
New values dance and old ones sway.
With beacons bright and tokens new,
The chains align, a wondrous view.
Hops of joy, the rabbit sings,
For every change, a world it brings! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c976212 and a6faa78.

📒 Files selected for processing (1)

• script/deployedContracts.json (1 hunks)

🧰 Additional context used

🪛 Gitleaks

script/deployedContracts.json

9-9: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

10-10: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

🔇 Additional comments (6)

script/deployedContracts.json (6)

12-15: LGTM: Contract addresses updated as expected.

The changes in this section of clientChain are consistent with the PR objectives. The addresses for proxyAdmin, vaultBeacon, and vaultImplementation have been updated, while wstETH remains unchanged. All updated addresses are valid Ethereum addresses.

---

21-21: Confirmed: lzEndpoint address remains unchanged.

The lzEndpoint address in the exocore section has not been modified, which is consistent with the expected changes for this update.

---

9-10: Note: False positive static analysis warnings.

The static analysis tool Gitleaks reported potential Generic API Key detections on lines 9 and 10. These are false positives as the detected strings are valid Ethereum addresses, not API keys. No action is required.

🧰 Tools

🪛 Gitleaks

9-9: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

10-10: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

Line range hint 1-23: LGTM: All changes are consistent with PR objectives.

This review confirms that all changes in the script/deployedContracts.json file are consistent with the PR objectives of updating contract addresses for testnet v6. The modifications include:

1. In the clientChain section:

   • Added new entries: bootstrap, bootstrapLogic, and erc20Token.
   • Updated existing entries: capsuleBeacon, capsuleImplementation, clientGatewayLogic, proxyAdmin, vaultBeacon, and vaultImplementation.

2. In the exocore section:

   • Updated existing entries: exocoreGateway and exocoreGatewayLogic.
   • Added a new entry: exocoreProxyAdmin.

3. The lzEndpoint addresses in both sections remain unchanged.

All new and updated addresses are valid Ethereum addresses, and the JSON structure remains intact. The changes accurately reflect the redeployment of new contracts for testnet v6 as described in the PR objectives.

🧰 Tools

🪛 Gitleaks

9-9: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

10-10: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

5-10: LGTM: New contract addresses added and existing ones updated.

The changes in the clientChain section align with the PR objectives. New contract addresses for bootstrap, bootstrapLogic, and erc20Token have been added, while capsuleBeacon, capsuleImplementation, and clientGatewayLogic have been updated. All addresses appear to be valid Ethereum addresses.

To ensure consistency, let's verify these changes against the deployment logs or configuration:

#!/bin/bash
# Verify the new and updated contract addresses
grep -E "bootstrap|capsuleBeacon|capsuleImplementation|clientGatewayLogic|erc20Token" $(find . -name "*.log" -o -name "*.config" -type f)

🧰 Tools

🪛 Gitleaks

9-9: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

10-10: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

18-20: LGTM: Exocore contract addresses updated and new entry added.

The changes in the exocore section are in line with the PR objectives. The addresses for exocoreGateway and exocoreGatewayLogic have been updated, and a new entry exocoreProxyAdmin has been added. All addresses are valid Ethereum addresses.

To ensure consistency, let's verify these changes against the deployment logs or configuration:

---

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
• Mastodon
• Reddit
• LinkedIn

🪧 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 <commit_id>, please review it.
  • Generate unit testing code 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.