Upstream Uniswap v4 Deployments
This page mirrors selected upstream Uniswap v4 infrastructure addresses that a FewToken integration may use. Ring did not deploy the addresses in these tables. Treat them as external dependencies; inclusion does not mean that Ring supports the network or controls the contract.
The canonical source of current addresses and versions is the
Uniswap v4 deployment registry and its
deployments.json feed. Uniswap also publishes chain-specific
deployment records with transaction and source-version
references. Confirm the chain, contract version, deployer record, verified bytecode, and control model before
integrating. The tables below are a convenience snapshot, not a Ring deployment registry or a guarantee that an
upstream address is still the preferred version.
Contract-name links open the current upstream source for navigation; they do not prove that the current branch matches the deployed bytecode. Use the chain-specific deployment record and verified explorer source for exact provenance.
| Component | Upstream source |
|---|---|
| PoolManager and v4 core test contracts | Uniswap/v4-core |
| PositionDescriptor, PositionManager, V4Quoter, and StateView | Uniswap/v4-periphery |
| Universal Router | Uniswap/universal-router |
| Permit2 | Uniswap/permit2 |
The unqualified Universal Router rows reproduce Uniswap's upstream label; they do not mean "latest." Uniswap
publishes more than one Universal Router version on some networks, so select an explicit upstream version before use.
For Ring Swap (v2) swaps through the current Ring Interface, use the Ring Universal Router addresses on
Ring Swap Deployments.
FewToken pools and hooks
Ring-published Few Protocol hook contracts are documented separately because they are application-specific integrations built on top of this external v4 infrastructure.
For deployment details, integration notes, published mainnet hook addresses, PoolKeys, and machine-readable files, see FewToken Liquidity and Aggregator Integration.