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
Write contracts/docs/contracts-group-treasury-storage.md documenting contracts/contracts/group_treasury/src/storage.rs and token_interface.rs — member list storage, per-token balance storage, and the withdrawal-proposal record structure (fields, status enum values).
Acceptance criteria:
Every storage key/data structure is documented with its type and what it represents
The WithdrawProposal struct's fields and status transitions are documented as a small state diagram
Storage type (instance/persistent/temporary) and any TTL/bump behavior is documented
Congratulations, @abdulquadri123! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.
🧑💻 @abdulquadri123: 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.
@Leetmanixy has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
I would like to work on this issue because clear documentation of smart-contract storage is important for contributors who need to understand how contract state is structured and managed. Storage keys, withdrawal proposals, status transitions, and TTL behavior can be difficult to understand by reading the implementation alone, so documenting them would make the contract easier to work with and review.
I am particularly interested in this issue because it provides an opportunity to learn the "group_treasury" contract at a deeper level while producing documentation that will be useful to future contributors. I would trace the storage definitions in "storage.rs" and the relevant interfaces in "token_interface.rs", documenting each storage key and data structure, its type, purpose, and storage lifetime.
I have experience working with software projects, technical documentation, APIs, backend systems, and debugging existing codebases. I am comfortable reading implementations and translating technical behavior into concise documentation that other developers can use.
This issue would also allow me to strengthen my understanding of Soroban smart-contract storage, including instance, persistent, and temporary storage, TTL and bump behavior, token balances, and proposal state management. I would make sure the "WithdrawProposal" fields and status transitions are accurately represented with a small state diagram and that every documented behavior matches the actual contract implementation.
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
abdulquadri123 commentedon Jul 29, 2026
@abdulquadri123 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 @abdulquadri123 to this issue.
drips-wave commentedon Jul 29, 2026
Congratulations, @abdulquadri123! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.
🧑💻 @abdulquadri123: 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 🌊
Confidence001Jewel-cmd commentedon Aug 27, 2026
@Confidence001Jewel-cmd 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 @Confidence001Jewel-cmd to this issue.
Leetmanixy commentedon Aug 27, 2026
@Leetmanixy 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 @Leetmanixy to this issue.
eischideraa-unn commentedon Sep 25, 2026
@eischideraa-unn 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 @eischideraa-unn 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.