[FUNCTION] implement `reentrancy_lock_logic`

[Akshola00]

• Title: Add a manual check for reentrancy.
• Description: Implement a simple state-check pattern to prevent double-withdrawals in complex interactions.
• Requirements:
  • Test: Simulate a nested call (using mock environment) to verify the lock.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[luhrhenz]

@luhrhenz has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi! I'd like to pick this up for Wave 2. I will implement a manual reentrancy guard by adding a Locked state to the storage keys, enforcing a require_not_locked check before complex interactions, and ensuring the lock is released afterward. I'll also write a unit test simulating a blocked nested call by manipulating the mock environment's storage. Can I get assigned?

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

[Dannyswiss1]

@Dannyswiss1 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello, I’d like to take on this issue. I have experience building Web3 smart contracts with Solidity, Cairo and Rust.

I’m conversant with Rust smart contracts and the Soroban SDK. I'll deliver a modular deterministic solution.

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