The following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.

We voted FOR

Before voting, we asked our Research Team to independently verify the implementation, deployed contracts, and expected governance payloads associated with this proposal.

Our Research Team reviewed prop-4 in the Uniswap protocol-fees repository PR #130 and pinned the review to commit 83df8d7f. They rebuilt the commit and compared the deployed runtime bytecode on Celo, BNB, and Polygon against the build artifacts. All 10 relevant contracts matched after accounting for compiler metadata and immutable slots, and the immutable values read on-chain matched the expected values from Constants.sol.

The team also reconstructed the three proposal action payloads and produced the expected keccak256(datas[i]) hashes that should match once the on-chain proposal is submitted:

• Celo: 0xda4f141e0d1d27bfc513573f5a8e8e6fefedad7b6769d6f5a037cc0fd706424d
• BNB: 0x12a4d5c2bf9d982394d1716a301919870b2d000ea866216c0fd83082ac617e92
• Polygon: 0x1bee6e3efc6611d85f0810c271daff29a6f9b9a38466993860138a699166b34f

Based on the continuity with the previously approved framework, the unchanged fee structure, and the independent verification performed by our Research Team, we are comfortable supporting this proposal.

We also believe the protocol would benefit from a more comprehensive post-UNIfication report covering operational and economic metrics across deployed chains. As the fee framework continues to expand, providing delegates with clearer visibility into protocol revenue, burn activity, liquidity impact, and cross-chain operational performance would improve governance oversight and help inform future expansion proposals.

Voted FOR this proposal to continue the protocol fee rollout by expanding fee collection and UNI burn infrastructure to Polygon and BNB Chain, while completing Celo's activation through the corrected cross-chain governance path.

This is a logical continuation of UNIfication and the prior protocol fee expansion votes. The burn mechanism is live and working: fees accumulate in TokenJars across chains, searchers call release(), UNI is burned, and TokenJar assets are distributed. Since the first release on Dec. 29, 2025, the system has already produced meaningful burn activity across Ethereum, Base, Arbitrum, Unichain, and OP Mainnet.

For this vote, I also created an updated graphic to make the mechanism easier to understand. The first graphic explains the original protocol fee collection flow and first UNI burn. The new graphic summarizes verified burn counts from Dec. 29, 2025 through May 20, 2026, showing how the Firepit/Releaser system has continued operating across active chains.

Expanding to Polygon and BNB Chain makes sense given Uniswap's multi-chain footprint, while Celo should be completed because governance already approved its inclusion and the prior execution issue was a configuration problem rather than a policy rejection.

As more chains are added, delegates should continue monitoring cross-chain messaging complexity, burn activity, and protocol revenue by chain. But based on the continuity with the existing fee framework, unchanged fee levels, and the fact that the burn system is already operating as designed, Axia supports this proposal.

First Burn

Total Burns

See more here: https://rikagoldberg.xyz/work-samples

The following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.

We voted FOR

Before voting, we asked our Research Team to independently verify the implementation, deployed contracts, and expected governance payloads associated with this proposal.

Our Research Team reviewed prop-4 in the Uniswap protocol-fees repository PR #130 and pinned the review to commit 83df8d7f. They rebuilt the commit and compared the deployed runtime bytecode on Celo, BNB, and Polygon against the build artifacts. All 10 relevant contracts matched after accounting for compiler metadata and immutable slots, and the immutable values read on-chain matched the expected values from Constants.sol.

The team also reconstructed the three proposal action payloads and produced the expected keccak256(datas[i]) hashes that should match once the on-chain proposal is submitted:

• Celo: 0xda4f141e0d1d27bfc513573f5a8e8e6fefedad7b6769d6f5a037cc0fd706424d
• BNB: 0x12a4d5c2bf9d982394d1716a301919870b2d000ea866216c0fd83082ac617e92
• Polygon: 0x1bee6e3efc6611d85f0810c271daff29a6f9b9a38466993860138a699166b34f

Based on the continuity with the previously approved framework, the unchanged fee structure, and the independent verification performed by our Research Team, we are comfortable supporting this proposal.

We also believe the protocol would benefit from a more comprehensive post-UNIfication report covering operational and economic metrics across deployed chains. As the fee framework continues to expand, providing delegates with clearer visibility into protocol revenue, burn activity, liquidity impact, and cross-chain operational performance would improve governance oversight and help inform future expansion proposals.

Voted FOR this proposal to continue the protocol fee rollout by expanding fee collection and UNI burn infrastructure to Polygon and BNB Chain, while completing Celo's activation through the corrected cross-chain governance path.

This is a logical continuation of UNIfication and the prior protocol fee expansion votes. The burn mechanism is live and working: fees accumulate in TokenJars across chains, searchers call release(), UNI is burned, and TokenJar assets are distributed. Since the first release on Dec. 29, 2025, the system has already produced meaningful burn activity across Ethereum, Base, Arbitrum, Unichain, and OP Mainnet.

For this vote, I also created an updated graphic to make the mechanism easier to understand. The first graphic explains the original protocol fee collection flow and first UNI burn. The new graphic summarizes verified burn counts from Dec. 29, 2025 through May 20, 2026, showing how the Firepit/Releaser system has continued operating across active chains.

Expanding to Polygon and BNB Chain makes sense given Uniswap's multi-chain footprint, while Celo should be completed because governance already approved its inclusion and the prior execution issue was a configuration problem rather than a policy rejection.

As more chains are added, delegates should continue monitoring cross-chain messaging complexity, burn activity, and protocol revenue by chain. But based on the continuity with the existing fee framework, unchanged fee levels, and the fact that the burn system is already operating as designed, Axia supports this proposal.

First Burn

Total Burns

See more here: https://rikagoldberg.xyz/work-samples