Add request cancellation for market and activity fetches on unmount

[dimka90]

Type: Performance
Area: Data

Description

Async page hooks currently fire requests without a documented cancellation strategy when components unmount or parameters change quickly.

Problem Statement

Stale responses can race with newer state and waste network resources.

Acceptance Criteria

• Market and activity fetch hooks cancel or ignore stale requests safely on unmount or parameter changes.
• No state updates occur after the relevant component has unmounted.
• The implementation is covered by tests or documented behavior.

Test Cases

• Navigate away quickly during a fetch and verify no warnings or stale updates occur.
• Trigger rapid parameter changes and confirm only the latest response updates the UI.

[activatedkc]

@activatedkc has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hello,

I am a smart contract and full-stack developer interested in contributing to this issue. I am experienced with hands-on experience in Rust, Soroban, Go, Cairo, Solidity, and TypeScript.

I am passionate about building secure and scalable blockchain solutions, with a strong focus on writing clean, maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I would appreciate the opportunity to contribute and help move this forward.

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

[daree-dev]

@daree-dev has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Would like to work on this issue

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

[Sendi0011]

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

Gm team, can i handle thi? I can deliver ASAP
ETA: 3 min

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