Reference

Contracts

Every Hoodium contract in production, what it may do, and what it cannot. Each address below was read back from the chain before it was written here.

Key every lookup by chain id. Two Hoodium deployments share a byte-identical address on different chains: same deployer wallet, same nonce, different chain, different contract. An address alone is not an identity here.

BNB Chain chain id 56

ContractAddressWhat it can do
HoodiumAutomationPancakeSwap v3 0x75c4fc0A62B2AF11e57b89C9CDc689B3cb5aaEA0 Executes signed orders on positions that approved it. Proceeds go to the owner only.
HoodiumAutomationUniswap v3 0xFD0af42bD5e24d106dF6a7F91D095790026c40b4 The same contract, bound to the other venue’s position manager.
HoodiumClaimRouter 0xF6Ac754b840dc9Ceb2B708aFa48b8f7EAA5B2c68 Collects fees across both venues in one transaction, for msg.sender only. No governance, no pause, no fee switch.
HoodiumZapRouter 0xc2Db5E387e40C6d59529e4c446dFa0c95F57117C Builds a zap’s swap and mint together, through allowlisted venue routers.

Robinhood Chain chain id 4663

ContractAddressWhat it can do
HoodiumAutomationV4Uniswap v4 0x6D441Bdd9722F39b5cF792E1f198ed639D47b7e7 Compound, harvest, exit and rebalance on v4 positions. One instance for the chain: v4 has a single position manager fronting every pool.
HoodiumClaimRouter 0xe3adFA9e250A4cac842f6e848d4EC968760dBa48 Same contract as BNB’s, byte for byte. Spans the chain’s v3 and v4 managers.
Universal RouterHoodium’s own deployment 0x40d6bdac60c0810fC3ed30a988A4c3ac890fdd43 The canonical router for v4 swaps on this chain. Ownerless, holds nothing.

Launchpad

ContractAddressWhat it can do
HoodiumFactory0xA07329b233B2c7437BfcB6ed12a99AC36d69b05bMints a token and its curve. The one factory the launchpad indexes.
GraduationManager0xeD55Ff4C1a7366114aE60Dcfa3848A1E764F8426Creates the pool, mints the full-range position, credits mint dust to the creator.
LPLocker0xcBEbc60E34284A5A460841e20E67d312E80B3A47Holds every graduated position. No withdrawal path exists. It can collect fees and nothing else.
FeeVault0xE453d99813D0F6837Cf94b26182576179F0a5a8dReceives the protocol share of curve fees.

External contracts Hoodium points at

WhatChainAddress
PancakeSwap v3 position managerBNB0x46A15B0b27311cedF172AB29E4f4766fbE7F4364
Uniswap v3 position managerBNB0x7b8A01B39D58278b5DE7e48c8449c9f4F5170613
Uniswap v4 position managerRobinhood0x58daec3116aae6D93017bAAea7749052E8a04fA7
Uniswap v3 position managerRobinhood0x73991a25C818Bf1f1128dEAaB1492D45638DE0D3
USDGRobinhood0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168

Roles

RoleAddressPowers
Governance / treasury0x0A9c1C027b84812a4ea4dBd56aCb790c1C78Bb69Sets the executor, the allowlisted swap router and the fee within its coded cap; can pause relaying; receives platform fees. Cannot touch a position.
Executor (relayer)0x25Cc13a19c05dCe8D18Af0117617BC017F87b575Submits orders that owners signed, within the limits in those signatures. Nothing else. Its key lives on a server; governance’s does not.

Superseded deployments

Automation contracts have been redeployed several times. Orders signed against a previous instance die with its EIP-712 domain and are refused by both the relayer and the contract. That is a replay-safety property, and the reason owners re-sign after a redeploy. If you are auditing a historical transaction, note that these addresses were real and are no longer pointed at by anything: