Skip to content

feat(accord): add token validation to recurring proposal entrypoint - #560

Open
Musab1258 wants to merge 1 commit into
Ac0rdP:mainfrom
Musab1258:fix/batch-435-437-438-439
Open

feat(accord): add token validation to recurring proposal entrypoint#560
Musab1258 wants to merge 1 commit into
Ac0rdP:mainfrom
Musab1258:fix/batch-435-437-438-439

Conversation

@Musab1258

@Musab1258 Musab1258 commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Not done with this, but when completed:

Fixes #439
Fixes #435
Fixes #438
Fixes #437

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.
@vercel

vercel Bot commented Aug 31, 2026

Copy link
Copy Markdown

@Musab1258 is attempting to deploy a commit to the thegreatfeez's projects Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave

drips-wave Bot commented Aug 31, 2026

Copy link
Copy Markdown

@Musab1258 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment