TLDR: This proposal adds Manta Pacific to the v3 deployments record and grants Manta an Onboarding Package, which includes $250k of UNI incentives for three months on four key markets and Angle Merkl’s integration of Manta. Separate from this proposal, Manta has arranged for Oku to support Manta, and the contracts have been deployed.
The following are the proposed pools for the program, but they can be amended for the onchain vote.
The Manta team has committed to providing incentives alongside the Uniswap DAO and plans to solidify their exact plans once this Temperature is successful and prior to the onchain vote.
Key points:
For more information, please visit the forum thread.
TLDR: This proposal adds Manta Pacific to the v3 deployments record and grants Manta an Onboarding Package, which includes $250k of UNI incentives for three months on four key markets and Angle Merkl’s integration of Manta. Separate from this proposal, Manta has arranged for Oku to support Manta, and the contracts have been deployed.
The following are the proposed pools for the program, but they can be amended for the onchain vote.
The Manta team has committed to providing incentives alongside the Uniswap DAO and plans to solidify their exact plans once this Temperature is successful and prior to the onchain vote.
Key points:
For more information, please visit the forum thread.
https://gov.uniswap.org/t/onboarding-package-for-manta-pacific/23442/13
https://gov.uniswap.org/t/onboarding-package-for-manta-pacific/23442/13
I am raising this discussion to alert the DAO to the ongoing situation regarding Aperture Finance.
On January 26, 2026, Aperture Finance suffered a major exploit (approx. $3.6M lost). Security reports (including BlockSec) confirmed the vulnerability was an arbitrary-call capability in their smart contracts, allowing attackers to drain assets using transferFrom calls on existing user approvals.
I am raising this discussion to alert the DAO to the ongoing situation regarding Aperture Finance.
On January 26, 2026, Aperture Finance suffered a major exploit (approx. $3.6M lost). Security reports (including BlockSec) confirmed the vulnerability was an arbitrary-call capability in their smart contracts, allowing attackers to drain assets using transferFrom calls on existing user approvals.
Current Issues for Uniswap LPs:
30+ Days of Ghosting: The Aperture team has been completely silent since the exploit. No post-mortem has been shared, and no recovery plan has been proposed to the users who provided liquidity to Uniswap via their tool.
Tornado Cash Activity: On-chain data confirms that the exploited funds (1,200+ ETH) are currently being laundered through Tornado Cash, with no attempt from the team to negotiate with the hacker or secure the remaining funds.
Recent Security Banner: A banner recently appeared on aperture.finance advising users to revoke all approvals. This proves the team still has frontend access but chooses to remain silent regarding the $3.6M loss.
Aperture has been a featured partner for Uniswap V3/V4 automation and was part of several ecosystem discussions. To protect the integrity of the Uniswap ecosystem, I propose:
Official Warning: Request Uniswap Labs to add a high-risk warning to the Uniswap Interface for any interactions involving Aperture Finance contracts.
Audit Review: We need a community-led review to ensure no other "Intent-based" solvers using similar logic are putting Uniswap LPs at risk.
VC Accountability: We call on ecosystem investors who backed Aperture (such as Binance Labs/YZi, Krypital, etc.) to provide a statement on the status of the project.
Uniswap’s strength relies on the safety of its LP ecosystem. We cannot let automated management tools "ghost" the community after a major security failure.
Absolutely! This proposal seems like a strategic move to incorporate Manta Pacific into Uniswap's ecosystem. Including Manta's modular ZK solutions, backed by its impressive TVL and growing DeFi ecosystem, could significantly enhance Uniswap's scalability and reach. The proposed UNI incentives and integration with Angle Merkl further solidify this partnership, paving the way for mutual growth and innovation. I look forward to seeing its positive impact on Manta Pacific and Uniswap.
Thanks for your thoughts on this.
I don't think Oku's work is needed here. Aperture has done audit before going live on Manta, which verified the current deployment is a clean fork of Uniswap V3.
Thanks for your thoughts on this.
I don't think Oku's work is needed here. Aperture has done audit before going live on Manta, which verified the current deployment is a clean fork of Uniswap V3.
Because the nature of collaboration here: Aperture is transferring an existing fork with significant TVL & volume to Uniswap DAO, I would imagine there could be other nuances and details to be discussed by the community first before proceeding.
It may be better to create a different thread with more details from Aperture's end. For instance:
Based on the context above, in my humble opinion, it is a different set of discussion than what the current thread is intended for.
Adding more detail to @mcd-aperture's comments above. The existing deployment of Aperture's smart contract is a clean fork of Uniswap V3's. With its current state:
Adding more detail to @mcd-aperture's comments above. The existing deployment of Aperture's smart contract is a clean fork of Uniswap V3's. With its current state:
And Aperture as the leading protocol in Intent & Liquidity management space, it has helped to rebalance $1.3B worth of liquidity for LPs. And it is on track to rebalance more than $5B worth of liquidity annually. This is equivalent to:
It does not make sense to create another deployment of Uniswap V3 if Aperture is happy with transferring the ownership to Uniswap and working with Uniswap to benefit both Uni stakers and Aperture's community. As a matter of fact, deploying another Uniswap V3 would further fragment the liquidity and hurt both Manta and Uniswap community.
In addition, Aperture already has $MANTA grants secured to help attract liquidity. With the introduction of Aperture's recent points campaign, it would help boost up the liquidity even further.
All in all, I do not think it makes sense to create another deployment. The collaboration between Uniswap and Aperture would bring way more benefits to all.
Aperture Finance could also transfer the ownership of its UniV3 deployment (called ApertureSwap) to Uniswap.
Having ownership over this UniV3 deployment is not a priority for Aperture (which is more focussed on using solvers to help LPs).
Aperture Finance could also transfer the ownership of its UniV3 deployment (called ApertureSwap) to Uniswap.
Having ownership over this UniV3 deployment is not a priority for Aperture (which is more focussed on using solvers to help LPs).
Aperture can post a formal submission but we wanted to mention this here first.
is Manta matching the incentives to the listed pools? existing protocols such as Quickswap seem to be receiving boosted apy from $manta incentives, and it would be nice for Uniswap pools to get some boost to the yield to bootstrap liquidity / awareness
Seems like a win-win. This proposal can stay as it is with the exception of deploying new V3 contracts. However it would still require work from OKU: OKU can verify that the existing deployed manta uniswap V3 contracts are a clean fork/deployment, before integrating it into this proposal.
I am raising this discussion to alert the DAO to the ongoing situation regarding Aperture Finance.
On January 26, 2026, Aperture Finance suffered a major exploit (approx. $3.6M lost). Security reports (including BlockSec) confirmed the vulnerability was an arbitrary-call capability in their smart contracts, allowing attackers to drain assets using transferFrom calls on existing user approvals.
I am raising this discussion to alert the DAO to the ongoing situation regarding Aperture Finance.
On January 26, 2026, Aperture Finance suffered a major exploit (approx. $3.6M lost). Security reports (including BlockSec) confirmed the vulnerability was an arbitrary-call capability in their smart contracts, allowing attackers to drain assets using transferFrom calls on existing user approvals.
Current Issues for Uniswap LPs:
30+ Days of Ghosting: The Aperture team has been completely silent since the exploit. No post-mortem has been shared, and no recovery plan has been proposed to the users who provided liquidity to Uniswap via their tool.
Tornado Cash Activity: On-chain data confirms that the exploited funds (1,200+ ETH) are currently being laundered through Tornado Cash, with no attempt from the team to negotiate with the hacker or secure the remaining funds.
Recent Security Banner: A banner recently appeared on aperture.finance advising users to revoke all approvals. This proves the team still has frontend access but chooses to remain silent regarding the $3.6M loss.
Aperture has been a featured partner for Uniswap V3/V4 automation and was part of several ecosystem discussions. To protect the integrity of the Uniswap ecosystem, I propose:
Official Warning: Request Uniswap Labs to add a high-risk warning to the Uniswap Interface for any interactions involving Aperture Finance contracts.
Audit Review: We need a community-led review to ensure no other "Intent-based" solvers using similar logic are putting Uniswap LPs at risk.
VC Accountability: We call on ecosystem investors who backed Aperture (such as Binance Labs/YZi, Krypital, etc.) to provide a statement on the status of the project.
Uniswap’s strength relies on the safety of its LP ecosystem. We cannot let automated management tools "ghost" the community after a major security failure.
Absolutely! This proposal seems like a strategic move to incorporate Manta Pacific into Uniswap's ecosystem. Including Manta's modular ZK solutions, backed by its impressive TVL and growing DeFi ecosystem, could significantly enhance Uniswap's scalability and reach. The proposed UNI incentives and integration with Angle Merkl further solidify this partnership, paving the way for mutual growth and innovation. I look forward to seeing its positive impact on Manta Pacific and Uniswap.
Thanks for your thoughts on this.
I don't think Oku's work is needed here. Aperture has done audit before going live on Manta, which verified the current deployment is a clean fork of Uniswap V3.
Thanks for your thoughts on this.
I don't think Oku's work is needed here. Aperture has done audit before going live on Manta, which verified the current deployment is a clean fork of Uniswap V3.
Because the nature of collaboration here: Aperture is transferring an existing fork with significant TVL & volume to Uniswap DAO, I would imagine there could be other nuances and details to be discussed by the community first before proceeding.
It may be better to create a different thread with more details from Aperture's end. For instance:
Based on the context above, in my humble opinion, it is a different set of discussion than what the current thread is intended for.
Adding more detail to @mcd-aperture's comments above. The existing deployment of Aperture's smart contract is a clean fork of Uniswap V3's. With its current state:
Adding more detail to @mcd-aperture's comments above. The existing deployment of Aperture's smart contract is a clean fork of Uniswap V3's. With its current state:
And Aperture as the leading protocol in Intent & Liquidity management space, it has helped to rebalance $1.3B worth of liquidity for LPs. And it is on track to rebalance more than $5B worth of liquidity annually. This is equivalent to:
It does not make sense to create another deployment of Uniswap V3 if Aperture is happy with transferring the ownership to Uniswap and working with Uniswap to benefit both Uni stakers and Aperture's community. As a matter of fact, deploying another Uniswap V3 would further fragment the liquidity and hurt both Manta and Uniswap community.
In addition, Aperture already has $MANTA grants secured to help attract liquidity. With the introduction of Aperture's recent points campaign, it would help boost up the liquidity even further.
All in all, I do not think it makes sense to create another deployment. The collaboration between Uniswap and Aperture would bring way more benefits to all.
Aperture Finance could also transfer the ownership of its UniV3 deployment (called ApertureSwap) to Uniswap.
Having ownership over this UniV3 deployment is not a priority for Aperture (which is more focussed on using solvers to help LPs).
Aperture Finance could also transfer the ownership of its UniV3 deployment (called ApertureSwap) to Uniswap.
Having ownership over this UniV3 deployment is not a priority for Aperture (which is more focussed on using solvers to help LPs).
Aperture can post a formal submission but we wanted to mention this here first.
is Manta matching the incentives to the listed pools? existing protocols such as Quickswap seem to be receiving boosted apy from $manta incentives, and it would be nice for Uniswap pools to get some boost to the yield to bootstrap liquidity / awareness
Seems like a win-win. This proposal can stay as it is with the exception of deploying new V3 contracts. However it would still require work from OKU: OKU can verify that the existing deployed manta uniswap V3 contracts are a clean fork/deployment, before integrating it into this proposal.
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’re generally supportive of Uniswap deployments on Ethereum L2s and as such we’ll be voting in favor of adding Manta to the v3 deployment records and including an onboarding package.
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’re generally supportive of Uniswap deployments on Ethereum L2s and as such we’ll be voting in favor of adding Manta to the v3 deployment records and including an onboarding package.
thanks for the proposal @GFXlabs I second the comments made earlier on matching incentives.
Over the last several days, we have been in touch with the Aperture team, Manta team, and several Uniswap delegates, discussing the opportunity to migrate the ApertureSwap deployment to become an official Uniswap deployment. We appreciate the Aperture team's contributions to the Uniswap ecosystem and the opportunity extended here. It is the first time such an opportunity has presented itself. Unfortunately, after deliberating and discussing with everyone, we do not believe it is the best path forward for Uniswap to adopt the deployment. Instead, it should stick with precedent and continue the regular deployment process.
GFX Labs would like to thank the delegates who took the time to consider the opportunity.
Over the last several days, we have been in touch with the Aperture team, Manta team, and several Uniswap delegates, discussing the opportunity to migrate the ApertureSwap deployment to become an official Uniswap deployment. We appreciate the Aperture team's contributions to the Uniswap ecosystem and the opportunity extended here. It is the first time such an opportunity has presented itself. Unfortunately, after deliberating and discussing with everyone, we do not believe it is the best path forward for Uniswap to adopt the deployment. Instead, it should stick with precedent and continue the regular deployment process.
GFX Labs would like to thank the delegates who took the time to consider the opportunity.
Update: The Temperature Check is live. Voting ends Wednesday evening.
The following are the proposed pools for the program, but they can be amended for the onchain vote.
The Manta team has committed to providing incentives alongside the Uniswap DAO and plans to solidify their exact plans once this Temperature Check is successful and prior to the onchain vote.
I do think those L2s committing resources to also support Uniswap would be beneficial. If there are difficulties, it's fair for the community to explore different approaches
We'll get in touch with the Aperture team and circle back to the forums once we have info to share. Pending review and due diligence, if Aperture is willing to transfer control of the factory contract, it is probably the best path forward.
Support! There is no reason not to incentivize Manta, as opposed to the other chains we have voted to incentivize.
One potential concern arises again regarding evaluation and follow-up. Let's say that three months have passed. The Manta chain returns and expresses interest in another round of incentives. What happens then, and how does the DAO assess whether the program has been successful?
Hi everyone,
Thanks for the support thus far. We're in talks with Manta about matching the incentives and other avenues for Manta to show support in addition to covering Oku's costs. We should have more information in the coming days.
Hi everyone,
Thanks for the support thus far. We're in talks with Manta about matching the incentives and other avenues for Manta to show support in addition to covering Oku's costs. We should have more information in the coming days.
Questions
The Manta chain returns and expresses interest in another round of incentives. What happens then, and how does the DAO assess whether the program has been successful?
I also wonder if there is a maintainence cost associated with this deployment?
Based on your experience with deployments on other networks, do you have any idea on what will be the expected TVL that uniswap can capture from these incentives?
thanks for the proposal @GFXlabs I second the comments made earlier on matching incentives.
Over the last several days, we have been in touch with the Aperture team, Manta team, and several Uniswap delegates, discussing the opportunity to migrate the ApertureSwap deployment to become an official Uniswap deployment. We appreciate the Aperture team's contributions to the Uniswap ecosystem and the opportunity extended here. It is the first time such an opportunity has presented itself. Unfortunately, after deliberating and discussing with everyone, we do not believe it is the best path forward for Uniswap to adopt the deployment. Instead, it should stick with precedent and continue the regular deployment process.
GFX Labs would like to thank the delegates who took the time to consider the opportunity.
Over the last several days, we have been in touch with the Aperture team, Manta team, and several Uniswap delegates, discussing the opportunity to migrate the ApertureSwap deployment to become an official Uniswap deployment. We appreciate the Aperture team's contributions to the Uniswap ecosystem and the opportunity extended here. It is the first time such an opportunity has presented itself. Unfortunately, after deliberating and discussing with everyone, we do not believe it is the best path forward for Uniswap to adopt the deployment. Instead, it should stick with precedent and continue the regular deployment process.
GFX Labs would like to thank the delegates who took the time to consider the opportunity.
Update: The Temperature Check is live. Voting ends Wednesday evening.
The following are the proposed pools for the program, but they can be amended for the onchain vote.
The Manta team has committed to providing incentives alongside the Uniswap DAO and plans to solidify their exact plans once this Temperature Check is successful and prior to the onchain vote.
I do think those L2s committing resources to also support Uniswap would be beneficial. If there are difficulties, it's fair for the community to explore different approaches
We'll get in touch with the Aperture team and circle back to the forums once we have info to share. Pending review and due diligence, if Aperture is willing to transfer control of the factory contract, it is probably the best path forward.
Support! There is no reason not to incentivize Manta, as opposed to the other chains we have voted to incentivize.
One potential concern arises again regarding evaluation and follow-up. Let's say that three months have passed. The Manta chain returns and expresses interest in another round of incentives. What happens then, and how does the DAO assess whether the program has been successful?
Hi everyone,
Thanks for the support thus far. We're in talks with Manta about matching the incentives and other avenues for Manta to show support in addition to covering Oku's costs. We should have more information in the coming days.
Hi everyone,
Thanks for the support thus far. We're in talks with Manta about matching the incentives and other avenues for Manta to show support in addition to covering Oku's costs. We should have more information in the coming days.
Questions
The Manta chain returns and expresses interest in another round of incentives. What happens then, and how does the DAO assess whether the program has been successful?
I also wonder if there is a maintainence cost associated with this deployment?
Based on your experience with deployments on other networks, do you have any idea on what will be the expected TVL that uniswap can capture from these incentives?