UnlockModal doesn't show transaction fee estimate

[ritaifeoluwa]

What changed

• src/components/UnlockModal/UnlockModal.tsx submits unlock transactions without showing the estimated network fee
• Users don't know the cost until Freighter prompts for signing

Why

• Users should see the estimated fee before committing to the transaction
• Stellar fees are low but transparency builds trust

How to test

1. Open the unlock modal for a locked position
2. Observe no fee estimate before the Freighter signing prompt

[oscar24357]

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

Hello boss, good evening, can you please assign this issue to me.

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

[Mitch5000]

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

Can I work on this?

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

[GazzyLee]

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

gm boss, I’d love to work on this. I can update UnlockModal to fetch and display the estimated Stellar network fee before the user reaches the Freighter signing prompt, giving them clear cost information before committing the transaction. I’ll handle loading and estimation failures gracefully so the unlock flow isn’t unnecessarily blocked, keep the displayed fee consistent with the transaction being signed, and add tests for the estimated fee, loading state, and estimation failure cases.

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

[hauwauyahass-byte]

@hauwauyahass-byte has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd be glad to handle this issue. I'll keep the implementation concise, maintainable, and well-documented.

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

[ogenyialice120]

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

Hey maintainer! I wish to work on this issue

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

[richardtoms100]

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

I can work on this please

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

[drips-wave]

Congratulations, @richardtoms100! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@richardtoms100's PR #259 was approved and merged by @ritaifeoluwa.

🏆 @richardtoms100: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (226 total points). Track your full progress on GrantFox.

👏 Great work, @richardtoms100! Keep contributing to SmartDropLabs.