bet(testnet/config): Update app.toml according to the new releases

[chuck-bear]

Since v0.2.0-alpha.5 the app.toml file has a lof of deprecated config. This PR will update the testnet config to avoid any confusion.

Summary by CodeRabbit

• New Features

  • Introduced new configuration sections for beacon-kit.block-store-service and beacon-kit.node-api, both disabled by default.

• Changes

  • Updated rpc-jwt-refresh-interval from "30s" to "20s".

• Removed Features

  • Significant reduction in configuration options, including API, state sync, streaming, and mempool settings.

[coderabbitai]

Walkthrough

The pull request introduces significant changes to the app.toml configuration file, including the removal of several sections related to API, state sync, streaming, and mempool configurations. New sections for beacon-kit.block-store-service and beacon-kit.node-api have been added, both set to disabled by default. Additionally, a minor update was made to the rpc-jwt-refresh-interval parameter, changing its value from "30s" to "20s".

Changes

File Path	Change Summary
testing/networks/80084/app.toml	- Removed API configuration section, including server settings and timeout configurations.
	- Removed state sync configuration, including snapshot intervals and retention settings.
	- Removed streaming configuration, eliminating ABCI listener settings.
	- Removed mempool configuration, which included transaction limits.
	- Updated rpc-jwt-refresh-interval from "30s" to "20s".
	- Added new sections: [beacon-kit.block-store-service] and [beacon-kit.node-api], both disabled by default.

Possibly related PRs

• chore(testing/config): Update testing config #2000: The changes in both PRs involve modifications to the app.toml configuration file, specifically related to timeout settings, indicating a direct connection in the configuration adjustments being made.

Suggested reviewers

• itsdevbear
• ocnc

Poem

In the meadow where bunnies play,
Configs change in a bright new way.
APIs gone, but new friends arrive,
With BeaconKit, our hopes will thrive!
Hopping forward, we cheer and sing,
For every change, a joyful spring! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 7cbda07 and b9e566a.

📒 Files selected for processing (1)

• testing/networks/80084/app.toml (2 hunks)

🔇 Additional comments not posted (4)

testing/networks/80084/app.toml (4)

166-171: Please provide more information about the new block store service.

A new beacon-kit.block-store-service section has been added with the following configurations:

1. The service is disabled by default.
2. An availability window of 8192 slots is set.

Could you please provide more context on:

1. The purpose and functionality of this new service?
2. The implications of enabling this service?
3. How the availability window of 8192 slots was determined and its potential impact on system resources?

This information will help in assessing the appropriateness of these default settings.

To gather more information about this new service, please run the following script:

#!/bin/bash
# Description: Search for any documentation or code related to the new block store service.

echo "Searching for block store service documentation:"
rg --type md 'block store service'

echo "Searching for block store service implementation:"
ast-grep --lang go --pattern $'type BlockStoreService struct {
  $$$
}'

Please review the results to provide more context about this new service.

---

173-181: Please provide more information about the new node API and consider security implications.

A new beacon-kit.node-api section has been added with the following configurations:

1. The API is disabled by default.
2. It's set to bind to all interfaces (0.0.0.0) on port 3500.
3. Logging for this API is disabled by default.

Could you please provide more context on:

1. The purpose and functionality of this new API?
2. The implications of enabling this API?
3. The security considerations for binding to all interfaces (0.0.0.0)?

Additionally, consider the following security recommendations:

1. If the API is intended for local use only, consider binding it to localhost (127.0.0.1) instead of all interfaces.
2. Ensure that proper authentication and authorization mechanisms are in place before enabling this API.
3. Consider enabling logging by default to aid in troubleshooting and security auditing.

To gather more information about this new API and its security implications, please run the following script:

#!/bin/bash
# Description: Search for any documentation or code related to the new node API and its security measures.

echo "Searching for node API documentation:"
rg --type md 'node API'

echo "Searching for node API implementation and security measures:"
ast-grep --lang go --pattern $'func setupNodeAPI() {
  $$$
}'

Please review the results to provide more context about this new API and its security measures.

---

Line range hint 1-181: Please clarify the implications of removed configuration sections.

According to the AI-generated summary, several configuration sections have been removed, including:

1. API configuration
2. State sync configuration
3. Streaming configuration
4. Mempool configuration

Could you please provide more context on:

1. The reasoning behind removing these configuration sections?
2. How the functionality previously controlled by these configurations is now managed?
3. Any potential impacts on system behavior or performance due to these removals?
4. Whether these changes are part of a larger architectural shift or update?

Understanding these points will help ensure that the removal of these configurations doesn't inadvertently impact the system's functionality or performance.

To assess the impact of these removals, please run the following script:

#!/bin/bash
# Description: Search for any references to the removed configurations in the codebase.

echo "Searching for references to removed configurations:"
rg --type go 'API config|State sync|Streaming config|Mempool config'

echo "Checking for any migration scripts or update notes:"
rg --type md 'configuration changes|removed configs'

Please review the results to provide more context about the implications of these configuration removals.

---

121-121: Verify the impact of reduced JWT refresh interval.

The JWT refresh interval has been reduced from 30 seconds to 20 seconds. While this could potentially improve security by refreshing the JWT more frequently, it's important to verify that this change doesn't negatively impact performance or increase network traffic significantly.

To assess the impact, please run the following script:

Please review the results to ensure that this change aligns with the overall system performance goals.

---

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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 22.39%. Comparing base (7cbda07) to head (b9e566a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2023      +/-   ##
==========================================
- Coverage   22.39%   22.39%   -0.01%     
==========================================
  Files         358      358              
  Lines       16046    16043       -3     
  Branches       13       12       -1     
==========================================
- Hits         3594     3593       -1     
+ Misses      12303    12301       -2     
  Partials      149      149              

Flag	Coverage Δ
	22.39% <ø> (-0.01%)	⬇️

see 2 files with indirect coverage changes