# Proposal Template 2.0 - Upgrade for Deployments & Agreements **URL:** \ **Category:** Governance-Meta\ **Created:** [January 5, 2023, 5:54pm UTC](https://gov.uniswap.org/t/proposal-template-2-0-upgrade-for-deployments-agreements/19936 "2023-01-05T17:54:58Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![tobyshorin](https://sea2.discourse-cdn.com/flex016/user_avatar/gov.uniswap.org/tobyshorin/32/3867_2.png) [@tobyshorin](https://gov.uniswap.org/u/tobyshorin)\ **Post date:** [January 5, 2023, 5:54pm UTC](https://gov.uniswap.org/t/proposal-template-2-0-upgrade-for-deployments-agreements/19936/1 "2023-01-05T17:54:58Z")
💡 This proposal is an improvement to the [Cross-Chain Deployment Proposal Template](https://gov.uniswap.org/t/proposed-template-for-future-cross-chain-deployment-proposals/16611/2) that adds accountability mechanisms to ensure terms of the agreements with Uniswap deployers and partners are upheld. It addresses accountability by requiring: - KPIs & success metrics - Engagement terms - Budget & financing - Proposal code Future deployments and partnership offers to Uniswap DAO may this template to improve the credibility of proposals to delegates. This template is one output of a working group convened by Other Internet in November and December to address [accountability issues](https://otherinter.net/research/uniswap-accountability/) in Uniswap partnerships. The template is intended to be complemented by a full Accountability Committee that we will be proposing in the coming weeks. _Contributors: Toby Shorin, Charlie Feng (Agora), Laura Lotti, Aaron Lewis_ * * * # Proposal Title **Point of Contact:** [Name, Contact Information, ETH Address] _This person will be the main point of contact on the partner’s side throughout the proposal and engagement process._ ### Proposal summary _Tweet-length summary of the proposal_ ### **Overview of proposal** _Description of the proposal including timeline, benefits to Uniswap, and other relevant information._ ### **Motivation** _What opportunity or challenge is this partnership addressing, and why is it impactful for Uniswap?_ # Partner Details **Partner Details** _Who is making this proposal and what should we know about them? Who is on the proposer team?_ **Partner Legal** _What legal entity, if any, is making this proposal? Clarify whether the partner is an unincorporated DAO or a legal entity in a jurisdiction._ **Delegate Sponsor** _Is a delegate co-authoring or sponsoring this proposal on behalf of the partner team? What is the delegate’s relationship with the proposed partner?_ **Conflict of Interest Declaration** _Partner organization and team members must disclose any past or existing financial or contractual relationship to Uniswap Labs, UNI token, or investments of Uniswap Labs Ventures._ **Additional information for cross-chain deployments** _If you’re proposing a cross-chain deployment, please include some information about the application ecosystem, size of user base, daily transfer volume, etc. + stage of development of the project (e.g. pre-launch, testnet, mainnet)_ # Engagement Terms ## Project Financing **Itemized Budget (denominated in USD)** _What is the proposed budget for this project, if it is going to be funded by Uniswap Treasury? Please list a detailed cost breakdown including:_ - _Team rates_ - _License, subscription, or server costs_ - _Other resource costs_ **What discounts or subsidies if any are applied?** **Funds Provided (denominated in USD)** **What payments, subsidies, or grants if any are being offered to Uniswap?** ## KPI & Success Criteria **KPIs & Metrics** _Which KPI or Strategic Priority is this initiative targeting? There are generally 2 forms of projects:_ - _Growth-driven projects: on-chain, trackable metrics preferred here._ - _Strategic Initiatives: that targets a specific goal (e.g. Uniswap Foundation core initiatives). These are more completion based._ **Success Criteria** _What does success look like?_ **Risk Profile** _What potential risks are there for this project’s success? How could they be mitigated?_ ## Protocol security _Please address the following questions if you’re proposing a cross-chain deployment:_ - _Does the bridge support arbitrary message passing?_ - _Is the bridge secured by a trusted entity, by a multi sig, or a protocol/set of incentivized nodes?_ - _Does the bridge leverage the security of the source chain (e.g. Ethereum L1) or destination chain, or is security provided by another third party entity?_ - _Is it possible for a fraudulent message to be passed to the destination chain? If so, are there any recall mechanisms?_ - _What are the ramifications of fraud to the malicious actor?_ - _Has the bridge code been audited? By a third party? What attack vectors and vulnerabilities were identified, if any? Have the identified vulnerabilities been remedied?_ ## Timeline & Engagement Structure **Milestones** _What milestones are relevant for budget disbursement? Note: Preference placed towards milestones that are attached to KPI or Success Criteria._ _On what timeline is this partnership reevaluated for renewal, if relevant?_ - Duration & milestones of the engagement - Criteria after which engagement is considered complete ## On-Chain Details **Proposal Code** > **Proposal Code Listed Here** > > ```auto > Proposal code goes here > > ``` **Code Description** _In plain language, explain the intended state of the chain after a successful on-chain vote._ \*Note: _Proposal code_ _ **must** be included to proceed to the Consensus Check phase._ ## License exemption details **Legal entity receiving the exemption** _Sample language for a Layer 2 solution: "Team [or Company] X may use the Licensed Work to deploy it on Y, a layer 2 solution for Ethereum, provided that the deployment is subject to Ethereum layer 1 Uniswap Protocol governance and control.”_ ---
**Author:** ![dennisonb](https://sea2.discourse-cdn.com/flex016/user_avatar/gov.uniswap.org/dennisonb/32/1860_2.png) [@dennisonb](https://gov.uniswap.org/u/dennisonb)\ **Post date:** [January 5, 2023, 9:03pm UTC](https://gov.uniswap.org/t/proposal-template-2-0-upgrade-for-deployments-agreements/19936/2 "2023-01-05T21:03:12Z")
This is excellent to see. A question, where is this proposal to actually live- In the forum in this format? How should this proposal template translate to the voting platforms? IE: What should be used when creating a Snapshot versus what should be used when creating the On-Chain vote on Tally? It would be interesting to standardize this proposal template in general across proposals to make them easier to read, and act upon. ---
**Author:** ![tobyshorin](https://sea2.discourse-cdn.com/flex016/user_avatar/gov.uniswap.org/tobyshorin/32/3867_2.png) [@tobyshorin](https://gov.uniswap.org/u/tobyshorin)\ **Post date:** [January 5, 2023, 9:31pm UTC](https://gov.uniswap.org/t/proposal-template-2-0-upgrade-for-deployments-agreements/19936/3 "2023-01-05T21:31:53Z")
This isn’t really a proposal, it doesn’t need approval by the community to be used. It’s a heuristic that (I hope it is self-evident) is an improvement over the existing heuristics. Unfortunately the forum is basically the best thing we have for documentation. To your last point - most proposals are already converging to subsets of things identified in this template, so I’m expecting people to use some variation of this as time goes on.