PGOV is submitting the proposal on GFX Labs' behalf because GFX no longer has sufficient voting power to submit.
GFX Labs proposes that the Uniswap DAO allocate funding to support the integration of Uniswap V4 on Ethereum in Oku, and to add support for Unichain on Oku. This initiative aims to enhance Uniswap's reach, encourage liquidity migration to V4, and solidify the protocol’s position as the leading decentralized exchange.
In 2022, GFX Labs was granted $1.6M from the Uniswap DAO to scale the Uniswap ecosystem and expand the protocol's presence across EVM chains. Today, Oku is live across 30+ chains, and we have expanded our services to offer best-in-class bridge and trade aggregation. With a dedicated interface for V3 pool analytics and a simplified LP management interface, Oku has served as a consistent and scalable growth channel for the wider Uniswap ecosystem.
We’ve deployed to a wide range of chains at our own expense – far exceeding the original scope of the grant – and have generated a high ROI by accelerating Uniswap adoption across new environments. Now, with the advent of Uniswap V4, it’s time to build the next generation of tooling for the next wave of liquidity.
Since the launch of Uniswap V4 in January 2025, we’ve seen a surge in interest from users, partners, and hook developers eager to experiment with the new protocol’s capabilities. As one of the most active contributors to the Uniswap ecosystem infrastructure, GFX Labs views this momentum as a timely opportunity to scale V4 usage, reduce friction for LP’ing, and host an environment for hook developers to showcase their innovative pool adaptations. As we have provided for V3, GFX Labs will develop a dedicated V4 analytics interface to support hooked pool discovery and performance tracking.
The Uniswap DAO’s ability to expand V4’s reach heavily depends on ecosystem builders and infrastructure. That is why supporting the flywheel between hook builders, liquidity migrators/providers, and traders is crucial. With V4’s flexibility also comes complexity. It is key that each stakeholder's user experience and needs are addressed and iterated upon so V4 can become the dominant DEX protocol. Oku will fill the gaps and support ecosystem players as a base layer user interface for developers, LPs, traders, and chains. EVM chains with V4 enabled will have separate interfaces to distinguish between hooked and vanilla pools.
Hook Devs: Hook developers thrive when LP’ing is made easy, unlocking exposure to their unique market architecture
LPs: Intuitive position management tools and highlighted yield farming opportunities for V4 pools
Traders: Option to include V4 “hooked” pools for unique trading strategies & best execution
DAO: Expand V4 footprint across all chains and highlight market opportunities for unique market structures
V4 Development Scope
For the one-time integration and build-out of V4 on Ethereum Mainnet into Oku, we are requesting a total of $250K. The Uniswap DAO could expect delivery within two months of the proposal passing. Post launch, Oku will continue to improve the V4 interface and iterate based on feedback.
Given our long-standing relationship with the DAO and our concurrent request for the initial V4 integration, GFX Labs will waive the standard integration fee for integrating Unichain with Oku. Recognizing the benefit of a synergistic V3/V4 offering, instead we are requesting $90k - $7.5k per month - to cover operational and maintenance related costs. This cost structure is representative of preferential pricing for the Uniswap DAO.
With a new emphasis on V4 infrastructure, Oku further aligns itself as a standard bearer for the Uniswap ecosystem, with a focus on expanding utility and interoperability across EVM environments. By funding this proposal, the DAO positions itself to scale V4 usage, promote novel onchain markets, and support unique market innovation from the ground up.
PGOV is submitting the proposal on GFX Labs' behalf because GFX no longer has sufficient voting power to submit.
GFX Labs proposes that the Uniswap DAO allocate funding to support the integration of Uniswap V4 on Ethereum in Oku, and to add support for Unichain on Oku. This initiative aims to enhance Uniswap's reach, encourage liquidity migration to V4, and solidify the protocol’s position as the leading decentralized exchange.
In 2022, GFX Labs was granted $1.6M from the Uniswap DAO to scale the Uniswap ecosystem and expand the protocol's presence across EVM chains. Today, Oku is live across 30+ chains, and we have expanded our services to offer best-in-class bridge and trade aggregation. With a dedicated interface for V3 pool analytics and a simplified LP management interface, Oku has served as a consistent and scalable growth channel for the wider Uniswap ecosystem.
We’ve deployed to a wide range of chains at our own expense – far exceeding the original scope of the grant – and have generated a high ROI by accelerating Uniswap adoption across new environments. Now, with the advent of Uniswap V4, it’s time to build the next generation of tooling for the next wave of liquidity.
Since the launch of Uniswap V4 in January 2025, we’ve seen a surge in interest from users, partners, and hook developers eager to experiment with the new protocol’s capabilities. As one of the most active contributors to the Uniswap ecosystem infrastructure, GFX Labs views this momentum as a timely opportunity to scale V4 usage, reduce friction for LP’ing, and host an environment for hook developers to showcase their innovative pool adaptations. As we have provided for V3, GFX Labs will develop a dedicated V4 analytics interface to support hooked pool discovery and performance tracking.
The Uniswap DAO’s ability to expand V4’s reach heavily depends on ecosystem builders and infrastructure. That is why supporting the flywheel between hook builders, liquidity migrators/providers, and traders is crucial. With V4’s flexibility also comes complexity. It is key that each stakeholder's user experience and needs are addressed and iterated upon so V4 can become the dominant DEX protocol. Oku will fill the gaps and support ecosystem players as a base layer user interface for developers, LPs, traders, and chains. EVM chains with V4 enabled will have separate interfaces to distinguish between hooked and vanilla pools.
Hook Devs: Hook developers thrive when LP’ing is made easy, unlocking exposure to their unique market architecture
LPs: Intuitive position management tools and highlighted yield farming opportunities for V4 pools
Traders: Option to include V4 “hooked” pools for unique trading strategies & best execution
DAO: Expand V4 footprint across all chains and highlight market opportunities for unique market structures
V4 Development Scope
For the one-time integration and build-out of V4 on Ethereum Mainnet into Oku, we are requesting a total of $250K. The Uniswap DAO could expect delivery within two months of the proposal passing. Post launch, Oku will continue to improve the V4 interface and iterate based on feedback.
Given our long-standing relationship with the DAO and our concurrent request for the initial V4 integration, GFX Labs will waive the standard integration fee for integrating Unichain with Oku. Recognizing the benefit of a synergistic V3/V4 offering, instead we are requesting $90k - $7.5k per month - to cover operational and maintenance related costs. This cost structure is representative of preferential pricing for the Uniswap DAO.
With a new emphasis on V4 infrastructure, Oku further aligns itself as a standard bearer for the Uniswap ecosystem, with a focus on expanding utility and interoperability across EVM environments. By funding this proposal, the DAO positions itself to scale V4 usage, promote novel onchain markets, and support unique market innovation from the ground up.
FranklinDAO voted against due to lack of accountability measures. We need quarterly public usage metrics, governance abstention on own proposals, and outcome-based deliverables focused on incremental activity. Open to reconsidering with proper transparency. Full reasoning here: https://gov.uniswap.org/t/scaling-v4-and-supporting-unichain/25484/51
FranklinDAO voted against due to lack of accountability measures. We need quarterly public usage metrics, governance abstention on own proposals, and outcome-based deliverables focused on incremental activity. Open to reconsidering with proper transparency. Full reasoning here: https://gov.uniswap.org/t/scaling-v4-and-supporting-unichain/25484/51
https://gov.uniswap.org/t/l2beat-delegate-platform/22449/12
https://gov.uniswap.org/t/l2beat-delegate-platform/22449/12
Hey! Thanks for presenting Lighthouse; I personally find some of the features interesting. About getting feedback, I think you could probably request a slot in the next community call (not sure how it's managed) – also, I wanted to ask if you could elaborate a bit more on points 3.h and i?
Hey! Thanks for presenting Lighthouse; I personally find some of the features interesting. About getting feedback, I think you could probably request a slot in the next community call (not sure how it's managed) – also, I wanted to ask if you could elaborate a bit more on points 3.h and i?
Small update we will be presenting ourselves and the proposal in the upcoming Community Call. Please join if you have any questions you would like to ask.
Thanks @AbdullahUmar for organising.
Thanks for the reply! Requesting a slot is a good idea. I will explore how best to action that.
Regarding the sub points: I will expand inline. They were high level ideas based on our general observations in the space and the idea is to expand and develop them in conjunction with various leading orgs to push the needle forward.
3h. Delegate Accountability and Scoring
Thanks for the reply! Requesting a slot is a good idea. I will explore how best to action that.
Regarding the sub points: I will expand inline. They were high level ideas based on our general observations in the space and the idea is to expand and develop them in conjunction with various leading orgs to push the needle forward.
3h. Delegate Accountability and Scoring
We have observed that there is a large gap when measuring Delegates activity. We also have the problem where we have high context DAO members who contribute who are not delegates.
How do we surface, adjust and reward accordingly?
Also given discussions:
Given that the expected behaviour is that delegates report in a forum thread makes it very hard to synthesize voting activity and behaviours. Especially when they sit across multiple DAOs.
Our thinking here is to explore how this critical activity can be improved to bring it on-chain so we support the good actors and create robust systems for DAOs to make better data driven decisions.
We love @Curia and think they do an amazing job with their dashboards.
However this is static, how do we move towards building a dynamic delegate cohort that reflects and rewards good actors in a given system?
This also means tracking attendance in calls, on-chain to further contribute to these evaluations.
An extremely simplified example being, A member who participates in all votes, calls and discussions WITH positive feedback SHOULD naturally be ranked higher than members who do not.
We should be able to objectively achieve this.
** 3i. Streamlined Grants Program
This was another observation and experience that informed the development of https://github.com/0xLighthouse/signals
Currently it is extremely hard for the Grants and broader Initiatives to be allocated, so we have started building out a general purpose protocol that leverages gov tokens and game theory to help prioritise what gets funded/supported or addressed in a given community.
We think this is interesting because its a form of conviction voting that only places a users voting power at risk and the downside is their ability to not sell their tokens.
I am not proposing to bin existing programs but advocating for more experimentation in how projects and initiatives can be evaluated in a decentralised manner.
Cheers, will keep an eye on the call and register interest once its announced.
Unfortunately @eek637 will not be at DevCon. Heads down for us at the moment. Happy to always connect with people in LDN.
Hi All,
I appreciate I/Lighthouse is a relatively new player in the governance space. However I did think our track record of:
Hi All,
I appreciate I/Lighthouse is a relatively new player in the governance space. However I did think our track record of:
Would at least warrant some feedback on this RFC.
What would be the best way in the context of the Uniswap DAO norms to introduce ourselves more concretely so we drive get more feedback?
Small update we will be presenting ourselves and the proposal in the upcoming Community Call. Please join if you have any questions you would like to ask.
Thanks @AbdullahUmar for organising.
Thanks for the reply! Requesting a slot is a good idea. I will explore how best to action that.
Regarding the sub points: I will expand inline. They were high level ideas based on our general observations in the space and the idea is to expand and develop them in conjunction with various leading orgs to push the needle forward.
3h. Delegate Accountability and Scoring
Thanks for the reply! Requesting a slot is a good idea. I will explore how best to action that.
Regarding the sub points: I will expand inline. They were high level ideas based on our general observations in the space and the idea is to expand and develop them in conjunction with various leading orgs to push the needle forward.
3h. Delegate Accountability and Scoring
We have observed that there is a large gap when measuring Delegates activity. We also have the problem where we have high context DAO members who contribute who are not delegates.
How do we surface, adjust and reward accordingly?
Also given discussions:
Given that the expected behaviour is that delegates report in a forum thread makes it very hard to synthesize voting activity and behaviours. Especially when they sit across multiple DAOs.
Our thinking here is to explore how this critical activity can be improved to bring it on-chain so we support the good actors and create robust systems for DAOs to make better data driven decisions.
We love @Curia and think they do an amazing job with their dashboards.
However this is static, how do we move towards building a dynamic delegate cohort that reflects and rewards good actors in a given system?
This also means tracking attendance in calls, on-chain to further contribute to these evaluations.
An extremely simplified example being, A member who participates in all votes, calls and discussions WITH positive feedback SHOULD naturally be ranked higher than members who do not.
We should be able to objectively achieve this.
** 3i. Streamlined Grants Program
This was another observation and experience that informed the development of https://github.com/0xLighthouse/signals
Currently it is extremely hard for the Grants and broader Initiatives to be allocated, so we have started building out a general purpose protocol that leverages gov tokens and game theory to help prioritise what gets funded/supported or addressed in a given community.
We think this is interesting because its a form of conviction voting that only places a users voting power at risk and the downside is their ability to not sell their tokens.
I am not proposing to bin existing programs but advocating for more experimentation in how projects and initiatives can be evaluated in a decentralised manner.
Cheers, will keep an eye on the call and register interest once its announced.
Unfortunately @eek637 will not be at DevCon. Heads down for us at the moment. Happy to always connect with people in LDN.
Hi All,
I appreciate I/Lighthouse is a relatively new player in the governance space. However I did think our track record of:
Hi All,
I appreciate I/Lighthouse is a relatively new player in the governance space. However I did think our track record of:
Would at least warrant some feedback on this RFC.
What would be the best way in the context of the Uniswap DAO norms to introduce ourselves more concretely so we drive get more feedback?
Think community call is a great idea though it looks like next month's may be cancelled b/c of devcon. @1a35e1 will you be in bangkok?
Think community call is a great idea though it looks like next month's may be cancelled b/c of devcon. @1a35e1 will you be in bangkok?
