feat: Soroban auth-entry batching (single approval for multi-step flows)

[joelpeace48-cell]

Background & current state

Multi-step user flows (e.g., register → credit → claim, or approve → spend) can require multiple signatures, hurting UX. Soroban auth entries can sometimes be composed so a user approves once. The frontend currently signs each step separately.

Goal

Compose multiple contract authorizations into a single user approval where the protocol allows, reducing signature prompts in multi-step flows.

Technical design

• Build a single transaction with multiple Soroban operations / InvokeHostFunction auth entries, collect the required SorobanAuthorizationEntrys, and have the user sign them in one prompt via the wallet provider.
• Provide a helper in the SDK/frontend (composeAuth(entries)); fall back to sequential signing where composition isn't valid.

Edge cases

• Operations requiring different signers → can't compose; fall back.
• Auth-entry expiry (signatureExpirationLedger) → set sensibly; handle expiry mid-flow.
• Simulation needed per op to build correct auth → ensure ordering/nonce correctness.
• Partial failure within a composed tx → all-or-nothing semantics; communicate clearly.

Task breakdown

• Auth-entry composition helper + simulation.
• Wallet provider single-prompt signing of multiple entries.
• Fallback to sequential signing when invalid.
• E2E measuring signature prompts before/after.

Acceptance criteria

• A representative multi-step flow requires one signature instead of N where composable.
• Non-composable flows fall back correctly.

Testing & verification

• E2E counting wallet prompts pre/post; unit tests for composition + expiry.

Out of scope

• Protocol changes; cross-wallet differences beyond the abstraction.

Dependencies / related

• Benefits all multi-step flows; relates to SDK (NEW-085).

References

• Soroban authorization framework; auth entries.

Difficulty: medium · Effort: M · dx

[Properprogress1]

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

Let me work on this please

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

[devjayy43]

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

I would like to work on this, please assign

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

[osasfaith]

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

I would love to work on this issue.

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

[drips-wave]

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

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