You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tutorial: create and run a group treasury on testnet #634
Branch: Open your PR against dev. PRs targeting main are closed automatically.
Description:
Write contracts/docs/tutorial-testnet-treasury.md: a step-by-step walkthrough using only the stellar CLI and contracts/scripts/deploy_*.sh — deploy group_treasury, add three members with a threshold of two, deposit a test asset, propose a withdrawal, approve it twice, and execute it.
Acceptance criteria:
Every command shown with its expected output, verified by actually running it on testnet
Covers creating and funding testnet identities and obtaining a test token contract address
Shows the failure cases a learner should try: approving twice from the same member, executing below threshold
@LightX5 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
Hi Maintainer, I’d be interested in working on this tutorial. I’ll first go through the existing deployment scripts and treasury contract flow so the walkthrough follows the project’s actual setup. I’ll document each step, from funding testnet identities and deploying the contract to member approvals and withdrawal execution, including the expected outputs and failure cases. I’ll also cover the frontend environment variables and make sure the PR targets dev. I’d appreciate the opportunity to contribute.
@Depo-dev has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
Hello team.
I’m Depodev, a software engineer with a strong background in building scalable systems and contributing to open-source projects. I’ve taken some time to go through the repository and understand the current implementation, and I’m clear on the issue, its context, and the expected outcome.
I’d love to work on this and take ownership of the fix. I’m confident I can cleanly resolve it while keeping everything aligned with the existing codebase and ensuring all criteria are met. Would appreciate being assigned to this issue.
Congratulations, @Depo-dev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Depo-dev: 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.
😎 @Depo-dev: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.
Activity
LightX5 commentedon Oct 19, 2026
@LightX5 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @LightX5 to this issue.
Depo-dev commentedon Oct 20, 2026
@Depo-dev has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Depo-dev to this issue.
drips-wave commentedon Oct 20, 2026
Congratulations, @Depo-dev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Depo-dev: 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 🌊
docs: add token transfer flow, testnet treasury tutorial, rest endpoi…
github-actions commentedon Oct 20, 2026
Closed by #649, merged into
dev.drips-wave commentedon Oct 20, 2026
This issue has been completed by @Depo-dev as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Depo-dev: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.