[Contracts] Implement Notification Expiration Logic

[Abd-Standard]

Description

Allow notifications stored on-chain to expire after a configurable duration.

Tasks
Add expiration timestamp support.
Prevent interaction with expired notifications.
Emit expiration events.
Write contract tests.

Acceptance Criteria
Expired notifications are invalid.
Events emit correctly.
Tests pass successfully.

[Clement-coder]

Hi,

I'm a full-stack software and blockchain engineer with experience delivering production-grade solutions across frontend, backend, infrastructure, analytics, and blockchain systems.

I'd like to take ownership of this issue. I've reviewed the requirements and have a clear approach for implementing a robust, scalable, and maintainable solution that satisfies all acceptance criteria. I'll ensure the implementation follows project conventions, includes comprehensive testing, and is properly documented.

I can start immediately and will provide consistent updates throughout development. Looking forward to contributing to the project.

[naninu123]

Hello, this matches my skill set.

I've been actively contributing to Stellar projects via GrantFox — from Soroban contract optimization to backend API work and frontend fixes. I know how to scope work to requirements without over-engineering.

Steps:

1. Understand the problem deeply
2. Code the solution following existing patterns
3. Validate with tests and submit

Can start immediately!

[Ebenezer199914]

can i work on this issue

[MoscowDev]

I'd like to take this issue.

This appears to be a notification lifecycle enhancement rather than just a timestamp addition. My focus would be on making expiration a first-class contract state that is consistently enforced across reads, interactions, and event emission.

My approach would be:

• Review the notification data model and contract entrypoints to identify all user actions that should become invalid once a notification expires.

• Add an expiration timestamp field to the notification structure and validate it during notification creation.

• Introduce centralized expiration checks so interaction logic consistently rejects expired notifications instead of relying on scattered conditional checks.

• Ensure expired notifications cannot be acknowledged, acted upon, or otherwise mutated through supported contract flows.

• Emit explicit expiration-related events so indexers, explorers, and frontends can react to notification lifecycle changes.

• Add comprehensive contract tests covering:

  • notification creation with expiration metadata
  • interaction before expiration
  • interaction after expiration
  • boundary conditions at the expiration timestamp
  • event emission correctness
  • invalid expiration scenarios

• Review storage and state-transition behavior to ensure expiration logic does not introduce inconsistent contract state.

The goal is to make notification expiration deterministic, observable, and fully enforced at the contract layer rather than treated as a frontend-only concern.

[grantfox-oss]

🦊 GrantFox — @MoscowDev has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #129)
2. Your PR will be reviewed by the Core-Foundry maintainers

Good luck! Track your progress on GrantFox.