Skip to content

Implement invoice versioning #1056

Closed

Description

@Kingsman-99

Overview

Support versioning of invoices with change history.

Requirements

  • Design version system
  • Track changes
  • Support rollback
  • Create history

Acceptance Criteria

  • Versioning works
  • Changes tracked
  • Rollback safe
  • History clear
  • Tests pass

Definition of Done

All CI checks must pass before the PR is reviewed.

Activity

  1. rupesh-kumar-sah commented on Oct 16, 2026

    @rupesh-kumar-sah

    Hi maintainers,

    I reviewed "Implement invoice versioning" and have a structured approach ready for implementation:

    Technical Implementation Outline:

    1. Review contract state storage keys, TTL policies, and auth guards (Address::require_auth).
    2. Implement safe state transition logic with checked arithmetic preventing under/overflow.
    3. Write comprehensive Soroban unit tests covering standard flows, unauthorized callers, and reverts.
    4. Verify contract execution footprint passes Soroban CPU/memory budget limits.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  2. maztah1 commented on Oct 17, 2026

    @maztah1
    Contributor

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

    Hi, I’d be happy to contribute to resolving this issue. I'll first assess the affected components, then implement and test the changes while keeping the solution maintainable and consistent with the codebase.

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

  3. drips-wave commented on Oct 17, 2026

    @drips-wave

    Congratulations, @maztah1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

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

  4. grantfox-oss commented on Oct 19, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @maztah1's PR #1151 was approved and merged by @Kingsman-99.

    🏆 @maztah1: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (990 total points). Track your full progress on GrantFox.

    👏 Great work, @maztah1! Keep contributing to Stellar-split.

  5. drips-wave commented on Oct 19, 2026

    @drips-wave

    This issue has been completed by @maztah1 as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @maztah1: 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.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions