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.

• 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.