[Frontend] Add a build-info footer showing version, commit SHA, and network

[Akpolo]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Labels: enhancement, good first issue, frontend, Stellar Wave

There's no way to tell which build of the frontend you're looking at or which network it points to.

During a wave with frequent deploys, QA and support keep asking "is this the new version?" and nobody can confirm it. A small footer showing the commit SHA and target network (testnet/mainnet) makes every deploy verifiable, and if it also reads the backend GET /version (#881) you can spot frontend/backend drift at a glance. This is a DX and release-verification thing, not a fix.

What the fix has to hold to

• Version and network come from build-time metadata (NEXT_PUBLIC_* env or Next build info), not hardcoded.
• The footer is subtle, accessible, and hidden from print.
• All copy goes through i18n (frontend/messages/*.json).
• Don't expose anything beyond the commit SHA and network name.

Done when

• Commit SHA and network are exposed at build time.
• A subtle footer/badge in the dashboard layout shows version + network.
• Optionally reads the backend version from GET /version ([Backend] Add GET /version endpoint exposing build SHA, build time, and contract IDs #881) to flag drift.
• Footer is accessible, unobtrusive, hidden from print, and localized.
• npm run lint, typecheck, and build pass; CI green.

Where to start
frontend/src/app/[locale]/layout.tsx (or a shared footer component), the env/next.config wiring, and frontend/messages/*.json for strings. The backend /version endpoint and any release-notes UI are out of scope. Small, a day or so.

[temisan0x]

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

Hi team, I will love to take on this task

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

[drips-wave]

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

🧑‍💻 @temisan0x: 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 marked as completed by a Drips Wave moderator for @temisan0x as part of the Stellar Wave Program's 5th Wave 🥳

Moderator's reason: [Auto-assessed] The PR #981 directly and comprehensively addresses the issue by implementing build-time environment variable injection, adding a dedicated footer component with i18n support, and updating the project layout. Although CI is currently 'unstable', the contributor has clarified that these failures are pre-existing on the main branch, and there are no maintainer objections.

😎 @temisan0x: You earned 100 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.