Active

Protocol Fee Expansion: Vote 3


ID 96

ID 96

Proposed on: May 22nd, 2026

Proposed on: May 22nd, 2026

Votes

Actions

Type

Address

Details

Custom

0xf5F4...615a

sendMessage(..)

Custom

Account

0xf5F4...615a

Method

sendMessage(..)

Custom

0xf5F4...615a

sendMessage(..)

Custom

Account

0xf5F4...615a

Method

sendMessage(..)

Custom

0xfe5e...89a2

sendMessageToChild(..)

Custom

Account

0xfe5e...89a2

Method

sendMessageToChild(..)

Proposal

Proposal Spec

If this proposal passes, it will execute three actions, each of which has multiple inner calls.

On BNB Chain and Polygon, the actions will execute the following transactions:

/// Set the recipient of V2 protocol fees to the TokenJar
V2_FACTORY.setFeeTo(address(tokenJar));

/// Set the owner of the V3 Factory to the V3OpenFeeAdapter
V3_FACTORY.setOwner(address(v3OpenFeeAdapter));

On Celo, the action will execute the following transactions:

/// Set the recipient of V2 protocol fees to the TokenJar
V2_FACTORY.setFeeTo(address(tokenJar));

/// Transfer feeToSetter role from Wormhole to the CrossChainAccount
V2_FACTORY.setFeeToSetter(address(crossChainAccount));

/// Set the owner of the V3 Factory to the V3OpenFeeAdapter
V3_FACTORY.setOwner(address(v3OpenFeeAdapter));

/// Transfer ownership of the V4 PoolManager to the CrossChainAccount
POOL_MANAGER.transferOwnership(address(crossChainAccount));

Relevant Addresses

Celo

BNB Chain

ContractNetworkAddress
TokenJarBNB Chain0xc6Ae6373CEcc9e595A6C8b9fe581925a8c84f70A
V3OpenFeeAdapterBNB Chain0x3F07F08b45912dCd6691C5B9412975D5113B2910
UniswapV3FactoryBNB Chain0xdB1d10011AD0Ff90774D0C6Bb92e5C5c8b4461F7
UniswapV2FactoryBNB Chain0x8909Dc15e40173Ff4699343b6eB8132c65e18eC6
UniswapWormholeMessageReceiverBNB Chain0x341c1511141022cf8eE20824Ae0fFA3491F1302b
Wormhole SenderEthereum0xf5F4496219F31CDCBa6130B5402873624585615a

Polygon

Proposal

This proposal continues the protocol fee rollout, following proposals #93, #94, and #95. It uses the expedited governance process approved in UNIfication, where fee parameter update proposals can bypass the RFC stage and go directly to a five-day Snapshot followed by an onchain vote.

Since protocol fees went live on Ethereum mainnet in late December, the rollout has extended to 73 additional chains (Arbitrum, Base, OP Mainnet, Soneium, X Layer, Worldchain, and Zora). The burn system is working as designed, with fees accumulating in TokenJars across chains. From there, searchers claim them in exchange for burning UNI by bridging it back to mainnet and sending it to the burn address.

This proposal:

  • Extends the infrastructure for collecting and burning protocol fees to BNB Chain and Polygon
  • Enables v2 and v3 protocol fees on these chains
  • Completes Celo's fee activation through a corrected cross-chain governance path, which was approved in a previous proposal but did not execute due to a configuration error

Implementation Details

Fees on each chain will be routed to the TokenJar on that respective chain. UNI burned on these chains is bridged back to Ethereum mainnet and sent to the burn address.

Celo uses the same architecture as other OP-stack chains. On BNB and Polygon, we make use of Wormhole’s Native Token Transfer (NTT) mechanism for multichain token management. Details on our implementation can be found here.

Protocol fee levels are the same on all other chains where fees are live, see breakdown here.

Votes
Status