Uniswap V4: control-plane safety record
4 indexed control-plane surfaces for Uniswap V4, each pinned to a canonical Ethereum and Base block and compared with what the protocol documents. Contracts: 0x000000000004444c5dc75cB358380D2e3dE08A90, 0x498581fF718922c3f8e6A244956aF099B2652b2b, 0x89A5D5bF00a27D55c02951E49078a5C5771051dB.
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Not determined · Upgrade path not in the published records
- Timelock floor
- Strong · 2d minimum enforced delay across control surfacesEvidence: uniswap-v4-poolmanager-owner-timelock-s24: observed_delay_seconds = 172800
- Signer quorum
- Not determined · No signer quorum in the published records
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Strong · Chain matches or is stronger than the documentation
Each slice is derived only from the pinned records on this page and their controller facts (/api/v1/scorecards.json). A hollow slice is not determined by the published evidence (never a guess); docs-vs-chain parity is uncompared for RPC-observed protocols. How to read it.
Check it live (free)
The pre-flight API re-reads the controller, proxy and capabilities of one contract at the latest block. No key, no wallet. The score rates that single contract, not the whole protocol.
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0x000000000004444c5dc75cB358380D2e3dE08A90"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x000000000004444c5dc75cB358380D2e3dE08A90"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x000000000004444c5dc75cB358380D2e3dE08A90"})Owner: the 2-day governance Timelock run by GovernorBravo
Observed onchain. PoolManager 0x000000000004444c5dc75cB358380D2e3dE08A90 (Sourcify match): owner() = Timelock 0x1a9C8182C09F50C8318d769245beA52c32BE35BC: delay() = 172800s (2 days) = MINIMUM_DELAY(), admin() = GovernorBravoDelegator 0x408ED6354d4973f66138C91495F2f2FCbd8724C3.
Documented. developers.uniswap.org (v4 deployments, governance reference): 'Ethereum: 1 Contract Address PoolManager 0x000000000004444c5dc75cB358380D2e3dE08A90' / 'The contracts below are actively deployed on Ethereum mainnet.' / 'Timelock 0x1a9C8182C09F50C8318d769245beA52c32BE35BC' / 'Uniswap Governance has specific controls under its domain, including: Spend funds from the treasury Set and activate the protocol fee'
cast call 0x000000000004444c5dc75cB358380D2e3dE08A90 \ "owner()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
Base pools: fees routed to the listed Base V4FeeAdapter (chain 8453)
Observed onchain. PoolManager 0x498581fF718922c3f8e6A244956aF099B2652b2b (Base, block #58534152): protocolFeeController() = V4FeeAdapter 0xc53DD825dedBE7814562528A1A30e8e5BCbB4b55 (POOL_MANAGER() = this PoolManager, TOKEN_JAR() = 0x9bD25e67bF390437C8fAF480AC735a27BcF6168c); owner() of the PoolManager and the adapter = 0x31FAfd4889FA1269F7a13A66eE0fB458f27D72A9, whose stored L1 owner is the Ethereum Timelock 0x1a9C8182C09F50C8318d769245beA52c32BE35BC.
Documented. developers.uniswap.org (Base fee contracts): 'Base: 8453 Contract Address Deployer 0x076f84717f3601B8Cd177bb84b217A2679B38b7d TokenJar 0x9bD25e67bF390437C8fAF480AC735a27BcF6168c Releaser (OptimismBridgedResourceFirepit) 0xFf77c0ED0B6b13A20446969107E5867abc46f53a V3OpenFeeAdapter 0xaBEA76658b205696d49B5F91b2a03536cB8A3bE1 V4FeeAdapter 0xc53DD825dedBE7814562528A1A30e8e5BCbB4b55' / 'Base: 8453 Contract Address PoolManager 0x498581ff718922c3f8e6a244956af099b2652b2b' / 'Governance can update which Releaser a TokenJar uses or adjust configuration on Fee Adapters, but the core contracts themselves are immutable.'
cast call 0x498581fF718922c3f8e6A244956aF099B2652b2b \ "protocolFeeController()" \ --block 58534152 --rpc-url "$BASE_RPC_URL" cast block 58534152 --field hash --rpc-url "$BASE_RPC_URL" # expect 0x7b884f4d029427b5d15f71c50b128bd69ac7c6da6962ced946ca87b0b4e6e843
Ethereum pools: fees routed to the listed V4FeeAdapter
Observed onchain. PoolManager 0x000000000004444c5dc75cB358380D2e3dE08A90: protocolFeeController() = V4FeeAdapter 0x89A5D5bF00a27D55c02951E49078a5C5771051dB (Sourcify exact match): POOL_MANAGER() = this PoolManager, TOKEN_JAR() = 0xf38521f130fcCF29dB1961597bc5d2B60F995f85, policy() = 0x1cd822b70a0591420F65E94b9B3A0D0b0fB3a314.
Documented. developers.uniswap.org (fee adapter list): 'V4FeeAdapter 0x89A5D5bF00a27D55c02951E49078a5C5771051dB' / 'Ethereum: 1 Contract Address PoolManager 0x000000000004444c5dc75cB358380D2e3dE08A90' / 'Each protocol component that generates fees (v2, v3, v4, UniswapX, Unichain, and others) routes those fees through an associated Fee Adapter contract.'
cast call 0x000000000004444c5dc75cB358380D2e3dE08A90 \ "protocolFeeController()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
Who sets v4 protocol fees: the Timelock as owner and feeSetter
Observed onchain. V4FeeAdapter 0x89A5D5bF00a27D55c02951E49078a5C5771051dB: feeSetter() = owner() = Timelock 0x1a9C8182C09F50C8318d769245beA52c32BE35BC; its fee policy 0x1cd822b70a0591420F65E94b9B3A0D0b0fB3a314 has owner() = feeSetter() = the Timelock.
Documented. developers.uniswap.org (protocol fee overview): 'Governance can update which Releaser a TokenJar uses or adjust configuration on Fee Adapters, but the core contracts themselves are immutable.' / 'V4FeeAdapter 0x89A5D5bF00a27D55c02951E49078a5C5771051dB' / 'Timelock 0x1a9C8182C09F50C8318d769245beA52c32BE35BC'
cast call 0x89A5D5bF00a27D55c02951E49078a5C5771051dB \ "feeSetter()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
Embed Live Control-Plane Badge
Show Uniswap V4's Base-EAS-attested Aligned control-plane status in a README, docs page or forum post. The badge links back to this record.
[](https://pacta.wtf/protocols/uniswap-v4/)
<a href="https://pacta.wtf/protocols/uniswap-v4/"><img src="https://pacta.wtf/badges/uniswap-v4.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/uniswap-v4.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/uniswap-v4.svg (5-minute cache).
Operating Uniswap V4? Add Continuous Monitoring
Continuous Monitoring ($1,500 USDC / month) re-checks your control plane after governance proposals, signer rotations and timelock upgrades, and refreshes the dossier and attestation. It does not buy a status: the result can still be Delta whenever docs and chain diverge.