Skip to content

Issue 17: Backend - Dispute Intake and Automated Execution Pipeline #28

@soomtochukwu

Description

@soomtochukwu

Description:
Once the Soroban Escrow contract fires a DisputeRaised event, the backend must leap into action. This issue requires building the automated pipeline that constantly runs in the background (or webhook receiver), listening for these on-chain dispute events. Upon detecting a dispute, the intake pipeline fetches all relevant IPFS records, bundles the CaseFile, and triggers the Agent Judge (the logic established in issues 15 & 16). Once the verdict is generated and validated, the pipeline must initiate the final transactional phase. It will utilize the Stellar SDK to construct a resolve_dispute transaction, sign it with the highly guarded Agent Judge private key, and submit it directly to the Stellar network to execute the payout according to the split.
Requirements:

  • Build a background worker or indexer interface tracking Soroban events for DisputeRaised.
  • Connect the event detection to the OpenClaw verdict generation pipeline.
  • Utilize the stellar-sdk inside Rust to dynamically craft the escrow resolution transaction enforcing the verdict split.
  • Manage the Agent Judge secret key securely restricting access entirely to this automated pipeline.
    Acceptance Criteria:
  • The end-to-end pipeline automatically detects a dispute flag and reaches a simulated resolution.
  • The constructed Stellar transaction reflects the exact percentage split mandated by the AI.
  • Transaction submission correctly handles network fees and sequence numbers dynamically.

Frontend Integration (Next.js + Web3)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions