Reference

Contracts

Every address Sluice touches, on the chain this site is configured for.

Addresses

These are read from the address book this build was compiled against, so the list is whatever the running site actually uses rather than a copy of it. Each one links to the explorer.

ContractAddressWhat it does
Sluice0x4F290248…460BEfa7Holds the position, issues shares, compounds fees, settles withdrawals.
Implementation0x59210D49…7aC66795The code behind the proxy today. The governor key can replace it.
Governor0x65c0F179…B624F504Sets governed parameters and can replace the implementation. Cannot block a withdrawal.
WETH0x0Bd7D308…1EAcAD73Wrapped ETH. Pools hold this rather than native ETH.
Uniswap v3 factory0x1f7d7550…05FD2EfACanonical factory. Sluice checks a pool against it before registering one.
Uniswap v4 PoolManager0x8366a39C…43e40951The singleton every v4 pool lives inside.
Sluice hook (v4)0x8AAEe3e7…2CE69aE0Creates Uniswap v4 pools and is the sole liquidity provider in them. Prices each swap off realised volatility and compounds fees into the position inside the swap. Immutable — no upgrade path, no owner over the position.Deposits and withdrawals for its pools are available from the pool list. Deposits are native ETH only — the hook swaps half inside the pool.
Position builder (v3)0x503EA15c…126B1d5dMints a ladder of concentrated v3 positions in one transaction. The NFTs go straight to you — it holds nothing.
Position builder (v4)0x3379d4f1…28Cac3F7The same ladder against a v4 pool. Also mints straight to you, and also holds nothing afterwards.
Position builder (Ramses)0x89dd3fC3…0ef696AfThe same ladder against a Ramses V3 pool. Mints straight to you and holds nothing. A separate contract because Ramses keys its factory by tick spacing, not by fee.Each builder only accepts pools from its own venue. This one is for Ramses V3 pools; the v3 row above is for Uniswap V3.
Session-key router0x280F3e92…d73eb0BfThe only address an agent can move your shares through, and it can only ever hand them back to you. Immutable, ownerless, and it cannot withdraw.Approve this address and nothing else. Granting an agent’s own address instead hands it every share you hold, in every pool, permanently.

Checking it yourself

Source for the contracts is verified on the explorer, so you can read what is deployed rather than what is described. The read functions are public: total shares outstanding, the position’s liquidity, the deposit ceiling and the current fee split can all be called by anyone, from anywhere, without going through this site.

On Robinhood Chain mainnet, every Sluice contract is a full-match verification: the compiled bytecode agrees with the published source all the way through the trailing metadata hash, not merely up to it. The build settings are solc 0.8.26, the optimizer on at 200 runs, viaIR on, EVM version cancun — enough to rebuild the artifact from the repository and compare it yourself. The testnet deployment is a partial match instead: same logic, metadata not byte-identical.

The vault is behind a proxy, and the explorer resolves it: the implementation address is listed against the proxy, so the read and write functions you see there are the ones actually running. The implementation changes on an upgrade; the proxy address does not.

What verification does and does not tell you.

It proves the deployed bytecode came from the published source. It says nothing about whether that source is correct. There is no external audit of these contracts and none is planned.

If a number here ever disagrees with the chain, the chain is right. Every figure on this site is derived from a call you can make yourself.