Skip to content

Utix: Add release rollback verification for newly deployed protocol behavior #193

Closed

Description

@prissca

Summary

After a rollback, maintainers need verification that user-facing state, background jobs, and external references are consistent with the restored behavior.

This issue is scoped to Utix, a ticketing and event access protocol. Contributors should account for the current stack and integration points: TypeScript, ticket issuance, transfer, redemption, event operations, fraud controls, and organizer dashboards.

Difficulty

High - 200 points

Scope

  • Define rollback verification checks.
  • Add command or runbook section for post-rollback validation.
  • Include checks for pending operations and partially processed records.

Acceptance criteria

  • Verification detects records requiring manual repair after rollback.
  • Checks are read-only by default.
  • Tests or fixtures cover clean rollback, partial rollback, and failed rollback validation.

Technical notes

  • Keep the implementation aligned with the existing repository architecture.
  • Include automated tests, fixtures, or a clear validation command.
  • Update contributor-facing documentation when behavior, setup, or API contracts change.
  • Do not add labels; maintainers will assign labels manually.

Pull request expectations

  • Explain design decisions and tradeoffs.
  • Include relevant test output, screenshots, logs, or API examples.
  • Call out any migration, configuration, or deployment steps.

Activity

  1. ravimahatonp commented on Oct 3, 2026

    @ravimahatonp

    Hi,

    I have experience with similar implementations and would like to take this on.

    Implementation approach:

    1. Audit storage layout and state invariants ensuring strict auth guards.
    2. Implement deterministic state transitions with safe checked arithmetic.
    3. Add hermetic unit and regression tests covering authorized, unauthorized, and boundary edge cases.
    4. Profile instruction and CPU/gas limits under Soroban host environment.

    I can deliver a clean, tested PR within 24 hours. Please assign!

  2. Vicky08100 commented on Oct 18, 2026

    @Vicky08100
    Contributor

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

    Hi maintainer, I would love to work on this issue. please kindly assign me the issue

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

  3. drips-wave commented on Oct 18, 2026

    @drips-wave

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

    🧑‍💻 @Vicky08100: 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. drips-wave commented on Oct 18, 2026

    @drips-wave

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

    😎 @Vicky08100: 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

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions