Stellar multisig stealth withdrawal guide

[truthixify]

Tier: M (2-4 days) Type: writing

Context

Stealth withdrawals from multisig source accounts require careful coordination (signer weight, threshold, ordering). SDK will gain helpers; docs need to show patterns.

Scope

Write docs/guides/stellar-multisig-withdrawal.mdx:

• Stellar native multisig primer
• Building a multisig-source-account stealth withdrawal
• Coordinating N signatures (sequence, weight, transfer)
• Using the SDK multisig helpers
• Recovery scenarios (lost signer, threshold change)
• Worked 3-of-5 example end-to-end

Acceptance criteria

• Page committed
• 3-of-5 example verified on futurenet
• Linked from SDK Stellar + Security overview

Files to start with

• New: docs/guides/stellar-multisig-withdrawal.mdx

[baedboibidex-cmyk]

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

I would love to take on this issue and author the comprehensive guide for Stellar multisig stealth withdrawals. Coordinating threshold signatures alongside advanced cryptographic stealth addresses requires an absolute clarity of sequence, and I have solid experience with Stellar's native multi-signature system and threshold orchestration.

To deliver an exceptional, technically accurate guide, I will structure docs/guides/stellar-multisig-withdrawal.mdx by implementing:

1. Stellar Native Multisig Architecture: Providing a clear, technical primer on how master weights, thresholds (low, medium, high), and signature aggregation operate directly on-chain.
2. Stealth Transaction Sequencing: Mapping out the step-by-step coordination pipeline needed to build the transaction structure, gather signatures sequentially, and maintain correct sequence numbers when dealing with multi-sig source accounts.
3. End-to-End 3-of-5 Worked Example: Creating a practical, copy-pasteable scenario using the new SDK helpers, completely verified on Futurenet, detailing how a threshold of 3 weights satisfies the transaction submission.
4. Resiliency & Recovery Playbooks: Documenting explicit recovery strategies for common edge cases, including handling unresponsive or lost signers, and safely modifying account thresholds.

I am ready to deliver a production-ready, bulletproof cryptographic guide for the Wraith Protocol docs!

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

[truthixify]

@baedboibidex-cmyk Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. Silence is the only thing that costs you the assignment; if you get stuck or context changes, just say so on the PR.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building.

[drips-wave]

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

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