Upgrade to new RateRegistry contract #1617
Open
+96
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

TL;DR
Added support for scheduled rate changes by introducing a
--start-timeparameter to thexmtpd-cli rates addcommand.What changed?
StartTimefield to theAddRatesOptsstruct in the CLI--start-timeflag to therates addcommand that accepts a Unix timestamp--start-timeis omitted, it defaults to 2 hours from nowstartTimeparameter in theRatesUpdatedeventstartTimeparameterv2026.02.10-1How to test?
Why make this change?
This change enables operators to schedule rate changes in advance, allowing for better planning and communication of fee adjustments. By supporting a start time parameter, the system can now transition between different rate structures at predetermined times without requiring manual intervention at the exact moment of change.