Implement Aegis compliance lifecycle checks

[El-swaggerito]

Description

Difficulty: Expert

Type: Feature

Summary

Implement compliance lifecycle checks for restricted RWA operations.

Current Behaviour

Compliance state may not fully cover approved, blocked, revoked, pending, and unknown states across minting and transfers.

Expected Behaviour

Contracts should enforce compliance lifecycle state consistently for restricted operations.

Suggested Implementation

Create lifecycle model, state checks, transition validation, events, tests, and docs.

Files or Areas Likely Affected

• src/
• tests/
• docs/
• README.md

Acceptance Criteria

• Compliance lifecycle model is implemented.
• Restricted operations check compliance state.
• Invalid transitions are rejected.
• Events are emitted for compliance changes.
• Tests cover major lifecycle states.
• Docs explain compliance limitations.

Additional Notes

This is a core RWA contract issue.

[sebas11042]

Hi, I’d like to work on this issue.

I would first review the current compliance registry, restricted operations, and existing contract error patterns, then implement a clear lifecycle model covering pending, approved, blocked, revoked, and unknown states. I would enforce those states consistently across minting and transfer flows, validate allowed and invalid transitions, emit the expected lifecycle events, and add focused tests to confirm unauthorized or invalid-state operations fail without mutating contract state. I would also document the lifecycle rules and any compliance limitations so the behavior remains clear for SDK and dashboard integrations.

Estimated time: 2 hour.

Thanks!

[Carlys17]

I'd like to work on this. I'll implement a compliance‑state check that validates restricted operations against a
ComplianceStatus flag, reject disallowed actions, add the corresponding events, and write tests covering all permitted
and rejected flows.