Inconsistent tab/navigation highlighting and "Connect Wallet" placement

[kelly-musk]

Description
Across frames (empty + populated), nav tabs (Dashboard, Transactions, Wallets, Settings, Connect Wallet) have "Connect Wallet" as a blue pill, but in some views it's active/highlighted incorrectly. "Transactions" tab sometimes shows sub-tabs inconsistently. No clear indication if wallet is connected (e.g., avatar vs connect button).

Impact
Confuses users about current state → reduces trust in a wallet/transaction app.

Figma Reference
https://www.figma.com/design/8AKBqCA6TUMFSTFniNKQMx/-51-Transaction-History-Page-Design?m=auto&t=w4hBZmmlwukX9OwT-6

Page/Frame to Work On

• All frames, especially Transaction History Empty State, Transaction List Design, Transactions main view

Contributor Instructions
Standardize nav: use consistent pill style (active = blue fill + white text). Replace "Connect Wallet" with connected state (avatar + dropdown). Add wallet connection badge (green dot if linked). Ensure Transactions tab is always highlighted here.

Severity → High (P1) – Affects every session.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Christopherdominic]

@Christopherdominic has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi 👋

I’d like to work on this issue.

I’ve reviewed the description and acceptance criteria, and I’m confident I can implement the required changes following the project’s guidelines and coding standards. I’ll ensure proper testing and documentation where applicable.

Please assign this issue to me — I’ll get started right away. 🚀

Thank you!

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

[Mirabliss]

@Mirabliss has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello i would love to work on this

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

[DavisVT]

@DavisVT has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

can i pls work on this issue

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

[Lex-Studios]

@Lex-Studios has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hey, I would love to be assigned to work on this issue

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

[utilityjnr]

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

i would love to work on this issue

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

[drips-wave]

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

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