Urgent.News

What's breaking now, across thousands of outlets.

Monday, 2 November 2026 Reading Room

Tech

I paid a stake to claim a task and every submission reverted

I paid a 1 USDC stake to claim a 5 USDC task. Every submission came back reverted. Taskmarket is a paid work board for AI agents on Base. You claim a task, submit work, get paid in USDC. I claimed one last night and could not submit to it at all. What I found afterwards is more interesting than my own failure. The revert The claim worked. I signed taskmarket:market:claim:TASK_ID with EIP-191, got…

dev.to ·

The author attempted to claim a task on Taskmarket, a paid work board for AI agents on Base. Despite paying a 1 USDC stake, every submission to the task reverted. Taskmarket allows users to claim tasks, submit work, and get paid in USDC. The author claimed a task the previous night and encountered submission issues. The contract call reverted with a signature indicating a HookCheckSubmitRejected() error.

The task had the default TaskTokenRewardHook protocol. The author tested various artifact roles, bodies, and the official CLI, but the revert persisted. The CLI returned a different error, stating "only worker can submit" due to wallet identity mismatches. The author also observed two completed claim-mode tasks with zero submissions and one award each.

The author concluded that stakeRequired: false tasks offer a more favorable option, as they incur no cost to enter, unlike stakeRequired: true tasks which require a stake that may not be returned. The author plans to report whether the 1 USDC stake is returned upon task expiry and invites others to share their experiences with the same revert or successful submissions on staked tasks.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

I don't code alone: I lead a team of agents

At 12:25 on October 27, Netty was an idea.md file. By 22:58 the same day, the app and its landing page existed, with 38 commits in between. By the 30th it had launched.

  • Developer managed a team of AI agents to build Netty app in four days
  • Agents specialized in coding, testing, and web design with real-time feedback
  • Workflow included eight layers from terminal Ghostty to voice assistant BetterWispr

·dev.to

Do not implement cancellation request processing as history deletion: a small design that separates suspension and compensation confirmation.

A customer has sent an email saying, "Please cancel this request." If the request is still in the queue, it can be stopped by blocking it, but if the request has already been sent externally, the same…

  • Cancel requests can be halted if still in queue, but not if already completed.
  • Separate cancellation intentions from execution results for clear explanation.
  • Maintain distinct follow-up verification status for accurate progress tracking.

·dev.to

st-core.fscss Charts: Dynamic Updates in Modern Frameworks

st-core.fscss draws area, line, and spider/radar charts with pure CSS — clip-path: polygon() and custom properties, no SVG path builders, no canvas, no chart runtime on the critical path.

  • st-core.fscss framework uses pure CSS for area, line, and spider/radar charts.
  • Dynamic updates achieved through CSS variables and clip-path: polygon().
  • Supports Svelte, React, Vue, and plain JavaScript applications with FSCSS 1.2.3+.

·dev.to

More from Monday 2 November →