203 — EasyClaw Club: autonomous-posting instructions, unavailable data host
Updated 2026-09-06 UTC

Sources
https://club.easyclaw.com/
https://club.easyclaw.com/api.js
https://club.easyclaw.com/main.js
https://raw.githubusercontent.com/icebergwuw/lobster-skill/main/skill.md
https://dns.google/resolve?name=pcnxplffylcvvanjpaet.supabase.co&type=A
This is distinct from easyclaw.link reviewed in193–196. Similar branding is not sufficient to merge operators or activity.

Observed frontend
Homepage HTTP200,19,442bytes. It advertises agent-authored work logs and shows zero counters with a loading message. The frontend retrieves posts from a named Supabase project. Zero values in unhydrated HTML are not a verified count of agents or posts.
api.js includes published-post queries, a seed-post filter and related rendering code. A seed-post code path does not prove any actual posts are seeded; it is a reason to inspect that field if records become accessible.

Access outcome
A narrowly selected published-post GET, using the intentionally public client key supplied by the site, failed before HTTP because the data hostname did not resolve. Google DNS-over-HTTPS independently returned Status3 (NXDOMAIN) for the same hostname. No post bodies, work logs, agents or comments were returned.
This supports an unavailable configured backend at collection time, not proof of global site closure or no historical use. The frontend remains reachable. A mainland machine is not a demonstrated fix for this DNS result.

Posting mechanism described by the project
The linked skill document, version3.2.0, tells a joining agent to register and publish a first log, then inform its owner. It also describes hourly daytime checks and automatic subsequent posts for qualifying tasks, with privacy exclusions and an explicit-owner-stop exception. The homepage instead says agents ask whether to post after finishing work. This is a documentary mismatch; observed enforcement is unknown.
These instructions could explain apparently spontaneous posts by a configured agent, if actual outputs are found. They do not demonstrate any successful execution. The file was treated solely as evidence: no installation, registration, heartbeat, posts, votes, comments or other mutations were performed.

Assessment
A concrete public instruction set encourages recurring agent-community activity, but this pass recovers no actual activity records. No swarm, Chinese-model/lab attribution, escaped behavior or XZ connection established. Deprioritize repeated queries to the nonexistent configured hostname unless new DNS or a replacement endpoint appears.

Preservation
203-private contains homepage/text, frontend scripts, external skill as plain text, DNS response, access-error note and SHA256 hashes. Raw sources remain private; this reviewed assessment is published. No private credentials were obtained. The browser-facing publishable key is not reproduced in the report.
Next leads should prioritize reachable public outputs over additional promotional catalogues; retain this project only as a documented mechanism and historical-archive candidate.