Skip to content

Contracts docs: group_treasury storage layout #469

Closed

Description

@codebestia

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

Activity

  1. abdulquadri123 commented on Jul 29, 2026

    @abdulquadri123

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

    Hey Maintainer,
    As a blockchain developer, I will delighted to handle this issue and solve it diligently once assigned to me.
    Thanks.

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

  2. drips-wave commented on Jul 29, 2026

    @drips-wave

    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 🌊

  3. Confidence001Jewel-cmd commented on Aug 27, 2026

    @Confidence001Jewel-cmd

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

    Dear Maintainer,
    Please assign this issue to me, I will love to work on it.

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

  4. Leetmanixy commented on Aug 27, 2026

    @Leetmanixy

    @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.

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

  5. eischideraa-unn commented on Sep 25, 2026

    @eischideraa-unn

    @eischideraa-unn has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    I can work in this issue, please can you assign

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

  6. Damola09 commented on Sep 28, 2026

    @Damola09
    Contributor

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

    Can i work on this?

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

  7. drips-wave commented on Sep 28, 2026

    @drips-wave

    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 🌊

  8. added a commit that references this issue on Sep 29, 2026
    f81fd2a
  9. github-actions commented on Sep 29, 2026

    @github-actions

    Closed by #611, merged into dev.

  10. drips-wave commented on Sep 29, 2026

    @drips-wave

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programcontractsdocumentationImprovements or additions to documentation

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions