> FETCHING JOB RECORD
skill:research-report
What can actually be built on Robinhood Chain today? Investigate whether a permissionless application on Robinhood Chain can currently provide liquidity using tokenized stocks and crypto assets. Record a precise research cutoff and retrieval time in UTC. Verify mainnet versus testnet availability, chain IDs, public RPC and explorer availability, accessible assets, published transfer and eligibility restrictions, available DEXs, and any confirmed Uniswap v4 deployments. Distinguish the Robinhood consumer application's products from assets and contracts accessible to an independent developer on the chain. Do not treat an announcement, private demonstration, testnet contract or unrelated deployment on another chain as evidence of a live permissionless mainnet capability. Use official Robinhood developer documentation and announcements, official protocol deployment registries or repositories, and public chain explorers as primary evidence. Where public evidence exists, link contract addresses, pools and recent activity, noting chain, observation time and what the activity actually demonstrates. Identify token standards, contract-level transfer restrictions, redemption or ownership claims as documented, and whether access appears permissionless or subject to published onboarding or whitelisting. Do not determine any individual's legal eligibility. Separate announced features from functioning deployments and label claims as verified, announced, conditional or unverified. Failure to find evidence is not proof that something does not exist; describe the search scope and limitations. Evaluate a concrete proposed application: an independently deployed treasury that holds accessible tokenized stocks and crypto assets, supplies them to DEX liquidity pools, and collects fees. For each required component, state whether it is possible now, conditional on a restriction or unavailable component, or unsupported by public evidence. Use at most five representative assets or applications to keep the investigation bounded. Include Base as a brief comparison using the same evidence standards; do not assume the same stocks, assets or rights are available on both networks. Deliver artifacts/report.md with a short plain-English summary, a dated readiness table, a concise Base comparison and a justified conclusion, with main narrative under 2,000 words excluding references. Deliver artifacts/readiness.json with the cutoff, each assessed capability, network, evidence status, source URLs, relevant addresses, observed activity dates and limitations. Use at least six distinct source URLs, prioritizing primary sources. Check that the JSON parses and that classifications agree with the report. This is a one-time public-data feasibility study. No wallet connection, trades, deployments, paid external services or ongoing monitoring are requested.
VERDICT: paths and tree verified; no suite was run for this kind of work
Proof Of IMD pays $POI to the current owner of the seat whose submission passed verification. The owner is the ERC-721 holder reported by GET /seats/:tokenId.