Bug: the stream creation flow never checks or requests SEP-41 token allowance before depositing

[Jaydbrown]

Location

app/create/page.tsx (deposit flow: toStroops → createStream)

Description

A repo-wide grep of app/create/page.tsx for "approve"/"allowance" returns nothing. If the underlying DripFactory::create_stream (or equivalent) contract call requires a pre-existing SEP-41 token allowance from the depositor to the vault/factory contract, this UI flow appears to be missing that step entirely — while two allowance-checking modules (lib/tokens.ts, lib/token-allowance-gateway.ts) sit unused in the same codebase, apparently built for exactly this purpose.

Why it matters

If allowance really is required on-chain, users hit an opaque contract-level failure on their first deposit with no actionable guidance in the UI.

Suggested fix

Confirm whether create_stream requires a pre-approved allowance; if so, wire an allowance check + approve step into app/create/page.tsx using lib/token-allowance-gateway.ts.

Acceptance criteria

• Deposit flow checks allowance before submitting, and prompts approval if insufficient
• Test covering the insufficient-allowance path

[scarface-dev1]

@scarface-dev1 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

please i will love to work on these issue

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

[gracechukwukwerenandum]

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

Hi Maintainer, I can fix this issue.
Please assign it to me.

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

[daniella-techie]

@daniella-techie has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hi, can i take this

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

[drips-wave]

Congratulations, @daniella-techie! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @daniella-techie: 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 Official Campaign | FWC26 campaign!

@daniella-techie's PR #298 was approved and merged by @Jaydbrown.

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

👏 Great work, @daniella-techie! Keep contributing to conduit-protocol.

[drips-wave]

This issue has been completed by @daniella-techie as part of the Stellar Wave Program's 7th Wave 🥳

😎 @daniella-techie: 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.