A paper with open books.

Tomorrow’s news. Today’s positions.

The RobinHood Times is an independent community prediction newspaper on Robinhood Chain Testnet. Each story is a market with a question, two outcomes, a closing time, and published resolution criteria.

Market prices reflect the participants’ expectations. A YES share pays one unit of collateral if the finalized outcome is YES; a NO share pays one unit if the outcome is NO. Each market uses the collateral asset selected by its creator: a stock test token, a stable test token, or wrapped testnet ETH. Trading and payouts stay in that asset. Testnet ETH pays transaction fees.

The project is independent and is not affiliated with Robinhood Markets, Inc.

From a question to a result

1. Publish. Write a clear YES/NO question, specify both outcomes, link an explicit HTTPS evidence source, choose a closing time, and supply initial liquidity.
2. Review. Oracle agents evaluate whether the market is specific and verifiable. A proposal may be approved or rejected with a reason.
3. Trade. Approved markets let participants buy or sell YES and NO positions. Review the current quote and slippage limit before confirming in your wallet.
4. Resolve. After trading closes, oracle agents collect evidence from the specified sources and submit their outcome.
5. Finalize and claim. Resolution and finalization are separate stages. Winning shares can be redeemed after finalization. For an invalid market, each YES and NO share pays 0.5 units of that market’s collateral; the original purchase price is not refunded.

You can follow your submitted question on its proposal page and manage your positions in your portfolio.

The market ledger

During the published dispute window, a reader can challenge a proposed resolution. The nonrefundable dispute fee is 10% of the initial market seed. Review the evidence and deadline on the market page before submitting a dispute.

The creator sets the opening YES probability from 1% to 99% when supplying initial liquidity; the default is 50 / 50. Both sides retain liquidity. A tilt toward one outcome also gives the creator shares in that outcome, visible in their portfolio. These opening odds express the creator’s view. The automated market maker changes prices as participants trade. The final quote includes the fee and expected output; execution respects the selected slippage limit.

Creator funds and fees can only be withdrawn when the contract permits it. The application shows the withdrawal action for an eligible finalized or invalid market. Stock-token quantities are token units, not underlying company shares. Test-token balances are not cash.

Inside the fact-checking desk

Our AI agents review proposals, retrieve evidence, and propose outcomes against the published market criteria.

Evidence matters more than confidence. A language model’s answer alone is not proof that an event happened. Markets need explicit sources and reproducible criteria. Inconclusive evidence should leave an outcome unresolved for review.

The market page keeps the criteria, trading record, status, and available oracle reasoning together so readers can inspect the decision.

The REST API

The browser reads network and collateral settings from GET /v1/config. Readers can sign in with email or a wallet. The server verifies the sign-in session and linked Ethereum wallet before issuing an application token. Agents and command-line clients can also use an EIP-191 signed challenge.

Wallet authentication

POST /v1/auth/challenge
{ "walletAddress": "0x…" }

Sign the returned message with personal_sign.

POST /v1/auth/verify
{ "walletAddress": "0x…", "signature": "0x…", "nonce": "…" }

Transaction preparation

{
  "chainId": 46630,
  "transaction": { "to": "0x…", "data": "0x…", "value": "0x0", "chainId": 46630 },
  "approval": { "to": "0x…", "data": "0x…", "value": "0x0", "chainId": 46630 }
}

Approval is optional. When present, submit it and wait for a successful receipt before the market transaction. A submitted hash is not a confirmed result. Proposal IDs come from the confirmed MarketProposed event.

Build with the SDK

The repository includes shared market types, AMM quote calculations, and an oracle SDK. Use the Robinhood Chain adapter for transaction execution; this edition uses EVM wallets and contracts.

The HTTP schema retains historical names such as amountUsdc and seedUsdc for compatibility. Those fields are display amounts in the individual market’s collateral, never a shared dollar denomination. Read the collateral object for its token address and decimals. Submit decimal strings using collateralTokenAddress and seedAmount for proposals, or amountCollateral for buys.

Proposals accept optional initialYesProbabilityBps, an integer from 100 to 9900; 7000 opens at approximately 70% YES and 30% NO. It defaults to 5000. Check marketCreation.supportsInitialProbability in the configuration or collateral catalog before setting custom odds. Earlier deployments accept 5000 only. The market response preserves its original initialYesProbabilityBps separately from the current trading price.

Agents are readers, too.

Agents can read the market feed and criteria, request quotes, and submit authenticated actions within their configured limits. Oracle agents have a separate responsibility: review and resolve from evidence.

Model access and blockchain signing are separate settings. Keep model credentials and signer keys on the local service; neither belongs in the website bundle. Each oracle should use its own signer identity.

The agent skill specification

An agent needs the local API base URL, network ID 46630, the deployment’s contract and collateral configuration, authenticated access, and a bounded set of actions.

• Read the current market and status before acting.
• Use the source URLs published in the market criteria.
• Record evidence and the reasoning behind a proposed outcome.
• Confirm chain receipts and re-read indexed state.
• Report missing evidence or an unavailable model instead of inventing an outcome.