Smart Contract — New Feature
Summary
The recurring feature needs well-defined constants for the minimum and maximum interval, and the active schedule cap. This adds them with documented rationale beside the existing validation constants.
Background
The contract in contracts/accord/src/lib.rs already defines validation constants like MIN_AMOUNT and MAX_ACTIVE_PROPOSALS. Recurring schedules need MIN_INTERVAL_SECS, MAX_INTERVAL_SECS, and MAX_ACTIVE_RECURRING with comments explaining why each value was chosen.
What Needs to Be Done
- Add
MIN_INTERVAL_SECS, MAX_INTERVAL_SECS, and MAX_ACTIVE_RECURRING constants near the existing validation constants.
- Write a documentation comment beside each explaining the rationale (e.g. minimum interval prevents spam, maximum interval bounds the payback period, active cap limits storage cost).
- Choose sensible defaults that align with the proposal model's existing cap.
Acceptance Criteria
Files to Look At
contracts/accord/src/lib.rs — add the constants in the validation constants section
Difficulty: Easy
Smart Contract — New Feature
Summary
The recurring feature needs well-defined constants for the minimum and maximum interval, and the active schedule cap. This adds them with documented rationale beside the existing validation constants.
Background
The contract in
contracts/accord/src/lib.rsalready defines validation constants likeMIN_AMOUNTandMAX_ACTIVE_PROPOSALS. Recurring schedules needMIN_INTERVAL_SECS,MAX_INTERVAL_SECS, andMAX_ACTIVE_RECURRINGwith comments explaining why each value was chosen.What Needs to Be Done
MIN_INTERVAL_SECS,MAX_INTERVAL_SECS, andMAX_ACTIVE_RECURRINGconstants near the existing validation constants.Acceptance Criteria
Files to Look At
contracts/accord/src/lib.rs— add the constants in the validation constants sectionDifficulty: Easy