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
Concepts docs: Group treasury multisig/authorization model #471
Write contracts/docs/concepts-treasury-multisig-model.md explaining the group_treasury contract's authorization design: membership management, the approval-threshold model, and why withdrawal requires proposal + N approvals rather than any single member's signature.
Acceptance criteria:
Explains the threshold model in plain terms (what "threshold" means, how it's set, whether/how it can change)
Explains the security property this achieves and any known limitations (e.g. what happens if approvals never reach threshold, member removal mid-vote)
Cross-references the API doc (api-group-treasury.md) for exact function signatures
@yunus-dev-codecrafter has applied to work on this issue as part of the Stellar Wave Program's 7th wave.
Hi! I've carefully reviewed the entire task description and fully understand the requirements and expected outcome.
I have experience working on similar tasks and I'm confident I can complete this within about an hour. I'd be happy to take ownership of this issue and submit a clean, well-tested solution promptly.
If it's available, please assign it to me. Thank you!
Congratulations, @cythecode! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.
🧑💻 @cythecode: 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.
@niftymoney01 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Having reviewed the issue and its requirements, I’d be interested in taking this fforward I’ll focus on understanding the existing flow first, then implementing the necessary changes without compromising the surrounding functionality
Congratulations, @Damola09! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @Damola09: 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.
😎 @Damola09: 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.
Activity
Mhidesav commentedon Jul 29, 2026
@Mhidesav has applied to work on this issue as part of the Stellar Wave Program's 7th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mhidesav to this issue.
yunus-dev-codecrafter commentedon Jul 29, 2026
@yunus-dev-codecrafter has applied to work on this issue as part of the Stellar Wave Program's 7th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @yunus-dev-codecrafter to this issue.
cythecode commentedon Jul 29, 2026
@cythecode has applied to work on this issue as part of the Stellar Wave Program's 7th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @cythecode to this issue.
drips-wave commentedon Jul 29, 2026
Congratulations, @cythecode! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.
🧑💻 @cythecode: 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 🌊
muhsar27 commentedon Aug 27, 2026
@muhsar27 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @muhsar27 to this issue.
niftymoney01 commentedon Sep 23, 2026
@niftymoney01 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @niftymoney01 to this issue.
Damola09 commentedon Sep 28, 2026
@Damola09 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Damola09 to this issue.
drips-wave commentedon Sep 28, 2026
Congratulations, @Damola09! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @Damola09: 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: document group_treasury storage/multisig, local object store, a…
github-actions commentedon Sep 29, 2026
Closed by #611, merged into
dev.drips-wave commentedon Sep 29, 2026
This issue has been completed by @Damola09 as part of the Stellar Wave Program's 9th Wave 🥳
😎 @Damola09: 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.