Authors: @AbdullahUmar (Arana Digital), @Juanbug (PGov), @alicecorsini (kpk)
The purpose of this report is of two-fold:
Part 1: Descriptive Report
This section outlines the operations and programs with UAC oversight and provides a financial recap of account balances and expenditures.
Contents
- Background
- Uniswap v3 Deployments Growth
- Incentive Packages and Target Chain Commitments
- Developing Plans for Uniswap v4 Adoption
- Multisig Operations and Transparency
- Uniswap Foundation Feedback Group
- Governance Community Calls
- Accounting and Financials
Part 2: Request for Comment (RFC)
Based on the information from Part 1, this section proposes a renewal of the UAC for Season 4 and requests rebalancing of program accounts under deficits. The renewal and the rebalancing aspects will be conducted as two separate temperature checks. Season 4 renewal is requested to last until the end of 2025.
Part 1: Descriptive Report
Background
The UAC has now been operating for the past three seasons, each of which span a duration of roughly 7 months. An evolution of the committee has led it to become the DAO’s go-to operational body for handling a multitude of different responsibilities, although it merely began as a committee to oversee cross-chain deployments upon expiration of the Uniswap v3 Business Source License (BSL). Today, the UAC oversees:
- Cross-chain deployment coordination
- ENS record management
- Disbursement and accounting of service provider, grantee, and working groups’ compensation
- Custody of DAO-approved funds on Ethereum mainnet
- Incentive distribution across a multitude of EVM-compatible chains
- Governance community calls
- Assisting with miscellaneous DAO operations like helping teams sponsor proposals
- Managing the newly established Foundation Feedback Group (FFG)
This report outlines the specific operations behind the UAC from the previous season, along with an update regarding the financial situation of DAO programs and working groups. The last section will act as the request for comment (RFC) to renew the UAC and balance accounts.
Uniswap v3 Deployments Growth
Whenever a target chain is interested in attaining an official Uniswap v3, or v2, deployment, the UAC is responsible for interfacing with the chain, helping them structure the RFC for attaining optimistic approval for the deployment. We work closely with front-end teams—which also take care of the backend contract deployment—like Oku and Reservoir, sending them any deal flow that we may attain. Once the front-end providers deploy and verify all of the required contracts, the UAC double checks that all of the necessary deployment details have been completed, like the transfer of contract ownership to the timelock.
During Season 3, the UAC oversaw the deployment of 17 total v3 deployments, a significant increase from the previous season, which saw 7 deployments. As per the below graphic, the past seven months have seen a dramatic rise in official deployments.
Due to the release of L2/L3 standards like the OP Stack (Superchain) and ZK Chains (Elastic Network), the possible markets that Uniswap has been able to expand to has dramatically increased. We continue to see this trend transpire and anticipate no shortage in demand from target chains to deploy an official instance of Uniswap v3.
Of all deployments, GFX Labs has been directly responsible for 21 of them, with Protofire and Uniswap Labs taking care of 7 and 5 deployments, respectively. However, Oku users are nonetheless able to access 31 out of the active 41 deployments, making Oku.trade the most accessible DAO-approved front-end for interacting with official deployments in terms of sheer chain breadth. Uniswap.org is the most used and prominent front-end, giving access to 13 total chains. Reservoir allows users to interact with Uni v3 on 7 chains, with chains like Abstract having pushed Uniswap v3 as their chain’s canonical DEX.
Incentive Packages and Target Chain Commitments
The incentive package is composed of three types of capital allocations:
- Incentives for distribution
- Distribution partner integration cost
- Front-end integration cost
The three pieces above do not need to be requested in tandem, rather, a target chain has the ability to select one or more of the above aspects of the incentive package. In December, the UAC published a guideline to assist target chains with the v3 deployment process, helping them assess which parts of the package are most important to request. The forum post can be found here.
X Layer requested an Oku subsidy from the DAO without asking for any incentives at the time; therefore, the DAO voted to allocate $105k UNI to help X Layer cover this cost, contingent on them providing $1M of POL on Uni v3 pools.
The UAC and Oku mediated this relationship, calling for X Layer to set up a combined multisig with representatives from the various organizations in order to ensure the POL on their end was delivered, but their team backed out part way through the process. X Layer therefore does not have a front-end to interact with the v3 contracts, and Oku was not paid for this deployment due to X Layer falling short. The $105k that was sent to the UAC from this proposal remains in the Primary UAC Wallet and is now accounted for as an Account surplus and not a liability to be paid out (see “Accounting and Financials” section for more details).
Gnosis Chain asked for a full package, including all three of the above components, with the incentives for distribution amounting to $250k. No matching was provided by Gnosis. All of the Gnosis incentives have been successfully disbursed, and their team continues to allocate capital to growing the deployment. For example, in March, they put forth $250k GNO to incentivize their tokenized TSLA pool.
Sonic asked the DAO to cover the Merkl integration and $250k worth of incentives. Only 40% of this capital was disbursed due to a shift in the Sonic team’s strategy partway through the campaigns. They still allocated $150k, while we spent $100k. The remainder of the funds are now a part of the UAC surplus (see “Accounting and Financials” section for more details).
Celo asked for the Oku subsidy along with $250k of incentives for distribution. The Celo migration to an OP L2 concluded in March. Their team wanted to wait until this process was complete before allocating the assigned incentives. The UAC will allocate these incentives soon, and updates will show on this forum thread.
During Season 2, the UAC ran 13 campaigns for 12 chains (zkSync was tranched into 2 parts), while only the Gnosis Chain and Sonic incentives were newly administered during Season 3. The Uniswap Revitalization and Growth Program was meant to be a way to increase v3’s market share across the given chains, of which, some were successful, while others were not. Forse helped analyze the results for four of these chains: Arbitrum, Base, Blast, and Scroll.
Matching Incentives and Expense Ratios
Ever since this incentives sprint from Season 2, the DAO has become more fastidious with its incentives spending. A handful of chains have requested incentives over the last few months but have either failed to go past the Snapshot phase or have shown reluctance in posting an RFC due to the fear of having the proposal fall short. During Season 3, the UAC began advising target chains to match a portion of their incentives request in order to have a chance for delegates to grant them liquidity incentives. This is in part why the Uniswap Ecosystem Incentives Initiative (UEII) was voted in during Q4 ‘24, which granted the participating members an incentive to source and negotiate the highest amount of matching from target chains as possible, along with pursue separate grant programs on behalf of the DAO.
Notably, this shift in strategy has increased the amount of capital committed by partner chains relative to Season 2. The following table shows all of the incentive allocations and matches from Season 2. The sum equates to $350k.
It’s clear that barely any matching was considered during this initial sprint on incentives, as it largely wasn’t a requirement for target chains. The DAO unilaterally decided to allocate funds to the above chains without first taking them through a negotiating process. There also wasn’t any negotiation that occurred with Gnosis Chain. The only instance of an active strategy to secure a grant from a target chain was with Arbitrum.
The expense ratio for the Arbitrum allocation was 1.2 because the current UEII team applied for the Arbitrum LTIPP program in collaboration with Gauntlet. This instance exemplifies the benefits of actively scoping incentives from alternative ecosystems.
The UAC began negotiating with chains after roughly September ‘24. That’s why the ratio for Sonic is more satisfactory. We had weeks of back and forth with the target chain team in order to land on a match amount that would be sufficient for the DAO. Now, the negotiations are handled by the UEII and have thus far been successful, as seen by the recent Celo match.
Lisk’s incentives deal never proceeded from Snapshot to the onchain vote due to the large number of “No” votes. Note Lisk was promising $1M of POL as a result of these incentives, but that’s a very different commitment from incentives that represent an explicit expenditure.
However, to our surprise, the Saga proposal also failed, even though the chain was proposing to allocate the largest amount of matching the DAO has yet seen. A handful of chains have been advised to hold off on asking for incentives unless they can offer a compelling enough match, otherwise their proposal is likely to fail, especially if the requesting team is not well-known. There are 5+ chains in this scenario at the moment. BOB’s incentive package proposal recently passed the Snapshot phase, however, indicating that the DAO indexes heavily on existing chain traction.
Other chains, including LightLink and Telos, have started running their internal incentive programs as a precursor to asking for the onboarding package. This way, chains are able to approach Uniswap with existing example commitments.
Developing Plans for Uniswap v4 Adoption
There are a handful of prerequisites that must be dealt with prior to actually executing a Uni v4 cross-chain deployment initiative. The first step towards increasing v4 adoption was taken by the DAO once it approved the Uniswap Unleashed and Unichain/v4 Liquidity Incentives proposals in March. These UF-led programs should aid in bootstrapping and accelerating liquidity and activity on v4, notably on larger chains like Base and Arbitrum. Strategy around alternative chains is presently taking place and will be substantiated in the coming few months.
The first actionable step that the DAO is able to take regarding v4 adoption is instituting the legal and operational infrastructure for deploying v4 across alternative EVM environments. Last week, the UAC created a forum post elucidating the steps behind granting license exemptions to particular entities for deploying official instances of v4.
To learn more, please visit this forum post.
Multisig Operations and Transparency
Unchanged from Season 2, the UAC continues to use two multisig addresses to conduct its operations:
- Primary UAC Wallet Address: 0x3B59C6d0034490093460787566dc5D6cE17F2f9C
- UAC Incentives Wallet Address: 0xEBCCf1ce13F63c6B98811F03964F51fC43cef851
- This wallet is deployed across various EVMs
Since the UAC has grown from four to five total members between Season 2 and 3, we’ve correspondingly increased the multisigs’ threshold from ¾ to ⅗.
In March, we signed an agreement with SafeNotes to increase transparency around capital flows between the UAC Primary and UAC Incentives wallets. The DAO will now be able to easily track inflows and outflows, as they will be categorized and detailed by the UAC team, a functionality not available with block explorers. Any future additions to the suite of UAC-operated multisigs will be automatically added to the SafeNotes interface.
We’ve also acquired the “uac.eth” ENS domain to make it easier for delegates and external teams to easily identify the Primary UAC Wallet, and the UAC Incentives wallet has also been granted a subname, called “incentives.uac.eth.”
Users are able to toggle between each multisig address and view the inflows and outflows associated with each address. For example, the below discloses the flow for the UAC Incentives Wallet.
Uniswap Foundation Feedback Group (FFG)
The FFG is a newly proposed initiative aimed at strengthening accountability, transparency, and alignment between the UF and the Uniswap DAO. It is being developed in collaboration with the UAC and incorporates feedback from delegates, stakeholders, and community members. The FFG will hold meetings with the UF every other month to track progress on their roadmap, communicating salient points of discussion to the DAO.
Reporting regarding financial, grants, etc is not substituted by this group. The UF will continue their customary reporting process. The FFG simply provides a more intimate layer of oversight, allowing external parties to verify and communicate that the UF is prudently meeting its mandates. This type of oversight is important because not every aspect of the UF’s operations needs to be debated on a public forum—and some aspects, like partnerships, need to remain private. However, a small group external to the Foundation, with alignment to token holders and the DAO, can provide reassurance that the UF is acting responsibly.
Six entities/individuals, including the UAC, will be a part of the FFG for the duration of 2025. Once we obtain confirmation from them, they will be disclosed on the forum.
Prospective Team
We are awaiting final confirmation from a few of the final members. The below should give context as to the types of characteristics we looked for when selecting FFG members. Collectively, the group will hold the following attributes:
- Legal background
- Large UNI token stake
- High strategic acuity
- Constructive and neutral delegate(s)
- Diversity of useful expertise, like in market making
- Previous grantee or protocol that relies on Uniswap for its success
- High context around Uniswap DAO operations
Governance Community Calls
Since September 2024, the UAC has been hosting monthly virtual community calls to keep DAO participants informed of ongoing operations. We have invited multiple guest presenters to the calls, from the front-end providers, target chains requesting incentive grants, other working groups, delegates with active RFCs, and the Uniswap Foundation.
Beyond keeping the community updated, these calls also serve as an important criterion behind Delegate Rewards Cycle 2—and continue to play a role in Cycle 3 of the program. The second cycle showed a 81.25% average attendance rate in paid delegates, and the overall average attendance between September and March amounted to ~40 people. Hence, 32.5% of community call attendees constitute paid delegates.
Note that November is not included in this diagram since that month’s call was canceled due to Uniday Bangkok.
————————————————————————————————————
Continue reading for Accounting and Financials Section