Skip to content

[Contract] Dispute escalation tiers + arbiter staking/slashing #43

Open

Description

@Gbangbolaoluwagbemiga

Goal

Make dispute resolution economically honest and scalable: add escalation tiers and put arbiters'
own funds at stake so good-faith, timely rulings are rewarded and bad/absent ones are penalized.

What needs to be done

  • Staking: arbiters must lock a stake to be eligible (extends authorize_arbiter in admin.rs)
  • Slashing: an arbiter who is overturned on escalation, or who fails to vote within a deadline,
    loses part of their stake; honest/timely arbiters earn a fee share
  • Escalation tiers: Tier 1 = assigned arbiters (voting [Contract] Implement arbiter voting mechanism for dispute resolution #3); Tier 2 = larger panel / owner
    review on appeal within a window
  • Track per-arbiter stats (rulings, overturn rate) for reputation

Acceptance criteria

  • Eligibility requires an active stake
  • Overturned/absent arbiters are slashed; correct ones rewarded — all unit-tested
  • Escalation moves a dispute to the next tier within the configured window

Relevant files

contracts/secureflow/src/admin.rs, refund_system.rs, ties to #3 (arbiter voting)

Activity

  1. changed the title [-]Dispute escalation tiers + arbiter staking/slashing[/-] [+][Contract] Dispute escalation tiers + arbiter staking/slashing[/+] on Jun 17, 2026
  2. Ranjeet2063 commented on Oct 6, 2026

    @Ranjeet2063

    Hi maintainers,

    I reviewed this issue and would like to contribute the fix.

    Technical outline:

    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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew product capability

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions