Contracts and addresses

Every address on this page is live on Robinhood Chain, chain id 4663. The Hookr addresses hold the deployed release; the upstream addresses are Uniswap's own deployments.

Every Hookr address, id and share below is rendered from the deployment record the app ships, the same file published as deployments/robinhood-4663.v2.json in the public contracts repository. None of them is typed into this page. The source commit behind the deployed code is 8db7fc940938f811f508ba9cb0c8f2d3f24c9a25.

Explorer: Robinhood Blockscout. Machine-readable ABIs: ABIs.

Mainnet Deployments

Robinhood Chain: 4663

The contracts, in deployment order.

The root hook's address is mined by CREATE2 so its low fourteen bits equal 0x28cc. See Hook permissions.

Linked Libraries

HookrMarketCoordinatorV5, HookrSwapAccountingKernelV3 and HookrModularHookV6 link libraries. Each is compiled without them: the addresses below are written into the __$…$__ placeholders in the compiled bytecode, so the deployed code carries the metadata of a library-free compilation. Three of these libraries already stood on chain holding the same runtime code, apart from the immutable each one keeps for its own address, and are linked where they stand. HookrMarketCoordinatorTokenDeployerV3 holds different code at the address it could have been linked from, so it has one of its own.

The CREATE2 factory the root hook is mined through is HookrReleaseCreate2FactoryV1 at 0xBc54e888C1A5B71744B035DfeC5611B4DC69ccDe. Its authorizedDeployer() is the deployer address below, and only that address can deploy through it.

Upstream Dependencies

These are live and independently verified on chain 4663.

The Universal Router address on chain 4663 has two conflicting official sources. Uniswap's deployment registry gives 0x06afBA43fd06227fA663b0dAeCF536F6eaA6BF99; the rendered deployments page gives 0x8876789976dEcBfCbBbe364623C63652db8C0904. The fork evidence behind this documentation used 0x8876789976dEcBfCbBbe364623C63652db8C0904, and swaps settled correctly through it.

Both addresses hold a deployed router, both are 24,546 bytes, and both report the same poolManager(). Their runtime code hashes differ, so they are not the same build:

Nothing in the Hookr graph pins either one: the hook accepts any caller, and a pool's trusted-router slot holds HookrKernelRouterV3, not a Universal Router. The choice belongs to whoever routes through this hook. Pin the address you tested against, record its runtime code hash alongside the evidence, and say which one you pinned. This documentation does not choose for you.

Tokens on Chain 4663

NFLX and AAPL are Robinhood tokenized stocks. Read RWA and ERC-20 quotes before pairing one.

Wiring, Read Back From the Chain

Every one-shot bind and every pinned address, as the chain reports them.

The coordinator, the registry, the catalog and the forwarder are all owned by the deployer. The forwarder's target is the same address today; rotating it is the one payout change that does not touch a pinned address. See Immutability and ownership.

Registry Identifiers

The values registerModule, registerIntegration, registerKernel and sealRootProfile returned, which an integrator reads back rather than recomputing.

The last three are hashes of fixed strings and read back off the contracts that hold them: the kernel family id is HookrKernelRouterV3.KERNEL_FAMILY_ID and HookrKernelQuoterV1.KERNEL_FAMILY_ID, both keccak256("HOOKR_SWAP_DELTA_V1"); the module key is HookrNativeMechanicsBlockV2.MODULE_KEY, keccak256("HOOKR_NATIVE_MECHANICS"); the root profile id is keccak256("HOOKR_LAUNCH_V2_MIN_ROOT_PROFILE"), the permanent identity of the sealed profile.

Verification

Every contract above holds verified source on Blockscout as a full match, and Sourcify holds the same 16 addresses as exact matches. Verification records the build settings and the address-by-address comparison.