Add freeze status indexing and freeze/unfreeze admin endpoints

[Chucks1093]

Summary

Index key freeze events from the contract and expose endpoints to fetch freeze status, initiate an emergency freeze, and submit an unfreeze through the multi-sig flow.

Scope

• GET /keys/:keyId/freeze — current freeze status, reason, and timestamp
• POST /keys/:keyId/freeze — admin-only emergency freeze endpoint
• POST /keys/:keyId/unfreeze — initiates multi-sig unfreeze proposal
• Freeze events indexed on contract event stream
• Freeze status cache invalidated on state change

Acceptance Criteria

• Freeze status returns correct state, reason, and timestamp
• Emergency freeze validates admin authorization before executing
• Unfreeze creates multi-sig proposal correctly
• Freeze events indexed in correct order without gaps
• Cache invalidated immediately on freeze or unfreeze confirmation

ETA

12 hours

[guptakumarranjeet150]

Hey team,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Implement backend logic for Add freeze status indexing and freeze/unfreeze admin endpoints with strict schema validation and idempotent execution.
• Testing: Verify API response schemas, authentication middleware, and database rollback safety.

Excited to work on this—please assign to me and I will submit a clean PR shortly!

[T-kesh]

@T-kesh has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Please assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @T-kesh to this issue.

[mazikush365]

@mazikush365 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I’d like to work on this issue because it combines backend API development, contract event indexing, authorization, multi-sig workflows, and cache consistency.

I’ll first review the existing server architecture, key management flow, contract event handling, authentication/authorization, and caching implementation. I’ll then implement the freeze status endpoint, admin-only emergency freeze flow, and multi-sig unfreeze proposal flow while keeping the behavior consistent with the existing APIs.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mazikush365 to this issue.

[Cmitchelle7]

@Cmitchelle7 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer, I've reviewed this issue thoroughly and I'm well positioned to resolve it — experienced across the relevant stack and comfortable navigating the existing codebase. Ready to start right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Cmitchelle7 to this issue.

[drips-wave]

Congratulations, @Cmitchelle7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @Cmitchelle7: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊