Robinhood Chain Launchpad Contract Registry

Copy the complete 42-character address from the transaction preview. Compare it character for character with the current first-party source, then open the Blockscout address page and check deployed bytecode, proxy status, verified source and recent transactions. Confirm the network is chain ID 4663 before signing.

Factories deploy or coordinate launches, lockers or vaults hold positions, and routers forward swaps. Shared Uniswap contracts are not owned by each launchpad merely because the launchpad calls them. Proxy and implementation addresses must also remain distinct because an upgrade can change behavior without changing the proxy users call.

Nock's current client references Robinhood Chain's Uniswap v4 PoolManager, PositionManager, Quoter, Universal Router and Permit2. Uniswap's deployment registry independently maps those contracts to chain 4663. Nock deploys per-launch tokens and pools; the checked implementation does not establish a shared Nock token factory, so this registry does not invent one.

The historical DYOR Fun documentation described its Factory and Fee Locker as UUPS proxies and its token implementation through an upgradeable beacon, while describing the LP Vault as immutable and outside that authority. That documentation domain no longer resolved at the July 16 recheck, so current terms are unavailable; the factory proxy remains inspectable on Blockscout. LeaveHood publishes proxy addresses whose EIP-1967 implementation slots resolved to separate implementation contracts at the last check. Those distinctions matter more than a generic verified badge.

A locker with deployed bytecode is not automatically a no-withdrawal locker. The relevant source code, proxy admin, implementation and callable functions must support that conclusion. This page reports precise roles and evidence status rather than turning vendor terminology into an independent security guarantee.

RobinPad documentation published Factory 0x5C1C1dE6950F9DCfE31BE99D457Fa7732B2Ce93B, LPLocker 0xf26b957a2fEde96137f773daD10139443AF66BEc and FeeRouter 0xb0528AD7b14F28F729c66c90214484b8AFAf7BB0. Direct eth_getCode checks returned 0x for all three at the last check, so they are excluded from the current-contract table.

The same documentation labeled 0x8bcEaA40B9AcdfAedF85AdF4FF01F5Ad6517937f as the canonical v3 factory, while current Uniswap material identifies it as the Robinhood Chain v2 factory and identifies 0x1f7d7550B1b028f7571E69A784071F0205FD2EfA as v3. Verify current code and documentation rather than resolving that conflict by assumption.

The Greenwood's public launch form embeds factory 0x81de990be508b95540b3c519417e7c0755b42977 and a client-side launch topic. A July 17 check found 17,297 bytes of runtime code at that address and nine matching logs, with the latest at block 9,269,937 on July 14. This establishes a deployed contract and matching event activity, not verified source, exclusive platform ownership, audit status or a permanent-lock implementation.

The same site mixes live labels with launching-soon language. Preserve that operating-status conflict and verify the full transaction target before signing; a website form, bytecode and event count do not by themselves prove that the current interface, fee path and LP custody match the vendor description.

Primehod publishes open-source factory code and factory 0x57EfC7cE5250C96B0b0E7C554c9d9743A18b794f. A July 17 RPC check found 20,616 bytes of runtime code and five logs matching the source-published TokenLaunched(address,address,address,address,uint256) event. Its public board displayed six tokens, so the board total is not relabeled as a current-factory event count. The repository's internal security review is not an independent third-party audit.

Leavehood publishes factory proxy 0x2C81Cd8acF4886F4abAd332216b4444aE927FDb7, core proxy 0x5090C9cd2228b0C4e6a83Ee44ab77Ce2e4cd89E3 and lock 0x8F1C12050BB6aAA89f8fB5ddcA77c3EdF022CBF4. Their July 17 EIP-1967 implementation slots resolved to deployed code at 0xC7C85dF578397d7982DCd36b347deeA48DBf1050 and 0x7ddF651feB2632D686619FF35b4cC81105924aEE. Leavehood's commissioned AI-assisted review describes the two proxies as owner-controlled UUPS contracts and the separate lock as non-upgradeable; it is a self-published point-in-time review, not an independent professional audit.

Recurve's current documentation publishes contract 0xd41a03a01369a734a5e22c3d6484b4040ae9acfd, and the former pad.hoodscan.ai surface redirects to Recurve. A July 17 RPC check at block 11,992,762 found 18,303 bytes of runtime code at the published address. This supports a current brand and deployed-contract match; it does not independently prove the site's non-upgradeability, custody or fee-control descriptions.

HoodRich's live /api/config response publishes separate curve, instant, flywheel and vendor-labeled “Ponzi Launch” factories plus instant and branded-mode lock addresses. The same July 17 check found deployed code at all six named contracts. Its current token API returned records attributed to the instant and branded-mode factories. These are configuration, bytecode and first-party API observations, not a code audit or proof that every advertised lock restriction and fee path is enforced.

Merry Men's current first-party client publishes factory 0xfa4B952c15BC9d418ae4f552F7Fc76b4470596fE, LP locker 0xd404C0fF8dE11841a4ff9CC4382eA5F6e4010751, swap router 0x19204230c4077F437a757934d73175F72FE9F476 and fee viewer 0xada9aE7e8710A4490B299151915b2056D9e0571b. All four returned deployed code at the check block. No raw log total is relabeled as a launch count without a decoded, qualifying event set.

• Comparing shortened addresses instead of all 40 hexadecimal characters.
• Treating a shared Uniswap router as a launchpad-owned factory.
• Checking an implementation while the wallet calls an upgradeable proxy.
• Assuming verified source means audited or safe.
• Copying a contract from a social reply, screenshot or search snippet.
• Using an address from another chain or a retired launchpad version.