🛑 System-Safety | Inter-Process Mutex Barriers for Shared Local State Mappings

[Sadeequ]

Description

When the engine forks secondary worker processes to handle intense multi-hop cryptographic paths, simultaneous writes to local shared state maps risk causing data collision exceptions.

Technical Requirements

• Replace standard thread-level locks with strict inter-process mutex structures (multiprocessing.Lock) inside src/utils/state.py.

• Guarantee that only one application process can modify or swap local tracking metrics profiles at any single moment.

If you find this implementation useful, please star the project and leave a review! 😊

[Devadakene]

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

I am confident that I can implement this having worked on similar issues in the past

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

[martinshub-tech]

@martinshub-tech has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd like to take this issue. I've analyzed the root cause and am confident I can deliver a reliable fix with proper testing

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

[Jerry-Tekh]

@Jerry-Tekh has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

hi repo maintainer,

please let me take this issue.

I'll replace thread-level locks with inter-process multiprocessing.Lock in src/utils/state.py to guard writes to shared local state maps, ensuring only one worker process can modify or swap tracking metrics profiles at a time.

i am ready, or pls assign me

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