Vote Type: Threshold Token Holder DAO GB Sponsors: Elected committee members of the Threshold Marketing Guild (MG). Full Budget Request: [MG 2024 Budget Request](https://docs.google.com/spreadsheets/d/19FBb4OdS2t3sKJR-TQqEvQF3_3in3nbDXjqvm4MY0tY/edit) Brief: This proposal seeks a budget of $306,000 USD for May - December 2024. The funds will support Threshold DAO’s marketing initiatives and cover the specified line items for administrative costs and program execution. Milestones and Deadlines: * Proposal Forum period - this proposal will be on the forum for a minimum of 5 days before moving to Snapshot. * Snapshot Voting - 5 days. If the proposal passes Snapshot it will move to GovernorBravo for on-chain governance and execution. * GovernorBravo - 10 days. Budget Management and Request Breakdown: Funds to be managed by the MG multi-sig wallet, with clear accounting and reporting for each category. Program: * Sponsorship and participation in major events including ETHBrussels, ETHOnline, ETHIndia, and others. * Content Creation: $35,000 to produce high-quality marketing and educational content. * Do Cool Shit MG Contributor Program: $25,000 * Discretionary Fund: $50,000 reserved for emergent needs and strategic opportunities. Administrative: * Tools & Subscriptions: $20,000* for essential software and services. * Gas Fees: $1,000 to cover transaction costs. * Other Administrative Costs: $5,000 for miscellaneous administrative expenses. Total Requested Budget: $306,000 USD for the overall growth and marketing initiatives of the Guild and DAO from May to December 2024. Expiry/Timing of Budget Spend: * There is no set expiry for the use of the budget, allowing for flexibility and strategic allocation. Transaction Details: * Funds should be directly transferred from the Threshold DAO GovernorBravo contract to the Marketing Guild Committee Multisig. ETH Address: [0xd55c4261145EA1752662faA0485AfBC8C431b0CA](https://etherscan.io/address/0xd55c4261145EA1752662faA0485AfBC8C431b0CA) Mitigating Loss of Value: * We request that in the event that the amount upon receipt by the MG is >4% below the requested budget, a singular “top-off” transaction be created and executed by the Threshold Council to reconcile the deficit. *$14,800 of the $20k software/services is Twitter Verified Affiliates Program, which includes $10k of advertising credits.

## tldr The goal of the proposal is to revoke minting permissions on the first two deprecated thUSD contracts as a security measure. This involves a streamlined process that addresses operational challenges under the current governance mechanism. ## Background Threshold USD has been built as a public good for the Threshold Network. Value is created for the Threshold DAO instead of captured by a protocol token. Deployment Details: First Deployment: *https://etherscan.io/token/0xa10a5e2d813a51374592d6ce440b149f01cf9a7d* was deployed on Oct/5/23 Second Deployment: *https://etherscan.io/token/0xac76FAB49c7b24b15d564f348C248C6791888965* was deployed on Oct/18/23 The thUSD token was designed with governable safeguards due to contracts immutability (Persistent on chain over time). One such parameter allows for control over the token mint list. There is a balance between the certainty of immutability with adapting to new information * The deployed contracts are immutable so users can audit and trust them * Upgradability is preserved through a mintlist on the thUSD token contract * Changes to the mintlist are made through a two step, time gated governance vote on Governor Bravo * Governance votes can be vetoed by the Threshold Council After the first deployment, it quickly became apparent that a new set of thUSD contracts had to be redeployed to correct and improve a performance feature in the stability pool, which is responsible for protecting the system during collateral liquidation processes (for details refer to the discussions in the B-protocol channel on discord). In contrast, the second deployment had to be also deprecated shortly after its launch due to a vulnerability reported by Tellor in their contracts. Since Tellor contracts are also immutable, it was essential to update our contracts to reflect the newly fixed Tellor price feed. Based on these discussions, a fix was implemented with the redeployment. **Therefore the first two sets of contracts were then deprecated.** ## Proposal As an additional security measure, the DAO should revoke Mint authorization for the collaterals on the deprecated first two thUSD token contracts. Authorized contracts to mint thUSD are the old borrowerOperations contracts for both collaterals (tBTC and ETH) of each deployment set. ### Revoke Mint Process The revoking mint capability process involves two steps on the token contract, executable only by the owner, which is Governor Bravo. The steps are startRevokeMintList and finalizeRevokeMintList, with a 90-day governance delay. This needs to be executed for the borrowerOperations contracts of each collateral for both sets of deployments. First Deployment BorrowerOperations for tBTC Collateral: 0xB38EE6134D20344f7Cb0DE58a2E857209F307072 [*(verify here)*](https://github.com/Threshold-USD/dev/blob/fb15ebed750fe1e206aa2a1b01fc4ad30c324e1b/packages/lib-ethers/deployments/default/tbtc/v1/mainnet.json) BorrowerOperations for ETH Collateral: 0x5E8e6374605C1FA413F50fB2bF9191bE20cc0f7E [*(verify here)*](https://github.com/Threshold-USD/dev/blob/fb15ebed750fe1e206aa2a1b01fc4ad30c324e1b/packages/lib-ethers/deployments/default/eth/v1/mainnet.json) The current BorrowerOperations contract mint capability of the first thUSD token deployed can be checked in mintList function in ](https://github.com/Threshold-USD/dev/blob/fb15ebed750fe1e206aa2a1b01fc4ad30c324e1b/packages/lib-ethers/deployments/default/eth/v1/mainnet.json)https://etherscan.io/address/0xa10A5e2d813a51374592D6ce440B149F01CF9A7D#readContract [1. The ](https://github.com/Threshold-USD/dev/blob/fb15ebed750fe1e206aa2a1b01fc4ad30c324e1b/packages/lib-ethers/deployments/default/eth/v1/mainnet.json)Governor Bravo calls startRevokeMintList for BorrowerOperations for ETH Collateral (0x5E8e6374605C1FA413F50fB2bF9191bE20cc0f7E) on the thUSD token contract [0xa10a5e2d813a51374592d6ce440b149f01cf9a7d](https://etherscan.io/token/0xa10a5e2d813a51374592d6ce440b149f01cf9a7d). 2[. ](https://github.com/Threshold-USD/dev/blob/fb15ebed750fe1e206aa2a1b01fc4ad30c324e1b/packages/lib-ethers/deployments/default/eth/v1/mainnet.json)After the governance delay of 90 days, Governor Bravo calls finalizeRevokeMintList on the thUSD token contract [0xa10a5e2d813a51374592d6ce440b149f01cf9a7d](https://etherscan.io/token/0xa10a5e2d813a51374592d6ce440b149f01cf9a7d). 3[. ](https://github.com/Threshold-USD/dev/blob/fb15ebed750fe1e206aa2a1b01fc4ad30c324e1b/packages/lib-ethers/deployments/default/eth/v1/mainnet.json)The Governor Bravo then calls startRevokeMintList for BorrowerOperations for tBTC (0xB38EE6134D20344f7Cb0DE58a2E857209F307072) on the same thUSD token contract [0xa10a5e2d813a51374592d6ce440b149f01cf9a7d](https://etherscan.io/token/0xa10a5e2d813a51374592d6ce440b149f01cf9a7d). 4[. ](https://github.com/Threshold-USD/dev/blob/fb15ebed750fe1e206aa2a1b01fc4ad30c324e1b/packages/lib-ethers/deployments/default/eth/v1/mainnet.json)After another 90 days, Governor Bravo calls finalizeRevokeMintList on the same thUSD token contract [0xa10a5e2d813a51374592d6ce440b149f01cf9a7d](https://etherscan.io/token/0xa10a5e2d813a51374592d6ce440b149f01cf9a7d). Second Deployment BorrowerOperations for tBTC: 0xf72E47D561D0dD5C685603e91c5FAF1FE92B7A8d BorrowerOperations for ETH Collateral: 0xeed6efEdc8a709b78C9Ce108777f412628e558e7 The current[ BorrowerOperations contract mint capability of the second thUSD token deployed can be checked in mintList function in ](https://github.com/Threshold-USD/dev/blob/fb15ebed750fe1e206aa2a1b01fc4ad30c324e1b/packages/lib-ethers/deployments/default/eth/v1/mainnet.json)[https://etherscan.io/address/0xac76FAB49c7b24b15d564f348C248C6791888965#readContrac](https://etherscan.io/address/0xa10A5e2d813a51374592D6ce440B149F01CF9A7D#readContract)t [1. The ](https://github.com/Threshold-USD/dev/blob/fb15ebed750fe1e206aa2a1b01fc4ad30c324e1b/packages/lib-ethers/deployments/default/eth/v1/mainnet.json)Governor Bravo calls startRevokeMintList for BorrowerOperations for ETH Collateral (0xeed6efEdc8a709b78C9Ce108777f412628e558e7) on the thUSD token contract [0xac76FAB49c7b24b15d564f348C248C6791888965](https://etherscan.io/token/0xac76FAB49c7b24b15d564f348C248C6791888965). 2. After the governance delay of 90 days, Governor Bravo calls finalizeRevokeMintList on the thUSD token contract [0xac76FAB49c7b24b15d564f348C248C6791888965](https://etherscan.io/token/0xac76FAB49c7b24b15d564f348C248C6791888965). 3. The Governor Bravo then calls startRevokeMintList for BorrowerOperations for tBTC (0xf72E47D561D0dD5C685603e91c5FAF1FE92B7A8d) on the same thUSD token contract [0xac76FAB49c7b24b15d564f348C248C6791888965](https://etherscan.io/token/0xac76FAB49c7b24b15d564f348C248C6791888965). 4. After another 90 days, Governor Bravo calls finalizeRevokeMintList on the same thUSD token contract [0xac76FAB49c7b24b15d564f348C248C6791888965](https://etherscan.io/token/0xac76FAB49c7b24b15d564f348C248C6791888965). * The existing procedures for each thUSD token deployment (first and second deployments) can happen simultaneously. This means that the Governance Bravo can initiate and progress the revoking process for both thUSD tokens at the same time. * Across both deployments, the Governance Bravo will need to execute a total of 8 function calls. This includes 4 calls (2 startRevokeMintList and 2 finalizeRevokeMintList) for each thUSD token deployment. * The entire procedure, spanning both deployments, should take 180 days to complete. This duration accounts for two 90-day governance delay periods, one for each set of borrower operations revoking process (one for ETH collateral and one for tBTC collateral) within each thUSD token deployment. ## Solution: thUSD Owner Contracts Recognizing the operational challenge this revocation process presents, we've developed a tailored solution: the deployment of two THUSD Owner contracts. Each of these contracts corresponds to a deprecated thUSD token that should get its mint capabilities revoked. This approach allows for a more streamlined and efficient revocation process. **Operational Role of the THUSD Owner Contracts** These contracts, managed by the Integrations Guild, will oversee the revocation process. Here's how they will function: * Each THUSD Owner contract will initiate and complete the mint list revocation for its respective thUSD token collateral. * This design significantly reduces the complexity involved in the revocation process, enhancing the operational efficiency of the DAO. * The contracts enable the Integrations Guild to transfer ownership of the thUSD tokens back to Governor Bravo when necessary. Addresses of the THUSD Owner Contracts: thUSD Owner Contract for 1st Deployment: [*0x883fC0B2EF845603a5c9012172e7F8c34c28d63* ](https://etherscan.io/address/0x883fC0B2EF845603a5c9012172e7F8c34c28d632)thUSD Owner Contract for 2nd Deployment: [*0x033951c469e54ef19Be43B19c70a4DD273026468*](https://etherscan.io/address/0x033951c469e54ef19Be43B19c70a4DD273026468) Request for Ownership Transfer The core of this proposal is to request the DAO to approve the transfer of ownership of the deprecated thUSD tokens to the THUSD Owner contracts. This transfer is crucial for implementing the outlined revocation process expeditiously and securely. ## Governance process for ad-hoc security issues This proposal is an ad-hoc action guided by the IG and the thUSD workgroup to enhance security and protect the community by disabling a functionality and avoiding confusion with the new thUSD deployment. This forum post should be active for 7 days to allow adequate time for questions and discussions. If there aren’t major issues or setbacks the voting process with enacting transactions will be triggered directly on GB avoiding the normal temp check process via Snapshot.

### Tl;dr The goal of this proposal is to add 10 community node operators to the tBTC Beta Staker program. ### Background tBTC currently relies on a permissioned group of nodes, referred to as "Beta Stakers", to secure the wallets that contain the BTC that backs tBTC. These nodes are highly reliable, and stake a significant amount of T. The goal of Part 2 of TIP-067 is to expand the Beta Staker by adding 10 additional community run nodes, and T staked across the beta staker nodes by 400M T. An increase in the number of beta staker nodes will increase the geographic dispersion of beta-stake operators, and also increase the distribution of key shares during DKG ceremony to improve system decentralization. ### Proposal The tBTC development team will vet and select 10 community node operators from applicants via this forum to be added to the Beta Staker permissioned group. ### Duration New Beta Stakers will be required to run their respective nodes until the conclusion of the Beta Staker program, expected to occur within 12 months. It is not possible to exit the Beta Staker program once added, which means that operators must continue to participate until the retirement of the program. ### Requirements Operators of Beta Staker nodes are expected to be extremely responsive, especially in regards to upgrades requested by software contributors. Ideally, they should be able to upgrade their nodes within 24 hours of notification. Community applicants will be vetted for demonstrable uptime via a review of historical T rewards, led by the Integrations Guild. Operators of Beta Staker nodes must be technically capable. They are responsible for ensuring high availability (more than 96% uptime) and security of the node. A Beta Staker node performs more computationally expensive operations (DKG, threshold signing, etc) compared to a standard Threshold node. To ensure a high level of service, a Beta Staker node requires a machine with: * 4 CPUs * 4 GB of RAM * 1 GB of persistent disk space * 80 Mbps of network bandwidth * Linux OS Other requirements include: * At least 1 year of historical uptime OR strong community presence and technical skills. * A minimum stake of 40M T, directly owned or delegated. Additional documentation can be found here: [https://docs.threshold.network/staking-and-running-a-node/tbtc-Beta Stakers-program](https://docs.threshold.network/staking-and-running-a-node/tbtc-beta-stakers-program) The DAO will reimburse Ethereum transaction fees (in ETH) directly to the respective operator addresses on a quarterly basis. ### Payment The DAO will make a payment of $1,500 USD/month to each community participant to cover additional overheads. Additional terms: * Payment terms are subject to nodes meeting the 96% uptime requirement in the month prior. Uptime below the minimum will result in forfeiture of that month’s payment. * Payments will be made in T in accordance with the T/USD price at 10am UTC on the final day of the month, as reported by CoinGecko. * Cost for the program will be covered by staking rewards generated from the delegated T in TIP-067 Part 1. * T rewards will be claimable by the Treasury Guild and distributed accordingly. ### Indicative Timeline * Nominations & Discussion Period - December 13th - December 27th * Candidate selection period - December 27th - January 3rd * Technical setup and troubleshooting - January 3rd - January 17th * Treasury Guild Delegation Execution - January 18th * New Beta Stakers added incrementally - January 19th - onward