From 98fff97dcc6f6929c0c8d54435b696c7af1f6c12 Mon Sep 17 00:00:00 2001 From: musab1258 Date: Mon, 31 Aug 2026 12:50:36 +0100 Subject: [PATCH] feat(accord): add token validation to recurring proposal entrypoint Adds `validate_token(&env, &token)?` to `create_recurring_proposal` at line 2726 to ensure the proposal asset is legitimate. This completes the required validation suite for recurring proposals, aligning it with existing checks: - amount bounds check - interval duration check - contract self-recipient restriction - token address validation (new) The implementation mirrors the proven validation patterns found in `create_proposal` and `create_recurring_schedule`. Pre-existing compilation errors in the contract are unrelated to this change. --- contracts/accord/src/lib.rs | 1 + 1 file changed, 1 insertion(+) diff --git a/contracts/accord/src/lib.rs b/contracts/accord/src/lib.rs index cbd1f28..600b034 100644 --- a/contracts/accord/src/lib.rs +++ b/contracts/accord/src/lib.rs @@ -2723,6 +2723,7 @@ impl AccordContract { if recipient == env.current_contract_address() { return Err(ContractError::InvalidRecipient); } + validate_token(&env, &token)?; validate_description(&description)?; validate_deadline(&env, deadline)?;