Skip to content

Conversation

@notdanilo
Copy link
Contributor

@notdanilo notdanilo commented Oct 8, 2025

Status Type ⚠️ Core Change Issue
Ready Tooling No None

Problem

ephemeral-validator is outdated

Solution

Update it

Greptile Overview

Updated On: 2025-10-08 14:00:30 UTC

Summary

This PR updates the ephemeral-validator dependency and configuration across the Bolt framework. The main changes involve updating the ephemeral-validator configuration template to use a new schema format required by the newer version of the tool.

The most significant change is in the ephemeral-validator.toml template file, where the configuration format has been modernized from underscore-separated keys to hyphenated keys (millis_per_slotmillis-per-slot, frequency_millisfrequency-millis). Additionally, the remote configuration has been restructured from a simple string value to a nested object (remote = "url"remote.url = "url").

To support the dependency update, the sysinfo dependency in the root Cargo.toml has been pinned to an exact version (=0.36.1) instead of using a flexible constraint (^0). This ensures reproducible builds and prevents potential compatibility issues.

The .gitignore file has been updated to exclude new test ledger directories created by the updated ephemeral-validator, which now generates directories with the -magicblock suffix pattern. This change maintains consistency with existing ignore patterns for test artifacts.

These changes are part of a tooling update that doesn't affect core functionality but ensures the development environment uses the latest ephemeral-validator with its updated configuration schema.

Important Files Changed

Changed Files
Filename Score Overview
.gitignore 5/5 Added gitignore entry for new test ledger directories with -magicblock suffix
Cargo.toml 4/5 Pinned sysinfo dependency to exact version =0.36.1 for reproducible builds
crates/bolt-cli/src/templates/ephemeral-validator.toml 4/5 Updated configuration template to use new hyphenated field names and nested remote object structure

Confidence score: 4/5

  • This PR is safe to merge with minimal risk as it primarily updates tooling configuration
  • Score reflects straightforward dependency and configuration updates with potential for minor compatibility issues
  • Pay close attention to the ephemeral-validator template configuration changes to ensure compatibility

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3 files reviewed, no comments

Edit Code Review Agent Settings | Greptile

@notdanilo notdanilo merged commit f5186d9 into main Oct 8, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants