Uniswap Proposes Expanding Protocol Fee Infrastructure to BNB Chain and Polygon

iconKuCoinFlash
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
Uniswap has proposed a protocol update to extend its fee collection and destruction infrastructure to BNB Chain and Polygon, while finalizing activation on Celo. The on-chain updates include setting TokenJar as the V2 protocol fee receiver on BNB Chain, Polygon, and Celo; assigning V3OpenFeeAdapter as the owner of the V3 Factory; and transferring key roles on Celo to CrossChainAccount. Fees will be aggregated into TokenJar, bridged to Ethereum, and sent to the burn address.

Odaily Planet Daily report: A Uniswap governance proposal seeks to extend the protocol fee collection and burning infrastructure to BNB Chain and Polygon, and complete the fee activation process on Celo that was previously unexecuted due to configuration errors.

The proposal includes setting TokenJar as the fee receiver for the V2 protocol on BNB Chain, Polygon, and Celo, and assigning V3OpenFeeAdapter as the owner of the V3 Factory on the respective chains. On Celo, the feeToSetter role and ownership of the V4 PoolManager will also be transferred to CrossChainAccount. The proposal states that fees from each chain will be aggregated into the corresponding TokenJar, after which UNI will be bridged cross-chain back to Ethereum Mainnet and sent to a burn address.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.