Repository navigation
PREWAVE-BE-007 — Publish Dispute, Appeal, and Settlement Read Models #602
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
- Define dispute register/detail, eligibility, bond, appeal availability, resolution timeline, settlement, refund, reward, and slashing schemas.
- Separate provisional decisions, appealable outcomes, settlement pending, and finalized results.
- Carry canonical transaction/event references and data freshness.
- Publish fixtures for tie/refund-only and unavailable paths.
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
- Dispute-window and bond boundary tests.
- Appeal, tie, expiry, refund, slashing, and reorg tests.
- Schema/fixture drift and wrong-release tests.
Acceptance criteria
- No provisional decision is serialized as final.
- Appeal availability is contract-derived.
- Economic values preserve exact integer units and asset metadata.
- Batch 4 screens can render without invented states.
Dependencies
- PREWAVE-BE-005 (PREWAVE-BE-005 — Publish Versioned Claim List and Claim Detail Read Models #600)
- Contract PREWAVE-BE-080 — Sanitize Public Incident Projection Fields #674
- Contract feat(v2-be): version ABI decoding, harden SIWE nonce binding, and session rotation/revocation #525
- 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
DEV-CHIDIOFFICIAL commentedon Oct 15, 2026
@DEV-CHIDIOFFICIAL 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 @DEV-CHIDIOFFICIAL to this issue.
bigpoppaofny commentedon Oct 16, 2026
@bigpoppaofny 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 @bigpoppaofny to this issue.
drips-wave commentedon Oct 16, 2026
Congratulations, @bigpoppaofny! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @bigpoppaofny: 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 18, 2026
This issue has been completed by @bigpoppaofny as part of the Stellar Wave Program's 10th Wave 🥳
😎 @bigpoppaofny: 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.