Add transaction status icon component

[Chucks1093]

Summary

Add a reusable icon component or pattern for transaction status states.

Scope

• support success, pending, and failed states
• keep the component lightweight and reusable
• make it easy to drop into transaction feedback surfaces

Acceptance Criteria

• transaction states can show one consistent icon treatment
• component supports at least the main three states
• styling works alongside existing status messaging

Contributor note: comment on the issue first and reach out in Telegram for updates or coordination: https://t.me/accesslayerorg

[OpadijoIdris]

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

Good day. i would love to work on this

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

[Johnsmichael150]

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

https://github.com/Johnsmichael150/MentorsMind-Contract.git

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

[ChaoLing140]

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

I’m a full-stack engineer experienced in Soroban smart contracts, backend systems, and modern frontend development, and I can take full ownership of this issue from contract logic to UI integration. I design features holistically defining clear on-chain state transitions, secure backend orchestration, and intuitive frontend flows to ensure consistency and scalability. My implementation will follow strict typing, proper validation, clean architecture boundaries, and careful edge-case handling across contracts and APIs. I prioritize readable commits, thorough local testing, and alignment with the existing codebase conventions. Expected timeline: architecture breakdown within a few hours, core implementation within 24–48 hours (depending on scope), testing and refinement shortly after, with a production-ready PR delivered promptly.

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

[drips-wave]

Congratulations, @ChaoLing140! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

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

[drips-wave]

This issue has been completed by @ChaoLing140 as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @ChaoLing140: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.