Quickstart README: full create -> withdraw example

[Jaydbrown]

A copy-pasteable script from new Conduit(...) through creating a stream and withdrawing, using a testnet key.

[graceanya796-maker]

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

Hello
I would love to work on this issue please

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

[69starman]

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

Hello sir maintainer....
I have a vast experience in solving github issues ...
Please do well to assign me this let me get it done for you ✅.
Thank you 😊

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

[Olayinka93]

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

Hello, this issue aligns well with my skills and experience. I’m confident I can resolve it effectively and deliver a proper solution. Kindly consider assigning it to me.

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

[wenxiaojie1]

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

I will replace the placeholder-only README fragment with one executable, copy-pasteable testnet quickstart that uses separate funded sender and recipient keys from environment variables: construct Conduit clients, create a native-asset stream, report its IDs/hashes, poll withdrawable with a bounded timeout, switch to the recipient signer, and withdraw only when funds are available. I will reuse the existing create/withdraw examples, never print secrets, validate required addresses/config up front, add mocked tests for sequencing and zero/timeout failures, and verify the example through typecheck, lint, unit tests, and build without performing a real transaction.

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

[bade22brazy]

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

hello maintainer, kindly assign these issues to me. i am sure of handling thenm after careful and thorough review

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

[drips-wave]

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

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