This temperature check will gauge delegates' interest/support for deploying the onboarding package to Mantle.
I've attached the forum thread for the full context.
TLDR: The Uniswap Onboarding Package is for new deployments of Uniswap v3 to get set up with three-month liquidity incentives, a frontend (Oku), and incentives distribution tooling (Angle Merkl). These resources will help position Uniswap to have a formidable presence on new EVM chains.
How the vote works: The temperature check will be considered met as long as the total number of votes cast for the funding options is over >10M. If there isn't a clear winner for which level of incentives the chain should receive, a discussion can be had before the onchain proposal.
Notes:
This temperature check will gauge delegates' interest/support for deploying the onboarding package to Mantle.
I've attached the forum thread for the full context.
TLDR: The Uniswap Onboarding Package is for new deployments of Uniswap v3 to get set up with three-month liquidity incentives, a frontend (Oku), and incentives distribution tooling (Angle Merkl). These resources will help position Uniswap to have a formidable presence on new EVM chains.
How the vote works: The temperature check will be considered met as long as the total number of votes cast for the funding options is over >10M. If there isn't a clear winner for which level of incentives the chain should receive, a discussion can be had before the onchain proposal.
Notes:
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616/47?u=kaereste
Hi all,
Uniswap v3 liquidity incentives are live on Mantle!
The distribution is as follows:
$50k in UNI - USDT/WETH 0.05% - 0x076eb72E74C16b208c692EEAB3750978D76B8F28
$37.5k in UNI - WMNT/WETH 0.05% - 0xFc60a4d05ac8C93F62276e046Ad5a098f5C7820a
$37.5k in UNI - USDT/WMNT 0.30% - 0x4cdFc22bF05209de87Ee564746Dc7E5174631d2b
$37.5k in UNI - USDC/USDT 0.01% - 0x8cfee38ab8b8f4bc2ff662e8cc8bdfb0439c9d2c
Hi all,
Uniswap v3 liquidity incentives are live on Mantle!
The distribution is as follows:
$50k in UNI - USDT/WETH 0.05% - 0x076eb72E74C16b208c692EEAB3750978D76B8F28
$37.5k in UNI - WMNT/WETH 0.05% - 0xFc60a4d05ac8C93F62276e046Ad5a098f5C7820a
$37.5k in UNI - USDT/WMNT 0.30% - 0x4cdFc22bF05209de87Ee564746Dc7E5174631d2b
$37.5k in UNI - USDC/USDT 0.01% - 0x8cfee38ab8b8f4bc2ff662e8cc8bdfb0439c9d2c
$87.5k in UNI - METH/WETH 0.01% - 0x48EF5640E71001CaC842f5627A0bfec1EF09DeB7
Anyone looking to participate can create a position on Oku and collect the UNI rewards on Merkl.
Analytics on the deployment’s volume, TVL, and fees are available here.
Hi all,
Uniswap v3 liquidity incentives are live on Mantle!
The distribution is as follows:
$50k in UNI - USDT/WETH 0.05% - 0x076eb72E74C16b208c692EEAB3750978D76B8F28
$37.5k in UNI - WMNT/WETH 0.05% - 0xFc60a4d05ac8C93F62276e046Ad5a098f5C7820a
$37.5k in UNI - USDT/WMNT 0.30% - 0x4cdFc22bF05209de87Ee564746Dc7E5174631d2b
$37.5k in UNI - USDC/USDT 0.01% - 0x8cfee38ab8b8f4bc2ff662e8cc8bdfb0439c9d2c
Hi all,
Uniswap v3 liquidity incentives are live on Mantle!
The distribution is as follows:
$50k in UNI - USDT/WETH 0.05% - 0x076eb72E74C16b208c692EEAB3750978D76B8F28
$37.5k in UNI - WMNT/WETH 0.05% - 0xFc60a4d05ac8C93F62276e046Ad5a098f5C7820a
$37.5k in UNI - USDT/WMNT 0.30% - 0x4cdFc22bF05209de87Ee564746Dc7E5174631d2b
$37.5k in UNI - USDC/USDT 0.01% - 0x8cfee38ab8b8f4bc2ff662e8cc8bdfb0439c9d2c
$87.5k in UNI - METH/WETH 0.01% - 0x48EF5640E71001CaC842f5627A0bfec1EF09DeB7
Anyone looking to participate can create a position on Oku and collect the UNI rewards on Merkl.
Analytics on the deployment’s volume, TVL, and fees are available here.
Quick Update - The $250k of UNI incentives are live on Manta!
Manta has matched the liquidity incentives, bringing the total to $500k across the three incentivized pools. The distribution is as follows:
$200k in UNI & MANTA - STONE/wETH 0.05% - 0x7881dc8e59e644517a95a9687a6b58b86d98db78
$200k in UNI & MANTA - wETH/USDC 0.05% - 0xc108d8702d42bae7b3d7d8209a9b40613a7b1d37
Quick Update - The $250k of UNI incentives are live on Manta!
Manta has matched the liquidity incentives, bringing the total to $500k across the three incentivized pools. The distribution is as follows:
$200k in UNI & MANTA - STONE/wETH 0.05% - 0x7881dc8e59e644517a95a9687a6b58b86d98db78
$200k in UNI & MANTA - wETH/USDC 0.05% - 0xc108d8702d42bae7b3d7d8209a9b40613a7b1d37
$100k in UNI & MANTA - USDC/USDT 0.01% - 0x060f2babc09826687be9cbf5c7ede3b3cd00dd78
Anyone looking to participate can create a position on Oku and collect the UNI rewards on Merkl .
No staking is required. Whichever address holds the position can claim the rewards.
Analytics on the deployment’s volume, TVL, and fees are available here
Another Update - Uniswap v3 is live on Sei along with the $500k in liquidity incentives!
The distribution is as follows:
$200k in UNI - ETH/USDC 0.05% - 0x8a1a9efb7f7f74ace10a31f2f5f9f7e804f957b1
$150k in UNI - USDT/USDT 0.01% - 0x41eea09c971294fcde3b6e553902b04a47be7442
$75k in UNI - WSEI/USDC 0.05% - 0x5cfa8db453c9904511c4ea9eb0bfc903e36b9f5f
Another Update - Uniswap v3 is live on Sei along with the $500k in liquidity incentives!
The distribution is as follows:
$200k in UNI - ETH/USDC 0.05% - 0x8a1a9efb7f7f74ace10a31f2f5f9f7e804f957b1
$150k in UNI - USDT/USDT 0.01% - 0x41eea09c971294fcde3b6e553902b04a47be7442
$75k in UNI - WSEI/USDC 0.05% - 0x5cfa8db453c9904511c4ea9eb0bfc903e36b9f5f
$75k in UNI - WSEI/WETH 0.05% - 0xa3a573c8d14c93fca8fdecb7db168619563d9b00
Anyone looking to participate can create a position on Oku and collect the UNI rewards on Merkl .
No staking is required. Whichever address holds the position can claim the rewards.
Analytics on the deployment’s volume, TVL, and fees are available here
Following up on Juanbug's post above - the Scroll incentives are live!
$250k of UNI will be distributed as follows:
Following up on Juanbug's post above - the Scroll incentives are live!
$250k of UNI will be distributed as follows:
Anyone looking to participate can create a position on Oku and collect the UNI rewards on Merkl.
No staking is required. Whichever address holds the position can claim the rewards.
Analytics on the deployment’s volume, TVL, and fees are available here
I support this proposal (though, am currently traveling and don't have the means to vote in support of it on-chain).
Maintaining an active set of deployments across as many networks as possible, while actively growing users, is clearly in the protocol's interest.
I support this proposal (though, am currently traveling and don't have the means to vote in support of it on-chain).
Maintaining an active set of deployments across as many networks as possible, while actively growing users, is clearly in the protocol's interest.
While a more targeted (per chain vote) approach would be better, these packages are on the "low end" size-wise, and I could see them as a baseline with per chain votes in the future for augmenting the packages.
Hey Pablo from Merkl here. I'm sorry I should have commented earlier on this, and we've been in communication with the GFX Labs and other stakeholders on this proposal. We're excited on our side to collaborate with the Uniswap governance to facilitate the growth of the protocol on Uniswap V3. On every chain where Uniswap deploys, we want to provide tools for Uniswap governance and also any protocol to incentivize liquidity on the DEX in the most efficient way possible. The Merkl engine rewards people based on the efficiency of their liquidity, while leaving them the flexibility to LP however they want, tight range, wide range, through an ALM and without facing any opportunity cost. On top of providing the engine to distribute rewards, we are also going to provide with the interface for everyone to find the yield opportunities and take advantage of them. We provide reporting tools for people to assess as well the efficiency of their budget.
Note that Merkl is evolving and what was once meant around concentrated liquidity will soon be able to cover any type of use cases. We're working so people can add custom rules to the base Merkl implementation, like only reward LPs who stayed more than x amount of time, or only reward LPs which have been LP-ing across several pools, ... And all of this will be offered on all these new chains so this program will enable Uniswap to bootstrap on new chains and give everyone the tools to pursue this growth rather than seeking for liquidity from other forks.
Hey Pablo from Merkl here. I'm sorry I should have commented earlier on this, and we've been in communication with the GFX Labs and other stakeholders on this proposal. We're excited on our side to collaborate with the Uniswap governance to facilitate the growth of the protocol on Uniswap V3. On every chain where Uniswap deploys, we want to provide tools for Uniswap governance and also any protocol to incentivize liquidity on the DEX in the most efficient way possible. The Merkl engine rewards people based on the efficiency of their liquidity, while leaving them the flexibility to LP however they want, tight range, wide range, through an ALM and without facing any opportunity cost. On top of providing the engine to distribute rewards, we are also going to provide with the interface for everyone to find the yield opportunities and take advantage of them. We provide reporting tools for people to assess as well the efficiency of their budget.
Note that Merkl is evolving and what was once meant around concentrated liquidity will soon be able to cover any type of use cases. We're working so people can add custom rules to the base Merkl implementation, like only reward LPs who stayed more than x amount of time, or only reward LPs which have been LP-ing across several pools, ... And all of this will be offered on all these new chains so this program will enable Uniswap to bootstrap on new chains and give everyone the tools to pursue this growth rather than seeking for liquidity from other forks.
Uniswap V3 has been the reason for Merkl being built, and we can't wait to accompany it on its future phases of growth.
Hey all!
We're thrilled to announce that the Uniswap v3 deployment on Blast is live, along with $250k UNI incentives, distributed through Merkl.
The incentivized pool is the 0.05% WETH/USDB pool, attached here.
No staking is required. Any address holding a position in the incentivized pool can claim rewards on Merkl at this link.
Analytics on the deployment's volume, TVL, and fees are available here.
Good job, I can't wait to see how amazing this turned out to be.
Quick Update - The $250k of UNI incentives are live on Manta!
Manta has matched the liquidity incentives, bringing the total to $500k across the three incentivized pools. The distribution is as follows:
$200k in UNI & MANTA - STONE/wETH 0.05% - 0x7881dc8e59e644517a95a9687a6b58b86d98db78
$200k in UNI & MANTA - wETH/USDC 0.05% - 0xc108d8702d42bae7b3d7d8209a9b40613a7b1d37
Quick Update - The $250k of UNI incentives are live on Manta!
Manta has matched the liquidity incentives, bringing the total to $500k across the three incentivized pools. The distribution is as follows:
$200k in UNI & MANTA - STONE/wETH 0.05% - 0x7881dc8e59e644517a95a9687a6b58b86d98db78
$200k in UNI & MANTA - wETH/USDC 0.05% - 0xc108d8702d42bae7b3d7d8209a9b40613a7b1d37
$100k in UNI & MANTA - USDC/USDT 0.01% - 0x060f2babc09826687be9cbf5c7ede3b3cd00dd78
Anyone looking to participate can create a position on Oku and collect the UNI rewards on Merkl .
No staking is required. Whichever address holds the position can claim the rewards.
Analytics on the deployment’s volume, TVL, and fees are available here
Another Update - Uniswap v3 is live on Sei along with the $500k in liquidity incentives!
The distribution is as follows:
$200k in UNI - ETH/USDC 0.05% - 0x8a1a9efb7f7f74ace10a31f2f5f9f7e804f957b1
$150k in UNI - USDT/USDT 0.01% - 0x41eea09c971294fcde3b6e553902b04a47be7442
$75k in UNI - WSEI/USDC 0.05% - 0x5cfa8db453c9904511c4ea9eb0bfc903e36b9f5f
Another Update - Uniswap v3 is live on Sei along with the $500k in liquidity incentives!
The distribution is as follows:
$200k in UNI - ETH/USDC 0.05% - 0x8a1a9efb7f7f74ace10a31f2f5f9f7e804f957b1
$150k in UNI - USDT/USDT 0.01% - 0x41eea09c971294fcde3b6e553902b04a47be7442
$75k in UNI - WSEI/USDC 0.05% - 0x5cfa8db453c9904511c4ea9eb0bfc903e36b9f5f
$75k in UNI - WSEI/WETH 0.05% - 0xa3a573c8d14c93fca8fdecb7db168619563d9b00
Anyone looking to participate can create a position on Oku and collect the UNI rewards on Merkl .
No staking is required. Whichever address holds the position can claim the rewards.
Analytics on the deployment’s volume, TVL, and fees are available here
Following up on Juanbug's post above - the Scroll incentives are live!
$250k of UNI will be distributed as follows:
Following up on Juanbug's post above - the Scroll incentives are live!
$250k of UNI will be distributed as follows:
Anyone looking to participate can create a position on Oku and collect the UNI rewards on Merkl.
No staking is required. Whichever address holds the position can claim the rewards.
Analytics on the deployment’s volume, TVL, and fees are available here
I support this proposal (though, am currently traveling and don't have the means to vote in support of it on-chain).
Maintaining an active set of deployments across as many networks as possible, while actively growing users, is clearly in the protocol's interest.
I support this proposal (though, am currently traveling and don't have the means to vote in support of it on-chain).
Maintaining an active set of deployments across as many networks as possible, while actively growing users, is clearly in the protocol's interest.
While a more targeted (per chain vote) approach would be better, these packages are on the "low end" size-wise, and I could see them as a baseline with per chain votes in the future for augmenting the packages.
Hey Pablo from Merkl here. I'm sorry I should have commented earlier on this, and we've been in communication with the GFX Labs and other stakeholders on this proposal. We're excited on our side to collaborate with the Uniswap governance to facilitate the growth of the protocol on Uniswap V3. On every chain where Uniswap deploys, we want to provide tools for Uniswap governance and also any protocol to incentivize liquidity on the DEX in the most efficient way possible. The Merkl engine rewards people based on the efficiency of their liquidity, while leaving them the flexibility to LP however they want, tight range, wide range, through an ALM and without facing any opportunity cost. On top of providing the engine to distribute rewards, we are also going to provide with the interface for everyone to find the yield opportunities and take advantage of them. We provide reporting tools for people to assess as well the efficiency of their budget.
Note that Merkl is evolving and what was once meant around concentrated liquidity will soon be able to cover any type of use cases. We're working so people can add custom rules to the base Merkl implementation, like only reward LPs who stayed more than x amount of time, or only reward LPs which have been LP-ing across several pools, ... And all of this will be offered on all these new chains so this program will enable Uniswap to bootstrap on new chains and give everyone the tools to pursue this growth rather than seeking for liquidity from other forks.
Hey Pablo from Merkl here. I'm sorry I should have commented earlier on this, and we've been in communication with the GFX Labs and other stakeholders on this proposal. We're excited on our side to collaborate with the Uniswap governance to facilitate the growth of the protocol on Uniswap V3. On every chain where Uniswap deploys, we want to provide tools for Uniswap governance and also any protocol to incentivize liquidity on the DEX in the most efficient way possible. The Merkl engine rewards people based on the efficiency of their liquidity, while leaving them the flexibility to LP however they want, tight range, wide range, through an ALM and without facing any opportunity cost. On top of providing the engine to distribute rewards, we are also going to provide with the interface for everyone to find the yield opportunities and take advantage of them. We provide reporting tools for people to assess as well the efficiency of their budget.
Note that Merkl is evolving and what was once meant around concentrated liquidity will soon be able to cover any type of use cases. We're working so people can add custom rules to the base Merkl implementation, like only reward LPs who stayed more than x amount of time, or only reward LPs which have been LP-ing across several pools, ... And all of this will be offered on all these new chains so this program will enable Uniswap to bootstrap on new chains and give everyone the tools to pursue this growth rather than seeking for liquidity from other forks.
Uniswap V3 has been the reason for Merkl being built, and we can't wait to accompany it on its future phases of growth.
Hey all!
We're thrilled to announce that the Uniswap v3 deployment on Blast is live, along with $250k UNI incentives, distributed through Merkl.
The incentivized pool is the 0.05% WETH/USDB pool, attached here.
No staking is required. Any address holding a position in the incentivized pool can claim rewards on Merkl at this link.
Analytics on the deployment's volume, TVL, and fees are available here.
Good job, I can't wait to see how amazing this turned out to be.
Great idea that could indeed be a good way to drive Uniswap's growth on emerging chains!
Jumping in to mention that Angle Labs has Merkl available to help the DAO distribute rewards, in line with @Jl_Defiedge's recommendation above!
Great idea that could indeed be a good way to drive Uniswap's growth on emerging chains!
Jumping in to mention that Angle Labs has Merkl available to help the DAO distribute rewards, in line with @Jl_Defiedge's recommendation above!
Briefly, Merkl is currently used to distribute approx. 1.8M ARB to Uniswap Arbitrum pools, 50+ Uniswap v3 pools have been incentivized through Merkl by various protocols and on various chains, 8+ liquidity managers have been integrated to Merkl to manage liquidity on Uniswap v3, and Merkl is today the most familiar, easy, and straightforward way to incentivize liquidity on Uniswap.
In case this initiative goes forward,feel free to reach out with any question or ask directly here. Happy to help and see this type of proactive developments!
I'm a big fan of this idea. To date, I think Uniswap has largely relied on brand recognition to drive market share. I think we can do more. I'm supportive of making co-incentives a standard part of chain deployments.
I think it's worth considering a parallel program designed to co-incentivize growth on existing chains like Arbitrum where there is still significant market share to be had and a clear opportunity for Uniswap to acquire significant grants for this purpose e.g. https://snapshot.org/#/arbitrumfoundation.eth/proposal/0x8112be08246466f870d0b91590fe99211f73d15cfdadac62ff3f1e6b2f74869a
This is a nice initiative to attract new users from these new Layer 2s. For the distribution, I suggest Uniswap utilize Merkl for fairer and better distribution of the $250K $UNI incentives
this is a great idea!
there is really no reason that uniswap should be losing market share to generic forks across different chains. another major area where uniswap wins is through a powerful brand. a lot of newer chains have DEXs from anonymous teams, and rug pulls have become very common across a lot of these chains, especially when looking at something like zksync.
this is a great idea!
there is really no reason that uniswap should be losing market share to generic forks across different chains. another major area where uniswap wins is through a powerful brand. a lot of newer chains have DEXs from anonymous teams, and rug pulls have become very common across a lot of these chains, especially when looking at something like zksync.
the proposed incentive program, along with the accountability committee, can really drive uniswap's dominance further. one thing to consider is the question of who would be in charge of managing this program - would it be added to the accountability committee's duties? would it be a separate working group?
regardless, at surface level i like this program and its goal. we at blockworks research are eager to help out in any way possible in getting this across the finish line :saluting_face:
Love the initiative and focus on core KPI of market share. Downstream of that is volume. Would be supportive of standardizing a process for launching new chains.
another major area where uniswap wins is through a powerful brand. a lot of newer chains have DEXs from anonymous teams, and rug pulls have become very common across a lot of these chains,
I note that recent court case in UK suggest that exchanges be interpreted as constructive trustee. Whilst onboarding new deployments is a short-term subsidy, the long-term is to create legitimacy that underpins trust that LPs and users will get a fair bite of the cherry (balanced treatment)
another major area where uniswap wins is through a powerful brand. a lot of newer chains have DEXs from anonymous teams, and rug pulls have become very common across a lot of these chains,
I note that recent court case in UK suggest that exchanges be interpreted as constructive trustee. Whilst onboarding new deployments is a short-term subsidy, the long-term is to create legitimacy that underpins trust that LPs and users will get a fair bite of the cherry (balanced treatment)
Jahangir Piroozzadeh v Persons Unknown & Others [2023] EWHC 1024 (Ch)
Victims of crypto fraud have so far been bringing claims against fraudsters (who are typically identified as a group of “persons unknown”) and including crypto exchanges as defendants. This is done to seek disclosure of account information from the crypto exchange but also to impose a role of constructive trustee on the crypto exchange to help preserve any crypto that remains in wallets held on the crypto exchange.
The above judgment demonstrates that the proposition of crypto exchanges being constructive trustees cannot be taken for granted. It will be fact dependent and needs careful consideration. Also, there will need to be good reason for why crypto exchanges are added as defendants, particularly where applications are being made without notice to them. This judgment could help streamline the process between victims and crypto exchanges by encouraging greater pre-action communication and limiting the scope of the orders being sought against crypto exchanges. The goal being to build an ecosystem in which victims of crypto fraud can recover their crypto at minimal cost and without having to put the crypto exchanges off-side.
Since Uniswap labs frontend was available with the deployment of the v3 contracts. Does it still make sense to pay Oku the 45k deployment cost + ongoing 5k a month fee for this Blast deployment? Perhaps I am missing something here.
My initial read of this proposal was that Oku were to be part of the package if the chain being launched on did not have a Uniswap Labs frontend/contracts launched. In order to move quickly to more L2 chains.
Since Uniswap labs frontend was available with the deployment of the v3 contracts. Does it still make sense to pay Oku the 45k deployment cost + ongoing 5k a month fee for this Blast deployment? Perhaps I am missing something here.
My initial read of this proposal was that Oku were to be part of the package if the chain being launched on did not have a Uniswap Labs frontend/contracts launched. In order to move quickly to more L2 chains.
"1. Blast: $500k (w/Oku + Merkl)"
Great idea that could indeed be a good way to drive Uniswap's growth on emerging chains!
Jumping in to mention that Angle Labs has Merkl available to help the DAO distribute rewards, in line with @Jl_Defiedge's recommendation above!
Great idea that could indeed be a good way to drive Uniswap's growth on emerging chains!
Jumping in to mention that Angle Labs has Merkl available to help the DAO distribute rewards, in line with @Jl_Defiedge's recommendation above!
Briefly, Merkl is currently used to distribute approx. 1.8M ARB to Uniswap Arbitrum pools, 50+ Uniswap v3 pools have been incentivized through Merkl by various protocols and on various chains, 8+ liquidity managers have been integrated to Merkl to manage liquidity on Uniswap v3, and Merkl is today the most familiar, easy, and straightforward way to incentivize liquidity on Uniswap.
In case this initiative goes forward,feel free to reach out with any question or ask directly here. Happy to help and see this type of proactive developments!
I'm a big fan of this idea. To date, I think Uniswap has largely relied on brand recognition to drive market share. I think we can do more. I'm supportive of making co-incentives a standard part of chain deployments.
I think it's worth considering a parallel program designed to co-incentivize growth on existing chains like Arbitrum where there is still significant market share to be had and a clear opportunity for Uniswap to acquire significant grants for this purpose e.g. https://snapshot.org/#/arbitrumfoundation.eth/proposal/0x8112be08246466f870d0b91590fe99211f73d15cfdadac62ff3f1e6b2f74869a
This is a nice initiative to attract new users from these new Layer 2s. For the distribution, I suggest Uniswap utilize Merkl for fairer and better distribution of the $250K $UNI incentives
this is a great idea!
there is really no reason that uniswap should be losing market share to generic forks across different chains. another major area where uniswap wins is through a powerful brand. a lot of newer chains have DEXs from anonymous teams, and rug pulls have become very common across a lot of these chains, especially when looking at something like zksync.
this is a great idea!
there is really no reason that uniswap should be losing market share to generic forks across different chains. another major area where uniswap wins is through a powerful brand. a lot of newer chains have DEXs from anonymous teams, and rug pulls have become very common across a lot of these chains, especially when looking at something like zksync.
the proposed incentive program, along with the accountability committee, can really drive uniswap's dominance further. one thing to consider is the question of who would be in charge of managing this program - would it be added to the accountability committee's duties? would it be a separate working group?
regardless, at surface level i like this program and its goal. we at blockworks research are eager to help out in any way possible in getting this across the finish line :saluting_face:
Love the initiative and focus on core KPI of market share. Downstream of that is volume. Would be supportive of standardizing a process for launching new chains.
another major area where uniswap wins is through a powerful brand. a lot of newer chains have DEXs from anonymous teams, and rug pulls have become very common across a lot of these chains,
I note that recent court case in UK suggest that exchanges be interpreted as constructive trustee. Whilst onboarding new deployments is a short-term subsidy, the long-term is to create legitimacy that underpins trust that LPs and users will get a fair bite of the cherry (balanced treatment)
another major area where uniswap wins is through a powerful brand. a lot of newer chains have DEXs from anonymous teams, and rug pulls have become very common across a lot of these chains,
I note that recent court case in UK suggest that exchanges be interpreted as constructive trustee. Whilst onboarding new deployments is a short-term subsidy, the long-term is to create legitimacy that underpins trust that LPs and users will get a fair bite of the cherry (balanced treatment)
Jahangir Piroozzadeh v Persons Unknown & Others [2023] EWHC 1024 (Ch)
Victims of crypto fraud have so far been bringing claims against fraudsters (who are typically identified as a group of “persons unknown”) and including crypto exchanges as defendants. This is done to seek disclosure of account information from the crypto exchange but also to impose a role of constructive trustee on the crypto exchange to help preserve any crypto that remains in wallets held on the crypto exchange.
The above judgment demonstrates that the proposition of crypto exchanges being constructive trustees cannot be taken for granted. It will be fact dependent and needs careful consideration. Also, there will need to be good reason for why crypto exchanges are added as defendants, particularly where applications are being made without notice to them. This judgment could help streamline the process between victims and crypto exchanges by encouraging greater pre-action communication and limiting the scope of the orders being sought against crypto exchanges. The goal being to build an ecosystem in which victims of crypto fraud can recover their crypto at minimal cost and without having to put the crypto exchanges off-side.
Since Uniswap labs frontend was available with the deployment of the v3 contracts. Does it still make sense to pay Oku the 45k deployment cost + ongoing 5k a month fee for this Blast deployment? Perhaps I am missing something here.
My initial read of this proposal was that Oku were to be part of the package if the chain being launched on did not have a Uniswap Labs frontend/contracts launched. In order to move quickly to more L2 chains.
Since Uniswap labs frontend was available with the deployment of the v3 contracts. Does it still make sense to pay Oku the 45k deployment cost + ongoing 5k a month fee for this Blast deployment? Perhaps I am missing something here.
My initial read of this proposal was that Oku were to be part of the package if the chain being launched on did not have a Uniswap Labs frontend/contracts launched. In order to move quickly to more L2 chains.
"1. Blast: $500k (w/Oku + Merkl)"
The initiative to bootstrap new chains makes sense. However, the cost for this proposal vs the intended Uni rewards seems high. Please clarify if I am misinterpreting the delopyment costs.
In the scenerio that all 10 deloyments pass the vote at 250k:
250k x 10 deployments = $2.5 million
Oku front end deployment costs = $450k (45k x 10 deployments)
The initiative to bootstrap new chains makes sense. However, the cost for this proposal vs the intended Uni rewards seems high. Please clarify if I am misinterpreting the delopyment costs.
In the scenerio that all 10 deloyments pass the vote at 250k:
250k x 10 deployments = $2.5 million
Oku front end deployment costs = $450k (45k x 10 deployments)
Oku ongoing per month cost = $50k per month (5k per month x 10 deployments)== 500k per year
Merkl Angle = 200k euro (20k x 10 deployments)
Distributed rewards cost for Merkl = $75k
Total cost (ex Uni reward distribution) after 1 year = $1,225,000
In other words, for the $2.5 million in UNI rewards for the purpose of liquidity mining. UNI dao will be spending about 50% for the intended goal in costs. Bringing the total cost to $3,725,000.
Is this thinking correct Getty? Or am I misunderstanding how the deployments scale out?
EDIT: Also why is a UNI pair not incentivized part of the L2 deployments? I.e. UNI/USDC, UNI/ETH, if paying the rewards in UNI it gives liquidity providers a reason to use those UNI rewards by further liquidity providing or selling UNI by LPing in tight range, it also give users an outlet to sell the UNI if choosing to.
Selling the UNI for ETH or USDC to fund the Merkle should be a non-starter imo.
The initiative to bootstrap new chains makes sense. However, the cost for this proposal vs the intended Uni rewards seems high. Please clarify if I am misinterpreting the delopyment costs.
In the scenerio that all 10 deloyments pass the vote at 250k:
250k x 10 deployments = $2.5 million
Oku front end deployment costs = $450k (45k x 10 deployments)
The initiative to bootstrap new chains makes sense. However, the cost for this proposal vs the intended Uni rewards seems high. Please clarify if I am misinterpreting the delopyment costs.
In the scenerio that all 10 deloyments pass the vote at 250k:
250k x 10 deployments = $2.5 million
Oku front end deployment costs = $450k (45k x 10 deployments)
Oku ongoing per month cost = $50k per month (5k per month x 10 deployments)== 500k per year
Merkl Angle = 200k euro (20k x 10 deployments)
Distributed rewards cost for Merkl = $75k
Total cost (ex Uni reward distribution) after 1 year = $1,225,000
In other words, for the $2.5 million in UNI rewards for the purpose of liquidity mining. UNI dao will be spending about 50% for the intended goal in costs. Bringing the total cost to $3,725,000.
Is this thinking correct Getty? Or am I misunderstanding how the deployments scale out?
EDIT: Also why is a UNI pair not incentivized part of the L2 deployments? I.e. UNI/USDC, UNI/ETH, if paying the rewards in UNI it gives liquidity providers a reason to use those UNI rewards by further liquidity providing or selling UNI by LPing in tight range, it also give users an outlet to sell the UNI if choosing to.
Selling the UNI for ETH or USDC to fund the Merkle should be a non-starter imo.
I agree with the responses in this forum and the package should be informally agreed on and then reach out to L2 chains. Would Gauntlet be willing to escrow the funds as an expansion of the liquidity program it is running?
I agree with the responses in this forum and the package should be informally agreed on and then reach out to L2 chains. Would Gauntlet be willing to escrow the funds as an expansion of the liquidity program it is running?
Oku and Merkl ( Escrow: Gauntlet, Accountability Commitee?)
Flexible funding for intrested chains w/ potential matching from those chains.
Cost outlays (Oku, Merkl, Escrow Partner)
The list of chains who were reached out to and want a package
How much each chain is wanting
How much each chain is willing to match into the package
The onchain vote would be for:
The onchain vote is to bulk approve the list of chain packages. This will minimize the amount of onchain votes, and get to the primary action of executing the proposal (i.e. Wave 1 of L2 Liquidity Campaign)
I agree with the responses in this forum and the package should be informally agreed on and then reach out to L2 chains. Would Gauntlet be willing to escrow the funds as an expansion of the liquidity program it is running?
I agree with the responses in this forum and the package should be informally agreed on and then reach out to L2 chains. Would Gauntlet be willing to escrow the funds as an expansion of the liquidity program it is running?
Oku and Merkl ( Escrow: Gauntlet, Accountability Commitee?)
Flexible funding for intrested chains w/ potential matching from those chains.
Cost outlays (Oku, Merkl, Escrow Partner)
The list of chains who were reached out to and want a package
How much each chain is wanting
How much each chain is willing to match into the package
The onchain vote would be for:
The onchain vote is to bulk approve the list of chain packages. This will minimize the amount of onchain votes, and get to the primary action of executing the proposal (i.e. Wave 1 of L2 Liquidity Campaign)
Love the initiative but aren't we better off waiting to do this on v4?
Great idea! The cost is low considering the goals.
If I am understanding the package correctly, there will be two different functions 1. The front-end UI options and 2. The staking contract, and who will run it
Great idea! The cost is low considering the goals.
If I am understanding the package correctly, there will be two different functions 1. The front-end UI options and 2. The staking contract, and who will run it
I remember the Uniswap UX having the staking options. Although it was not used very long. Is it possible to fork this staking UI into Oku or other UI's looking to provide staking access? This gives option to a recommended frontend as part of the package, but also opens up to new teams looking to break into the Uniswap V3 trading user interface space. It would help with directing users to a lower cost trading interface on newer chains.
The backend staking contract would be a Uniswap Foundation/protocol/app package that can be plugged into from Multiple UI's. Perhaps the chain chooses the staking contract manager?
Love the initiative but aren't we better off waiting to do this on v4?
Great idea! The cost is low considering the goals.
If I am understanding the package correctly, there will be two different functions 1. The front-end UI options and 2. The staking contract, and who will run it
Great idea! The cost is low considering the goals.
If I am understanding the package correctly, there will be two different functions 1. The front-end UI options and 2. The staking contract, and who will run it
I remember the Uniswap UX having the staking options. Although it was not used very long. Is it possible to fork this staking UI into Oku or other UI's looking to provide staking access? This gives option to a recommended frontend as part of the package, but also opens up to new teams looking to break into the Uniswap V3 trading user interface space. It would help with directing users to a lower cost trading interface on newer chains.
The backend staking contract would be a Uniswap Foundation/protocol/app package that can be plugged into from Multiple UI's. Perhaps the chain chooses the staking contract manager?
Quick update: We have sent, bridged, and are set to start the $250k of UNI incentives on Scroll today!
https://gov.uniswap.org/t/uniswap-deployments-accountability-committee-update-thread/21835/7
Just wanted to post an update for this package. We are currently in the process of working with Oku and Merkl to deploy voted in funds!
Update: https://gov.uniswap.org/t/uniswap-deployments-accountability-committee-update-thread/21835/4
The below response reflects the views of L2BEAT’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
Following our participation in the series of temp checks on what amount we should deploy on which chain, we’ll be voting in favor of the on-chain vote. We followed the discussion happening above this response and our understanding is that this initiative is more reliant on the DAO wanting to push to capture a bigger market share in the chains mentioned than it is on the chain's willingness to match our incentive packages.
The below response reflects the views of L2BEAT’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
Following our participation in the series of temp checks on what amount we should deploy on which chain, we’ll be voting in favor of the on-chain vote. We followed the discussion happening above this response and our understanding is that this initiative is more reliant on the DAO wanting to push to capture a bigger market share in the chains mentioned than it is on the chain's willingness to match our incentive packages.
When we initially voted for this proposal during temp-check, it was exactly that thinking that led us to support it, and we saw the possibility of chains matching the incentives as a bonus. What’s more important to us, however, as we already mentioned, is a post-implementation analysis of the initiative to get some data that can help us make better-informed decisions in the future.
It would be helpful if that was mentioned proactively before the vote was live. While we voted against, it seems we didn't have the latest info around the progress.
We are supportive of this proposal but unfortunately can't change our vote now.
We would have changed our voting but do worry about this finding. But if this is true @AbdullahUmar then doesn’t it make sense to only go with ones that Uniswap support on its front ends?
Hi Doo,
We had discussed the proposal with @AbdullahUmar prior to posting it. We went through the various chains and ultimately decided it made sense to post the proposal. We respect your decision to vote against it, however, in the future please reach out or post here so we have an opportunity give you the necessary information.
We voted Against as we're in agreement with @AbdullahUmar and @Doo_StableLab here. This is a bit premature.
We had discussed the proposal with @AbdullahUmar prior to posting it. We went through the various chains and ultimately decided it made sense to post the proposal. We respect your decision to vote against it, however, in the future please reach out or post here so we have an opportunity give you the necessary information.
Hi Doo,
Two parts here. Multiple chains have invested in Oku integrations, so there is clear demand here. Practically every chain that hasn't been adopted by Labs has relied on Oku. Polygon zkEVM, Scroll, Moonbeam, and I think others have entered into confidential agreements with the Oku team to bootstrap some liqudity/provide incentives. Like Polygon zkEVM has six figures committed. So there is demand.
Hi Doo,
Two parts here. Multiple chains have invested in Oku integrations, so there is clear demand here. Practically every chain that hasn't been adopted by Labs has relied on Oku. Polygon zkEVM, Scroll, Moonbeam, and I think others have entered into confidential agreements with the Oku team to bootstrap some liqudity/provide incentives. Like Polygon zkEVM has six figures committed. So there is demand.
The issue is around doubling down and attaining a higher degree of commitments from these chains. Oku is getting us from 0 to 1. But chains aren't willing to double down to step 3 or 4. So, my personal perspective is that Oku is certainly helping with expansion--but there are inherent limitation from a negotiating standpoint for the accountability committee since we cannot promise the Uni brand.
Thank you Getty. Looks like we're on track to send this through via an onchain vote--just a couple of things:
The Deployment Accountability Committee is currently having meetings with each of the target chains from the series of snapshots. Our goal for these conversations is to see whether or not the target chain is open to matching a portion of the incentives provided by Uniswap. The forms of contributions that we’re looking for are either bootstrapping pool liquidity on the target chain or also providing incentives on such pools. Another important point is to note that most of these chains are not aware of this program. We believe that there should be a degree of alignment between Uniswap and the target chains, so making sure they’re conscious of our commitment is important. It could open up more opportunities in the future, even if the target chains aren't open to matching today.
Considering it's a large amount of transfer, we believe that the community should review it more before proceeding including on method to leverage its negotiations.

Hi @Userisky,
Oku's frontend offers Uniswap v3 users a more advanced experience when interfacing with Uniswap v3 deployments. In addition to the trading interface, Oku has a robust analytics platform that includes user, position, pool, and token information. Both the Trade and Analytics sites are powered by Oku's in-depth Uniswap v3 API, which is available for developers and projects.
Quick update: We have sent, bridged, and are set to start the $250k of UNI incentives on Scroll today!
https://gov.uniswap.org/t/uniswap-deployments-accountability-committee-update-thread/21835/7
Just wanted to post an update for this package. We are currently in the process of working with Oku and Merkl to deploy voted in funds!
Update: https://gov.uniswap.org/t/uniswap-deployments-accountability-committee-update-thread/21835/4
The below response reflects the views of L2BEAT’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
Following our participation in the series of temp checks on what amount we should deploy on which chain, we’ll be voting in favor of the on-chain vote. We followed the discussion happening above this response and our understanding is that this initiative is more reliant on the DAO wanting to push to capture a bigger market share in the chains mentioned than it is on the chain's willingness to match our incentive packages.
The below response reflects the views of L2BEAT’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking, and ideation of the two.
Following our participation in the series of temp checks on what amount we should deploy on which chain, we’ll be voting in favor of the on-chain vote. We followed the discussion happening above this response and our understanding is that this initiative is more reliant on the DAO wanting to push to capture a bigger market share in the chains mentioned than it is on the chain's willingness to match our incentive packages.
When we initially voted for this proposal during temp-check, it was exactly that thinking that led us to support it, and we saw the possibility of chains matching the incentives as a bonus. What’s more important to us, however, as we already mentioned, is a post-implementation analysis of the initiative to get some data that can help us make better-informed decisions in the future.
It would be helpful if that was mentioned proactively before the vote was live. While we voted against, it seems we didn't have the latest info around the progress.
We are supportive of this proposal but unfortunately can't change our vote now.
We would have changed our voting but do worry about this finding. But if this is true @AbdullahUmar then doesn’t it make sense to only go with ones that Uniswap support on its front ends?
Hi Doo,
We had discussed the proposal with @AbdullahUmar prior to posting it. We went through the various chains and ultimately decided it made sense to post the proposal. We respect your decision to vote against it, however, in the future please reach out or post here so we have an opportunity give you the necessary information.
We voted Against as we're in agreement with @AbdullahUmar and @Doo_StableLab here. This is a bit premature.
We had discussed the proposal with @AbdullahUmar prior to posting it. We went through the various chains and ultimately decided it made sense to post the proposal. We respect your decision to vote against it, however, in the future please reach out or post here so we have an opportunity give you the necessary information.
Hi Doo,
Two parts here. Multiple chains have invested in Oku integrations, so there is clear demand here. Practically every chain that hasn't been adopted by Labs has relied on Oku. Polygon zkEVM, Scroll, Moonbeam, and I think others have entered into confidential agreements with the Oku team to bootstrap some liqudity/provide incentives. Like Polygon zkEVM has six figures committed. So there is demand.
Hi Doo,
Two parts here. Multiple chains have invested in Oku integrations, so there is clear demand here. Practically every chain that hasn't been adopted by Labs has relied on Oku. Polygon zkEVM, Scroll, Moonbeam, and I think others have entered into confidential agreements with the Oku team to bootstrap some liqudity/provide incentives. Like Polygon zkEVM has six figures committed. So there is demand.
The issue is around doubling down and attaining a higher degree of commitments from these chains. Oku is getting us from 0 to 1. But chains aren't willing to double down to step 3 or 4. So, my personal perspective is that Oku is certainly helping with expansion--but there are inherent limitation from a negotiating standpoint for the accountability committee since we cannot promise the Uni brand.
Thank you Getty. Looks like we're on track to send this through via an onchain vote--just a couple of things:
The Deployment Accountability Committee is currently having meetings with each of the target chains from the series of snapshots. Our goal for these conversations is to see whether or not the target chain is open to matching a portion of the incentives provided by Uniswap. The forms of contributions that we’re looking for are either bootstrapping pool liquidity on the target chain or also providing incentives on such pools. Another important point is to note that most of these chains are not aware of this program. We believe that there should be a degree of alignment between Uniswap and the target chains, so making sure they’re conscious of our commitment is important. It could open up more opportunities in the future, even if the target chains aren't open to matching today.
Considering it's a large amount of transfer, we believe that the community should review it more before proceeding including on method to leverage its negotiations.

Hi @Userisky,
Oku's frontend offers Uniswap v3 users a more advanced experience when interfacing with Uniswap v3 deployments. In addition to the trading interface, Oku has a robust analytics platform that includes user, position, pool, and token information. Both the Trade and Analytics sites are powered by Oku's in-depth Uniswap v3 API, which is available for developers and projects.
We would have changed our voting but do worry about this finding. But if this is true @AbdullahUmar then doesn’t it make sense to only go with ones that Uniswap support on its front ends?
I think one of the nice secondary benefits of this proposal is that, if it is successful, it will at least incrementally loosen the coupling in public perception between the Uniswap Protocol and app.uniswap.org.
We had discussed the proposal with @AbdullahUmar prior to posting it. We went through the various chains and ultimately decided it made sense to post the proposal. We respect your decision to vote against it, however, in the future please reach out or post here so we have an opportunity give you the necessary information.
Thank you for clarification. That would been a helpful information.
The current direction is using Oku. Target chains, however, are not quite as comfortable with this.
We would have changed our voting but do worry about this finding. But if this is true @AbdullahUmar then doesn't it make sense to only go with ones that Uniswap support on its front ends?
Sure thing, I'll ask them to make a post.
Can we discuss more details about the potential success criteria and follow-ups?
We'll put together some stats on how the Onboarding Packages perform, and perhaps if delegates want something further the UF could put up an RFP.
At the moment I’m inclined to vote “Abstain” in particular because the vote is for all 10 chains at once and ~25% of the funds are planned to be spent on BSC. It’s difficult to see the justification for that
Separately, we agree opBNB could be good chain for the DAO to consider.
Thank you Getty. Looks like we're on track to send this through via an onchain vote--just a couple of things:
The Deployment Accountability Committee is currently having meetings with each of the target chains from the series of snapshots. Our goal for these conversations is to see whether or not the target chain is open to matching a portion of the incentives provided by Uniswap. The forms of contributions that we’re looking for are either bootstrapping pool liquidity on the target chain or also providing incentives on such pools. Another important point is to note that most of these chains are not aware of this program. We believe that there should be a degree of alignment between Uniswap and the target chains, so making sure they’re conscious of our commitment is important. It could open up more opportunities in the future, even if the target chains aren't open to matching today.
So far, we’ve conversed with Base, Moonbeam, Blast, and Taiko--but have active chats with all. Four meeting are taking place this week.
Base is on board with helping on the marketing side, if the Uni Foundation or Oku Tweet something related to the incentives that is pre-approved by Base's team, they'll RT. They're also very interested in exploring collaborations in the long-run, like with v4 permissioned pools where KYC'd actors can use Uniswap. That's tangential to this post, but again, good to know from an alignment perspective. It's also worth having these conversations since the chain can give input on the pools, like Base told us not to incentivize wBTC pools on their chain since it wasn't native--yet. So, that pool was replaced with a cbETH pool.
Blast is a straight "no" since they don't want to inflict bias towards any DEX, which is fine since this deployment is more so an immediate go-to-market strategy from Uniswap's end to quickly capture trading volume.
Moonbeam has spend some money on boostrapping pools as well as Oku integration costs, and they don't want their efforts to be wasted, so they'll come back to us shortly with a matching proposition from Moonbeam foundation. Not sure on the exact amounts yet.
Taiko will be mainnet sometime in April. Their team is keen on adding incentives and/or liquidity--currently discussing numbers.
Another final point is that chains like Mantle are prioritizing their native ecosystem. That's verbatim what they texted us. That's another good datapoint for the DAO to consider. Some chains are not worth incentivizing if we're just going to see mercenary liquidity. A Uni v3 fork on one of these chains will do better simply because of a brand shift and new token.
So, before we more to an onchain vote that bundles all of these up, perhaps its best to stagger them, with multiple rounds of voting. Biweekly, we could put up an onchain vote with three target chains, for example. Delegates should have a datapoint included in the onchain vote regarding where our relationship stands with the target chain. As of today, Base and Blast are the only ones we have a definite answer from regarding their alignment with this program.
Hi @Userisky,
Oku's frontend offers Uniswap v3 users a more advanced experience when interfacing with Uniswap v3 deployments. In addition to the trading interface, Oku has a robust analytics platform that includes user, position, pool, and token information. Both the Trade and Analytics sites are powered by Oku's in-depth Uniswap v3 API, which is available for developers and projects.
We believe there is more than enough room for both applications to exist, serve their respective demographics, and ultimately produce a better experience for everyone in the Uniswap ecosystem.
Specifically, for the Blast deployment, we were not aware that Uniswap Labs intended to add the Blast deployment to their frontend until after the onchain vote had passed. We deployed the Uniswap v3 contracts, set up the initial pools, verified the contracts, and relayed the information to the Uniswap Labs team for their integration.
Lastly, the Oku integration with Blast was completed 28 days ago. However, it took us longer than we thought to set up Angle Merkl's incentives since it was the first chain in the batch. Moving forward, we expect to move faster.
Hey, a couple questions / suggestions:
Hey, a couple questions / suggestions:
At the moment I'm inclined to vote "Abstain" in particular because the vote is for all 10 chains at once and ~25% of the funds are planned to be spent on BSC. It's difficult to see the justification for that, as I have doubts about the future growth potential of that chain relative to others (it's already one of the largest!) and the fit of Uniswap v3 and it's ability to take market share, as most of the tokens launched on BSC are fee-on-transfer, not supported by Uni v3. I might be wrong, but as of now it looks like opBNB would be much better fit, conceptually, to the incentive program.
Edit: voted for in the end, see here.
So, before we more to an onchain vote that bundles all of these up, perhaps its best to stagger them, with multiple rounds of voting. Biweekly, we could put up an onchain vote with three target chains, for example. Delegates should have a datapoint included in the onchain vote regarding where our relationship stands with the target chain. As of today, Base and Blast are the only ones we have a definite answer from regarding their alignment with this program.
So, before we more to an onchain vote that bundles all of these up, perhaps its best to stagger them, with multiple rounds of voting. Biweekly, we could put up an onchain vote with three target chains, for example. Delegates should have a datapoint included in the onchain vote regarding where our relationship stands with the target chain. As of today, Base and Blast are the only ones we have a definite answer from regarding their alignment with this program.
We find it a bit puzzling that despite the suggestion from @AbdullahUmar
@Getty and @GFXlabs team decided to go ahead and putting into "onchain vote that bundles all of these up" instead of taking more individual approaches or at least responding to his suggestions. While we understand that some community members want to push for them quickly, we do think it's best that the community takes its time and consideration.

Just want to provide some more clarity here. We’ve been in close contact with Getty through this process, although the recent forum posts may not seem to display this. As the accountability committee finalizes its conversations, the majority of the feedback we’ve received from target chain has been, well, more disappointing than we hoped. Most are not looking to match our incentive package, unfortunately. They’re open to co market on X, but providing liquidity or incentives seems to be a no-go for most chains. To that end, these multi chain expansions seem primarily to hinge on the Uniswap dao. It’s up to us to decide whether or not we’d like to expand into these markets with more force, even if the target chain isn’t willing to contribute to this initiative. The accountability committee will remain in close contact with these teams in case any forms of reciprocity arise.
I’ll be putting in a Yes vote shortly for this proposal since, as a potential bull run ensues, it's ideal for Uniswap to be well-positioned across these deployments.
Just want to provide some more clarity here. We’ve been in close contact with Getty through this process, although the recent forum posts may not seem to display this. As the accountability committee finalizes its conversations, the majority of the feedback we’ve received from target chain has been, well, more disappointing than we hoped. Most are not looking to match our incentive package, unfortunately. They’re open to co market on X, but providing liquidity or incentives seems to be a no-go for most chains. To that end, these multi chain expansions seem primarily to hinge on the Uniswap dao. It’s up to us to decide whether or not we’d like to expand into these markets with more force, even if the target chain isn’t willing to contribute to this initiative. The accountability committee will remain in close contact with these teams in case any forms of reciprocity arise.
I’ll be putting in a Yes vote shortly for this proposal since, as a potential bull run ensues, it's ideal for Uniswap to be well-positioned across these deployments.
Another note--chains aren't exactly incentivized to match this program. They have Uni v3 forks that are native to their ecosystem that naturally attract new users. It's akin to Uniswap, an established brand, expanding to a "new country"--but that country is more focused on supporting its "local businesses". The edge that Uniswap has is brand. People can rely on a trusted product that's uniform no matter where they go. The target chains see value in this secure brand. Many of their own users will only want to use Uniswap due to this value proposition. BUT the main issue here is front-end. The value of a front-end for retail is perhaps the most important aspect behind reliability and familiarity, and that's a large reason why chains don't want to double down with us regarding incentives. I'm not too sure how we can immediately address this. The current direction is using Oku. Target chains, however, are not quite as comfortable with this. I just wish we could do some type of white labeling with Oku and Uni Labs. It'll be interesting to see how the BNB incentives do since that deployment is on the Labs front-end.
The onchain proposal has been posted. We have updated the proposal description.
Voting will end on the 24th.
It's actually a quite difficult vote for us as while we don't think we should close off the opportunity of collaboration, but it makes more sense for those chains to provide incentive and also pay up for the integration costs. If the reasoning is simply because we want to expand on those chains, then shouldn't we look for most effective and efficient method? Rather than spending so much on operation?
Good question. I don't think all of them will pass, but if they do, you're right on a per-deployment basis; however, Oku already supports (or will very shortly) six of the above chains. The deployment and maintenance costs would only apply to new chains. As for Merkl, it also depends on what they currently support and how much the total number of rewards are approved for. In both cases, the infrastructure is the base cost and can be helpful for further chain growth.
Regarding the UNI rewards/pair point. Maybe we should. Once we get through this set of polls (or maybe in tandem), we can decide whether rewards should be paid in UNI and, if so, if a UNI pair makes sense or if we should distribute them in ETH.
Thank you to everyone who participated in the ten polls.
Here is the summary of the outcomes
Thank you to everyone who participated in the ten polls.
Here is the summary of the outcomes
Some of the temperature checks were quite close. For those, I default toward the popular vote, but if a delegate feels strongly that one of the amounts should be different, please post a comment.
Pools I have gone through the top DEXs for each chain and came up with 3-5 pools for each chain and the allocation amount of the incentives. Please take a look here and feel free to message me with comments or post on this thread. In addition to the pools, I also included the top DEXs for each chain. Generally, I was looking for three things: top pools by volume, top pools where the volume traded exceeds the liquidity available, and how the liquidity was distributed.
Next steps I'd like to send an onchain proposal this week that approves the following Onboarding Packages.
This excludes Taiko because their chain deployment is a few months away but includes Blast because the mainnet is expected in the immediate future. As for Moonbeam, the temperature check seemed indecisive. I figure we can always grant it an onboarding package at a later date.
Of the eight above chains, Oku currently supports all except for Blast, Mantle, Linea, and Polygon zkEVM. Oku has already announced Polygon zkEVM will be supported, so this proposal would only require three new additions.
Angle Merkl's current support can be found here. Merkl will need to support five new chains and their Uniswap v3 deployments; they support Polygon zkEVM, so they only need to add UniV3; they currently fully support base, and I need to confirm before the on-chain proposal that they can support zkSync.
Please review the linked spreadsheet and either post here or message me if you have feedback.
The below response reflects the views of L2Beat’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking and ideation of the two.
We have gone through the above discussion and we agree with the arguments that some targeted investments to increase Uniswap's position in the above chains would be beneficial in the long term.
The below response reflects the views of L2Beat’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking and ideation of the two.
We have gone through the above discussion and we agree with the arguments that some targeted investments to increase Uniswap's position in the above chains would be beneficial in the long term.
At this point, we don't have a strong opinion about the exact amount that should be spent to have a justifiable effect, we would rather see it as an experiment that may need to be followed up with additional investment based on the results and effect observed.
However, looking at @WintermuteGovernance analysis we think it's reasonable to already distinguish chains that might use a higher investment already (BSC, zkSync Era, Avalanche) and others where we can take a more defensive approach. We are not sure about Blast as we don't see it covered in the discussion but from the current results we see a strong sentiment towards funding it with rather a higher amount, we will just abstain at this point.
Although we are voting to fund these onboarding packages, we would like to see some sort of post-implementation analysis included in the budget so that we can have some lessons learned and insights that would allow us to make a more informed decision on how to move forward.
But do think for bigger TVL networks and potentially big TVL networks, it might be worth the operation cost so we will be voting accordingly
We believe this should been a separate voting as well. Having it as a bundled vote to such masks true cost we afraid
Another point that comes to mind is whether paying out incentives in UNI makes the most sense. We'd need to bridge UNI to the destination chain and either bootstrap a market for it or expect liquidity providers to accept it as a reward. That might be fine, but perhaps we should consider trading the UNI for ETH, then bridging ETH, and using that for incentives. Open to discussion.
Quick follow-up here. I confirmed with the Merkl team that they can support zkSync.
The above proposal format seems like the right direction forward from a voting perspective. Let's reach out to a couple of the deployments next week to see if we can onboard like 2 chains for piloting this program.
As for what asset incentives should be paid out in: It’ll likely be too taxing for the DAO to create a market for the UNI token from scratch on multiple chains. The best bet is to probably have the escrow entity swap the UNI for either a stablecoin or ethereum. That asset would then be bridged to the destination chain. I would also assume that LPs simply prefer getting paid in a more reliable and liquid token, so it could further help incentivize liquidity.
Great to see community discussion to align objectives, thanks for posting and setting up the approach Getty! The questions you pose are all important to ensuring funded programs are structured properly. We faced similar challenges and decisions for the ARB LM program that we are currently working on with the DAO, and we have found valuable insights that could benefit this initiative.
As we understand it and similar to above community sentiments, three key questions to think about when considering leveraging liquidity mining for this purpose are:
I feel fairly strongly that the incentives should be paid in UNI tokens. One exception could be if the treasury swap is done – but almost none of the chains in Getty's list have a native token. (I'd add Mantle to the list, by the way!)
Reasons:
I feel fairly strongly that the incentives should be paid in UNI tokens. One exception could be if the treasury swap is done – but almost none of the chains in Getty's list have a native token. (I'd add Mantle to the list, by the way!)
Reasons:
This is a great initiative and we are super supportive of it.
Designing the onboarding package for new/nascent chains seems rather straightforward as we’re providing incentives in the hope of gaining meaningful TVL that then grows with the ecosystem.
This is a great initiative and we are super supportive of it.
Designing the onboarding package for new/nascent chains seems rather straightforward as we’re providing incentives in the hope of gaining meaningful TVL that then grows with the ecosystem.
But for existing and new(ish) chains the decision is a bit more nuanced so we quickly dug a little deeper into Uni V3’s market share for chains with available data:
(Note we are still working on data for BSC & Linea, but given discussion is moving quickly we thought we’d post what we have thus far)
Uni V3 TVL Rank Across Deployments
While the main focus is on volume market share, having context of Uni V3’s TVL position is still an important consideration as that’s what these LM efforts are targeting.
The table below illustrates Uni V3’s TVL rank on each respective deployment (ranked by worst to best). Clearly, there are a couple of deployments that could benefit from the growth program: zkSync Era, Scroll, Moonbeam, Avalanche, and BSC.
Source: DefiLlama
However, as we know TVL is not the clearest indicator of volume market share due to differing smart contract configurations amongst competitors, so let’s take a look at volume market share for chains with available data.
Uni V3: DEX Monthly Trading Volume Market Share Summary Stats
When looking at the 6-month (+ Jan) volume market share of Uni V3 across available deployments vary considerably.
Key takeaways:
Source: DefiLlama
(Missing chains: Moonbeam, Linea, Scroll, Rootstock, Boba)
Thus, we think it’s important for the DAO to assess the benefits of a growth packages for zkSync Era and Avalanche based on each chain’s activity and future prospects. Furthermore, it could be valuable to provide Base with a growth package despite being the dominant DEX to ensure we can solidify Uni V3’s position.
We’ve also included some charts below for individual chains to illustrate Uni V3’s volume market share amongst top competitors:
Celo:

Polygon:

zkSync Era:

Avalanche:

Optimism:

Base:

Arbitrum:

After looking at the available voting systems on Snapshot, I think our best course of action is to make individual polls for each chain. The downside is delegates will have a series of polls to participate in, but the upside is delegates can better demonstrate their opinion.
Each vote will follow the same format and contain the following.
After looking at the available voting systems on Snapshot, I think our best course of action is to make individual polls for each chain. The downside is delegates will have a series of polls to participate in, but the upside is delegates can better demonstrate their opinion.
Each vote will follow the same format and contain the following.
The voting options.
As long as the total number of votes cast for the funding options is over >10M the temperature check will be considered met. If there isn't a clear winner for which level of incentives the chain should receive, a discussion can be had before the onchain proposal.
Here are the chains we'll make polls for (that are also live or going live very soon)(in no particular order). If anyone wants to add something, feel free to comment here.
Great point. Thankfully, we've done a good job establishing Oku as a Uniswap v3 frontend on new chains at this point, and we have a robust marketing strategy that we can apply for each of these.
It would be good to loop in the UF on these to see where they can lend a hand in marketing new chains and helping drive growth.
Also @Getty, from a marketing perspective, it's going to be important to account for how effective incentives will be considering we are routing new protocol front-end interactions via Oku.
If someone wants to visit Trader Joe, they use traderjoexyz.com. If someone wants to visit Quickswap, they use quickswap.exchange. Etc. Same with Uniswap. The different Oku domain will make this task more difficult, but hopefully consumers recognize Oku and Uniswap as one in the same. Certainly not an easy task, and Oku has gained a lot more mindshare lately. Wish Labs would help out somehow, but probably too much to ask for.
We echo the sentiment from @Doo_StableLab here. This discussion needs more time for delegates and the community to evaluate before reaching the Temp check phase.
We would have changed our voting but do worry about this finding. But if this is true @AbdullahUmar then doesn’t it make sense to only go with ones that Uniswap support on its front ends?
I think one of the nice secondary benefits of this proposal is that, if it is successful, it will at least incrementally loosen the coupling in public perception between the Uniswap Protocol and app.uniswap.org.
We had discussed the proposal with @AbdullahUmar prior to posting it. We went through the various chains and ultimately decided it made sense to post the proposal. We respect your decision to vote against it, however, in the future please reach out or post here so we have an opportunity give you the necessary information.
Thank you for clarification. That would been a helpful information.
The current direction is using Oku. Target chains, however, are not quite as comfortable with this.
We would have changed our voting but do worry about this finding. But if this is true @AbdullahUmar then doesn't it make sense to only go with ones that Uniswap support on its front ends?
Sure thing, I'll ask them to make a post.
Can we discuss more details about the potential success criteria and follow-ups?
We'll put together some stats on how the Onboarding Packages perform, and perhaps if delegates want something further the UF could put up an RFP.
At the moment I’m inclined to vote “Abstain” in particular because the vote is for all 10 chains at once and ~25% of the funds are planned to be spent on BSC. It’s difficult to see the justification for that
Separately, we agree opBNB could be good chain for the DAO to consider.
Thank you Getty. Looks like we're on track to send this through via an onchain vote--just a couple of things:
The Deployment Accountability Committee is currently having meetings with each of the target chains from the series of snapshots. Our goal for these conversations is to see whether or not the target chain is open to matching a portion of the incentives provided by Uniswap. The forms of contributions that we’re looking for are either bootstrapping pool liquidity on the target chain or also providing incentives on such pools. Another important point is to note that most of these chains are not aware of this program. We believe that there should be a degree of alignment between Uniswap and the target chains, so making sure they’re conscious of our commitment is important. It could open up more opportunities in the future, even if the target chains aren't open to matching today.
So far, we’ve conversed with Base, Moonbeam, Blast, and Taiko--but have active chats with all. Four meeting are taking place this week.
Base is on board with helping on the marketing side, if the Uni Foundation or Oku Tweet something related to the incentives that is pre-approved by Base's team, they'll RT. They're also very interested in exploring collaborations in the long-run, like with v4 permissioned pools where KYC'd actors can use Uniswap. That's tangential to this post, but again, good to know from an alignment perspective. It's also worth having these conversations since the chain can give input on the pools, like Base told us not to incentivize wBTC pools on their chain since it wasn't native--yet. So, that pool was replaced with a cbETH pool.
Blast is a straight "no" since they don't want to inflict bias towards any DEX, which is fine since this deployment is more so an immediate go-to-market strategy from Uniswap's end to quickly capture trading volume.
Moonbeam has spend some money on boostrapping pools as well as Oku integration costs, and they don't want their efforts to be wasted, so they'll come back to us shortly with a matching proposition from Moonbeam foundation. Not sure on the exact amounts yet.
Taiko will be mainnet sometime in April. Their team is keen on adding incentives and/or liquidity--currently discussing numbers.
Another final point is that chains like Mantle are prioritizing their native ecosystem. That's verbatim what they texted us. That's another good datapoint for the DAO to consider. Some chains are not worth incentivizing if we're just going to see mercenary liquidity. A Uni v3 fork on one of these chains will do better simply because of a brand shift and new token.
So, before we more to an onchain vote that bundles all of these up, perhaps its best to stagger them, with multiple rounds of voting. Biweekly, we could put up an onchain vote with three target chains, for example. Delegates should have a datapoint included in the onchain vote regarding where our relationship stands with the target chain. As of today, Base and Blast are the only ones we have a definite answer from regarding their alignment with this program.
Hi @Userisky,
Oku's frontend offers Uniswap v3 users a more advanced experience when interfacing with Uniswap v3 deployments. In addition to the trading interface, Oku has a robust analytics platform that includes user, position, pool, and token information. Both the Trade and Analytics sites are powered by Oku's in-depth Uniswap v3 API, which is available for developers and projects.
We believe there is more than enough room for both applications to exist, serve their respective demographics, and ultimately produce a better experience for everyone in the Uniswap ecosystem.
Specifically, for the Blast deployment, we were not aware that Uniswap Labs intended to add the Blast deployment to their frontend until after the onchain vote had passed. We deployed the Uniswap v3 contracts, set up the initial pools, verified the contracts, and relayed the information to the Uniswap Labs team for their integration.
Lastly, the Oku integration with Blast was completed 28 days ago. However, it took us longer than we thought to set up Angle Merkl's incentives since it was the first chain in the batch. Moving forward, we expect to move faster.
Hey, a couple questions / suggestions:
Hey, a couple questions / suggestions:
At the moment I'm inclined to vote "Abstain" in particular because the vote is for all 10 chains at once and ~25% of the funds are planned to be spent on BSC. It's difficult to see the justification for that, as I have doubts about the future growth potential of that chain relative to others (it's already one of the largest!) and the fit of Uniswap v3 and it's ability to take market share, as most of the tokens launched on BSC are fee-on-transfer, not supported by Uni v3. I might be wrong, but as of now it looks like opBNB would be much better fit, conceptually, to the incentive program.
Edit: voted for in the end, see here.
So, before we more to an onchain vote that bundles all of these up, perhaps its best to stagger them, with multiple rounds of voting. Biweekly, we could put up an onchain vote with three target chains, for example. Delegates should have a datapoint included in the onchain vote regarding where our relationship stands with the target chain. As of today, Base and Blast are the only ones we have a definite answer from regarding their alignment with this program.
So, before we more to an onchain vote that bundles all of these up, perhaps its best to stagger them, with multiple rounds of voting. Biweekly, we could put up an onchain vote with three target chains, for example. Delegates should have a datapoint included in the onchain vote regarding where our relationship stands with the target chain. As of today, Base and Blast are the only ones we have a definite answer from regarding their alignment with this program.
We find it a bit puzzling that despite the suggestion from @AbdullahUmar
@Getty and @GFXlabs team decided to go ahead and putting into "onchain vote that bundles all of these up" instead of taking more individual approaches or at least responding to his suggestions. While we understand that some community members want to push for them quickly, we do think it's best that the community takes its time and consideration.

Just want to provide some more clarity here. We’ve been in close contact with Getty through this process, although the recent forum posts may not seem to display this. As the accountability committee finalizes its conversations, the majority of the feedback we’ve received from target chain has been, well, more disappointing than we hoped. Most are not looking to match our incentive package, unfortunately. They’re open to co market on X, but providing liquidity or incentives seems to be a no-go for most chains. To that end, these multi chain expansions seem primarily to hinge on the Uniswap dao. It’s up to us to decide whether or not we’d like to expand into these markets with more force, even if the target chain isn’t willing to contribute to this initiative. The accountability committee will remain in close contact with these teams in case any forms of reciprocity arise.
I’ll be putting in a Yes vote shortly for this proposal since, as a potential bull run ensues, it's ideal for Uniswap to be well-positioned across these deployments.
Just want to provide some more clarity here. We’ve been in close contact with Getty through this process, although the recent forum posts may not seem to display this. As the accountability committee finalizes its conversations, the majority of the feedback we’ve received from target chain has been, well, more disappointing than we hoped. Most are not looking to match our incentive package, unfortunately. They’re open to co market on X, but providing liquidity or incentives seems to be a no-go for most chains. To that end, these multi chain expansions seem primarily to hinge on the Uniswap dao. It’s up to us to decide whether or not we’d like to expand into these markets with more force, even if the target chain isn’t willing to contribute to this initiative. The accountability committee will remain in close contact with these teams in case any forms of reciprocity arise.
I’ll be putting in a Yes vote shortly for this proposal since, as a potential bull run ensues, it's ideal for Uniswap to be well-positioned across these deployments.
Another note--chains aren't exactly incentivized to match this program. They have Uni v3 forks that are native to their ecosystem that naturally attract new users. It's akin to Uniswap, an established brand, expanding to a "new country"--but that country is more focused on supporting its "local businesses". The edge that Uniswap has is brand. People can rely on a trusted product that's uniform no matter where they go. The target chains see value in this secure brand. Many of their own users will only want to use Uniswap due to this value proposition. BUT the main issue here is front-end. The value of a front-end for retail is perhaps the most important aspect behind reliability and familiarity, and that's a large reason why chains don't want to double down with us regarding incentives. I'm not too sure how we can immediately address this. The current direction is using Oku. Target chains, however, are not quite as comfortable with this. I just wish we could do some type of white labeling with Oku and Uni Labs. It'll be interesting to see how the BNB incentives do since that deployment is on the Labs front-end.
The onchain proposal has been posted. We have updated the proposal description.
Voting will end on the 24th.
It's actually a quite difficult vote for us as while we don't think we should close off the opportunity of collaboration, but it makes more sense for those chains to provide incentive and also pay up for the integration costs. If the reasoning is simply because we want to expand on those chains, then shouldn't we look for most effective and efficient method? Rather than spending so much on operation?
Good question. I don't think all of them will pass, but if they do, you're right on a per-deployment basis; however, Oku already supports (or will very shortly) six of the above chains. The deployment and maintenance costs would only apply to new chains. As for Merkl, it also depends on what they currently support and how much the total number of rewards are approved for. In both cases, the infrastructure is the base cost and can be helpful for further chain growth.
Regarding the UNI rewards/pair point. Maybe we should. Once we get through this set of polls (or maybe in tandem), we can decide whether rewards should be paid in UNI and, if so, if a UNI pair makes sense or if we should distribute them in ETH.
Thank you to everyone who participated in the ten polls.
Here is the summary of the outcomes
Thank you to everyone who participated in the ten polls.
Here is the summary of the outcomes
Some of the temperature checks were quite close. For those, I default toward the popular vote, but if a delegate feels strongly that one of the amounts should be different, please post a comment.
Pools I have gone through the top DEXs for each chain and came up with 3-5 pools for each chain and the allocation amount of the incentives. Please take a look here and feel free to message me with comments or post on this thread. In addition to the pools, I also included the top DEXs for each chain. Generally, I was looking for three things: top pools by volume, top pools where the volume traded exceeds the liquidity available, and how the liquidity was distributed.
Next steps I'd like to send an onchain proposal this week that approves the following Onboarding Packages.
This excludes Taiko because their chain deployment is a few months away but includes Blast because the mainnet is expected in the immediate future. As for Moonbeam, the temperature check seemed indecisive. I figure we can always grant it an onboarding package at a later date.
Of the eight above chains, Oku currently supports all except for Blast, Mantle, Linea, and Polygon zkEVM. Oku has already announced Polygon zkEVM will be supported, so this proposal would only require three new additions.
Angle Merkl's current support can be found here. Merkl will need to support five new chains and their Uniswap v3 deployments; they support Polygon zkEVM, so they only need to add UniV3; they currently fully support base, and I need to confirm before the on-chain proposal that they can support zkSync.
Please review the linked spreadsheet and either post here or message me if you have feedback.
The below response reflects the views of L2Beat’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking and ideation of the two.
We have gone through the above discussion and we agree with the arguments that some targeted investments to increase Uniswap's position in the above chains would be beneficial in the long term.
The below response reflects the views of L2Beat’s governance team, composed of @kaereste and @Sinkas, and it’s based on the combined research, fact-checking and ideation of the two.
We have gone through the above discussion and we agree with the arguments that some targeted investments to increase Uniswap's position in the above chains would be beneficial in the long term.
At this point, we don't have a strong opinion about the exact amount that should be spent to have a justifiable effect, we would rather see it as an experiment that may need to be followed up with additional investment based on the results and effect observed.
However, looking at @WintermuteGovernance analysis we think it's reasonable to already distinguish chains that might use a higher investment already (BSC, zkSync Era, Avalanche) and others where we can take a more defensive approach. We are not sure about Blast as we don't see it covered in the discussion but from the current results we see a strong sentiment towards funding it with rather a higher amount, we will just abstain at this point.
Although we are voting to fund these onboarding packages, we would like to see some sort of post-implementation analysis included in the budget so that we can have some lessons learned and insights that would allow us to make a more informed decision on how to move forward.
But do think for bigger TVL networks and potentially big TVL networks, it might be worth the operation cost so we will be voting accordingly
We believe this should been a separate voting as well. Having it as a bundled vote to such masks true cost we afraid
Another point that comes to mind is whether paying out incentives in UNI makes the most sense. We'd need to bridge UNI to the destination chain and either bootstrap a market for it or expect liquidity providers to accept it as a reward. That might be fine, but perhaps we should consider trading the UNI for ETH, then bridging ETH, and using that for incentives. Open to discussion.
Quick follow-up here. I confirmed with the Merkl team that they can support zkSync.
The above proposal format seems like the right direction forward from a voting perspective. Let's reach out to a couple of the deployments next week to see if we can onboard like 2 chains for piloting this program.
As for what asset incentives should be paid out in: It’ll likely be too taxing for the DAO to create a market for the UNI token from scratch on multiple chains. The best bet is to probably have the escrow entity swap the UNI for either a stablecoin or ethereum. That asset would then be bridged to the destination chain. I would also assume that LPs simply prefer getting paid in a more reliable and liquid token, so it could further help incentivize liquidity.
Great to see community discussion to align objectives, thanks for posting and setting up the approach Getty! The questions you pose are all important to ensuring funded programs are structured properly. We faced similar challenges and decisions for the ARB LM program that we are currently working on with the DAO, and we have found valuable insights that could benefit this initiative.
As we understand it and similar to above community sentiments, three key questions to think about when considering leveraging liquidity mining for this purpose are:
I feel fairly strongly that the incentives should be paid in UNI tokens. One exception could be if the treasury swap is done – but almost none of the chains in Getty's list have a native token. (I'd add Mantle to the list, by the way!)
Reasons:
I feel fairly strongly that the incentives should be paid in UNI tokens. One exception could be if the treasury swap is done – but almost none of the chains in Getty's list have a native token. (I'd add Mantle to the list, by the way!)
Reasons:
This is a great initiative and we are super supportive of it.
Designing the onboarding package for new/nascent chains seems rather straightforward as we’re providing incentives in the hope of gaining meaningful TVL that then grows with the ecosystem.
This is a great initiative and we are super supportive of it.
Designing the onboarding package for new/nascent chains seems rather straightforward as we’re providing incentives in the hope of gaining meaningful TVL that then grows with the ecosystem.
But for existing and new(ish) chains the decision is a bit more nuanced so we quickly dug a little deeper into Uni V3’s market share for chains with available data:
(Note we are still working on data for BSC & Linea, but given discussion is moving quickly we thought we’d post what we have thus far)
Uni V3 TVL Rank Across Deployments
While the main focus is on volume market share, having context of Uni V3’s TVL position is still an important consideration as that’s what these LM efforts are targeting.
The table below illustrates Uni V3’s TVL rank on each respective deployment (ranked by worst to best). Clearly, there are a couple of deployments that could benefit from the growth program: zkSync Era, Scroll, Moonbeam, Avalanche, and BSC.
Source: DefiLlama
However, as we know TVL is not the clearest indicator of volume market share due to differing smart contract configurations amongst competitors, so let’s take a look at volume market share for chains with available data.
Uni V3: DEX Monthly Trading Volume Market Share Summary Stats
When looking at the 6-month (+ Jan) volume market share of Uni V3 across available deployments vary considerably.
Key takeaways:
Source: DefiLlama
(Missing chains: Moonbeam, Linea, Scroll, Rootstock, Boba)
Thus, we think it’s important for the DAO to assess the benefits of a growth packages for zkSync Era and Avalanche based on each chain’s activity and future prospects. Furthermore, it could be valuable to provide Base with a growth package despite being the dominant DEX to ensure we can solidify Uni V3’s position.
We’ve also included some charts below for individual chains to illustrate Uni V3’s volume market share amongst top competitors:
Celo:

Polygon:

zkSync Era:

Avalanche:

Optimism:

Base:

Arbitrum:

After looking at the available voting systems on Snapshot, I think our best course of action is to make individual polls for each chain. The downside is delegates will have a series of polls to participate in, but the upside is delegates can better demonstrate their opinion.
Each vote will follow the same format and contain the following.
After looking at the available voting systems on Snapshot, I think our best course of action is to make individual polls for each chain. The downside is delegates will have a series of polls to participate in, but the upside is delegates can better demonstrate their opinion.
Each vote will follow the same format and contain the following.
The voting options.
As long as the total number of votes cast for the funding options is over >10M the temperature check will be considered met. If there isn't a clear winner for which level of incentives the chain should receive, a discussion can be had before the onchain proposal.
Here are the chains we'll make polls for (that are also live or going live very soon)(in no particular order). If anyone wants to add something, feel free to comment here.
Great point. Thankfully, we've done a good job establishing Oku as a Uniswap v3 frontend on new chains at this point, and we have a robust marketing strategy that we can apply for each of these.
It would be good to loop in the UF on these to see where they can lend a hand in marketing new chains and helping drive growth.
Also @Getty, from a marketing perspective, it's going to be important to account for how effective incentives will be considering we are routing new protocol front-end interactions via Oku.
If someone wants to visit Trader Joe, they use traderjoexyz.com. If someone wants to visit Quickswap, they use quickswap.exchange. Etc. Same with Uniswap. The different Oku domain will make this task more difficult, but hopefully consumers recognize Oku and Uniswap as one in the same. Certainly not an easy task, and Oku has gained a lot more mindshare lately. Wish Labs would help out somehow, but probably too much to ask for.
We echo the sentiment from @Doo_StableLab here. This discussion needs more time for delegates and the community to evaluate before reaching the Temp check phase.
The above proposal format seems like the right direction forward from a voting perspective. Let's reach out to a couple of the deployments next week to see if we can onboard like 2 chains for piloting this program.
As for what asset incentives should be paid out in: It’ll likely be too taxing for the DAO to create a market for the UNI token from scratch on multiple chains. The best bet is to probably have the escrow entity swap the UNI for either a stablecoin or ethereum. That asset would then be bridged to the destination chain. I would also assume that LPs simply prefer getting paid in a more reliable and liquid token, so it could further help incentivize liquidity.
Selling millions of dollars of UNI tokens may raise alarms for certain stakeholders—just something to keep in mind. Another option is collaborating more closely with the destination chain to conduct a swap between the DAO’s UNI tokens and the other chain’s native token from its treasury. This way, there may not be immediate sell pressure for the UNI token, the target chain’s treasury can be further diversified, and if they choose, the destination chain can become a participant in the UNI DAO. Our allotment of the destination chain's native token can be used to incentivize the Uniswap pools. This scenario seems rather idealistic, especially with new chains. It would probably work best with an L2 like Arbitrum or Optimism, so for the most part, it’s best to stick with stables/ethereum.
Great to see community discussion to align objectives, thanks for posting and setting up the approach Getty! The questions you pose are all important to ensuring funded programs are structured properly. We faced similar challenges and decisions for the ARB LM program that we are currently working on with the DAO, and we have found valuable insights that could benefit this initiative.
As we understand it and similar to above community sentiments, three key questions to think about when considering leveraging liquidity mining for this purpose are:
From our experience, without alignment on definitions of success, due diligence on the environment where funds are deployed, and constant monitoring and optimization of the rewards allocations, liquidity mining programs can incur significant decreases in spend efficiency. Blue chip pools have higher variations in elasticity to rewards, requiring special attention and data insights per deployment. Is the community willing to spend more on these pools to capture market share? This could also be included in the vote.
Gauntlet’s Findings
In our latest liquidity mining work on Uniswap Arbitrum, we found that liquidity incentives are especially useful in bootstrapping liquidity and/or reviving pools with previously little to no activity, whereas large, blue-chip pools require more incentive capital to order for meaningful effects on market share, volume and LP revenue to be observed. Liquidity mining seems more effective on chains where Uniswap is still gaining a foothold, as shown by the stronger results on Arbitrum compared to Ethereum. This insight is particularly relevant to your plan of expanding Uniswap on emerging chains.
It’s important to strategically distribute these incentives. The goal should be to enhance the baseline activity of a pool sustainably, rather than merely creating a temporary spike in market share that dissipates once the incentives are withdrawn. The key is to ensure that improvements in price execution (as a result of increased liquidity) are maintained even after the removal of these incentives, thereby supporting a lasting increase in market share as more traders will be drawn to the destination with the best price execution.
We've detailed the performance of our liquidity mining program on Arbitrum in our midpoint retro report, which will be published on Monday. This report also includes insights on our methodology for future pool selection and other strategic considerations. For those interested in learning more on the key findings and how it relates to optimal allocation decisions, we will post it to the forums and follow up on this thread. For this current ARB program, it is too early to confidently assert the lasting impact ('stickiness') of the incentives, however, once these rewards are diminished or ceased, we are eager to share these findings with the community.
Incentive Budgets and Ongoing Optimization
When it comes to allocating the budget for incentives, it's crucial to base our decisions on the projected ROI (with respect to the primary objective function of this initiative). If the DAO agrees to extend rewards across various emerging chains, we should thoughtfully consider how to distribute the budget. For instance, should we allocate $300K for a Base rewards program and $200K for Binance Smart Chain? The key factors driving these decisions should include potential growth, chain-specific dynamics, and community engagement levels. Furthermore, what is the community’s approach to ongoing optimization efforts? We have observed that incentivized pools respond in a variety of ways, and require detailed monitoring to institute possible pivots in funding.
All to say there’s a trade off between speed via standards and efficacy enabled by optimization. We are keen to hear community feedback on the above thoughts and questions!
Ditto to @AbdullahUmar's points. We must get our ducks in a row before approaching the chains.
Also, we, delegates, need to recalibrate Uniswap's leverage and marketability toward these new chains. A core reason that I made this topic was because Uniswap's market position is pretty different today than what it was a year ago. It might not be realistic to request matching incentives or liquidity from some of the rising EVMs. Uniswap often goes up against local concentrated liquidity protocols or literal Uniswap v3 clones that the chain team favors.
Ditto to @AbdullahUmar's points. We must get our ducks in a row before approaching the chains.
Also, we, delegates, need to recalibrate Uniswap's leverage and marketability toward these new chains. A core reason that I made this topic was because Uniswap's market position is pretty different today than what it was a year ago. It might not be realistic to request matching incentives or liquidity from some of the rising EVMs. Uniswap often goes up against local concentrated liquidity protocols or literal Uniswap v3 clones that the chain team favors.
We need to approach this Onboarding Package as an introduction of Uniswap v3 to a new chain.
Uniswap could quickly take the lead on 5-10 chains without spending more than $2.5m. If one of these chains grows into a major player (like Arb/Op/Poly), it will have paid for the entire program multiple times over (assuming the fee switch is someday turned). Providing a modest onboarding package helps Uniswap diversify and develop new markets without waiting to see which chains become long-term relevant - at which point it is often too late or too costly to get market share.
Let's keep this topic to a modest Onboarding Package. Once we have established it, we can determine which chains/deployments make sense to double down on.
Great questions.
Will formalizing this package require an onchain vote? What will that vote execute? Or will onchain votes only occur every time we finalize a deal with a target chain?
Great questions.
Will formalizing this package require an onchain vote? What will that vote execute? Or will onchain votes only occur every time we finalize a deal with a target chain?
Should we predetermine a budget for this program, or is this better done on a case by case basis? Predetermining may have its benefits with negotiating a discount with Merkl.
Who should escrow the funds? UF, accountability committee, or someone else? We'll need someone to take on this role, whether we're budgeting from the start or working case by case.
I checked with the UF, but they are unable to play the escrow role here. It would be great if the accountability committee could play that role. Generally, the ops work required should be minimal.
Thank you for providing this TVL and volume overview @WintermuteGovernance!
Off the bat, there are a couple of chains worth circling back to regarding this program. The accountability committee will get started with this process as soon as the incentive package is finalized. But from the data above, and after skimming DeFiLlama a bit further, it seems like Base, zkSync, Scroll, Linea, Polygon zkEVM, and Avalanche are decent contenders from a growth perspective.
Thank you for providing this TVL and volume overview @WintermuteGovernance!
Off the bat, there are a couple of chains worth circling back to regarding this program. The accountability committee will get started with this process as soon as the incentive package is finalized. But from the data above, and after skimming DeFiLlama a bit further, it seems like Base, zkSync, Scroll, Linea, Polygon zkEVM, and Avalanche are decent contenders from a growth perspective.
This is just food for thought. First priority should be finalizing the incentive package.
Happy Monday, everyone. I've created ten polls. Each temperature check has the same text and options.
[quote] This temperature check will gauge delegates' interest/support for deploying the onboarding package to [chain].
I've attached the forum thread for the full context.
Happy Monday, everyone. I've created ten polls. Each temperature check has the same text and options.
[quote] This temperature check will gauge delegates' interest/support for deploying the onboarding package to [chain].
I've attached the forum thread for the full context.
TLDR: The Uniswap Onboarding Package is for new deployments of Uniswap v3 to get set up with three-month liquidity incentives, a frontend (Oku), and incentives distribution tooling (Angle Merkl). These resources will help position Uniswap to have a formidable presence on new EVM chains.
How the vote works: The temperature check will be considered met as long as the total number of votes cast for the funding options is over >10M. If there isn't a clear winner for which level of incentives the chain should receive, a discussion can be had before the onchain proposal.
Notes:
Polls:
Voting closes Saturday
There are two things we're trying to take care of. The first aspect is finalizing the package. The second part is determining which chains we should retroactively enable incentives on. Before speaking to chains about this program, we should first finalize the package itself.
We need to determine how stringent or flexible we'll be with the package. I’d encourage maintaining a degree of flexibility with the package parameters since this is a not a one size fits all scenario. Perhaps the initial package should give a range of guidelines, like the incentive amount a chain is eligible for lies between $250k - $1M. Getty lays out some of the parameters as follows:
There are two things we're trying to take care of. The first aspect is finalizing the package. The second part is determining which chains we should retroactively enable incentives on. Before speaking to chains about this program, we should first finalize the package itself.
We need to determine how stringent or flexible we'll be with the package. I’d encourage maintaining a degree of flexibility with the package parameters since this is a not a one size fits all scenario. Perhaps the initial package should give a range of guidelines, like the incentive amount a chain is eligible for lies between $250k - $1M. Getty lays out some of the parameters as follows:
amount of incentives, the pools to incentivize, duration, incentivization tool, and frontend
Incentive amount, pools, and duration should ideally be more flexible. Each chain has a different degree of maturity, and quite often, they're the best judges of which pools to activate and the level of incentivization required. The most probable conclusion will be incentivizing USDC, WBTC, WETH, and/or native token pools, but the final decision should be made after discussion with the target chain. Of course, if the chain wants to incentivize non-standard pools with, say, long-tail assets, we have the authority to deny such requests.
We can use different criteria to determine incentive amount and duration. One key aspect from the DAO's side will be our perspective on how much growth the target chain will bring to Uniswap. A new chain with a lot of potential and a nascent DeFi ecosystem should receive a larger allotment and perhaps a more aggressive incentive timeline. Another aspect is a matching program. We could offer better terms to chains that would like to offer incentives or protocol owned liquidity themselves to further compound the effects of this program. These determinations, I think, should be recommended by the accountability committee to reduce the DAO's overhead.
Potential Parameter and Chain Selection Process:
As for the other parameters, I doubt most protocols would have issues with tooling (Merkl) & front-end (Oku), as long as we have a streamlined process for implementing these incentives, so these two parameters can be more or less fixed.
Now, before reaching out to the target chains and advertising this program, a couple aspects around the package should be finalized.
The next step for this discussion is to determine what chain(s) the DAO would be interested in retroactively deploying liquidity incentives to and eventually broadcasting the Onboarding Package to new chains so they know they can apply for it.
Here is a table of current support:

The next step for this discussion is to determine what chain(s) the DAO would be interested in retroactively deploying liquidity incentives to and eventually broadcasting the Onboarding Package to new chains so they know they can apply for it.
Here is a table of current support:

In the immediate future, I think rolling this package out to Polygon zkEVM, Scroll, and Linea would be a great start. I also want to flag that Blast will launch sometime in February. It would be great if Uniswap were there on launch day.
If delegates have other chains they would like to include in the initial polls, please message me or post them here.
For the temperature check, I have two ideas.
I'd like to post the temperature check on Thursday/Friday. If delegates prefer one of the two options or have their own idea, it would be great to get some feedback.
Thank you, I'm glad you think it is a good initiative.
Assuming a deploying chain is not guaranteed liquidity for bootstrapping, and there will be a request process, it is appropriate that the deploying chain specify an amount that is right-sized for them with a specific plan in place for its utilization. The goal here is to increase the efficiency of the funding while encouraging the recipient to provide clear intentions for its use.
Thank you, I'm glad you think it is a good initiative.
Assuming a deploying chain is not guaranteed liquidity for bootstrapping, and there will be a request process, it is appropriate that the deploying chain specify an amount that is right-sized for them with a specific plan in place for its utilization. The goal here is to increase the efficiency of the funding while encouraging the recipient to provide clear intentions for its use.
Would you be open to this decision being tasked to a smaller group or attached to the incumbent chain’s deployment proposal? Not to expand their scope, but for the sake of simplicity we would be comfortable if the existing Uniswap Deployments Accountability Committee had some discretion or authority here.
To mitigate spam or any misuse of funds, we suggest a pre-defined list of pools that would be valuable in attracting liquidity for Uniswap ahead of time.
And this should of course happen before the temperature check as the chains would know their decision will impact the voting decision by the Uniswap community later. I think waiting for maybe 1 month to potentially get millions or at least chains able to match the amount the Uniswap community provide is worthwhile.
Amazing post! Thank you
I overall would recommend taking the idea a bit slowly so that more community can get involved in. For example, I think you already closed the poll and 1 or 2 days is not long enough to gather more feedbacks.
The below poll is to collect a quick sample of opinions from delegates on what they think a good amount is.
Very supportive of this initiative - i love the framing of a deployment vote changing from a rubber stamp to an action with an actual cost. Let me know if there's anything I/the UF can do to help.
I would also suggest maybe the new Accountability Committee members especially @AbdullahUmar (since he himself dealt with many chain onboardings) can spend a month to negotiate with chains to amplify as many of the chains actually committed to provide millions or at least significant amount of incentive to Uniswap ecosystem which they did not keep the promise. It makes sense that the community brings up the discussion and the chains themselves should also be willing to match such
Thanks for starting this discussion @getty; we agree with an incentive program to bootstrap liquidity on promising chains deploying Uniswap. This could strengthen our position where we are not the leading protocol in these chains' early stages of growth. Some initial thoughts:
Thanks for starting this discussion @getty; we agree with an incentive program to bootstrap liquidity on promising chains deploying Uniswap. This could strengthen our position where we are not the leading protocol in these chains' early stages of growth. Some initial thoughts:
Regarding the amount discussed, a higher incentive would allow chains to add more pools, extend the incentive period or raise the incentives on specific pools as the chains see fit. For this reason, we support up to the 750k option, but as a maximum amount to be requested.
Assuming a deploying chain is not guaranteed liquidity for bootstrapping, and there will be a request process, it is appropriate that the deploying chain specify an amount that is right-sized for them with a specific plan in place for its utilization. The goal here is to increase the efficiency of the funding while encouraging the recipient to provide clear intentions for its use.
So, it will be key that delegates decide which chains make sense to deploy this onboarding package and which do not.
Would you be open to this decision being tasked to a smaller group or attached to the incumbent chain's deployment proposal? Not to expand their scope, but for the sake of simplicity we would be comfortable if the existing Uniswap Deployments Accountability Committee had some discretion or authority here.
To mitigate spam or any misuse of funds, we suggest a pre-defined list of pools that would be valuable in attracting liquidity for Uniswap ahead of time. This list would also have the added benefit of streamlining decision-making and serve as a guide for the deploying chains.
karpatkey has experience working with Gnosis Chain bootstrapping AMM pools and pairs. In addition, we would happily serve this initiative as a non-custodial layer between the incentives protocol (like Merkl) and the DAO-related wallets. With the use of the Zodiac protocol and its role modifiers, it is possible to grant specific permission for a manager who will act on the DAO's behalf when interacting with external protocols.
GM. Thanks for the quick reply.
I agree it's important for the process to be open. I welcome anyone in the ecosystem to post other avenues for delegates to consider for both the frontend or the reward system.
GM. Thanks for the quick reply.
I agree it's important for the process to be open. I welcome anyone in the ecosystem to post other avenues for delegates to consider for both the frontend or the reward system.
Regarding the Merkl compensation. The one-time setup fee of €20k for going to an entirely new chain and €10k for a new Uniswap v3 instance on a chain they support were based on $250k of incentives. Since we're discussing increasing the incentives, I spoke with Merkl about updating their pricing. They have offered a 25% discount on their base 3% fee for incentives distributed between $2.5m-$5m, a 50% discount on incentives distributed between $5m-$10m, and a 75% discount on all incentives above $10m in a 365-day period.
For the pools to direct incentives toward, ETH-USDC 0.30%, WBTC-USDC 0.30%, and USDC-USDT 0.01% would be the three anchor pools; then, a fourth pool could be considered if there is a popular chain-specific asset. For example, if we were to deploy this program on Polygon, a MATIC-USDC pair would be a good idea. Generally, we should stick with blue chips.
As for the Merkl configuration, I've been trying to gather some data points as there doesn't seem to be a "best" configuration. Currently, the Uniswap Arbitrum Merkl incentives use a 1%-1%-98% (token0-token1-fees), which heavily directs liquidity toward the most actively contributing liquidity positions. That may be good for blue-chip pairs like the ones I'm suggesting. If you or other delegates have thoughts on the configuration, it would be great to exchange notes.
Now, for amounts, when in doubt, we should default to less rather than more for the program's inception, but then, in exchange, we should be liberal in deploying the program. If we default with a lower amount, like $250k or $500k, but then decide for a specific chain to go with a higher number, it's easier to go up rather than down.
You're right that creating a new chain has never been easier. So, it will be key that delegates decide which chains make sense to deploy this onboarding package and which do not. Although, we should be hesitant to set hard rules like a TVL requirement. I suggest we leave it to chains to make their pitch to the DAO and for delegates to conduct their due diligence. Ultimately, this package is meant to be easily deployable to new chains, but changes could be made on a chain-by-chain basis.
@kfx, thanks for the support.
Regarding the reward distribution options. Setting aside a custom build, there aren't too many options. Merkl seems to have the most flexible one because it doesn't require users to stake their position. Merkl runs an off-chain program once an hour to direct incentives. Since it's an off-chain calculation, they can allocate rewards more easily and efficiently than in an on-chain program.
@kfx, thanks for the support.
Regarding the reward distribution options. Setting aside a custom build, there aren't too many options. Merkl seems to have the most flexible one because it doesn't require users to stake their position. Merkl runs an off-chain program once an hour to direct incentives. Since it's an off-chain calculation, they can allocate rewards more easily and efficiently than in an on-chain program.
Another important thing to remember is the ease of integrating new chains. When I spoke with them about this idea at the end of last week, they were excited and said that going to new EVMs is not too hard for them. They need a one-time setup fee of €20k for going to an entirely new chain and €10k for a new Uniswap v3 instance on a chain they have support for.
It's also worth noting that other projects on the new chain looking for a liquidity incentive management system could use Merkl and Uniswap v3.
If there is a particular avenue you think should be explored, feel free to post it here.
As for frontend options, I'm biased, of course, but I think Oku is in its own category. The other Uniswap v3 frontends tend to be much simpler and generally rely on other infrastructure. With Oku, we've built it to be entirely standalone, and we have a lot of experience deploying the core protocol and the necessary periphery contracts for new deployments. Outside of Uniswap Labs, I don't think more than a few other folks have that experience. Lastly, we only support Uniswap v3 on Oku. Most other interfaces support competing DEXs.
@Doo_StableLab Good question. My hope is that three months of incentives and the deployment of Merkl and Oku will give Uniswap a good hold. Obviously, when incentives end, we can expect a drop in liquidity, but the hope is it's not substantial. Perhaps in the 3rd month, the DAO can discuss further incentives if delegates think it would be useful. It will be easier since Merkl and Oku will already be live.
A few delegates have mentioned adjusting the incentive amount for the Onboarding package. I had initially suggested $250k, mostly because I thought it was a reasonable minimum for the program.
In my initial post, I estimated that $250k in incentives, distributed over three months at a reward rate of ~10%, would incentivize approximately $10M in liquidity for three months.
A few delegates have mentioned adjusting the incentive amount for the Onboarding package. I had initially suggested $250k, mostly because I thought it was a reasonable minimum for the program.
In my initial post, I estimated that $250k in incentives, distributed over three months at a reward rate of ~10%, would incentivize approximately $10M in liquidity for three months.
The below poll is to collect a quick sample of opinions from delegates on what they think a good amount is. [poll type=regular results=on_vote public=true chartType=bar close=2024-01-25T05:45:00.000Z]
I do think one thing to do note is once the incentive runs out , how to continue to be competitive.
Another is also whether it makes sense to spread to all mainnets and L2s but rather focus on 2-4 viable chains and really push toward those selected chains.
Thanks for the writeup @getty! Some more thoughts.
I think it's important to everyone to see that the options we select for the package are the best available options at the moment, not because of personal ties to delegates or other reasons. You have put forward a clear rationale why Oku and the Merkl protocol are good options suitable for the task. What would make most sense to me is to invite anyone to come forward with any alternatives they offer / could support with votes (perhaps in this thread itself). If there are alternatives, we vote for them. If there are not, we go with Oku & Merkl protocol.
I'd support such a incentive package. For what it's worth, the benefits from a $ spent on incentivizing liquidity on a fledgling chain is likely to be much higher than from the same amount spent on an established one.
However, I think it would be better to do a brief survey of the available options for the frontend and the reward distribution system. It would help to make a more informed decision, and identify any shortcomings / blockers in the existing offers. Maybe foundation can arrange it?
The above proposal format seems like the right direction forward from a voting perspective. Let's reach out to a couple of the deployments next week to see if we can onboard like 2 chains for piloting this program.
As for what asset incentives should be paid out in: It’ll likely be too taxing for the DAO to create a market for the UNI token from scratch on multiple chains. The best bet is to probably have the escrow entity swap the UNI for either a stablecoin or ethereum. That asset would then be bridged to the destination chain. I would also assume that LPs simply prefer getting paid in a more reliable and liquid token, so it could further help incentivize liquidity.
Selling millions of dollars of UNI tokens may raise alarms for certain stakeholders—just something to keep in mind. Another option is collaborating more closely with the destination chain to conduct a swap between the DAO’s UNI tokens and the other chain’s native token from its treasury. This way, there may not be immediate sell pressure for the UNI token, the target chain’s treasury can be further diversified, and if they choose, the destination chain can become a participant in the UNI DAO. Our allotment of the destination chain's native token can be used to incentivize the Uniswap pools. This scenario seems rather idealistic, especially with new chains. It would probably work best with an L2 like Arbitrum or Optimism, so for the most part, it’s best to stick with stables/ethereum.
Great to see community discussion to align objectives, thanks for posting and setting up the approach Getty! The questions you pose are all important to ensuring funded programs are structured properly. We faced similar challenges and decisions for the ARB LM program that we are currently working on with the DAO, and we have found valuable insights that could benefit this initiative.
As we understand it and similar to above community sentiments, three key questions to think about when considering leveraging liquidity mining for this purpose are:
From our experience, without alignment on definitions of success, due diligence on the environment where funds are deployed, and constant monitoring and optimization of the rewards allocations, liquidity mining programs can incur significant decreases in spend efficiency. Blue chip pools have higher variations in elasticity to rewards, requiring special attention and data insights per deployment. Is the community willing to spend more on these pools to capture market share? This could also be included in the vote.
Gauntlet’s Findings
In our latest liquidity mining work on Uniswap Arbitrum, we found that liquidity incentives are especially useful in bootstrapping liquidity and/or reviving pools with previously little to no activity, whereas large, blue-chip pools require more incentive capital to order for meaningful effects on market share, volume and LP revenue to be observed. Liquidity mining seems more effective on chains where Uniswap is still gaining a foothold, as shown by the stronger results on Arbitrum compared to Ethereum. This insight is particularly relevant to your plan of expanding Uniswap on emerging chains.
It’s important to strategically distribute these incentives. The goal should be to enhance the baseline activity of a pool sustainably, rather than merely creating a temporary spike in market share that dissipates once the incentives are withdrawn. The key is to ensure that improvements in price execution (as a result of increased liquidity) are maintained even after the removal of these incentives, thereby supporting a lasting increase in market share as more traders will be drawn to the destination with the best price execution.
We've detailed the performance of our liquidity mining program on Arbitrum in our midpoint retro report, which will be published on Monday. This report also includes insights on our methodology for future pool selection and other strategic considerations. For those interested in learning more on the key findings and how it relates to optimal allocation decisions, we will post it to the forums and follow up on this thread. For this current ARB program, it is too early to confidently assert the lasting impact ('stickiness') of the incentives, however, once these rewards are diminished or ceased, we are eager to share these findings with the community.
Incentive Budgets and Ongoing Optimization
When it comes to allocating the budget for incentives, it's crucial to base our decisions on the projected ROI (with respect to the primary objective function of this initiative). If the DAO agrees to extend rewards across various emerging chains, we should thoughtfully consider how to distribute the budget. For instance, should we allocate $300K for a Base rewards program and $200K for Binance Smart Chain? The key factors driving these decisions should include potential growth, chain-specific dynamics, and community engagement levels. Furthermore, what is the community’s approach to ongoing optimization efforts? We have observed that incentivized pools respond in a variety of ways, and require detailed monitoring to institute possible pivots in funding.
All to say there’s a trade off between speed via standards and efficacy enabled by optimization. We are keen to hear community feedback on the above thoughts and questions!
Ditto to @AbdullahUmar's points. We must get our ducks in a row before approaching the chains.
Also, we, delegates, need to recalibrate Uniswap's leverage and marketability toward these new chains. A core reason that I made this topic was because Uniswap's market position is pretty different today than what it was a year ago. It might not be realistic to request matching incentives or liquidity from some of the rising EVMs. Uniswap often goes up against local concentrated liquidity protocols or literal Uniswap v3 clones that the chain team favors.
Ditto to @AbdullahUmar's points. We must get our ducks in a row before approaching the chains.
Also, we, delegates, need to recalibrate Uniswap's leverage and marketability toward these new chains. A core reason that I made this topic was because Uniswap's market position is pretty different today than what it was a year ago. It might not be realistic to request matching incentives or liquidity from some of the rising EVMs. Uniswap often goes up against local concentrated liquidity protocols or literal Uniswap v3 clones that the chain team favors.
We need to approach this Onboarding Package as an introduction of Uniswap v3 to a new chain.
Uniswap could quickly take the lead on 5-10 chains without spending more than $2.5m. If one of these chains grows into a major player (like Arb/Op/Poly), it will have paid for the entire program multiple times over (assuming the fee switch is someday turned). Providing a modest onboarding package helps Uniswap diversify and develop new markets without waiting to see which chains become long-term relevant - at which point it is often too late or too costly to get market share.
Let's keep this topic to a modest Onboarding Package. Once we have established it, we can determine which chains/deployments make sense to double down on.
Great questions.
Will formalizing this package require an onchain vote? What will that vote execute? Or will onchain votes only occur every time we finalize a deal with a target chain?
Great questions.
Will formalizing this package require an onchain vote? What will that vote execute? Or will onchain votes only occur every time we finalize a deal with a target chain?
Should we predetermine a budget for this program, or is this better done on a case by case basis? Predetermining may have its benefits with negotiating a discount with Merkl.
Who should escrow the funds? UF, accountability committee, or someone else? We'll need someone to take on this role, whether we're budgeting from the start or working case by case.
I checked with the UF, but they are unable to play the escrow role here. It would be great if the accountability committee could play that role. Generally, the ops work required should be minimal.
Thank you for providing this TVL and volume overview @WintermuteGovernance!
Off the bat, there are a couple of chains worth circling back to regarding this program. The accountability committee will get started with this process as soon as the incentive package is finalized. But from the data above, and after skimming DeFiLlama a bit further, it seems like Base, zkSync, Scroll, Linea, Polygon zkEVM, and Avalanche are decent contenders from a growth perspective.
Thank you for providing this TVL and volume overview @WintermuteGovernance!
Off the bat, there are a couple of chains worth circling back to regarding this program. The accountability committee will get started with this process as soon as the incentive package is finalized. But from the data above, and after skimming DeFiLlama a bit further, it seems like Base, zkSync, Scroll, Linea, Polygon zkEVM, and Avalanche are decent contenders from a growth perspective.
This is just food for thought. First priority should be finalizing the incentive package.
Happy Monday, everyone. I've created ten polls. Each temperature check has the same text and options.
[quote] This temperature check will gauge delegates' interest/support for deploying the onboarding package to [chain].
I've attached the forum thread for the full context.
Happy Monday, everyone. I've created ten polls. Each temperature check has the same text and options.
[quote] This temperature check will gauge delegates' interest/support for deploying the onboarding package to [chain].
I've attached the forum thread for the full context.
TLDR: The Uniswap Onboarding Package is for new deployments of Uniswap v3 to get set up with three-month liquidity incentives, a frontend (Oku), and incentives distribution tooling (Angle Merkl). These resources will help position Uniswap to have a formidable presence on new EVM chains.
How the vote works: The temperature check will be considered met as long as the total number of votes cast for the funding options is over >10M. If there isn't a clear winner for which level of incentives the chain should receive, a discussion can be had before the onchain proposal.
Notes:
Polls:
Voting closes Saturday
There are two things we're trying to take care of. The first aspect is finalizing the package. The second part is determining which chains we should retroactively enable incentives on. Before speaking to chains about this program, we should first finalize the package itself.
We need to determine how stringent or flexible we'll be with the package. I’d encourage maintaining a degree of flexibility with the package parameters since this is a not a one size fits all scenario. Perhaps the initial package should give a range of guidelines, like the incentive amount a chain is eligible for lies between $250k - $1M. Getty lays out some of the parameters as follows:
There are two things we're trying to take care of. The first aspect is finalizing the package. The second part is determining which chains we should retroactively enable incentives on. Before speaking to chains about this program, we should first finalize the package itself.
We need to determine how stringent or flexible we'll be with the package. I’d encourage maintaining a degree of flexibility with the package parameters since this is a not a one size fits all scenario. Perhaps the initial package should give a range of guidelines, like the incentive amount a chain is eligible for lies between $250k - $1M. Getty lays out some of the parameters as follows:
amount of incentives, the pools to incentivize, duration, incentivization tool, and frontend
Incentive amount, pools, and duration should ideally be more flexible. Each chain has a different degree of maturity, and quite often, they're the best judges of which pools to activate and the level of incentivization required. The most probable conclusion will be incentivizing USDC, WBTC, WETH, and/or native token pools, but the final decision should be made after discussion with the target chain. Of course, if the chain wants to incentivize non-standard pools with, say, long-tail assets, we have the authority to deny such requests.
We can use different criteria to determine incentive amount and duration. One key aspect from the DAO's side will be our perspective on how much growth the target chain will bring to Uniswap. A new chain with a lot of potential and a nascent DeFi ecosystem should receive a larger allotment and perhaps a more aggressive incentive timeline. Another aspect is a matching program. We could offer better terms to chains that would like to offer incentives or protocol owned liquidity themselves to further compound the effects of this program. These determinations, I think, should be recommended by the accountability committee to reduce the DAO's overhead.
Potential Parameter and Chain Selection Process:
As for the other parameters, I doubt most protocols would have issues with tooling (Merkl) & front-end (Oku), as long as we have a streamlined process for implementing these incentives, so these two parameters can be more or less fixed.
Now, before reaching out to the target chains and advertising this program, a couple aspects around the package should be finalized.
The next step for this discussion is to determine what chain(s) the DAO would be interested in retroactively deploying liquidity incentives to and eventually broadcasting the Onboarding Package to new chains so they know they can apply for it.
Here is a table of current support:

The next step for this discussion is to determine what chain(s) the DAO would be interested in retroactively deploying liquidity incentives to and eventually broadcasting the Onboarding Package to new chains so they know they can apply for it.
Here is a table of current support:

In the immediate future, I think rolling this package out to Polygon zkEVM, Scroll, and Linea would be a great start. I also want to flag that Blast will launch sometime in February. It would be great if Uniswap were there on launch day.
If delegates have other chains they would like to include in the initial polls, please message me or post them here.
For the temperature check, I have two ideas.
I'd like to post the temperature check on Thursday/Friday. If delegates prefer one of the two options or have their own idea, it would be great to get some feedback.
Thank you, I'm glad you think it is a good initiative.
Assuming a deploying chain is not guaranteed liquidity for bootstrapping, and there will be a request process, it is appropriate that the deploying chain specify an amount that is right-sized for them with a specific plan in place for its utilization. The goal here is to increase the efficiency of the funding while encouraging the recipient to provide clear intentions for its use.
Thank you, I'm glad you think it is a good initiative.
Assuming a deploying chain is not guaranteed liquidity for bootstrapping, and there will be a request process, it is appropriate that the deploying chain specify an amount that is right-sized for them with a specific plan in place for its utilization. The goal here is to increase the efficiency of the funding while encouraging the recipient to provide clear intentions for its use.
Would you be open to this decision being tasked to a smaller group or attached to the incumbent chain’s deployment proposal? Not to expand their scope, but for the sake of simplicity we would be comfortable if the existing Uniswap Deployments Accountability Committee had some discretion or authority here.
To mitigate spam or any misuse of funds, we suggest a pre-defined list of pools that would be valuable in attracting liquidity for Uniswap ahead of time.
And this should of course happen before the temperature check as the chains would know their decision will impact the voting decision by the Uniswap community later. I think waiting for maybe 1 month to potentially get millions or at least chains able to match the amount the Uniswap community provide is worthwhile.
Amazing post! Thank you
I overall would recommend taking the idea a bit slowly so that more community can get involved in. For example, I think you already closed the poll and 1 or 2 days is not long enough to gather more feedbacks.
The below poll is to collect a quick sample of opinions from delegates on what they think a good amount is.
Very supportive of this initiative - i love the framing of a deployment vote changing from a rubber stamp to an action with an actual cost. Let me know if there's anything I/the UF can do to help.
I would also suggest maybe the new Accountability Committee members especially @AbdullahUmar (since he himself dealt with many chain onboardings) can spend a month to negotiate with chains to amplify as many of the chains actually committed to provide millions or at least significant amount of incentive to Uniswap ecosystem which they did not keep the promise. It makes sense that the community brings up the discussion and the chains themselves should also be willing to match such
Thanks for starting this discussion @getty; we agree with an incentive program to bootstrap liquidity on promising chains deploying Uniswap. This could strengthen our position where we are not the leading protocol in these chains' early stages of growth. Some initial thoughts:
Thanks for starting this discussion @getty; we agree with an incentive program to bootstrap liquidity on promising chains deploying Uniswap. This could strengthen our position where we are not the leading protocol in these chains' early stages of growth. Some initial thoughts:
Regarding the amount discussed, a higher incentive would allow chains to add more pools, extend the incentive period or raise the incentives on specific pools as the chains see fit. For this reason, we support up to the 750k option, but as a maximum amount to be requested.
Assuming a deploying chain is not guaranteed liquidity for bootstrapping, and there will be a request process, it is appropriate that the deploying chain specify an amount that is right-sized for them with a specific plan in place for its utilization. The goal here is to increase the efficiency of the funding while encouraging the recipient to provide clear intentions for its use.
So, it will be key that delegates decide which chains make sense to deploy this onboarding package and which do not.
Would you be open to this decision being tasked to a smaller group or attached to the incumbent chain's deployment proposal? Not to expand their scope, but for the sake of simplicity we would be comfortable if the existing Uniswap Deployments Accountability Committee had some discretion or authority here.
To mitigate spam or any misuse of funds, we suggest a pre-defined list of pools that would be valuable in attracting liquidity for Uniswap ahead of time. This list would also have the added benefit of streamlining decision-making and serve as a guide for the deploying chains.
karpatkey has experience working with Gnosis Chain bootstrapping AMM pools and pairs. In addition, we would happily serve this initiative as a non-custodial layer between the incentives protocol (like Merkl) and the DAO-related wallets. With the use of the Zodiac protocol and its role modifiers, it is possible to grant specific permission for a manager who will act on the DAO's behalf when interacting with external protocols.
GM. Thanks for the quick reply.
I agree it's important for the process to be open. I welcome anyone in the ecosystem to post other avenues for delegates to consider for both the frontend or the reward system.
GM. Thanks for the quick reply.
I agree it's important for the process to be open. I welcome anyone in the ecosystem to post other avenues for delegates to consider for both the frontend or the reward system.
Regarding the Merkl compensation. The one-time setup fee of €20k for going to an entirely new chain and €10k for a new Uniswap v3 instance on a chain they support were based on $250k of incentives. Since we're discussing increasing the incentives, I spoke with Merkl about updating their pricing. They have offered a 25% discount on their base 3% fee for incentives distributed between $2.5m-$5m, a 50% discount on incentives distributed between $5m-$10m, and a 75% discount on all incentives above $10m in a 365-day period.
For the pools to direct incentives toward, ETH-USDC 0.30%, WBTC-USDC 0.30%, and USDC-USDT 0.01% would be the three anchor pools; then, a fourth pool could be considered if there is a popular chain-specific asset. For example, if we were to deploy this program on Polygon, a MATIC-USDC pair would be a good idea. Generally, we should stick with blue chips.
As for the Merkl configuration, I've been trying to gather some data points as there doesn't seem to be a "best" configuration. Currently, the Uniswap Arbitrum Merkl incentives use a 1%-1%-98% (token0-token1-fees), which heavily directs liquidity toward the most actively contributing liquidity positions. That may be good for blue-chip pairs like the ones I'm suggesting. If you or other delegates have thoughts on the configuration, it would be great to exchange notes.
Now, for amounts, when in doubt, we should default to less rather than more for the program's inception, but then, in exchange, we should be liberal in deploying the program. If we default with a lower amount, like $250k or $500k, but then decide for a specific chain to go with a higher number, it's easier to go up rather than down.
You're right that creating a new chain has never been easier. So, it will be key that delegates decide which chains make sense to deploy this onboarding package and which do not. Although, we should be hesitant to set hard rules like a TVL requirement. I suggest we leave it to chains to make their pitch to the DAO and for delegates to conduct their due diligence. Ultimately, this package is meant to be easily deployable to new chains, but changes could be made on a chain-by-chain basis.
@kfx, thanks for the support.
Regarding the reward distribution options. Setting aside a custom build, there aren't too many options. Merkl seems to have the most flexible one because it doesn't require users to stake their position. Merkl runs an off-chain program once an hour to direct incentives. Since it's an off-chain calculation, they can allocate rewards more easily and efficiently than in an on-chain program.
@kfx, thanks for the support.
Regarding the reward distribution options. Setting aside a custom build, there aren't too many options. Merkl seems to have the most flexible one because it doesn't require users to stake their position. Merkl runs an off-chain program once an hour to direct incentives. Since it's an off-chain calculation, they can allocate rewards more easily and efficiently than in an on-chain program.
Another important thing to remember is the ease of integrating new chains. When I spoke with them about this idea at the end of last week, they were excited and said that going to new EVMs is not too hard for them. They need a one-time setup fee of €20k for going to an entirely new chain and €10k for a new Uniswap v3 instance on a chain they have support for.
It's also worth noting that other projects on the new chain looking for a liquidity incentive management system could use Merkl and Uniswap v3.
If there is a particular avenue you think should be explored, feel free to post it here.
As for frontend options, I'm biased, of course, but I think Oku is in its own category. The other Uniswap v3 frontends tend to be much simpler and generally rely on other infrastructure. With Oku, we've built it to be entirely standalone, and we have a lot of experience deploying the core protocol and the necessary periphery contracts for new deployments. Outside of Uniswap Labs, I don't think more than a few other folks have that experience. Lastly, we only support Uniswap v3 on Oku. Most other interfaces support competing DEXs.
@Doo_StableLab Good question. My hope is that three months of incentives and the deployment of Merkl and Oku will give Uniswap a good hold. Obviously, when incentives end, we can expect a drop in liquidity, but the hope is it's not substantial. Perhaps in the 3rd month, the DAO can discuss further incentives if delegates think it would be useful. It will be easier since Merkl and Oku will already be live.
A few delegates have mentioned adjusting the incentive amount for the Onboarding package. I had initially suggested $250k, mostly because I thought it was a reasonable minimum for the program.
In my initial post, I estimated that $250k in incentives, distributed over three months at a reward rate of ~10%, would incentivize approximately $10M in liquidity for three months.
A few delegates have mentioned adjusting the incentive amount for the Onboarding package. I had initially suggested $250k, mostly because I thought it was a reasonable minimum for the program.
In my initial post, I estimated that $250k in incentives, distributed over three months at a reward rate of ~10%, would incentivize approximately $10M in liquidity for three months.
The below poll is to collect a quick sample of opinions from delegates on what they think a good amount is. [poll type=regular results=on_vote public=true chartType=bar close=2024-01-25T05:45:00.000Z]
I do think one thing to do note is once the incentive runs out , how to continue to be competitive.
Another is also whether it makes sense to spread to all mainnets and L2s but rather focus on 2-4 viable chains and really push toward those selected chains.
Thanks for the writeup @getty! Some more thoughts.
I think it's important to everyone to see that the options we select for the package are the best available options at the moment, not because of personal ties to delegates or other reasons. You have put forward a clear rationale why Oku and the Merkl protocol are good options suitable for the task. What would make most sense to me is to invite anyone to come forward with any alternatives they offer / could support with votes (perhaps in this thread itself). If there are alternatives, we vote for them. If there are not, we go with Oku & Merkl protocol.
I'd support such a incentive package. For what it's worth, the benefits from a $ spent on incentivizing liquidity on a fledgling chain is likely to be much higher than from the same amount spent on an established one.
However, I think it would be better to do a brief survey of the available options for the frontend and the reward distribution system. It would help to make a more informed decision, and identify any shortcomings / blockers in the existing offers. Maybe foundation can arrange it?
I overall would recommend taking the idea a bit slowly so that more community can get involved in. For example, I think you already closed the poll and 1 or 2 days is not long enough to gather more feedbacks.
The below poll is to collect a quick sample of opinions from delegates on what they think a good amount is.
Thanks for the writeup @getty! Some more thoughts.
I think it's important to everyone to see that the options we select for the package are the best available options at the moment, not because of personal ties to delegates or other reasons. You have put forward a clear rationale why Oku and the Merkl protocol are good options suitable for the task. What would make most sense to me is to invite anyone to come forward with any alternatives they offer / could support with votes (perhaps in this thread itself). If there are alternatives, we vote for them. If there are not, we go with Oku & Merkl protocol.
Re: compensation. Would the 20k+10k EUR fee be additional to the 3% cut Merkl takes from the rewards? If the DAO distributes $1M rewards on a chain then Merkl already gets $30k in fees, which already sounds like a reasonable compensation for their integration efforts, which I imagine aren't too extensive?
Re: pools to incentivize. Maybe leave the exact pools to the chain itself, as well as the reward distribution settings. (Merkl needs to be told the % of rewards proportional to the fees collected / % for token0 in the pool / % for token1.) The DAO could put some only basic constraints, like that no more than 20% of the incentivizes should be spent on small-cap token pools, to avoid any shenanigans where they spend all of it to pump their own token.
Re: amounts. I'm not going to unconditionally support e.g. $1M for any chain. It's not super hard to set up you own rollup already now, and it's getting easier by the day. There will be many low-effort L2 and L3 popping up. The reward amount could be tied with some KPI the chain has to hit, either a minimum TVL upfront, or some minimum growth during the program, for a tiered distribution. On the opposite side, distributing even $1M on Arbitrum will be a drop in the bucket; IMO better to aim this incentive package to newer chains and go for dedicated grants on these larger chains, looking for external incentives to attract.
Also, should we allocate some initial budget for the program, like $10M, allocate it on first-come-first-serve basis, and then re-evaluate the results?
I'd support such a incentive package. For what it's worth, the benefits from a $ spent on incentivizing liquidity on a fledgling chain is likely to be much higher than from the same amount spent on an established one.
However, I think it would be better to do a brief survey of the available options for the frontend and the reward distribution system. It would help to make a more informed decision, and identify any shortcomings / blockers in the existing offers. Maybe foundation can arrange it?
On the potential new Arbitrum incentive program, as @BlockAdopter mentions, the DAO is currently already running an incentive program on Arbitrum, where 1,779,950 ARB tokens (>$3M in the current prices) are distributed to liquidity providers. I'm sure there are some lessons to be learned from that before starting a new one.
Yeah this is a great idea. @AbdullahUmar and I have been keeping a close eye on the LTI’s and will certainly look to apply for something.
Thank you everyone for the support. Seems like this idea has some legs!
@TimeRows Uniswap did create the Uniswap v3 Staker Contract, but I don't believe it has been used by the DAO before. We need something that can quickly go to new chains and low-friction for users and developers. I will do more research on options, but I think Merkl, which is like a gen2 generalized rewards system for Uni v3, is probably our best bet. Their system doesn't require staking; it's proven, and they are already on some of the newer chains that would be good for deploying this onboarding package.
Thank you everyone for the support. Seems like this idea has some legs!
@TimeRows Uniswap did create the Uniswap v3 Staker Contract, but I don't believe it has been used by the DAO before. We need something that can quickly go to new chains and low-friction for users and developers. I will do more research on options, but I think Merkl, which is like a gen2 generalized rewards system for Uni v3, is probably our best bet. Their system doesn't require staking; it's proven, and they are already on some of the newer chains that would be good for deploying this onboarding package.
@0xkeyrock.eth I think for the purpose of this package, we should assume the chain doesn't have meaningful TVL or trading volume because the idea is to deploy this onboarding package at the chain launch or close to it. For example, Polygon zkEVM has a nascent DeFi ecosystem today, but that won't be the case in April. It would be ideal to deploy this package ASAP before it ramps up to secure Uniswap's position. Maybe there could be a follow-up package after this onboarding package that would be later developed for chains the DAO wants to further invest into.
@0xpibblez My goal is to create a package that is as concise and objective as possible to minimize the human management required. That said, we'll likely need a multisig to do the off-kick transactions that start incentives on new deployments, but once started, the ongoing work should be non-existent. Perhaps the Accountability Committee can assume that role or one of the other existing multisigs.
@Jl_Defiedge Yeah, I think Merkl is a good option. I'm going to do more research as well.
@Frisson Good call out on Arbitrum. Maybe the UADP can take the lead there. cc @Juanbug @AbdullahUmar
@BlockAdopter Great point. I'll reach out.
@Figu3 Uniswap v4 (by my guess) is 3-8 months away. Let's use that time to secure Uniswap a solid position at emerging chains before v2/v3 clones secure their first mover advantages so that when v4 is ready, we'll be in a great spot to roll it out across the ecosystem.
It's a very interesting idea. We would suggest that the amount of UNI is allotted based on a percentage of TVL and Trading volume on the chain but with caps.
For example if X chain launched 3 months ago and has $100m TVL + $40m Average Daily Volumes through AMMs, then Y% of UNI is allocated.
It's a very interesting idea. We would suggest that the amount of UNI is allotted based on a percentage of TVL and Trading volume on the chain but with caps.
For example if X chain launched 3 months ago and has $100m TVL + $40m Average Daily Volumes through AMMs, then Y% of UNI is allocated.
Reasoning behind this is that until deployment happens, it's more likely than not that the chain has grown exponentially and thus the set amount of $250k could be not impactful at all.
We also agree on focusing those incentives into "blue-chip" pools.
I overall would recommend taking the idea a bit slowly so that more community can get involved in. For example, I think you already closed the poll and 1 or 2 days is not long enough to gather more feedbacks.
The below poll is to collect a quick sample of opinions from delegates on what they think a good amount is.
Thanks for the writeup @getty! Some more thoughts.
I think it's important to everyone to see that the options we select for the package are the best available options at the moment, not because of personal ties to delegates or other reasons. You have put forward a clear rationale why Oku and the Merkl protocol are good options suitable for the task. What would make most sense to me is to invite anyone to come forward with any alternatives they offer / could support with votes (perhaps in this thread itself). If there are alternatives, we vote for them. If there are not, we go with Oku & Merkl protocol.
Re: compensation. Would the 20k+10k EUR fee be additional to the 3% cut Merkl takes from the rewards? If the DAO distributes $1M rewards on a chain then Merkl already gets $30k in fees, which already sounds like a reasonable compensation for their integration efforts, which I imagine aren't too extensive?
Re: pools to incentivize. Maybe leave the exact pools to the chain itself, as well as the reward distribution settings. (Merkl needs to be told the % of rewards proportional to the fees collected / % for token0 in the pool / % for token1.) The DAO could put some only basic constraints, like that no more than 20% of the incentivizes should be spent on small-cap token pools, to avoid any shenanigans where they spend all of it to pump their own token.
Re: amounts. I'm not going to unconditionally support e.g. $1M for any chain. It's not super hard to set up you own rollup already now, and it's getting easier by the day. There will be many low-effort L2 and L3 popping up. The reward amount could be tied with some KPI the chain has to hit, either a minimum TVL upfront, or some minimum growth during the program, for a tiered distribution. On the opposite side, distributing even $1M on Arbitrum will be a drop in the bucket; IMO better to aim this incentive package to newer chains and go for dedicated grants on these larger chains, looking for external incentives to attract.
Also, should we allocate some initial budget for the program, like $10M, allocate it on first-come-first-serve basis, and then re-evaluate the results?
I'd support such a incentive package. For what it's worth, the benefits from a $ spent on incentivizing liquidity on a fledgling chain is likely to be much higher than from the same amount spent on an established one.
However, I think it would be better to do a brief survey of the available options for the frontend and the reward distribution system. It would help to make a more informed decision, and identify any shortcomings / blockers in the existing offers. Maybe foundation can arrange it?
On the potential new Arbitrum incentive program, as @BlockAdopter mentions, the DAO is currently already running an incentive program on Arbitrum, where 1,779,950 ARB tokens (>$3M in the current prices) are distributed to liquidity providers. I'm sure there are some lessons to be learned from that before starting a new one.
Yeah this is a great idea. @AbdullahUmar and I have been keeping a close eye on the LTI’s and will certainly look to apply for something.
Thank you everyone for the support. Seems like this idea has some legs!
@TimeRows Uniswap did create the Uniswap v3 Staker Contract, but I don't believe it has been used by the DAO before. We need something that can quickly go to new chains and low-friction for users and developers. I will do more research on options, but I think Merkl, which is like a gen2 generalized rewards system for Uni v3, is probably our best bet. Their system doesn't require staking; it's proven, and they are already on some of the newer chains that would be good for deploying this onboarding package.
Thank you everyone for the support. Seems like this idea has some legs!
@TimeRows Uniswap did create the Uniswap v3 Staker Contract, but I don't believe it has been used by the DAO before. We need something that can quickly go to new chains and low-friction for users and developers. I will do more research on options, but I think Merkl, which is like a gen2 generalized rewards system for Uni v3, is probably our best bet. Their system doesn't require staking; it's proven, and they are already on some of the newer chains that would be good for deploying this onboarding package.
@0xkeyrock.eth I think for the purpose of this package, we should assume the chain doesn't have meaningful TVL or trading volume because the idea is to deploy this onboarding package at the chain launch or close to it. For example, Polygon zkEVM has a nascent DeFi ecosystem today, but that won't be the case in April. It would be ideal to deploy this package ASAP before it ramps up to secure Uniswap's position. Maybe there could be a follow-up package after this onboarding package that would be later developed for chains the DAO wants to further invest into.
@0xpibblez My goal is to create a package that is as concise and objective as possible to minimize the human management required. That said, we'll likely need a multisig to do the off-kick transactions that start incentives on new deployments, but once started, the ongoing work should be non-existent. Perhaps the Accountability Committee can assume that role or one of the other existing multisigs.
@Jl_Defiedge Yeah, I think Merkl is a good option. I'm going to do more research as well.
@Frisson Good call out on Arbitrum. Maybe the UADP can take the lead there. cc @Juanbug @AbdullahUmar
@BlockAdopter Great point. I'll reach out.
@Figu3 Uniswap v4 (by my guess) is 3-8 months away. Let's use that time to secure Uniswap a solid position at emerging chains before v2/v3 clones secure their first mover advantages so that when v4 is ready, we'll be in a great spot to roll it out across the ecosystem.
It's a very interesting idea. We would suggest that the amount of UNI is allotted based on a percentage of TVL and Trading volume on the chain but with caps.
For example if X chain launched 3 months ago and has $100m TVL + $40m Average Daily Volumes through AMMs, then Y% of UNI is allocated.
It's a very interesting idea. We would suggest that the amount of UNI is allotted based on a percentage of TVL and Trading volume on the chain but with caps.
For example if X chain launched 3 months ago and has $100m TVL + $40m Average Daily Volumes through AMMs, then Y% of UNI is allocated.
Reasoning behind this is that until deployment happens, it's more likely than not that the chain has grown exponentially and thus the set amount of $250k could be not impactful at all.
We also agree on focusing those incentives into "blue-chip" pools.