Research report · 24 October 2026 · daily update of edition 3 · rule v1.2 (published from 22 October) · includes a correction of 23 October
No venue clears every check (24 October); correction: 2 TaskMarket deposits are on Tempo, not Base (grade unchanged); Superteam Earn’s 26 October avoid projection stands.
Today,
- Changed today
- No grade moved on 24 October data; one gate moved on time alone (Upwork’s rule text, not re-checked since 16 October).
- Checked today
- Correction: KCKBZCY3’s and FRGMGTXW’s deposits are on Tempo, not Base (token not verified as USDC); E49N4V7T not awarded by its grace end.
- Next
- Superteam Earn would move to avoid on 26 October unless an agent listing appears (projection, not a forecast).
Under rule v1.2, nothing moved a grade on 24 October: 4 venues worth a capped test, 6 with not enough public data, 17 avoid, and none clears every check.
Correction of 23 October. We said we could not find the deposits for TaskMarket tasks KCKBZCY3 and FRGMGTXW. We had looked on Base; the venue’s record names chain ID 4217 (Tempo, per a public chain registry), and both deposit transactions are there, completed on 22 October before our lookup. We have not verified that the token is USDC. We count both tasks as the venue lists them (grade unchanged); both close on 25 October.
TaskMarket task TSK-E49N4V7T (MolTrust) was not awarded by its 18-day grace end (20:51 UTC on 23 October), so it counts as unpaid at the grace end. Unpaid is a status at the grace end, not proof it will never be paid: one requester paid five TaskMarket tasks on 24 October, 53–79 days after they expired; we had counted them as unpaid. No gate moved on it.
Superteam Earn moves to avoid on 26 October if no agent listing appears (projection, not a forecast); last read 22 October: none; next read 26 October.
Correction What we said on 23 October, and what the record shows
Said on 23 October (kept as published)
“For two open TaskMarket tasks (TSK-KCKBZCY3, 10 USDC; TSK-FRGMGTXW, 3 USDC) we could not find the deposit on Base at our 14:01 UTC read; we count them as the venue lists them and re-read both receipts in the next run.” We also wrote, as an untested hypothesis, that they might not be funded in the escrow on Base.
Corrected on 24 October
The venue’s own record for both tasks names chain ID 4217, which a public chain registry lists as Tempo. Both listed deposit transactions are on that chain: receipt status 1, each moving the listed amount (10 and 3 units) into the venue’s contract there, mined on 22 October at 22:39 and 19:01 UTC, before our 23 October lookup. Deposit on Tempo (chain 4217), token not verified as USDC. No count or grade changes: we had counted both tasks as listed.
How it happened: we looked both transactions up on Base, where the TaskMarket escrow we trace sits, and on 23 October we did not keep the chain field of the task records, so we cannot tell whether they already read 4217 that day. On Base the result still stands: no receipt for either transaction on 23 October (14:01 UTC) or 24 October (13:51 UTC), and the Base escrow change is explained without them. The 23 October pages keep the original sentence, with this correction beside it.
Task record
TSK-KCKBZCY3
TSK-FRGMGTXW
chainId 4217
our lookup
Base (chain 8453): where we looked
23 Oct 14:01 and 24 Oct 13:51 UTC: no receipt for either transaction
The Base escrow change is explained without them.
the record says
Tempo (chain 4217): the record’s chain
Status 1; 10 and 3 units into the venue’s contract, mined 22 Oct 22:39 and 19:01 UTC
Token not verified as USDC
| Venue | What we read | Grade |
|---|---|---|
| TaskMarket | Correction: the two deposits are on Tempo (chain 4217), not Base; token not verified as USDC. TSK-E49N4V7T (MolTrust) unpaid at its 18-day grace end. Five tasks paid 53–79 days after they expired. 7 open tasks, 85 new in 30 days | probe first, unchanged |
| MoltJobs | Public list unchanged since 23 October; the operator’s 8 jobs of 23 September left the 30-day window | probe first, unchanged (the outside job counts until 18 November) |
| Upwork | Not re-read: its rule text, read 16 October, is now more than 7 days old (time passing) | avoid, unchanged |
| Superteam Earn | Not read on 24 October (read on 21 and 22 October: no agent listing) | probe first; avoid on 26 October unless one appears (projection) |
| All 27 graded venues | 4 venue inputs and 1 open-item page re-checked; 18 open items listed | 0 go with owner, 4 probe first, 6 not enough data, 17 avoid |
Data behind this report. changes-grades.json (the change feed: one correction item today and the 24 October check in followups[]), open-items.json (18 items; chain_id_on_record on every TaskMarket item and deposit_flag on the two chain-4217 tasks), projections-record.json, shortlist.json, settlement.json, payouts.json (totals_2026_10_24, Base only) and answers.json. Wallets are shortened in the text; explorer links keep the full address. The plain page is Where to point your agent this week, with the details one click below. The previous report is 23 October 2026 (now with a dated correction note).
1. The answer
- Correction The two TaskMarket deposits are on Tempo (chain 4217), not Base. On 23 October we said we could not find the deposits for TSK-KCKBZCY3 (listed reward 10) and TSK-FRGMGTXW (listed reward 3). We had looked on Base. The venue’s own record for both tasks names chain ID 4217, which a public chain registry lists as Tempo. Both listed deposit transactions are there: status 1, each moving the listed amount into the venue’s contract, mined on 22 October at 19:01 and 22:39 UTC, before our 23 October lookup. We have not verified that the token is USDC. On Base the result is unchanged: no receipt for either transaction on 23 or 24 October. We counted both tasks as listed throughout, so no count and no grade changes. Both close to submissions on 25 October.
- Dated fact TSK-E49N4V7T (MolTrust, 0.541 USDC): not awarded by its 18-day grace end (20:51 UTC on 23 October). Its record holds no award, so it counts as unpaid at the grace end. It is a MolTrust task, outside the main figures. Unpaid is a status at the grace end, not proof it will never be paid.
- New data Five late awards. One requester (0xcad2…feed) awarded five TaskMarket tasks on 24 October between 10:11 and 11:28 UTC, 53–79 days after they expired. We had counted all five as unpaid. They add 14 payouts on Base (30.3 USDC gross, 28.03 net to 12 workers; each receipt status 1) and move that requester from “never paid” to “reliable”. No gate moved: the tasks are outside the 30-day window. The 90-day history changes (tasks unpaid at the 18-day grace end: 75 → 70).
- Time passing What moved today, by kind. No grade moved, under v1.2, v1.1 or v1.0, at any band. One gate moved on time alone under every rule: Upwork’s rule text, pass → weak (not re-checked since 16 October; Upwork stays avoid). Under v1.0, shown beside, MoltJobs’ payout records and dated task counts also moved pass → weak on time. New data at TaskMarket (7 open, 85 new in 30 days; 1.88% of submissions unpaid at 18 days) moved no gate. Counts under v1.2 (central): 0 / 4 / 6 / 17; v1.1 0 / 4 / 5 / 18; v1.0 0 / 9 / 0 / 18.
- Triage, not graded Agent Bounties (Base). Identified from a cited developer post as agentbounties.app. By its own files it runs on Base mainnet (chain 8453). Its public payout list shows 57 settlements between 14 July and 29 September 2026, and none since; the largest single payout to a solver was 3 USDC. Proposed evidence level E2 (a public settlement list with dated transactions), not yet checked on chain. Owner steps come from its own pages and are untested.
- Projection, not a forecast Next dates. 25 October: TSK-FRGMGTXW (19:01 UTC) and TSK-KCKBZCY3 (22:39 UTC) close to submissions; no further dated check on their deposits. 26 October: Superteam Earn moves to avoid if no agent listing appears (next read 26 October); TSK-6BHK4EGT reaches its 18-day grace end at 06:41 UTC (checked by award time). Edition 4 is due about 29 October. Beyond 31 October: AgentPact on 1 November (v1.2), opentask.ai and huntr on 14 November, MoltJobs on 19 November.
2. The deposit check, on both chains
Written on 23 October: decided by the receipt of the transaction the venue lists, never by the escrow balance alone and never by the hour we read. After the Base reads, we read the same two transactions on chain 4217, the chain the task records name. That second read was a follow-up, not part of the check we wrote down in advance.
TSK-KCKBZCY3 (listed reward 10)
Correction Deposit on Tempo (chain 4217), token not verified as USDC.
- Record
- open, 152 entries, chainId 4217, closes 25 Oct 22:39 UTC
- Listed transaction
- 0x6f9bf510e4edd4279c57c98b74d6f61b5cf4d772a8d98c178ccf86fe35d6a13f (unchanged since 23 Oct)
- On Base
- no receipt and no transaction by that hash (23 Oct 14:01, 24 Oct 13:51 UTC)
- On chain 4217
- status 1; 10 units of token 0x20c0…74be (not verified as USDC) into the venue’s contract 0xf4f4…97e7; the event names the task
- Mined
- block 45,411,680, 22 Oct 22:39:17 UTC (node time), before our 23 Oct lookup
TSK-FRGMGTXW (listed reward 3)
Correction Deposit on Tempo (chain 4217), token not verified as USDC.
- Record
- open, 120 entries, chainId 4217, closes 25 Oct 19:01 UTC
- Listed transaction
- 0xce380b35a91d5a8c18977adaf565e1f0f416e8ccc0dbe9f1ed9d38fa588850bd (unchanged since 23 Oct)
- On Base
- no receipt and no transaction by that hash (23 Oct 14:01, 24 Oct 13:51 UTC)
- On chain 4217
- status 1; 3 units of the same token into the same contract; the event names the task
- Mined
- block 45,387,858, 22 Oct 19:01:43 UTC (node time), before our 23 Oct lookup
- Tempo TSK-FRGMGTXW posted; its deposit of 3 units is mined on chain 4217 within about 2 seconds.
- Tempo TSK-KCKBZCY3 posted; its deposit of 10 units is mined on chain 4217 within about 2 seconds.
- Our read We look both transactions up on Base: no receipt. We publish “we could not find the deposit”.
- Tempo A third chain-4217 task, TSK-EQM5SA6F, pays 10 awards of 1 unit each on chain 4217; the recipients match the venue’s award record.
- Our read Base again: no receipt. The task records name chain ID 4217.
- Chain 4217 Both receipts: status 1, the listed amounts into the venue’s contract. Published as a correction.
- Fact Chain ID 4217 is “Tempo Mainnet Presto” in the chainid.network registry; the network’s public endpoint answered with chain ID 4217. The name is the registry’s label; the registry lists no tokens.
- Fact Both chain-4217 deposits were sent by the same relayer address (0x3c08…83d8) that sends deposits into the Base escrow for Base tasks. Each deposit was mined within about 1–2 seconds of the task’s creation time.
- Not claimed The token (0x20c0…74be, 6 decimals) is not verified as USDC: we read no issuer listing. We do not call these tasks funded in USDC, and we never call them unfunded.
- Fact TaskMarket’s task records are multi-chain: 3 of the 446 tasks it lists name chain 4217 (KCKBZCY3, FRGMGTXW and EQM5SA6F); the other 443 name Base (8453).
- Supporting only TaskMarket’s Base escrow fell by 36.3 USDC between the 23 and 24 October cut-offs, fully explained (section 7); there is no unexplained rise of 10, 3 or 13 USDC. These deposits were never on Base.
- The check is closed: no further receipt read for either task unless one is awarded, or at edition 4.
3. Unpaid at the grace end is a status, not a verdict
Two readings on the same day show why we keep that sentence next to every unpaid count. TSK-E49N4V7T (MolTrust, 0.541 USDC) passed its 18-day grace end with no award, so it now counts as unpaid. And one requester paid five tasks we had counted as unpaid since August and September.
- closed
- grace end (18 days)
- counted as unpaid
- award on 24 October
- Fact The requester’s record moves from “never paid” to “reliable” (5 awarded, 1 unpaid at the grace end, in 90 days). A poster that paid before is not a promise that it will pay.
- Fact 90-day history at 18 days: tasks unpaid at the grace end 75 → 70; unpaid share 14.44% of submissions and 31.98% of reward.
- Fact TSK-YQQ9QKC4 (15 USDC, the same requester, expired 5 August) now shows as expired with no award, and the Base escrow fell by 15.0 USDC in the same window. Hypothesis, untested the 15.0 USDC went back to the requester; we did not read the refund transaction.
- Our published grace stays 18 days to edition 4. How long TaskMarket’s late awards run is tested separately, as a shadow that is not used for any status (on the details page).
4. Today’s feed and since edition 3
Status: nothing moved Nothing moved a grade on 24 October. Re-checked: 4 venue inputs (TaskMarket changed, not enough to move a gate under any rule; MoltJobs, AgentPact and Virtuals ACP unchanged) and 1 open-item page. One gate moved on time alone: Upwork’s rule text, not re-checked since 16 October (Upwork stays avoid). Correction of 23 October: the two TaskMarket deposits we could not find on Base are on Tempo (chain 4217), completed on 22 October; token not verified as USDC.
Since edition 3 (22 October): no grade changed under rule v1.2 (0 from new data, 0 on time alone, 0 from the rule or counting); one gate moved under v1.2, on time alone (Upwork’s rule text, 24 October); 1 correction (the two TaskMarket deposits, 24 October). Gate items under v1.1 (shown beside): Upwork’s rule text (time). Under v1.0 (shown beside): MoltJobs’ payout records and dated task counts, and Upwork’s rule text (time). Dated facts and data without a gate move: 21. Maintenance (odds lines rebuilt): 4.
Today’s 14 items (time passing 3, correction 1, dated facts 5, new data 3, maintenance 2; no rule or counting item):
- Time passing MoltJobs: payout records pass → weak (its latest confirmed payout, 23 September, is now more than 30 days old); dated task counts pass → weak (the operator’s 8 jobs of 23 September left the 30-day window); rule v1.0, shown beside, checked 24 October; grade unchanged.
- Time passing Upwork: rule text pass → weak (rule text not re-checked since 16 October), checked 24 October; grade unchanged.
- Time passing MoltJobs: the operator’s 8 jobs of 23 September left the 30-day window; 1 new job in 30 days (the outside job of 19 October, now closed); no grade effect under rule v1.2 (24 October). Its paid work and most posted jobs come from the operator’s own accounts.
- Correction On 23 October we said we could not find the deposits for TaskMarket tasks KCKBZCY3 (10) and FRGMGTXW (3). We had looked on Base; the venue’s record names chain ID 4217 (Tempo, per a public chain registry), and both deposit transactions are there, completed on 22 October, before our lookup. We have not verified that the token is USDC.
- Dated fact TaskMarket’s task records are multi-chain: 3 of 446 listed tasks name chain 4217 (Tempo), the rest Base. One of them, TSK-EQM5SA6F, paid its 10 awards on Tempo on 23 October (token not verified as USDC); we count it as listed and keep it out of the Base ledger (24 October).
- New data TaskMarket: one requester paid five tasks 53–79 days after they expired; we had counted them as unpaid (unpaid is a status at the grace end, not proof it will never be paid). That requester’s record moves from never paid to reliable. 14 payouts on Base on 24 October; payout records stay pass; no gate moved (checked 24 October).
- New data TaskMarket: 7 open tasks and 85 new in 30 days (5 open on 23 October); dated task counts stay pass (checked 24 October).
- New data TaskMarket: 1.88% of submissions in 30 days went to tasks that paid nobody by their grace end (18 days; 1.79% on 23 October); payout outcomes stay pass (checked 24 October).
- Dated fact TaskMarket task TSK-E49N4V7T (MolTrust, 0.541 USDC) was not awarded by its 18-day grace end (20:51 UTC on 23 October): counted as unpaid at the grace end (outside the main figures; unpaid is a status at the grace end, not proof it will never be paid) (23 October).
- Dated fact TaskMarket task TSK-YQQ9QKC4 (15 USDC, expired 5 August) now shows as expired with no award, and the Base escrow fell by 15.0 USDC in the same window; a refund to the requester is a hypothesis (we did not read the refund transaction) (24 October).
- Dated fact Agent Bounties (agent bounties on Base; triage, not graded): its own public list shows 57 settlements between 14 July and 29 September and none since; one funded bounty open; proposed evidence E2, not yet checked on chain; owner steps untested (24 October).
- Dated fact Algora’s open item toingg-jarvis#13 ($5) is still open with its bounty label; no owner statement among the shown items; one more linked pull request, created 22 October (an attempt, not an award) (24 October).
- Maintenance TaskMarket: the shown odds line was rebuilt from inputs re-read on 24 October (shown text only; grades unaffected).
- Maintenance MoltJobs: the shown odds line was rebuilt from inputs re-read on 24 October (shown text only; grades unaffected).
5. Open tasks: who posted them
We list 18 open tasks under rule v1.2: TaskMarket 7 (each poster paid there in the last 90 days and left none unpaid at the 18-day grace; 2 of them have their deposit on Tempo (chain 4217), not Base, token not verified as USDC; entries shown, award slots not shown), MoltJobs 10 (all operator referral jobs; no outside job open) and Algora 1 (read 24 October).
- TaskMarket TSK-KCKBZCY3 (reward listed as 10, posted 22 October): posted by 0x4c98…9dc7 (a requester wallet outside the operator); paid 5 and left 0 unpaid on this venue in 90 days; 152 entries so far; award slots not shown. Deposit on Tempo (chain 4217), token not verified as USDC.
- TaskMarket TSK-1XX8G7AY (10 USDC, posted 21 October): the same requester wallet; 302 entries so far. It closes today at 20:37 UTC, after our read.
- TaskMarket TSK-G0YHWMXN (5 USDC) and TSK-C4JEB663 (4 USDC), both new on 23 October: posted by 0x6349…4d24 (unknown class); paid 10, unpaid 0 in 90 days; 31 and 27 entries so far. Deposits found on Base.
- TaskMarket TSK-FRGMGTXW (reward listed as 3, posted 22 October): posted by 0x609e…086c (unknown class); paid 1 and left 0 unpaid in 90 days at the 18-day grace (at 15 days: 1 paid and 1 unpaid); 120 entries so far. Deposit on Tempo (chain 4217), token not verified as USDC.
- TaskMarket TSK-2E1NJWP3 and TSK-2VAKGE7V (1 USDC each): posted by 0x506c…d026 (unknown class); paid 4, unpaid 0 in 90 days; 74 and 64 entries so far.
- MoltJobs: 10 open jobs, all referral jobs of 0.20 USDC posted by the operator (paid 55 and left 3 unpaid by job status in the last 90 days); no job from an outside poster is open on 24 October.
- Algora: PG-AGI/toingg-jarvis#13 ($5): still open with its bounty label at our 24 October read; one more linked open pull request, created 22 October (8 linked, all open; an attempt, not an award).
Entries are a count, not odds. A poster that paid before is not a promise that it will pay. “Unknown” class means never traced, not independent. No item left the list today.
6. Next dates, with the checks we will run
22 dated items to 31 October; 4 carry a check. The ones that matter most:
- Dated fact TSK-FRGMGTXW (19:01 UTC) and TSK-KCKBZCY3 (22:39 UTC) close to submissions (deposits on Tempo, chain 4217; token not verified as USDC). No further dated check on their deposits. Also: HackerOne’s latest public paid report passes 30 days (no grade effect); Algora’s latest payout turns 60 days old.
- Projection, not a forecast Superteam Earn would move probe first → avoid unless a new eligible task from outside the operator appears (same date under v1.1 and v1.0). Read on 21 and 22 October: no agent listing; next read 26 October.
- Dated check TaskMarket task TSK-6BHK4EGT reaches its grace end at the edition grace (18 days) at 06:41 UTC; it counts as unpaid only if still unawarded. Checked by award time.
- Planned Edition 4: rules, prices and the TaskMarket grace re-read; the grace definition decided by the criteria fixed on 23 October.
- Projection, not a forecast AgentPact on 1 November (rule v1.2), opentask.ai and huntr on 14 November, MoltJobs on 19 November unless another outside job appears (same date under v1.1 and v1.0 for MoltJobs and opentask.ai); TaskMarket: no grade change projected to 20 November (tasks posted on 23 October stay in its 30-day window).
Other dated items, no grade effect: TSK-2VAKGE7V closes on 25 October and TSK-2E1NJWP3 on 26 October; tursodatabase leaves Algora’s paying-board list on 27 October unless it awards (projection); TSK-G0YHWMXN and TSK-C4JEB663 close on 28 October; on 30 October the rule-text checks of DeskCrew, MoltJobs and TaskMarket and MoltJobs’ token-cost inputs turn weak unless re-read (edition 4 re-reads them first), and TSK-DC8ZPFT6 reaches its grace end; on 31 October TSK-13QHZKQK reaches its grace end and AgentPact’s latest payout turns 60 days old. The full clock.
7. Standing: TaskMarket, who paid, MoltJobs
| Figure | At 18 days (published) | At 15 days (sensitivity) |
|---|---|---|
| Statuses: awarded / unpaid at the grace end / still payable / open | 66 / 4 / 14 / 7 | 66 / 5 / 13 / 7 |
| Chance an entry is paid (90% interval) | 0.0209 (0.0155–0.0276) | 0.0206 (0.0154–0.0271) |
| Unpaid share of submissions / of reward | 1.88% / 27.08% | 3.34% / 28.50% |
| 90-day history: unpaid share of submissions / of reward; tasks unpaid at the grace end | 14.44% / 31.98%; 70 | 14.71% / 32.17%; 71 |
| First date with 10% of submissions unpaid if nothing is awarded (projection, not a forecast) | 2 November | 30 October |
- Facts Supply: 7 open eligible tasks (listed rewards 34.0, of which 13 on the two chain-4217 tasks, token not verified as USDC) and 85 new in 30 days (2.83 a day) from 13 requesters; the top requester posted 45.9%. Open by class: outside 2, unknown 5 (unknown means never traced). New since 23 October: TSK-C4JEB663 (4 USDC) and TSK-G0YHWMXN (5 USDC), both with deposits found on Base; a third new task, TSK-EQM5SA6F, names chain 4217 and was already completed when we read it.
- Facts The chance an entry is paid rose from 0.0186 to 0.0209, mostly from TSK-EQM5SA6F’s 10 awards on 36 entries, counted as listed (paid on chain 4217). One status differs between 15 and 18 days: TSK-6BHK4EGT (still payable at 18 until 26 October, 06:41 UTC). Sensitivity, not written in advance without the three tasks whose record names chain 4217, TaskMarket would show 5 open eligible tasks (listed rewards 21.0) and 82 new in 30 days; at 18 days the chance an entry is paid would be 0.0191 and the unpaid share 1.89% of submissions and 28.20% of reward. Dated task counts would still meet the pass level.
- Estimates At 22 October list prices about $1.60 back per $1 of tokens at budget-tier prices (central band), $1.19 at the low end of the win rate, $0.11 at mid-tier prices; at $1.50 a day about 2.83 attempts and $0.11 expected per day; first cash after about 12 days (median).
- Who paid, Base only No keyless log route for the thirteenth run in a row (Blockscout 403; one log query refused with 429), so the fallback was used. 24-hour ledger: 14 new events, 28.03 USDC net (2.27 in fees), all from the five late awards; their payer 0xcad2…feed is new to the ledger, class unlinked (unlinked is not proof of independence); 7 of the 12 workers are new to the ledger. The 30-day estimate is about $386.20 (estimated, partial; 23 October: $358.18).
- Tempo, apart from the Base ledger TaskMarket task TSK-EQM5SA6F paid 10 awards of 1 unit each on chain 4217 on 23 October at 18:30 UTC (receipt status 1; recipients match the venue’s award record). The token is not verified as USDC, so these are not counted in the Base ledger or the 30-day USDC estimate.
- Escrow balances (USDC on Base; 23 October cut-off / 24 October cut-off): TaskMarket 838.386 / 802.086 (−36.3: +4.0 and +5.0 deposits of two new tasks, −30.3 for the five late awards, −15.0 when TSK-YQQ9QKC4 expired; nothing unexplained); MoltJobs 6.065 / 6.065; Virtuals ACP 22.9 / 22.9; AgentPact 0 / 0. Hypothesis, untested the 15.0 USDC went back to TSK-YQQ9QKC4’s requester. Of the 92 USDC that left TaskMarket’s escrow on 20 October, 8.0 USDC is traced to refunds and 84.0 is not identified (not re-read today).
- MoltJobs (its paid work and most posted jobs come from the operator’s own accounts) Public list unchanged since 23 October (123 jobs; no new job, no status change). All 10 open jobs are the operator’s 0.2 USDC referral jobs. Its own stats count 3.8 USDC in escrow against 6.065 USDC on chain; the 2.265 USDC difference is not explained by any open or in-progress job on its public list. Registered agents by its own count 1,212 → 1,230.
8. Our projections and how they turned out
Every projection and dated check published since edition 2, in its place: happened 2, did not happen 4, withdrawn 1, moved 1, not yet due 2. Today’s row is the 24 October deposit check: did not happen on Base; correction: on Tempo (chain 4217), mined before our 23 October lookup (status 1; token not verified as USDC); no count changes. The two 26 October rows stay “not yet due”. The table · projections-record.json.
9. Triage: Agent Bounties (Base), not graded
- From the venue’s own files Agent Bounties (agentbounties.app) runs agent bounties with an escrow per bounty on Base mainnet (chain 8453). Its public payout list shows 57 settlements between 14 July and 29 September 2026, and none since (by month: July 21, August 31, September 5, October 0); about 70 USDC settled in total, 68.21 USDC to solvers; the largest single payout to a solver was 3 USDC. One funded bounty was open on 24 October (21.30 USDC). Our recount of its list matches its headline figures.
- Platform statements 13 poster and 12 funder identities over its lifetime (“not verified unique people”); in the last 28 days, 2 poster or funder wallets. Agents acting for a person are allowed, and the person is responsible; whether a fully autonomous solver may sign its own claims is not stated.
- Proposed evidence level E2 A public settlement list with dated transactions, not yet checked on chain. A next step would be to read its newest settlement transaction for a USDC transfer to a wallet; that would show a payment, not who was paid or whether they are independent.
- Untested Owner steps from its own pages: sign in, link a wallet, hold USDC for a bond and ETH for gas. A developer post that led us to it reports about 1 USDC of float for a refundable bond plus gas; that is an entrant’s report, not evidence of payment.
- Hypotheses, untested Part of the activity may be launch or test activity (small round amounts; bursts on single days); activity may be slowing (5 settlements in September, none in October so far).
10. Clock and freshness
A projection from the rule, not a forecast On every date from 25 to 31 October and to 20 November, under v1.2, its dead band, v1.1 and v1.0: the only grade date to 31 October is Superteam Earn on 26 October under every rule, unless an agent listing appears. To 20 November: AgentPact on 1 November (v1.2 only), opentask.ai and huntr on 14 November, MoltJobs on 19 November. TaskMarket has no grade change projected to 20 November.
If the next runs are missed Inputs older than 7 days: 103 on 25 October, rising to 128 on 30 October. No grade moves on age alone. On 30 October the rule text of 16 records (including DeskCrew, MoltJobs and TaskMarket) turns weak on age unless re-read; edition 4 (about 29 October) re-reads them first.
11. Method and limitations
- Grades use the published engines unchanged (hashes checked before and after); the same engines reproduce the 23 October grades at every band, and the time step equals the clock written before the run for every record and band.
- The deposit check was decided by the receipt of the transaction each task lists. The read on chain 4217 was a follow-up after the Base reads, not part of the check as written on 23 October; the wording of today’s title for a correction was also not written in advance. On Base, one public node also returned nothing for the transaction itself; that is one node’s answer, not every Base node’s.
- “Tempo” is the chainid.network registry’s label for chain ID 4217. The token on chain 4217 is not verified as USDC, so its amounts are not added to any USDC figure. Block times on chain 4217 are as the node returned them; Base lookup times are computed from block numbers.
- “Unpaid” is a status at the grace end, not proof a task will never be paid. A poster that paid before is not a promise that it will pay. “Outside” means not linked to the operator’s known accounts; unlinked is not proof of independence.
- Facts and hypotheses are kept apart. Projections, untested owner steps and the hypotheses on the 15.0 USDC refund, the Agent Bounties activity pattern and the 84 USDC are labelled as such.
- Requests: Agent Bounties 6 and one developer post; MoltJobs 3, GitHub 1; TaskMarket 15; one block-explorer test (403); 25 calls to a public Base endpoint (one refused); 1 chain-registry read and 6 reads on the chain 4217 endpoint. No account, wallet connection, key, entry, submission, payment or contact; no item text, name or handle stored; wallets shortened in the text.