Skip to content

Fix: Implement a Bonded Dispute and Challenge Workflow for Oracle Decisions - #489

Merged
techisigu merged 1 commit into
Refract-Protocol:mainfrom
rudeus112266:autosolve/issue-207
Oct 24, 2026
Merged

techisigu merged 1 commit into
Refract-Protocol:mainfrom
rudeus112266:autosolve/issue-207

Conversation

@rudeus112266

Copy link
Copy Markdown
Contributor

Resolves #207.

Opened automatically by autosolve-cli.

Closes #207

- Migration 007: claim_disputes (status, bond state, window, reversal link)
  and settlement_reversals (one owed reconciliation per decision).
- DisputeService: open/transition/get with explicit state machine, DB-clock
  challenge window per coverage type (DISPUTE_WINDOW_HOURS), duplicate and
  final-decision guards, in-flight settlement guard, row locks.
- DisputeController: POST /api/v1/disputes, GET /api/v1/disputes/:id,
  POST /api/v1/disputes/:id/transitions; ops-authenticated.
- trust.dispute events for every lifecycle step; refract_claim_disputes_open gauge.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
@techisigu
techisigu merged commit 42fdbd6 into Refract-Protocol:main Oct 24, 2026
1 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement a Bonded Dispute and Challenge Workflow for Oracle Decisions

2 participants