Protect against reentrancy attacks in smart contracts

[Smartdevs17]

Description

Smart contract functions that transfer tokens and update state are susceptible to reentrancy attacks. Implement checks-effects-interactions pattern and reentrancy guards.

Acceptance Criteria

• Reentrancy guard modifier on all mutative functions
• Checks-effects-interactions pattern verified across all functions
• Cross-contract reentrancy protection
• Fuzz testing for reentrancy scenarios
• Formal verification of reentrancy safety
• Emergency circuit breaker for reentrancy detection

Technical Scope

• contracts/src/lib.rs
• contracts/src/security_properties.rs
• contracts/test/foundry/
• Edge: read-only reentrancy, cross-function reentrancy, constructor reentrancy

[TUPM96]

Submitted PR: #411

It adds a storage-backed reentrancy guard, emergency pause/status surface, and runnable security-property coverage for guarded mutation flows.

Verification completed locally:

• cargo fmt
• cargo test (15 passed)
• cargo build
• git diff --check

Foundry was not run because forge is not installed in this local PATH.

[abdulqoyumadegoke]

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

I would like to work on this task

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

[Jumongweb]

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

Hi maintainer, i will like to solve this issue

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

[od-hunter]

@od-hunter has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi can i be assigned this issue please? I've gone through the description and I'm up for the task. Kindly assign me please.

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

[drips-wave]

Congratulations, @od-hunter! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @od-hunter: 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 🌊