dollar-platoon_skill

This skill helps you manage and optimize micro-gig payroll on Base L2, including gigs, proofs, and on-chain payouts.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill dollar-platoon

  • _meta.json306 B
  • SKILL.md36.4 KB

Overview

This skill provides a concise guide to Dollar Platoon, a peer-to-peer micro-gig payroll marketplace built on Base L2. It explains how clients create USDC-funded gigs, distribute tasks via email/webhook mailboxes, collect proofs, and pay gigworkers on-chain. The skill highlights the reputation-driven model, wallet and payout mechanics, and the platform's no-dispute, as-is risk posture.

How this skill works

Dollar Platoon lets clients create funded gigs with a price per task and distribution rules. Gigworkers receive mailbox endpoints, complete tasks, submit proofs, and earn USDC when proofs are approved or auto-approved after a timeout. A single treasury smart contract on Base L2 holds gig funds and executes payouts; all business logic (reputation, distribution, review) runs off-chain. Reputation is wallet-anchored and drives gating; there is no built-in dispute resolution.

When to use it

  • Create, fund, or configure a micro-gig and set pricing, review timeout, and distribution mode.
  • Join gigs as a gigworker, submit proofs, or share mailbox tokens for public submissions.
  • Review proofs, use rejection tags, and trigger or monitor rollup payouts on Base L2.
  • Manage wallets—choose managed or external custody—and ensure ETH for gas.
  • Integrate task publishers via email/webhook endpoints or build automated proof validation pipelines.

Best practices

  • Fund gigs with at least 110% of expected payouts to cover the 10% platform fee.
  • Always include a unique task_identifier and verifiable evidence (URLs, screenshots) in proofs.
  • Use presigned uploads: POST /upload/presign then include the returned URL in proofs.
  • Set reputation gating to filter applicants and review proofs promptly to avoid auto-approve.
  • Monitor available_funds and min_payout thresholds before approving proofs or triggering rollups.

Example use cases

  • A marketing client funds a $0.50 micro-task campaign, distributes tasks via webhook, and pays approved proofs automatically.
  • A gigworker joins targeted gigs, submits screenshot proofs with task IDs, and accumulates on-chain reputation and USDC earnings.
  • An operator integrates an AI agent to validate proofs via proof_webhook_url before manual review.
  • A publisher app sends tasks to token-protected gig mailboxes for large-scale task distribution.

FAQ

Proofs auto-approve after the configured review_timeout. Auto-approved proofs trigger payouts when the gig has sufficient funds; report bad auto-approved proofs to exclude them from payouts.

How are fees applied to payouts?

A 10% platform fee is charged on top of the worker gross. For example, a $10 payout costs the gig $11 from its on-chain balance.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational