Verify
What this build can actually do. The tables are derived rather than written: the chains come from the API’s registry, and the operations from the frozen API contract, where an operation that still declares a 501 is one nothing has built yet.
Chains
| Chain | Id | Environment | Enabled | Deployment |
|---|---|---|---|---|
| Robinhood Chain | 4663 | mainnet | Disabled | UNVERIFIED |
| Robinhood Chain Testnet | 46630 | testnet | Disabled in the registry; see below | UNVERIFIED source not yet published |
A chain begins disabled and unverified and can only be enabled by an explicit, recorded authorisation. Nothing about this interface can change that.
Robinhood Chain Testnet shows as Disabled and UNVERIFIED because the chain registry is left as it is until testnet-1's source is published, so it records no testnet-1 contract. This site does not take testnet-1's addresses from the registry: it takes them from testnet-1's recorded deployment. Before your wallet is asked to send anything, it checks the code at the factory, the price oracle and the WETH (test) contract against that record, and sends nothing if they differ; a launch's token and curve are the ones the factory itself names.
API operations (6 of 11 built)
| Operation | Endpoint | Status |
|---|---|---|
| listChainsV1 | GET /v1/chains | Built |
| listLaunchesV1 | GET /v1/launches | Built |
| getLaunchV1 | GET /v1/launches/{chainId}/{tokenAddress} | Built |
| listLaunchTradesV1 | GET /v1/launches/{chainId}/{tokenAddress}/trades | Built |
| listLaunchCandlesV1 | GET /v1/launches/{chainId}/{tokenAddress}/candles | Built |
| createQuoteV1 | POST /v1/quotes | Built |
| prepareCreateIntentV1 | POST /v1/intents/create | Not built |
| prepareTradeIntentV1 | POST /v1/intents/trade | Not built |
| requestCreateSponsorshipV1 | POST /v1/sponsorships/create | Not built |
| getOperationV1 | GET /v1/operations/{operationId} | Not built |
| getRankingV1 | GET /v1/rankings/{view} | Not built |
An operation that is not built answers 501 with a problem document naming what it is waiting for — not a 404, which on a declared path would be a false statement that the thing does not exist.
What this testnet build does and does not do
- Trading. Buying and selling work on Robinhood Chain Testnet only, with test ETH, against testnet-1's contracts: the page builds each transaction and your wallet signs it. Creating works the same way while the testnet price is fresh; when FairHatch's price keeper does not run, the factory refuses every create, and /create says so. 5 of the 11 API operations are not built, including both transaction intents.
- Wallets. A browser-extension wallet connects to the page; no third-party wallet service is in the path, and this site holds no key. Before anything is sent, the page refuses a wallet on any other chain and offers the switch to Robinhood Chain Testnet, and checks the code at testnet-1's factory, price oracle and WETH (test) contract against testnet-1's deployment record.
- Risk and ranking. Not built. A launch with no assessment is shown as unassessed rather than as safe.
- Contracts. testnet-1's contracts are deployed on Robinhood Chain Testnet (chain 46630) and nowhere else. Their source is not yet published, so the chain registry does not record them, and the chain shows as UNVERIFIED.
FairHatch