Deployments

HourGlass has no contract logic of its own. What it deploys are its own instances of MetaMask's audited caveat enforcers — unmodified bytecode at a different address — plus the DeleGatorModuleFactory that was missing on Ethereum mainnet.

Why redeploy something that already exists: the enforcer address is the emitter of the caveat events, so an HourGlass-owned instance makes a charge attributable to HourGlass by a single filter, with no central registry. The reasoning is in Analytics and the trust implications in Security.

What "unmodified" means here

Each address below was produced by CREATE2 from the salt bytes32("OURGLASS") and the compiled artifact of the corresponding @metamask/delegation-framework contract. The salt and the creation bytecode fully determine the address, so anyone can recompute it and confirm nothing else was deployed there.

The salt reads OURGLASS, not HOURGLASS: it predates the rename and is baked into every address above. Changing it would produce an entirely different address set, so it stays as deployed. Use OURGLASS when recomputing.

All of them carry verified source on Etherscan (solc 0.8.23, optimizer enabled at 200 runs, EVM version london). Most were accepted as already-verified on submission — Etherscan matched the bytecode against MetaMask's own verified instances, which is exactly the property being claimed.

Because the address depends only on the salt and the bytecode, the same contract has the same address on every chain. The tables below therefore apply to both Ethereum mainnet and Base — a given enforcer is at one address, everywhere.

Ethereum mainnet (chain 1) and Base (chain 8453)

Deployer: 0x2FF0363132d0dc5feb090790C46B77EF1ce96aa2. On Ethereum mainnet, the three enforcers HourGlass delegations reference were deployed 2026-06-25 and the rest of the suite on 2026-07-25. On Base, all 37 were deployed 2026-07-25.

Source is verified on Etherscan for mainnet and on Basescan for Base.

Infrastructure

The DelegationManager is MetaMask's canonical deterministic deployment, identical everywhere. The factory is not deterministic, so it differs per chain. Both factories carry verified source; their code lives in the delegator-safe-module project, not in the Delegation Framework.

Enforcers referenced by HourGlass delegations

These three are the ones the app actually routes through — a subscription cap, its optional end date, and the payroll stream.

Rest of the suite

Deployed so that any future delegation shape can reference an HourGlass-owned enforcer without a new deployment round. They are not wired into the app today.

Two of them take constructor arguments: LogicalOrWrapperEnforcer receives the DelegationManager, and NativeTokenPaymentEnforcer receives the DelegationManager plus the HourGlass ArgsEqualityCheckEnforcer above — not the canonical one. Both are part of the verified source on Etherscan.

Other chains

Base Sepolia and Ethereum Sepolia use MetaMask's canonical enforcer deployments. No HourGlass-owned instance exists there, so charges on those chains are not attributable by emitter address.

Verifying this yourself

The addresses in this page are the ones the app uses, held in src/config/addresses.ts under chains 1 and 8453. To confirm an address holds what it claims, compare the on-chain bytecode against the corresponding artifact from @metamask/delegation-framework — the deployed runtime code is byte-identical to the audited release.