Robinhood Chain emerging-product baseline — September 30, 2026

Shortlist for investigation, not a safety endorsement or token recommendation: Robinhood Pools and Verge. Afterhours is watch-only. This first run screened 25 GitHub repository records across two discovery searches and inspected four candidate repository pages. No funds were spent or transactions initiated.

Network baseline and method

Official documentation identifies Robinhood Chain as chain 4663, distinct from testnet 46630, with ETH as gas currency. Chain-specific evidence is required; a generic Robinhood trading tool does not qualify. Official network documentation

Repository creation dates and stars below come from the GitHub discovery snapshots. Creation dates establish repository age, not necessarily product launch dates. Stars indicate public attention, not customers, and low counts do not prove a product is unknown. Retrieved pages can be cached.

1. Robinhood Pools — highest-priority research utility

• Observed: repository created September 7; last push September 29; 62 stars in the discovery snapshot. Public source, installation instructions and tests directory are visible. The README describes a Python/SQLite LP observatory and explicitly distinguishes index freshness from HTTP availability. Its default service is described as observing/simulating without signing or broadcasting. Repository
• Chain evidence: inspected source sets CHAIN_ID = 4663 and defines a protocol registry. This verifies code targeting the chain, not correctness of every listed deployment. Registry source
• Working-product evidence: the hosted page rendered search, pool, wallet and accounting interfaces, but no populated live results in the browser extraction. The status endpoint returned no readable payload through this tool; freshness remains unverified. Hosted interface, status endpoint
• Why promising — inference: chain-specific indexing and explicit missing-data semantics could help researchers avoid misleading LP accounting.
• Caution: PR #24 was open in the retrieved snapshot and addresses recurring writer-induced index drift. Tests and production improvements described there are maintainer-reported, not independently reproduced. Actual users and uptime are unknown. Maintenance evidence
• Next gate: obtain readable freshness/coverage data and independently reproduce one pool-accounting example before recommending operational reliance.

2. Verge — conditional developer-infrastructure shortlist

• Observed: repository created September 22; pushed September 30; 0 stars in the discovery snapshot. The public tree includes SDK, facilitator, examples and tests directories. Repository
• Documented scope: HTTP 402 API payments with Robinhood Chain/USDG as default, Express/Hono examples and payment-proof verification. A first-party changelog lists releases beginning September 22 and updates through September 27. These are implementation/release claims, not independent feature verification. Developer docs, changelog
• Why promising — inference: per-request stablecoin billing could help developers monetize APIs without subscription onboarding. Differentiation is chain support and developer tooling, not invention of HTTP 402 payments.
• Caution: no independent paying users, settlement volume or performance benchmarks were verified. The npm package page returned 403, so publication was not confirmed. Production replay storage and agent-wallet encryption architecture need review; the trust page's client-side-encryption language and environment-decryption-key reference warrant clarification, not a vulnerability conclusion. Package check, security documentation
• Next gate: validate a no-funds payment challenge and package availability, then inspect replay and key handling. Do not fund an agent wallet on this evidence alone.

Watch-only: Afterhours

Repository created September 1; pushed September 30; 1 star in the discovery snapshot. It advertises archived tokenized-stock drift measurements every 15 minutes. That is an interesting monitoring use case, but archive accuracy and cadence were not validated; its linked application was inaccessible through the browsing tool, which does not establish an outage. Repository, linked application

Repeatable evaluation checklist

1. Chain fit: verify mainnet/testnet identity in code or deployment evidence.
2. Newness: record repository creation, earliest release and launch date separately; label missing launch evidence.
3. Substance: inspect artifacts, documentation and dated maintenance beyond promotional descriptions.
4. Usefulness: state the user problem and differentiation; label judgment as inference.
5. Adoption: seek independent integrations, reproducible usage or attributable users; never substitute stars or automated commits.
6. Safety and reliability: check signing/custody, permissions, replay controls, data provenance and freshness.
7. Decision gate: record observed facts, first-party claims, unknowns and a specific next validation step.

Bottom line: early implementation evidence exists for both shortlisted products, but independent adoption remains unverified. This is a baseline for future comparisons, not an exhaustive ecosystem ranking.