Espl

List Validation Rules

Returns the list of validation rules that a challenge must satisfy before it can be promoted to production. Call this before creating a challenge to ensure your inputs will pass validation. Rules cover value ranges, address formats, and timestamp constraints.

Estimate Challenge Cost

Estimates total cost (gas + locked reward pool + transfer fees) of creating a walking challenge. No on-chain transaction. Call this before create_challenge_draft so the user can confirm the cost.

Create Challenge Draft

THIS IS A FINANCIAL OPERATION. Creates a new walking challenge. Deploys a smart contract on-chain (consumes gas), locks the reward pool, and registers the challenge in espl's draft table. The challenge will be validated by an automated cron job and promoted to production within approximately 5 minutes. Always confirm parameters AND total cost with the user before calling. Call estimate_challenge_cost first.

Get Challenge Status

Returns the current status of a challenge draft by its draft_id. Possible status values: 'pending' (awaiting cron validation), 'promoted' (live in production app), 'rejected' (failed validation, includes reason). Read-only, no side effects.

Awc Get Challenge Progress

Returns step-count progress for every participant in a walking challenge identified by challenge_id. Wallet addresses + step counts ONLY — never names, employee IDs, emails, or other PII. Use this to drive individual interventions in the corporate dashboard (e.g. 'encourage everyone under 5000 steps via Slack'). The dashboard side is responsible for mapping wallet → employee inside the customer's own environment. Read-only, no side effects.

Awc List Active Challenges

Lists walking challenges deployed by a given sponsor wallet, with status (active / completed / cancelled), period, participant count, network, and contract address. Use this to discover which challenges to query for progress via awc_get_challenge_progress. Server-side scoping limits results to the sponsor wallet associated with the calling key. Read-only, no side effects.

Awc Get Participant History

Returns day-by-day step count history for one participant wallet over the last N days. Wallet + date + step count only — never names or other PII. Use this after awc_get_challenge_progress identifies a participant of interest (e.g. low-step employee, consistently high performer) to investigate their trend before composing a Slack DM or recognition note. Read-only, no side effects.

Awc Build Walking Challenge Deploy Tx

Phase 2 self-custody deploy (STEP 1 of 2). Builds an EIP-1559 unsigned deploy tx for a walking challenge contract. The backend creates a `preparing` draft row and returns the unsigned tx — the caller's wallet (via WalletConnect / wagmi) signs and broadcasts it. THE SERVER NEVER HOLDS THE DEPLOYER KEY. After the tx is mined, the caller MUST follow up with `awc_notify_walking_challenge_deployed` so the backend can verify the receipt, grant the NFT role, and queue promotion to production. Use `idem

Awc Notify Walking Challenge Deployed

Phase 2 self-custody deploy (STEP 2 of 2). Notify the backend that the deploy tx built by `awc_build_walking_challenge_deploy_tx` has been signed, broadcast, and mined. The backend verifies `receipt.status == 1`, `receipt.contractAddress` matches the claim, `receipt.from` matches the draft's deployer (the prepare-deploy signer), and the on-chain calldata matches the originally issued unsigned tx. On success it writes status='deployed', grants the NFT role, and the 2-min cron promotes the draft t