Summary
Add a secure intent/keeper framework so third parties can execute permissioned operational actions (resolve with supplied payload, claim on behalf with user signature, create-next from template) under explicit scopes and nonces.
Why this is complex / high impact
Cross-contract/keeper execution needs capability security: scoped auth, replay nonces, expiry, and abuse resistance—without weakening user custody assumptions.
Where to work
- new
intents.rs / auth helpers
- admin/oracle/user flows
- bindings helpers for keepers
- security tests
Architecture requirements
- Typed intents with expiry+nonce.
- Scope enumeration (RESOLVE, CLAIM, CREATE_NEXT).
- Signature/auth verification model appropriate for Soroban.
- Rate limits / pause respect.
- Events for keeper execution.
Acceptance Criteria
Difficulty
advanced
Summary
Add a secure intent/keeper framework so third parties can execute permissioned operational actions (resolve with supplied payload, claim on behalf with user signature, create-next from template) under explicit scopes and nonces.
Why this is complex / high impact
Cross-contract/keeper execution needs capability security: scoped auth, replay nonces, expiry, and abuse resistance—without weakening user custody assumptions.
Where to work
intents.rs/ auth helpersArchitecture requirements
Acceptance Criteria
Difficulty
advanced