Add mainnet example config

[Thaleszh]

Description

Prepare repo for mainnet by adding mainnet config example:

• Using mainnet chain ID
• Adjusting gas price
• Updating coin names

Type of change

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Documentation (updates documentation on the project)
• chore (Updates on dependencies, gitignore, etc)
• test (For updates on tests)

[coderabbitai]

Walkthrough

Two configuration example files for a price feeder application have been modified. A new comprehensive mainnet configuration file (config.mainnet.example.toml) was introduced, providing a complete template with sections for voting and server operation flags, server settings, gas parameters, account credentials, RPC endpoints, currency pairs (BTC, ETH, SOL, XRP, BNB, USDT, USDC, XAUT, TRX), deviation thresholds, provider endpoints, and telemetry instrumentation. The testnet configuration file received a single-line correction enabling the prometheus_retention parameter by removing an invalid prefix.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Review the structure and completeness of the mainnet configuration template to ensure all required sections are present
• Verify that the prometheus_retention fix in the testnet config properly corrects the TOML syntax
• Check that default values in the mainnet config are reasonable for mainnet deployment (gas prices, timeouts, etc.)

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add mainnet example config' directly and specifically describes the primary change in the PR, which adds a new mainnet configuration example file.
Description check	✅ Passed	The description is directly related to the changeset, explaining the purpose of adding mainnet config, mentioning specific adjustments like mainnet chain ID and gas price updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/mainnet

---

📜 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 388c157 and ebe7535.

📒 Files selected for processing (2)

• config.mainnet.example.toml (1 hunks)
• config.testnet.example.toml (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• config.mainnet.example.toml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: analyze

🔇 Additional comments (1)

config.testnet.example.toml (1)

306-306: Fix telemetry configuration by enabling prometheus_retention.

The correction to line 306 properly enables the prometheus_retention parameter in the telemetry section. This aligns with the telemetry enhancements described in the PR objectives.

Note: The PR objectives mention a new mainnet configuration file (config.mainnet.example.toml), but it was not provided for review. Only the testnet configuration was available. If you'd like me to review the mainnet configuration as well, please provide that file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}