Align wallet APIs with Stellar sync model and client refresh policy

[3m1n3nc3]

Problem

Wallet APIs currently operate as local ledger mutations and do not represent the specified Stellar network sync behavior.

Current State

• Funding and withdrawal directly mutate local wallet balance.
• Transaction history is fetched once and not refreshed on interval or focus.
• Asset-level balance sync is not modeled yet.

Acceptance Criteria

• Introduce sync strategy for Stellar balances and transaction ingestion.
• Separate simulated operations from on-chain operations behind explicit API flags.
• Add client refresh policy (interval/focus) and reconcile with server transaction state.
• Expose normalized wallet response with balance, assets, transactions, and lastSync metadata.

[Mistersmile4585]

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

Hi maintainers, I’m a fullstack developer with years experience and i will love to work on this issue. Thanks in advance.

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

[morapay-app]

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

I am applying to work on this issue because it is a concrete, scoped improvement in geevapp/geev that I can ship end-to-end with tests and clear acceptance criteria. The title (Align wallet APIs with Stellar sync model and client refresh policy) maps cleanly to a small implementation plan: reproduce the current behavior, add or adjust the minimal surface area (API/UI/config as appropriate), and verify with automated checks plus a short manual pass where needed. I will keep the change focused, document any assumptions, and open a PR that references this Wave issue for traceability.

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

[boys-cyberhub]

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

Please assign this issue to me

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

[drips-wave]

Congratulations, @boys-cyberhub! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @boys-cyberhub: 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 @boys-cyberhub as part of the Stellar Wave Program's 4th Wave 🥳

😎 @boys-cyberhub: 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.