LARP check · Robinhood Chain
$HUGINWORK
$HUGINWORK
Robinhood Chain6 claims read from its site. Its API at huginwork.com/api/feed answered with data (fields items). One working part of it answered our reads; a second kind would make it found.
Read 9 h ago · mcap at check — · now — · since check —
What it says, and what we found
- not found“every pick that agrees earns $0.01” its sitewe could not find a contract, a working app or recent code of its own that backs this
- not found“From a pool contract on Robinhood Chain that anyone can look up.” its sitewe could not find a contract, a working app or recent code of its own that backs this
- partly“Three people rate every pair, the majority wins” its siteits API at huginwork.com/api/feed answered with data (fields items)
- not found“everyone with $0.50 or more is paid automatically every night at 00:05 UTC” its sitewe could not find a contract, a working app or recent code of its own that backs this
- not found“Wallets that miss too many are removed and their balance is not paid.” its sitea second reader of our reads found they do not back this
- not found“CA 0x876b4de9286510e342bb412b459998917317bc69” its sitea working part answering does not show this; we could not check it
The claims are their own words, quoted by Claude Haiku 5.5; Claude Sonnet 5.5 checked each result against our evidence and Claude Opus 5.5 had the final say; every check of them is our own read, and chain facts come from the chain.
Working parts we tested
- answeredAPI: its API at huginwork.com/api/feed answered with data (fields items) · huginwork.com/api/feed
- no answerMCP: no MCP server answered at huginwork.com/mcp, huginwork.com/api/mcp
- factX account @huginwork: exists (an account is not working tech; it backs no claim)
- readThe page we read: huginwork.com/ (declared at launch)
Holders of 1M $TOLL can re-read this now. Get $TOLL
Claude Opus 5.5 reviewed this read · holders see its notes. Get $TOLL
This dev's other coins we read
None yet: this is the first coin from this dev wallet that we read.
How we read it
We read what the project says in its own words: its website, its code README and its launch post. Each thing it says it offers is listed as a claim. Then we test it ourselves, and only our own reads count: the contracts it names on chain, who calls them and what they actually do; its app; its own API answering with data; its MCP server listing its tools; its x402 payments; its Chrome Web Store listing; its Telegram bot; its public code changed in the last 30 days. An X account that exists is shown as a fact; it never backs a claim.
- product found a contract of theirs is used by wallets other than the team, or two different working parts of theirs answered our reads.
- product partly found one working part of theirs answered, or weaker support (a contract only the team calls, a page of theirs that opens, fresh code).
- product not found we read their words, and nothing we could check backs them.
- product not read we could not read their words (no site or post, a site that did not open, or one that draws itself with scripts).
Facts, not a verdict: a quiet contract can be tech that launched yesterday, and a busy one can still lose you money. Not advice.