Add env.json

[fbac]

Summary by CodeRabbit

• New Features
  • Introduced an updated environment configuration for the testnet playground. This enhancement enables seamless connectivity to the blockchain network and integration with essential smart contract components through customizable settings.
  • Updated the key for the blockchain network identifier from chainId to chain_id in the configuration file.

[coderabbitai]

Walkthrough

The JSON configuration file env.json has been modified by renaming the key chainId to chain_id. This change affects the reference to the blockchain network identifier within the configuration, while all other properties, including name, nodes_contract_address, messages_contract_address, identity_updates_contract_address, and rates_manager_contract_address, remain unchanged.

Changes

File(s)	Summary
contracts/config/xmtp_testnet-playground/env.json	Renamed key from "chainId" to "chain_id"; all other properties remain unchanged.

Suggested reviewers

• neekolas

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5d5844d and 75a82f9.

📒 Files selected for processing (2)

• contracts/config/xmtp_testnet-playground/env.json (1 hunks)
• contracts/config/xmtp_testnet-playground/env.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• contracts/config/xmtp_testnet-playground/env.json
• contracts/config/xmtp_testnet-playground/env.json

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Build pre-baked anvil-xmtpd
• GitHub Check: Push Docker Images to GitHub Packages (xmtpd)

---

🪧 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 generate docstrings to generate docstrings for this 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 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

contracts/config/xmtp_testnet-playground/env.json (1)

1-9: Ensure Valid JSON Structure and Remove Extraneous Content

The configuration file is well-structured and includes all the necessary keys for the xmtp_testnet-playground environment. Each property is clearly defined and appears correctly formatted. However, please verify that the trailing line labeled “9” is not an accidental inclusion in the actual file—as any extraneous characters after the closing brace would make the JSON invalid. If this “9” is merely an artifact from the annotation, it should be removed from the file to maintain proper JSON syntax.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2a73ef3 and 5d5844d.

📒 Files selected for processing (1)

• contracts/config/xmtp_testnet-playground/env.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: abis
• GitHub Check: Build pre-baked anvil-xmtpd

[mkysel]

something tells me that we will need to redeploy identity_updates_contract_address soon