Repository navigation
PREWAVE-BE-010 — Rehearse PostgreSQL Migration, Rollback, and Zero-Data-Loss Recovery #605
Description
Problem context
The post-Wave-9 audit requires a reproducible Optimism Sepolia path. The current open backlog does not isolate this boundary as an independently reviewable contributor task.
Technical scope
- Inventory and order all canonical TypeORM migrations.
- Rehearse upgrade, application rollback compatibility, failed migration recovery, and restore into an isolated environment.
- Add expand/contract rules and destructive-change guards.
- Produce operator evidence and timings.
Security and architecture constraints
- Contracts and finalized canonical events remain authoritative for protocol state.
- Missing, stale, ambiguous, or wrong-release data must fail closed.
- Never log secrets, authorization material, protected rationale, or non-public evidence.
- Bind all chain-derived data to chain ID, release ID, deployment block, and artifact checksum.
Required tests
- Empty, representative, and large-dataset migration tests.
- Mid-migration failure and retry tests.
- Previous-version compatibility and restored-database integrity tests.
Acceptance criteria
- Fresh install and N-1 upgrade reach the same schema.
- Failed migration has a documented safe recovery path.
- Destructive changes require explicit reviewed evidence.
- Restore preserves projection cursor and audit integrity.
Dependencies
- STAB-BE-006 — Converge on One PostgreSQL Persistence Authority #585
- STAB-BE-005 — Restore the Post-Wave-9 Install and CI Baseline #584
- Frontend implementation matrix
Non-goals
- Deploying to mainnet.
- Inventing contract interfaces or frontend behavior.
- Applying
Stellar Waveor assigning a contributor.
Complexity and points
- High — 200 points
Candidate only; activation remains maintainer-controlled.
Activity
Ikechukwu-Patrick commentedon Oct 15, 2026
@Ikechukwu-Patrick has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ikechukwu-Patrick to this issue.
eriifeomoniyi-hue commentedon Oct 16, 2026
@eriifeomoniyi-hue has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @eriifeomoniyi-hue to this issue.
drips-wave commentedon Oct 16, 2026
Congratulations, @Ikechukwu-Patrick! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Ikechukwu-Patrick: 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 🌊
drips-wave commentedon Oct 19, 2026
This issue has been completed by @Ikechukwu-Patrick as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Ikechukwu-Patrick: 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.