Repository navigation
PREWAVE-BE-049 — Authorize and Make Dead-Letter Replay Idempotent #643
Description
Problem context
Post-Wave-9 source audit identified this as a distinct production-readiness boundary not fully owned by the existing candidate backlog.
Technical scope
- Require protected capability, reason, bounds, dry run, original payload hash, and audit record for replay.
- Prevent replay across release/schema incompatibility.
Required tests
- Unauthorized, stale release, duplicate replay, batch limit, poison message, partial failure, and audit tests.
Acceptance criteria
- Replay is denied by default.
- One message cannot produce duplicate effects.
- Original and replay references are linked immutably.
- Operators can stop/resume bounded batches.
Architecture and security constraints
- Canonical contracts/finalized events remain authoritative.
- Bind chain-derived data to chain ID, release ID, deployment block, and artifact checksum.
- Fail closed on stale, ambiguous, missing, or unauthorized state.
- Do not weaken CI, strict typing, privacy, or auditability.
Dependencies
- UX-BE-004 — Define Protected Operations, Safe-Retry, and Audit Interfaces #595
- PREWAVE-BE-037 (PREWAVE-BE-037 — Prove V2 Outbox Idempotency Under Concurrent Workers #633)
Non-goals
- Unrelated feature work or mainnet deployment.
- Applying
Stellar Wavebefore maintainer activation.
Complexity and points
- High — 200 points
Candidate only; activation remains maintainer-controlled.
Activity
isahpeter656-coder commentedon Oct 15, 2026
@isahpeter656-coder 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 @isahpeter656-coder to this issue.
Matrixthechoppedboy commentedon Oct 15, 2026
@Matrixthechoppedboy 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 @Matrixthechoppedboy to this issue.
Timrossid commentedon Oct 15, 2026
@Timrossid 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 @Timrossid to this issue.
drips-wave commentedon Oct 16, 2026
Congratulations, @Matrixthechoppedboy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Matrixthechoppedboy: 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 🌊
security: PREWAVE-BE-049 — Authorize and Make Dead-Letter Replay Idemp (
security: PREWAVE-BE-049 — Authorize and Make Dead-Letter Replay Idemp (
drips-wave commentedon Oct 19, 2026
This issue has been completed by @Matrixthechoppedboy as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Matrixthechoppedboy: 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.