ev-node v1.0.0-rc.1
This release candidate introduces forced inclusion and batch sequencing capabilities, adds new batching strategies, and includes several breaking changes that improve code clarity and metrics simplicity. Operators should carefully review the breaking changes section and plan for required configuration updates.
Tested upgrade paths
- ev-node v1.0.0-beta.11 -> ev-node v1.0.0-rc.1
⚠️ Breaking Changes
1. Genesis Configuration Update Required
What changed: Implemented forced inclusion and batch sequencing system that requires a new genesis configuration field.
Action required:
- Open your node's
genesis.jsonfile - Add the following field:
"da_epoch_forced_inclusion": 100 - The recommended value is
100(this represents the number of epochs) - Save the file and restart your node
Reference: #2797
2. Signer Path Configuration Update
What changed: Renamed evm-single to evm and grpc-single to evgrpc for improved clarity.
Action required:
- Open your
evnode.yamlconfiguration file - Locate the
signer.signer_pathfield - If it contains
evm-single, replace it withevm - If it contains
grpc-single, replace it withevgrpc - Save the configuration file
Note: This change may require manual modification if your $HOME folder path has changed.
Reference: #2839
3. Metrics Removal
What changed: Removed unused and confusing metrics from sequencers and block processing. This includes:
- Sequencer-specific metrics (gas price, blob size, transaction status, pending blocks)
- Channel buffer metrics
- Overly granular error metrics
- Block production categorization metrics
- Sync lag metrics
Essential metrics for DA submission health, block production, and performance monitoring are retained.
Action required:
- Review any monitoring dashboards or alerting rules that depend on the removed metrics
- Update Prometheus queries to use the retained essential metrics
- Remove or update any alerts that reference the removed metrics
- Test your monitoring setup to ensure critical operational visibility is maintained
Reference: #2904
4. DA Client Package Removal
What changed: Removed the core/da package and replaced DAClient with internal implementation. The DA client is now exposed as block.FullDAClient, block.DAClient, and block.DAVerifier without leaking implementation details.
Action required:
- If you have custom code or plugins that import
core/da, update them to use the new interfaces:block.FullDAClientblock.DAClientblock.DAVerifier
- Review and test any custom integrations that interact with the DA client
- Recompile any custom code or extensions
Note: This primarily affects users with custom code integrations. Standard node operations are not affected.
Reference: #2910
Full Changelog
For a complete list of all changes including new features, improvements, and bug fixes, see CHANGELOG.md.
Images
- ghcr.io/evstack/ev-node-evm:v1.0.0-rc.1
- ghcr.io/evstack/ev-node-grpc:v1.0.0-rc.1
- ghcr.io/evstack/ev-node-testapp:v1.0.0-rc.1