[Frontend Fix 01] Move ChatMessage type out of ChatInterface.tsx

[soomtochukwu]

Description

Area: Frontend
Summary: Move ChatMessage type out of ChatInterface.tsx
This issue comes from the additional audit report and should be handled as a tracked remediation item.
The current implementation either blocks production readiness, weakens maintainability, or leaves the product experience below the required standard.
The fix should be scoped, reviewed against existing project patterns, and verified with the relevant local commands.
Avoid unrelated refactors unless they are necessary to complete the acceptance criteria.

Requirements

• Implement the targeted frontend fix
• Add or update tests where relevant
• Keep UI behavior stable unless the issue requires a UX change

Acceptance Criteria

• Root or frontend tests cover the behavior where practical
• npm run lint has no new warnings
• npm run build passes

AI Implementation Prompt

AI code engineer prompt:
You are working in the dxmakers/smasage Next.js TypeScript frontend. Implement this issue: Move ChatMessage type out of ChatInterface.tsx. Preserve existing behavior unless explicitly changed, use strict types, and follow the audit frontend revamp direction. Use Tailwind CSS and Framer Motion where UI interaction is required. Include or update tests where practical, run lint/build, and summarize any follow-up risks.

[Creative-Titilayo]

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

I will love to work on this issue,pls 🙏 give me Sir

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

[damzempire]

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

I would love to tackle this issue for the current Stellar Wave. As a computer science student and full-stack developer focusing on Web3 user interfaces, I have strong familiarity with the Stellar network and building/testing Soroban smart contracts.

I understand the architecture of ephemeral accounts and how critical it is to cleanly wire verification logic like the claim_verifier to ensure secure execution paths. I can efficiently integrate the module into bridgelet-core, ensure all data keys/states match up seamlessly, and write the necessary unit tests to verify that the implementation meets acceptance criteria without introducing regressions. Ready to dive in immediately!

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

[Maximum-Prosper]

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

Hi maintainer.
I'm interested in resolving this issue., can you kindly assign?

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

[drips-wave]

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

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