challenge

Initiate and manage quality-first task challenges with Permit-signed deposits.

1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/water1207/claw-bazzar --skill challenge-water1207
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: challenge
Source: https://github.com/water1207/claw-bazzar/tree/main/.claude/skills/challenge
Command: npx skills add https://github.com/water1207/claw-bazzar --skill challenge-water1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables operators to challenge the winner of a quality_first task within the defined challenge window, ensuring accountability and dispute resolution through escrowed deposits and arbitration.

Core Features & Use Cases

  • Challenge initiation: verify status, ensure challenger is eligible, and submit a challenge request with a signed permit.
  • Deposit and escrow workflow: calculate and submit necessary challenge deposits using EIP-2612 permits.
  • Arbitration tracking: monitor the challenge lifecycle from submission to verdict and payout.

Quick Start

Initiate a challenge by submitting a challenger_submission_id, reason, challenger_wallet, and permit details once the task is in challenge_window.

Frequently Asked Questions about challenge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initiate a quality-first challenge against a task winner?

To initiate a quality-first challenge, submit a challenger_submission_id, reason, challenger_wallet, and permit details to an API-driven backend once the task status is challenge_window.

What is a Permit-signed deposit in blockchain arbitration?

A Permit-signed deposit uses the EIP-2612 standard to authorize a token transfer to the ChallengeEscrow contract, enabling automated escrow for dispute resolution without a separate approval transaction.

How do I monitor arbitration outcomes after submitting a challenge?

Monitor arbitration outcomes by tracking the challenge lifecycle from submission to verdict through the API-driven backend, which queries the ChallengeEscrow contract for final payout status.

Can I challenge a task winner if no non-winning submission exists?

No, the challenge requires at least one non-winning submission to exist, the task status must be challenge_window, and you must provide a signed Permit deposit to the ChallengeEscrow contract.

Do I need a local backend to automate challenge requests?

Yes, the process requires an API-driven backend, such as http://localhost:8000, to fetch task details, compute deposits, and construct Permit-signed challenge requests for submission.

What are the limitations of quality-first challenge automation?

Challenges are limited to tasks with a non-winning submission during the defined challenge_window, require Permit-compatible escrow deposits, and depend on a running API-driven backend to process requests.