# Complete Arbitrum and Base Comet Upgrade
## Summary
This is a follow-up to [Proposal 596](https://www.tally.xyz/gov/compound/proposal/596), which upgraded Comets on Arbitrum and Base to v1.2.1. That upgrade was split per network into a sub-proposal that bumped the Comet Factory's version to 1.2.1 and a sub-proposal that redeploys each Comet from that same factory.
The execution automation ran these out of order, so the redeploy step for four Comets ran before the factory's version was bumped, deploying the prior version instead:
- Arbitrum cUSDTv3 ('0xd98Be00b5D27fc98112BdE293e487f8D4cA57d07')
- Arbitrum cWETHv3 ('0x6f7D514bbD4aFf3BcD1140B7344b32f063dEe486')
- Base cAEROv3 ('0x784efeB622244d2348d4F2522f8860B96fbEcE89')
- Base cWETHv3 ('0x46e6b214b524310239732D51387075E0e70970bf')
These four are now on an earlier Service Patch release rather than v1.2.1. That patch predates v1.2.1 and does not include the auditor-identified fix for under-paying suppliers when a market has no borrowers, but since all those markets are live there is no impact on current functionality or funds. All other Comets from Proposal 596 upgraded correctly and are unaffected.
The Comet Factory is already at v1.2.1, so this proposal just re-runs 'deployAndUpgradeTo' for the four Comets to finish the upgrade.
## Proposal Actions
The first action sends a cross-chain message to Arbitrum calling 'deployAndUpgradeTo' for cUSDTv3 and cWETHv3.
The second action sends a cross-chain message to Base calling 'deployAndUpgradeTo' for cAEROv3 and cWETHv3.
# Update Comet version on Linea and Scroll
## Proposal summary
This proposal upgrades the Compound III USDC and WETH markets on Linea and the USDC market on Scroll to a new Comet version that changes how the base supply index is capped in markets that have lenders but no borrowers.
Previously, `accruedInterestIndices()` applied a post-accrual clamp: whenever `totalBorrowBase == 0`, if `presentValueSupply(totalSupplyBase)` exceeded the Comet's base token balance, `baseSupplyIndex` was forced down to `(balance * BASE_INDEX_SCALE) / totalSupplyBase`. This protected lender withdrawals in reserve-funded markets with no borrowers, but only corrected the index after it had already been pushed too far.
The new version enforces the same cap earlier, in `getSupplyRate()`: when utilization is `0` and `presentValueSupply(totalSupplyBase) >= balanceOf(this)`, the supply rate returns `0`, so accrual stops before the index overshoots rather than being corrected after the fact. Because a single accrual step still applies one rate over the full `timeElapsed`, a long gap between accruals can still overshoot the cap by a few wei; after that, `getSupplyRate()` returns `0` and the supply index no longer increases.
Further detailed information can be found in the corresponding [pull request](https://github.com/compound-finance/comet/pull/1139).
## Audit
The new Comet version has been audited by [Certora](https://certora.cdn.prismic.io/certora/o_tSg8jfh3YhErQ7_Woof-CometPRs-FinalReport.pdf) and no issues were found.
## Proposal Actions
The first action updates the Comet implementation version in V2 Factory on Linea and deploys and upgrades the USDC and WETH Comets to the new implementation.
The second action updates the Comet implementation version in V2 Factory on Scroll and deploys and upgrades the USDC Comet to the new implementation.
# Update cbBTC price feeds on Base to SVR
## Proposal summary
This proposal updates the cbBTC price feeds in the Compound III AERO, USDC, USDS, and WETH markets on Base to use the new SVR price feeds.
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1129) and [forum discussion for SVR](https://www.comp.xyz/t/request-for-proposal-rfp-oracle-extractable-value-oev-solution-for-compound-protocol/6786).
### SVR fee recipient
SVR generates revenue from liquidators and Compound DAO will receive that revenue as part of the protocol fee. The fee recipient for SVR on Base is set to Compound DAO multisig: 0xb3e79c7cac540ca833015e63d96d3032ba0c4129.
## Proposal Actions
The first action updates the cbBTC price feeds in the AERO and WETH markets.
The second action updates the cbBTC price feeds in the USDC and USDS markets.
# Franchiser Operational Upgrade and Rebalance
## Summary
This proposal upgrades Compound's treasury-delegation (Franchiser) system to a new pool-based architecture and, in the same step, carries out the first scheduled biannual delegate rebalancing under **Proposal 504 — [Compound Delegate Race (Cycle 2)](https://www.comp.xyz/t/compound-delegate-race-cycle-2/7302)**.
The total COMP delegated through the program does not change. Existing delegations migrate to the new pool with no interruption to voting power, and the pool reclaimed from under-participating delegates is redistributed to qualified active delegates. COMP remains in Governance-owned contracts throughout.
## Background
Proposal 504 established a standing six-monthly review of treasury-delegated voting power, with a uniform on-chain participation standard and a defined reallocation procedure. The first review window (Proposals 505–586) has closed and participation has been verified on-chain. The full review, application window, and waterfall are documented on the forum: [comp.xyz/t/7862](https://www.comp.xyz/t/7862).
## What this proposal does
1. **Upgrade.** Migrate the treasury-delegation program to the upgraded Franchiser pool: existing delegations move into a new Governance-funded pool, with the CGWG multisig set as Coordinator and a Guardian set for emergency oversight. Governance retains sole authority to fund, halt, or reclaim the pool in full.
2. **Rebalance.** As part of the migration, three delegations that fell below the participation standard are not renewed — releasing **81,178.58 COMP** — which is redistributed to the qualified applicants per the waterfall.
**Not renewed — 81,178.58 COMP reclaimed:**
| Delegatee | Address | COMP |
|---|---|---:|
| Michigan Blockchain | `0x13BD…8548` | 29,999.88 |
| Reservoir / AlphaGrowth | `0x4f89…fd3c` | 50,000.00 |
| Sharp | `0x72C5…7708` | 1,178.70 |
**Reallocated — 81,178.58 COMP:**
| Delegate | Address | COMP |
|---|---|---:|
| FranklinDAO | `0x0703…961b` | 8,262.46 |
| DAOplomats | `0xc554…7759` | 40,000.00 |
| blockful | `0x1F3D…0591` | 32,916.12 |
## The upgraded architecture
The upgrade replaces per-delegation Franchiser deployments with a single pool, split across three role-gated contracts:
- **FranchiserPoolFactory** — the Governance-only entry point. Governance creates, funds, and can halt a pool; halting recalls all delegates and returns the full COMP balance to the Timelock (the only path for COMP to leave the program).
- **FranchiserPool** — holds the program's idle COMP. A **Coordinator** (the CGWG multisig) can `delegate`, `recall`, and `reassign` voting power among delegates within Governance-set limits. A separate **Guardian** can emergency-`recall` a delegate or `freeze` the pool (10-day minimum), but can never move or delegate COMP.
- **Franchiser** — unchanged from V1: holds delegated COMP and grants voting power to a delegatee (who may name up to one sub-delegate).
Governance (the Timelock) sets each pool's parameters — delegate cap, Coordinator, Guardian, freeze period — and can change them or halt the program at any time by on-chain vote.
## Guarantees
- **Delegation only, never custody.** COMP stays in Governance-owned contracts at every step (Timelock → pool → Franchiser); no working group, Coordinator, or Guardian ever takes custody of the tokens.
- **Total set by governance.** This proposal does not change the program's total delegated COMP — it migrates and reallocates the existing pool. Any change to the total returns to an on-chain vote, and Governance can recall or reassign any delegation at any time.
# Update Linea and Scroll Comets to the service patch version
## Proposal summary
WOOF! proposes upgrading the Linea cUSDCv3, cWETHv3, and Scroll cUSDCv3 Comet markets to a new service patch version introducing several improvements and security enhancements:
- Extended Pause Controls: collateral interactions can now be paused independently per collateral asset.
- Price Feed Patch (Post-USDM incident response): skips price feed calls for assets with zero collateral factor, preventing unnecessary reverts.
- Collateral Deactivation Mechanism: introduces a Guardian-controlled emergency mechanism to deactivate unsafe collateral assets, with reactivation requiring a governance proposal.
- Utilization Peaking Protection: caps utilization at 200%, preventing additional borrowing when post-borrow utilization exceeds this threshold, while preserving lender withdrawals.
- Borrow Index Fix (Empty Market): prevents borrow interest accrual in markets without active borrowers.
- Supply Index Fix (Empty Market): ensures supply index only accrues when lenders are present.
- Lender Illiquidity Fix in Zero-Borrow Markets: prevents reserve depletion in markets with no borrowers by capping supply rate to zero when utilization is zero and reserves are exhausted.
- Accrue Interest on Collateral Actions (Post-USDM incident response): collateral actions (supply, withdraw, transfer) now trigger interest accrual for affected accounts.
- Technical Improvements: includes removal of redundant arguments in supplyInternal() and optimized price caching in absorbInternal(), improving gas efficiency without affecting protocol behavior.
This proposal takes the governance steps recommended and necessary to update Compound III USDC and WETH markets on Linea and Scroll. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario).
Detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1118).
### Bytecode Repository
This update is done with the use of the bytecode repository, which provides trustless and deterministic deployments.
Further details on the deployment can be found in the [Bytecode Repository git](https://github.com/woof-software/bytecode-repository) and [forum discussion](https://www.comp.xyz/t/rfc-bytecode-repository-and-deployment-pipeline-modernization/6965).
### Audit
Both service patch Comet update and Bytecode Repository have been audited by Certora and full reports can be found here:
- [Certora Comet Service Patch Audit](https://www.certora.com/reports/comet-service-patch)
- [Certora Bytecode Repository Audit](https://www.certora.com/reports/compound-bytecoderepository)
## Proposal Actions
The first action sets the factory to the newly deployed factory, extension delegate to the newly deployed contract and deploys and upgrades Comet to a new version on Linea.
The second action sets the factory to the newly deployed factory, extension delegate to the newly deployed contract and deploys and upgrades Comet to a new version on Scroll.
# Supply Cap Reduction Across L2 Comets
## Proposal summary
WOOF! proposes to update supply caps on cUSDCv3, cUSDC.ev3, cUSDTv3 and cWETHv3 on Arbitrum, cUSDCv3 and cWETHv3 on Base, cWETHv3 on Linea and cUSDev3 on Mantle networks. This proposal takes the governance steps recommended and necessary to update a Compound III markets on each network. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters are based on the [recommendations from Gauntlet](https://www.comp.xyz/t/supply-cap-reduction-across-l2-comets/7794/1).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1120) and [forum discussion](https://www.comp.xyz/t/supply-cap-reduction-across-l2-comets/7794).
## Proposal Actions
The first action sends a message to the Arbitrum network to update supply caps on the USDC and USDC.e Comets.
The second action sends a message to the Arbitrum network to update supply caps on the USDT and WETH Comets.
The third action sends a message to the Base network to update supply caps on the USDC and WETH Comets.
The fourth action sends a message to the Linea network to update supply caps on the WETH Comet.
The fifth action sends a message to the Mantle network to update supply caps on the USDe Comet.
# Ethereum Supply cap Reduction Across USD Based Comets
## Proposal summary
This proposal updates supply caps for a number of assets across the USD based Mainnet markets. The supply caps for the affected assets are being updated based on their current utilization and risk parameters.
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1115) and [forum discussion](https://www.comp.xyz/t/ethereum-supply-cap-reduction-across-comets/7793).
## Proposal actions
1 - 7. Updates supply caps for weETH and mETH to 0 and tBTC to 73, sFRAX to 33M, UNI to 310,336, and LINK to 210,317 on cUSDTv3 market and upgrades the Comet implementation to apply the changes.
8 - 10. Updates supply caps for weETH and tBTC to 0 on cUSDSv3 market and upgrades the Comet implementation to apply the changes.
11 - 14. Updates supply caps for tBTC to 40, UNI to 364,691, and LINK to 585,990 on cUSDCv3 market and upgrades the Comet implementation to apply the changes.
# Ethereum Supply cap Reduction Across Comets
## Proposal summary
This proposal updates supply caps for a number of assets across the Mainnet markets. The supply caps for the affected assets are being updated based on their current utilization and risk parameters.
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1115) and [forum discussion](https://www.comp.xyz/t/ethereum-supply-cap-reduction-across-comets/7793).
## Proposal actions
1 - 4. Updates supply caps for weETH and ezETH to 0 and tETH to 44 on cWstETHv3 market and upgrades the Comet implementation to apply the changes.
5 - 15. Updates supply caps for wOETH, tBTC, rswETH, rETH, osETH, and ETHx to 0 and weETH to 3,860, tETH to 1,545, pufETH to 105, and ezETH to 33,163 on cWETHv3 market and upgrades the Comet implementation to apply the changes.
16 - 18. Updates supply caps for pumpBTC and LBTC to 0 on cWBTCv3 market and upgrades the Comet implementation to apply the changes.
19 - 25. Updates supply caps for weETH and mETH to 0 and tBTC to 73, sFRAX to 33M, UNI to 310,336, and LINK to 210,317 on cUSDTv3 market and upgrades the Comet implementation to apply the changes.
26 - 28. Updates supply caps for weETH and tBTC to 0 on cUSDSv3 market and upgrades the Comet implementation to apply the changes.
29 - 32. Updates supply caps for tBTC to 40, UNI to 364,691, and LINK to 585,990 on cUSDCv3 market and upgrades the Comet implementation to apply the changes.
# WETH Comets Interest Rate Curve Recommendations on L2 networks
## Simple Summary
Given heightened market activity and elevated volatility across ETH markets Gauntlet recommends the following Interest Rate (IR) Curve updates across WETH comets on Ethereum. These changes are designed to keep borrow costs low and avoid liquidations during the volatile period.
## Motivation
The recent Kelp exploit has led to heightened volatility and shifting dynamics across ETH-correlated assets. In this environment LST/LRT-based looping strategies are facing a significantly high negative carry. The recommendations below flatten the slope below kink and compress the slope above kink resulting in lower kink and max borrow rates across all WETH markets.
The intent is to:
* Keep Compound’s WETH borrow rates not too high so that unwinding can happen gradually in a volatile environment.
* Decrease existing borrow positions gradually without pushing rates to a level that would unwind a high amount of the existing ETH-leverage positions. We will continue to monitor utilization and reserve growth and will adjust as conditions evolve.
## Specification
Target APRs at kink and at 100% utilization across the comets:
| Comet | Kink Rate | Max Rate |
| --------------- | --------- | -------- |
| Base WETH | 1.50% | 3.00% |
| Arbitrum WETH | 1.50% | 3.00% |
| Optimism WETH | 1.50% | 3.00% |
| Linea WETH | 1.50% | 3.00% |
| Unichain WETH | 1.50% | 3.00% |
Borrow kink is held at 90% across all markets. The base rate is held constant at current values. Slope Low and Slope High are updated to achieve the target kink and max rates above. [Forum Post](https://www.comp.xyz/t/weth-comet-interest-rate-curve-recommendations/7749)
# Reduce Borrow Collateral Factor and Supply Caps for USDe to 0 on Ethereum
This proposal reduces the Collateral Factor utilized on borrow and Supply Caps for USDe; once executed, USDe on Ethereum markets can not be used as collateral for new loans. Note that this proposal will not directly trigger any liquidations as the liquidation collateral factor remains unchanged.
The proposal will minimize the potential risk of an rsETH hack in case it affects USDe. 
# Update price feeds in cWETHv3 on Unichain with CAPO implementation.
## Proposal summary
This proposal updates existing price feed for wstETH, weETH, ezETH, and rsETH on the cWETHv3 market on Unichain.
### CAPO summary
CAPO is a price oracle adapter designed to support assets that grow gradually relative to a base asset - such as liquid staking tokens that accumulate yield over time. It provides a mechanism to track this expected growth while protecting downstream protocol from sudden or manipulated price spikes. wstETH, weETH, ezETH, and rsETH price feeds are updated to their CAPO implementation.
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1068) and [forum discussion for CAPO](https://www.comp.xyz/t/woof-correlated-assets-price-oracle-capo/6245).
### CAPO audit
CAPO has been audited by [OpenZeppelin](https://www.comp.xyz/t/capo-price-feed-audit/6631, as well as the LST / LRT implementation [here](https://www.comp.xyz/t/capo-lst-lrt-audit/7118).
## Proposal actions
The first action updates wstETH, weETH, ezETH, and rsETH price feeds to the CAPO implementation. This sends the encoded 'updateAssetPriceFeed' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Unichain.
# Return accidentally send funds
## Proposal summary
This proposal returns accidentally sended funds to a cUSDTv3 on Mainnet. Funds will be sent back to the user.
Further detailed information can be found on the corresponding [forum discussion](https://www.comp.xyz/t/woof-correlated-assets-price-oracle-capo/6245).
Accidental transfer tx hash: 0x92b03289ad09323ec897e106442096f3fc07f4c9cee4e02add7ee2b672d865e3
Amount sent: 19_958.414155
User address: 0x34074a8706e952a02f8a3def416bab745b54a3ed
## Proposal actions
The first action withdraws accidentally sent funds from a comet and transfers them back to the user.
# Service Providers Stream Revision
*Following the community discussion in [Service Providers Stream Revision](https://www.comp.xyz/t/service-providers-stream-revision/7622), this post presents the formal on-chain proposal with exact figures.*
## Summary
This proposal migrates all active Compound service provider streams from COMP to USDC, covering Risk Management, Security Services, Development, and Governance workstreams. New USDC streams will be created to fulfill remaining obligations for each vendor without further drawing down COMP reserves.
## Current Stream Balances
*Snapshot taken at 2026-02-23T21:08:16.000Z*
| Service Provider | Claimed to Date (USD) | Remaining Stream Balance (COMP) | Governance Pipeline (days) | Termination Period (days) | Stream Runway (days) |
| ----- | ----- | ----- | :---: | :---: | :---: |
| Woof Software | $ 1,471,298.3257 | 7,889.46 | 6.5 | 0 | 24.76 |
| SSP | $ 872,464.2314 | 8,451.24 | 6.5 | 60 | 30.16 |
| ZeroShadow | $ 112,235.8257 | 2,048.62 | 6.5 | 60 | 51.17 |
| Tally | $ 76,098.0594 | 812.49 | 6.5 | 30 | 33.82 |
| Gauntlet | $ 609,124.0183 | 13,393.04 | 6.5 | 60 | 51.95 |
**Definitions:**
- **Governance Pipeline** — Minimum days required for an on-chain proposal to pass (6.5 days).
- **Termination Period** — Days required to sweep a stream balance after cancellation, per each provider's agreement.
- **Stream Runway** — Days until the remaining COMP stream balance is fully claimed at the current COMP price.
## Stream Deficit Analysis
The table above shows that all streams, except Woof have a runway longer than the combined governance pipeline + termination period. This means that in the time required to pass and execute this proposal, providers will continue claiming COMP and their stream balances may be partially or fully depleted before the sweep occurs.
To conservatively estimate the remaining claimable COMP value, we assume an average COMP price of **$14** over the next **66.5 days** (governance pipeline + maximum termination period).
| Service Provider | Remaining Balance (COMP) | Assumed COMP Price | Total USD Value at $14 | Claimed to Date (USD) | Time to Termination (days) | COMP Claimed by Termination (USD at $14) | Estimated Deficit (USD) |
| :---- | :---- | :---- | :---- | :---- | :---- | :---- | :---- |
| Woof Software | 7,889.46 | $14 | $ 110,452.3879 | $ 1,471,298.3257 | 6.5 | $ 64,418.6327 | $ 464,283.0416 |
| SSP | 8,451.24 | $14 | $ 118,317.3916 | $ 872,464.2314 | 66.5 | $ 118,317.3916 | $ 759,218.3771 |
| ZeroShadow | 2,048.62 | $14 | $ 28,680.6323 | $ 112,235.8257 | 66.5 | $ 28,680.6323 | $ 109,083.5419 |
| Tally | 812.49 | $14 | $ 11,374.8534 | $ 76,098.0594 | 36.5 | $ 11,374.8534 | $ 62,527.0873 |
| Gauntlet | 13,393.04 | $14 | $ 187,502.6130 | $ 609,124.0183 | 66.5 | $ 187,502.6130 | $ 813,373.3687 |
**Total estimated deficit across all streams: 2,208,485.4166 USDC**
The deficit represents the gap between the USD value each provider is owed under their mandate and what they will have received by the time existing streams are terminated and swept.
[[Detailed calculations](https://docs.google.com/spreadsheets/d/1QVdpxSbFP5p83aoSaGBsO2M_kYE8NIMxthqSiFBFL3Q/edit?gid=0#gid=0)]
## New USDC Streams
To cover the deficit, this proposal creates five new USDC streams — one per service provider. Funding will be sourced primarily from the [Aera Vendor Vault](https://app.aera.finance/vaults/eth:0x8624f61cc6e5a86790e173712afdd480fa8b73ba), with a supplemental draw from the [Aera Reserves Vault](https://app.aera.finance/vaults/eth:0x3d6eef6a92b15361697698695334e98c5db91d6b) as needed.
| Service Provider | Recipient Address | USDC Stream Amount |
| :---- | :---- | :---- |
| Woof Software | 0x72bf2d7b05152ef282805f3e38752c436d94e4af | $ 464,283.0416 |
| SSP | 0xba3cdb9d5c2119137126989f81edaea8b50331d2 | $ 759,218.3771 |
| ZeroShadow | 0xe9c21ebc3815cdfbe07f721126d3cb46407fd79a | $ 109,083.5419 |
| Tally | 0x96a0029c945898de1072ea8f33aa88b7fde3b125 | $ 62,527.0873 |
| Gauntlet | 0x12875aed495cd573433f0c93d538c0ccc9e2b8fa | $ 813,373.3687 |
## Surplus Reconciliation
Because this proposal uses estimated values — including the assumed $14 average COMP price and variable governance timeline — the USDC streams are intentionally sized slightly above the minimum required to avoid any shortfall. Once all COMP streams are fully terminated and swept, Woof Software will publish a final reconciliation report and coordinate with each service provider to return any surplus USDC to the Compound Timelock.
## On-Chain Actions
This proposal will execute the following:
1. Cancel all active COMP streams to the five service providers
2. Withdraw USDC from the Aera Vendor and Aera Reserves Vaults
3. Fund new USDC streams for each service provider based on the deficit amounts above
# Depreciate cWRONv3 on Ronin
## Proposal summary
This proposal updates price feeds to API3, since Chainlink soon will no longer support Ronin and updates interest rate curve parameters for WRON market on Ronin.
It is done to prevent new suppliers from entering the market, reduces capital efficiency, making the market less appealing without causing users to become liquidatable and raises liquidation penalty to further disincentivizes usage by increasing the cost of liquidation, while reducing risk to the comet.
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1084) and [forum discussion](https://www.comp.xyz/t/gauntlet-depreciating-ronin-weth-and-wron-comets/7308).
## Proposal actions
The first proposal action approves the L1CCIPRouter to transfer GHO stable token from the timelock to pay for the proposal execution fee on Ronin.
The second proposal action sends the following encoded calls to the governance receiver on Ronin:
- Update USDC, WETH, AXS, and WRON price feeds to API3 oracle
- Set supply caps to 0 for all collateral assets
- Reduce collateral factors
- Increase liquidation penalties
- Update interest rate curve parameters:
- `setBorrowPerYearInterestRateBase`
- `setBorrowPerYearInterestRateSlopeLow`
- `setBorrowKink`
- `setBorrowPerYearInterestRateSlopeHigh`
- `setSupplyPerYearInterestRateBase`
- `setSupplyPerYearInterestRateSlopeLow`
- `setSupplyKink`
- `setSupplyPerYearInterestRateSlopeHigh`
- Deploy and upgrade to new configuration via `deployAndUpgradeTo`.
# Creation of the Ecosystem Protection and Continuity Fund (EPCF)
**SUMMARY**
This proposal establishes a capped, time-limited Ecosystem Protection and Continuity Fund (“**EPCF**”) to ensure that the Compound ecosystem can respond rapidly and effectively to events that can challenge the integrity, security, or operational continuity of the protocol or its participants. The EPCF authorizes the Compound Foundation to deploy resources, within defined constraints, to address adverse situations such as critical security incidents, parameter or governance attacks, regulatory or administrative challenges, actions targeting individual ecosystem contributors or service providers, or other material disruptions to ecosystem functioning.
The EPCF will be capitalized with USD 5,000,000 in USDC from the COMP Treasury, held in a Foundation-controlled wallet for a period of 48 months (and any unused funds will be returned to the COMP Treasury automatically at the end of this 48 month period). Disbursements may be made at the Foundation’s discretion, subject to a post-use disclosure obligation that respects overriding legal or regulatory constraints. The EPCF may be replenished only via a new governance action.
**MOTIVATION**
Compound has reached a stage of maturity where various forms of adversarial activity pose direct risks to ecosystem continuity. These types of risk include:
* External emergencies (e.g. Elixir de-peg).
* Situations in which adversarial or unanticipated interactions with protocol systems or dependencies create time sensitive operational failures that cannot be effectively resolved through standard governance processes alone.
* Actions by external actors (including regulatory bodies, technical and other types of adversaries, or market participants) that materially impair the ecosystem’s ability to function.
* Targeted actions against essential contributors, service providers, or infrastructure nodes whose impairment would create systemic operational risk.
* Circumstances in which rapid response capacity is necessary to avoid broader contagion or compensating losses across protocol participants.
The ecosystem’s history demonstrates that risks like these can and do manifest, and can harm the ecosystem. The ecosystem’s current governance and treasury architecture does not provide a pre-authorized, rapid-deployment capital mechanism for these categories of threats. Without such a mechanism, the ecosystem is exposed to delays, governance gridlock, and information-sensitive bottlenecks at precisely the moments rapid execution is required.
The EPCF resolves this structural deficiency by creating a flexible, time-bounded, and accountable fund that can be deployed by the Foundation to maintain ecosystem resilience.
The USD 5,000,000 fund size has been proposed as a good faith estimate of potential worst-case exposure across multiple concurrent ecosystem threats over the EPCF’s duration.
**SPECIFICATION**
**1. Establishment of the EPCF**
* Create the Ecosystem Protection and Continuity Fund (EPCF).
* Capitalization: USD 5,000,000 equivalent denominated in USDC, transferred from COMP Treasury to a Foundation-controlled two-of-three multi-sig wallet (SSP/vCISO (as part of their mandate) as the other signer).
* Duration: 48 months from the date of fund creation. At expiration, unused assets are returned to the COMP Treasury unless governance renews or modifies the Fund.
**2. Purpose and Scope of Use**
EPCF resources may be used solely for actions that directly protect or preserve the integrity, operational continuity, or security of the Compound ecosystem. Categories (non-exhaustive):
* Technical incident response and mitigation, including emergency work by external security firms or specialized contributors.
* Countermeasures in the event of governance manipulation, concentration attacks, or protocol-level decision-making impairments.
* Response to regulatory, administrative, litigation or other external actions that materially disrupt protocol operations or the functioning of essential ecosystem participants.
* Protection of key contributors, infrastructure providers, or service firms when hostile or coercive action against them endangers broader ecosystem continuity.
* Any other verifiable ecosystem-level threat where rapid intervention materially reduces systemic risk.
This scope is intentionally general. The purpose is protection of the ecosystem’s functioning, not the advancement of any party’s private interests.
**3. Asset Management and Governance Participation**
Subject always to the EPCF’s primary purpose as an ecosystem protection and continuity mechanism, the Foundation may, in its discretion:
* deploy idle EPCF assets in a manner intended to preserve capital and generate modest yield, including through low-risk on-chain or off-chain strategies;
* convert a portion of EPCF assets into COMP and delegate such COMP for the purposes of participating in Compound governance. Any such delegation shall be undertaken with the objective of supporting protocol integrity, continuity, and effective governance.
* Funds will be always held in the designated multisigs.
Yield-generation activities and governance participation must not impair the Foundation’s ability to deploy EPCF assets rapidly in response to qualifying ecosystem threats.
**4. Administration and Discretion**
* The Compound Foundation is authorized to manage the EPCF for the benefit of the ecosystem.
* The Foundation may advance or deploy funds at its discretion when, in its judgment, such use is necessary to mitigate or address a qualifying ecosystem threat.
* The Foundation must treat EPCF assets as segregated, special-purpose funds.
**5. Transparency and Reporting**
* The Foundation must provide the community with a high-level update within a reasonable period after any EPCF deployment.
* Reporting must balance transparency with legal, regulatory, and security constraints.
* If disclosure would prejudice the integrity of ongoing ecosystem protection, the Foundation may defer or redact details; however, it must provide disclosure at the earliest point at which constraints no longer apply.
**6. Wallet and Controls**
* EPCF assets will be held in a two-of-three multi-sig wallet, with the Foundation nominated two signers and the other signer nominated by ChainSecurity.
* The wallet address will be published upon fund creation.
* The EPCF may not be commingled with general Foundation operational reserves.
**7. Replenishment Mechanism**
* Governance may, but is not required to, replenish the EPCF up to its USD 5,000,000 cap.
* Any replenishment requires a new governance proposal.
**8. Wind-Down**
* At the end of 48 months, all unused funds return to the COMP Treasury unless governance renews or revises the EPCF.
* The Foundation must publish a closing report after wind-down, subject to the same legal and security constraints as interim reporting.
**RATIONALE**
This structure provides:
* Rapid response capacity without requiring governance action during an emergency event.
* Bounded discretion via a capped amount, time limitation, and mandatory disclosure framework.
* Protection of information-sensitive matters that cannot be publicly described at the outset without increasing ecosystem risk.
* Institutional alignment with the Foundation’s mandate to safeguard protocol continuity.
* Clear accountability to governance through mandatory reporting and return of unused assets.
* Minimal surface area for misinterpretation, avoiding explicit mention of legal defense while clearly enabling it under the broader ecosystem protection purpose.
This mirrors the structure used in the creation of the Compound Foundation—governance grants a defined authority, for a defined purpose, with finite capital and clear oversight.
**IMPLEMENTATION**
1. Transfer USD 5,000,000 equivalent from the COMP Treasury to the EPCF wallet.
2. Publish wallet address and initialize internal controls.
3. Foundation activates reporting schedule.
4. Governance tracker updated to reflect EPCF creation and 48-month expiry.
**CONCLUSION**
The EPCF ensures the Compound ecosystem has a pre-authorized, accountable, and operationally effective mechanism for handling adversarial events. It strengthens resilience, reduces systemic risk, and establishes a governance-aligned model for emergency response.
# Add XAUt as collateral into cUSDTv3 on Ethereum
## Proposal summary
WOOF! proposes to add XAUt into cUSDTv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDT market on Ethereum.
Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/gauntlet-xaut-risk-recommendations-for-mainnet-usdt/7539/1).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1085) and [forum discussion](https://www.comp.xyz/t/gauntlet-xaut-risk-recommendations-for-mainnet-usdt/7539).
## Proposal Actions
The first proposal action adds XAUt asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
# Depreciate cWETHv3 on Ronin
## Proposal summary
This proposal updates price feeds to API3, since Chainlink soon will no longer support Ronin and updates interest rate curve parameters for WETH market on Ronin.
It is done to prevent new suppliers from entering the market, reduces capital efficiency, making the market less appealing without causing users to become liquidatable and raises liquidation penalty to further disincentivizes usage by increasing the cost of liquidation, while reducing risk to the comet.
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1083) and [forum discussion](https://www.comp.xyz/t/gauntlet-depreciating-ronin-weth-and-wron-comets/7308).
## Proposal actions
The proposal sends the following encoded calls to the governance receiver on Ronin:
- Update USDC, AXS, and WRON price feeds to API3 oracle
- Set supply caps to 0 for all collateral assets
- Reduce collateral factors
- Increase liquidation penalties
- Update interest rate curve parameters:
- `setBorrowPerYearInterestRateBase`
- `setBorrowPerYearInterestRateSlopeLow`
- `setBorrowKink`
- `setBorrowPerYearInterestRateSlopeHigh`
- `setSupplyPerYearInterestRateBase`
- `setSupplyPerYearInterestRateSlopeLow`
- `setSupplyKink`
- `setSupplyPerYearInterestRateSlopeHigh`
- Deploy and upgrade to new configuration via `deployAndUpgradeTo`.
# Add USDC and USDT as collaterals into cWBTCv3 on Mainnet
## Proposal summary
WOOF proposes to add USDC and USDT into cWBTCv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III WBTC market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based on the [recommendations from Gauntlet](https://www.comp.xyz/t/gauntlet-usdc-usdt-risk-recommendations-for-mainnet-weth-wbtc-comets/7387/1).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1067) and [forum discussion](https://www.comp.xyz/t/gauntlet-usdc-usdt-risk-recommendations-for-mainnet-weth-wbtc-comets/7387).
## Proposal Actions
The first action adds USDC asset as collateral with corresponding configurations.
The second action adds USDT asset as collateral with corresponding configurations.
The third action upgrades Comet to a new version.
# Update price feeds in cUSDCv3, cUSDTv3 and cWETHv3 on Optimism with CAPO implementation.
## Proposal summary
This proposal updates existing price feeds for wstETH on the USDC, USDT and WETH markets and ezETH, wrsETH, weETH, and rETH on the WETH market on Optimism.
### CAPO summary
CAPO is a price oracle adapter designed to support assets that grow gradually relative to a base asset - such as liquid staking tokens that accumulate yield over time. It provides a mechanism to track this expected growth while protecting downstream protocol from sudden or manipulated price spikes. wstETH, ezETH, wrsETH, weETH, and rETH price feeds are updated to their CAPO implementations.
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1062) and [forum discussion for CAPO](https://www.comp.xyz/t/woof-correlated-assets-price-oracle-capo/6245).
### CAPO audit
CAPO has been audited by [OpenZeppelin](https://www.comp.xyz/t/capo-price-feed-audit/6631, as well as the LST / LRT implementation [here](https://www.comp.xyz/t/capo-lst-lrt-audit/7118).
## Proposal actions
The first action updates wstETH, ezETH, wrsETH, weETH, and rETH price feeds to the CAPO implementation. This sends the encoded 'updateAssetPriceFeed' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Optimism.
# Add tETH as collaterals into cUSDCv3, cUSDTv3 and cWETHv3 on Arbitrum
## Proposal summary
WOOF proposes to add tETH into cUSDCv3, cUSDTv3 and cWETHv3 on Arbitrum network. This proposal takes the governance steps recommended and necessary to update a Compound III wstETH market on Arbitrum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based on the [recommendations from Gauntlet](https://www.comp.xyz/t/listing-teth-arbitrum-as-collateral-for-compound-arbitrum/7299/2).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1059) and [forum discussion](https://www.comp.xyz/t/listing-teth-arbitrum-as-collateral-for-compound-arbitrum/7299).
## Proposal Actions
The first proposal action adds tETH to the USDC, USDT and WETH comets on Arbitrum. This sends the encoded 'addAsset' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Arbitrum.
# [Gauntlet] - Risk & Supply Cap Recommendations for Mainnet Stablecoin Comets
**Simple Summary**
Gauntlet recommends the following adjustments to the protocol:
**Motivation**
Full proposals and forum discussions can be found in the following posts.
\- [https://www.comp.xyz/t/gauntlet-risk-parameters-supply-cap-recommendations-for-mainnet-usdc-usds-and-usdt-comets/7372](https://www.comp.xyz/t/gauntlet-risk-parameters-supply-cap-recommendations-for-mainnet-usdc-usds-and-usdt-comets/7372)
**Specification**
The proposal updates the parameters by using the respective methods on the Configurator.
By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.xyz/tos
# Add tBTC as collateral into cUSDCv3 on Arbitrum
## Proposal summary
WOOF! proposes to add tBTC into cUSDCv3 on Arbitrum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDC market on Arbitrum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/gauntlet-tbtc-recommendations-across-comets-12-6-24/6036).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1027) and [forum discussion](https://www.comp.xyz/t/gauntlet-tbtc-recommendations-across-comets-12-6-24/6036).
## Proposal Actions
The first proposal action adds tBTC to the USDC Comet on Arbitrum. This sends the encoded 'addAsset' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Arbitrum.
# Update price feeds in cUSDCv3 on Mainnet with CAPO and Chainlink SVR implementation.
## Proposal summary
This proposal updates existing price feeds for wstETH, WBTC, WETH, LINK, rsETH, weETH and COMP on the USDC market on Mainnet.
### SVR summary
[RFP process](https://www.comp.xyz/t/oev-rfp-process-update-july-2025/6945) and community [vote](https://snapshot.box/#/s:comp-vote.eth/proposal/0x98a3873319cdb5a4c66b6f862752bdcfb40d443a5b9c2f9472188d7ed5f9f2e0) passed and decided to implement Chainlink's SVR solution for Mainnet markets, this proposal updates wstETH, WETH, WBTC, LINK, rsETH, weETH and COMP price feeds to support SVR implementations.
### CAPO summary
CAPO is a price oracle adapter designed to support assets that grow gradually relative to a base asset - such as liquid staking tokens that accumulate yield over time. It provides a mechanism to track this expected growth while protecting downstream protocol from sudden or manipulated price spikes. wstETH, rsETH and weETH price feeds are updated to their CAPO implementations.
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1031), [forum discussion for CAPO](https://www.comp.xyz/t/woof-correlated-assets-price-oracle-capo/6245) and [forum discussion for SVR](https://www.comp.xyz/t/request-for-proposal-rfp-oracle-extractable-value-oev-solution-for-compound-protocol/6786).
## CAPO audit
CAPO has been audited by [OpenZeppelin](https://www.comp.xyz/t/capo-price-feed-audit/6631), as well as the LST / LRT implementation [here](https://www.comp.xyz/t/capo-lst-lrt-audit/7118).
## SVR fee recipient
SVR generates revenue from liquidators and Compound DAO will receive that revenue as part of the protocol fee. The fee recipient for SVR is set to Compound DAO multisig: 0xd9496F2A3fd2a97d8A4531D92742F3C8F53183cB.
## Proposal actions
The first action updates wstETH price feed.
The second action updates WBTC price feed.
The third action updates WETH price feed.
The fourth action updates LINK price feed.
The fifth action updates rsETH price feed.
The sixth action updates weETH price feed.
The seventh action updates COMP price feed.
The eighth action deploys and upgrades Comet to a new version.
# Add tBTC as collateral into cUSDTv3 on Arbitrum
## Proposal summary
WOOF! proposes to add tBTC into cUSDTv3 on Arbitrum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDT market on Arbitrum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/gauntlet-tbtc-recommendations-across-comets-12-6-24/6036).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1028) and [forum discussion](https://www.comp.xyz/t/gauntlet-tbtc-recommendations-across-comets-12-6-24/6036).
## Proposal Actions
The first proposal action adds tBTC to the USDT Comet on Arbitrum. This sends the encoded 'addAsset' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Arbitrum.
# Add tBTC as collateral into cUSDCv3 on Arbitrum
## Proposal summary
WOOF! proposes to add tBTC into cUSDCv3 on Arbitrum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDC market on Arbitrum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/gauntlet-tbtc-recommendations-across-comets-12-6-24/6036).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1027) and [forum discussion](https://www.comp.xyz/t/gauntlet-tbtc-recommendations-across-comets-12-6-24/6036).
## Proposal Actions
The first proposal action adds tBTC to the USDC Comet on Arbitrum. This sends the encoded 'addAsset' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Arbitrum.
# Update sFRAX CAPO snapshot value on Mainnet
## Proposal summary
WOOF! Proposes to update snapshot value for sFRAX CAPO price feed to the correct value, since it was incorrectly set up before. The new and correct value is taken directly from the sFRAX contract on the 23397862 block.
## Proposed actions
The first proposal action updates the snapshot value for CAPO price feed for sFRAX.
# Initialize cWETHv3 on Linea network
## Proposal summary
WOOF! proposes the deployment of Compound III to the Linea network. This proposal takes the governance steps recommended and necessary to initialize a Compound III WETH market on Linea; upon execution, cWETHv3 will be ready for use. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/deploy-compound-iii-on-linea/4460/20).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/982), [deploy market GitHub action run](https://github.com/woof-software/comet/actions/runs/15211470652) and [forum discussion](https://www.comp.xyz/t/deploy-compound-iii-on-linea/4460).
## Proposal Actions
The first proposal action sends ether to the Linea Timelock so it can be wrapped and used to seed the reserves, sets the Comet configuration and deploys a new Comet implementation on Linea. This sends the encoded `setFactory`, `setConfiguration`, `deployAndUpgradeTo` calls across the bridge to the governance receiver on Linea.
The second action updates the ENS TXT record `v3-official-markets` on `v3-additional-grants.compound-community-licenses.eth`, updating the official markets JSON to include the new Linea cWETHv3 market.
# Deprecate wUSDM from Arbitrum and Optimism markets
## Proposal summary
WOOF! proposes to deprecate wUSDM from cUSDCv3 on Arbitrum network, and cUSDCv3 and cUSDTv3 on Optimism, since deprecation of USDM itself and its Chainlink oracle.
In order to achieve this price feed on both networks will be updated to a new one, which will return the smallest acceptable price - 0.00000001 (1e-8), and the supply cup will be set to 0 to prevent further deposits. This proposal takes the governance steps recommended and necessary to update a Compound III USDC market on Arbitrum, and a Compound III USDC and USDT market on Optimism. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1014).
## Proposal Actions
The first proposal action updates wUSDM's configuration to deprecate it from cUSDCv3 on Arbitrum. This sends the encoded 'updateAsset' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Arbitrum.
The second proposal action updates wUSDM's configuration to deprecate it from cUSDCv3 and cUSDTv3 on Optimism. This sends the encoded 'updateAsset' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Optimism.
# Add rsETH as collateral into cWETHv3 on Unichain
## Proposal summary
WOOF! proposes to add rsETH into cWETHv3 on Unichain network. This proposal takes the governance steps recommended and necessary to update a Compound III WETH market on Unichain. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/alphagrowth-add-market-eth-on-unichain/6712/8).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/1003) and [forum discussion](https://www.comp.xyz/t/alphagrowth-add-market-eth-on-unichain/6712).
## Proposal Actions
The first proposal action adds rsETH to the WETH Comet on Unichain. This sends the encoded 'addAsset' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Unichain.
# Add sdeUSD as collateral into cUSDSv3 on Mainnet
## Proposal summary
WOOF! proposes to add sdeUSD into cUSDSv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDS market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based on the [recommendations from Gauntlet](https://www.comp.xyz/t/add-collateral-deusd-sdeusd-staked-on-usdc-usds-usdt-on-mainnet/6112/6).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/994) and [forum discussion](https://www.comp.xyz/t/add-collateral-deusd-sdeusd-staked-on-usdc-usds-usdt-on-mainnet/6112).
## Proposal Actions
The first action adds sdeUSD asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
# Add pufETH as collateral into cWETHv3 on Mainnet
## Proposal summary
WOOF! proposes to add pufETH into cWETHv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III WETH market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based on the [recommendations from Gauntlet](https://www.comp.xyz/t/compound-listing-proposal-for-pufeth-from-puffer-finance/5725/2).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/943) and [forum discussion](https://www.comp.xyz/t/compound-listing-proposal-for-pufeth-from-puffer-finance/5725).
## Proposal Actions
The first action adds pufETH asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
# Add deUSD as collateral into cUSDCv3 on Mainnet
## Proposal summary
WOOF! proposes to add deUSD into cUSDCv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDC market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based on the [recommendations from Gauntlet](https://www.comp.xyz/t/add-collateral-deusd-sdeusd-staked-on-usdc-usds-usdt-on-mainnet/6112/6).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/990) and [forum discussion](https://www.comp.xyz/t/add-collateral-deusd-sdeusd-staked-on-usdc-usds-usdt-on-mainnet/6112).
## Proposal Actions
The first action adds deUSD asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
# [WOOF!] Top up Reward contract on Polygon
**Summary**
This proposal bridges 2,495 COMP tokens that have already been accrued by users in the Polygon USDT and USDC markets. Although rewards incentivization is currently turned off, these tokens remain unclaimed and will be transferred to the Polygon Rewards contract to enable user withdrawals.
# WOOF! <> Compound 2025
## Background
Since 2023, WOOF! has worked with Compound to support the new and ongoing developments.
Full details of the proposal can be found [here](https://www.comp.xyz/t/woof-compound-2025/6724/).
## Proposal
A proposal to renew WOOF!’s 12-month engagement with Compound to support core Compound Protocol developments, addressing the evolving needs of the community, including Compound v4, staked COMP, partial liquidations, and more, while also maintaining and supporting the existing infrastructure.
## Compensation Structure
The service fee structure will be a fixed annual fee of 2,000,000 USD using the COMP spot price.
COMP will be streamed via a custom solution developed by WOOF! and audited by OpenZeppelin.
Specification:
- Allocation: 53,011 COMP
- Streaming Duration: 1 year (continuously, second-by-second distribution)
- Distribution Currency: COMP, valued in USDC via Chainlink’s COMP/USDC price feed at the moment of claim.
- Claiming Cap: 2,000,000 USDC.
- Slippage Tolerance: 0.5% applied at the time of claim.
- Claim Safeguard: To protect the DAO from unfavorable claim conditions, any address may execute a claim on behalf of the stream if the last claim occurred more than 7 days ago.
- Anyone can return unclaimed COMP to the Comptroller after the end of the stream, plus a 10-day grace period.
- The stream can be canceled early via an on-chain governance vote.
- WOOF! will be able to withdraw the vested funds at any time.
More details can be found in the [forum post](https://www.comp.xyz/t/woof-compound-2025/6724/11?u=dmitriywoofsoftware).
By approving this proposal, you agree that any services provided by WOOF! shall be governed by the [Terms of Service](https://docs.google.com/document/d/1hvpHj9Sk73knuRUA5-Tlp-a6Iwqv2EDGMZxnuy06tfY/edit?tab=t.0) that were updated as of November 29, 2024.
# Add SKY as collateral into cUSDSv3 on Mainnet
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes to add SKY into cUSDSv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDS market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based on the [recommendations from Gauntlet](https://www.comp.xyz/t/add-sky-as-collateral-on-usds-usdc-usdt-markets-on-eth-mainnet/6074).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/966) and [forum discussion](https://www.comp.xyz/t/add-sky-as-collateral-on-usds-usdc-usdt-markets-on-eth-mainnet/6074).
## Proposal Actions
The first action adds SKY asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
# Initialize cWRONv3 on Ronin
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes deployment of Compound III to Ronin network. This proposal takes the governance steps recommended and necessary to initialize a Compound III WRON market on Ronin; upon execution, cWRONv3 will be ready for use. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite] (https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/deploy-compound-iii-on-ronin/6128/8).
Further detailed information can be found on the corresponding [deployment pull request](https://github.com/woof-software/comet/pull/146), [deploy market GitHub action run](https://github.com/woof-software/comet/actions/runs/14330759106/job/40166019433) and [forum discussion](https://www.comp.xyz/t/deploy-compound-iii-on-ronin/6128).
## Rewards
Gauntlet provided recommendations for COMP rewards, however, the COMP token is not whitelisted on CCIP. When the COMP token is whitelisted, we will create a proposal to bridge COMP tokens and set up speeds.
## Proposal Actions
The first proposal action bridges ETH using [roninl1NativeBridge](https://etherscan.io/address/0x64192819Ac13Ef72bF6b5AE239AC672B43a9AF08). Bridged ETH will be converted to WETH automatically and swapped for WRON in order to seed the reserves.
The second proposal action approves and swaps received WETH for WRON via native Katana exchange [router](https://app.roninchain.com/address/0xc05afc8c9353c1dd5f872eccfacd60fd5a2a9ac7). We allocate 20% of the slippage due to WETH and RON volatility at the moment of proposal execution (in 8 days from the proposal published on-chain). Swap should not be snipped because MEV infrastructure has not been developed on Ronin yet. The dynamic mechanism to prevent such slippage will be cost inefficient due to development and audit resource allocation.
The third proposal action sets the Comet configuration and deploys a new Comet implementation on Ronin. This sends the encoded `setConfiguration` and `deployAndUpgradeTo` calls across the [l1CCIPRouter](https://etherscan.io/address/0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D) to the bridge receiver on Ronin.
The fourth action updates the ENS TXT record `v3-official-markets` on `v3-additional-grants.compound-community-licenses.eth`, updating the official markets JSON to include the new Ronin cWRONv3 market.
# Add tETH as collateral into cWETHv3 on Mainnet
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes to add tETH into cWETHv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III WETH market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based on the [recommendations from Gauntlet](https://www.comp.xyz/t/listing-teth-on-compound/5925/4).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/955) and [forum discussion](https://www.comp.xyz/t/listing-teth-on-compound/5925).
## Proposal Actions
The first action adds tETH asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
# Initialize cUSDCv3 on Unichain
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes the deployment of Compound III to the Unichain network. This proposal takes the governance steps recommended and necessary to initialize a Compound III USDC market on Unichain; upon execution, cUSDCv3 will be ready for use. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/deploy-compound-iii-on-unichain/6320/9).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/961), [deploy market GitHub action run](https://github.com/woof-software/comet/actions/runs/13401421590/job/37432916447) and [forum discussion](https://www.comp.xyz/t/deploy-compound-iii-on-unichain/6320).
## Price feeds
The market uses all price feeds by Redstone. All other price feeds in the USDC market should be used from Redstone as well.
## Proposal Actions
The first action approves COMP tokens to be bridged.
The second action sends COMP tokens to the Unichain via a native standard bridge.
The third action approves USDC tokens to be bridged.
The fourth action sends USDC tokens to the Unichain via a CCTP bridge.
The fifth proposal action sets the Comet configuration and deploys a new Comet implementation on Unichain. This sends the encoded `setConfiguration`, `deployAndUpgradeTo`and `setRewardConfig` calls across the bridge to the governance receiver on Unichain.
The sixth action updates the ENS TXT record `v3-official-markets` on `v3-additional-grants.compound-community-licenses.eth`, updating the official markets JSON to include the new Unichain cUSDCv3 market.
# Alternate Governance track for Market Updates - Mantle
## Proposal summary
DoDAO has been examining various areas where improvements can be made to governance in Compound through tooling or automation. A significant issue raised repeatedly by many members concerns the time and effort required to apply Market Updates.
Currently, approximately 70-90% of the proposals pertain solely to updating market parameters. Gauntlet uses analytics and algorithms to determine new parameters based on current market conditions. These proposals are highly specific and require unique skills for validation. So far, we have seen minimal participation from other community members or teams in validating these parameters.
Assuming the total cost of reviewing a proposal (including the effort of all delegates) is $2,000 per proposal, we are spending upwards of $300,000 per year on a process that currently acts more as a friction layer without much safeguard, as these market update proposals are rarely reviewed thoroughly.
This not only slows down the process but also diverts focus from reviewing essential proposals related to new partnerships, the addition of new chains, and the introduction of assets, etc.
We propose a parallel process specifically for market updates that can bypass the normal governance lifecycle. This would enable us, as a Compound community, to move faster and concentrate on the most critical decisions.
This proposal has already been discussed here - https://www.comp.xyz/t/market-updates-alternate-governance-track/5379
The forum post includes two solutions, and OpenZeppelin has provided details and feedback on those solutions.
After discussing with OpenZeppelin, DoDAO and OZ together believe that given the amount of changes, updating the Configurator could be the best solution. OpenZeppelin mentioned a couple of important points in the forum post:
1. Grant the market admin role to an Safe address, which can be maintained by Gauntlet or other community members.
2. Market Updates to the Configurator will go through a timelock, providing sufficient time for the community to review or even block the market updates via this alternate route.
# Initialize cUSDSv3 on Base
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes the deployment of Compound III to the Base network. This proposal takes the governance steps recommended and necessary to initialize a Compound III USDS market on Base; upon execution, cUSDSv3 will be ready for use. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/gauntlet-base-usds-comet-recommendations/6278/1).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/959), [deploy market GitHub action run](<https://github.com/woof-software/comet/actions/runs/13189319692/job/36818817568>) and [forum discussion](https://www.comp.xyz/t/gauntlet-base-usds-comet-recommendations/6278).
## cbBTC collateral
Due to the high speed of the market deployment, Gauntlet provided recommendations for cbBTC internally. By the voting start of voting, Gauntlet should be able to update forum the thread with recommendations.
## sUSDS price feed
The sUSDS on Mainnet was a 4626 contract. However, on Base, the sUSDS contract has another contract standard. To speed up the development we decided to use the already deployed price feed of sUSDS/USDS on Base by Spark team. The [price feed](https://basescan.org/address/0x026a5B6114431d8F3eF2fA0E1B2EDdDccA9c540E#readContract) is compatible with our price feed interface and can be re-used. [The audit report of price feed](https://github.com/marsfoundation/xchain-ssr-oracle/blob/master/audits/ChainSecurity_SparkDAO_XChain_SSR_Oracle_audit.pdf).
## Proposal Actions
The first proposal action sets the Comet configuration, deploys a new Comet implementation on Base and sends the encoded 'setFactory', 'setConfiguration' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Base. It also calls 'setRewardConfig' on the Base rewards contract, to set the new Comet’s supply speed to 24 COMP/day and borrow speed to 12 COMP/day.
The second action reduces Compound’s [cDAI](https://etherscan.io/address/0x5d3a536E4D6DbD6114cc1Ead35777bAB948E3643) reserves and transfers it to Timelock, in order to convert it for USDS and then seed the market reserves for the cUSDSv3 Comet.
The third action approves [DaiToUsdsConverterAddress](https://etherscan.io/address/0x3225737a9Bbb6473CB4a45b7244ACa2BeFdB276A) to take Timelock’s DAI and covert it into USDS.
The fourth action converts DAI into USDS so it can be transferred to Base in order to seed the reserves.
The fifth action approves [L1USDSBridge](https://etherscan.io/address/0xA5874756416Fa632257eEA380CAbd2E87cED352A) to take Timelock's USDS.
The sixth action deposits 100K USDS from mainnet to the Base L1USDSBridge contract to bridge to the Comet.
The seventh action updates the ENS TXT record 'v3-official-markets' on 'v3-additional-grants.compound-community-licenses.eth', updating the official markets JSON to include the new Mantle cUSDSv3 market.
# Initialize cUSDSv3 on Base
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes the deployment of Compound III to the Base network. This proposal takes the governance steps recommended and necessary to initialize a Compound III USDS market on Base; upon execution, cUSDSv3 will be ready for use. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/gauntlet-base-usds-comet-recommendations/6278/1).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/959), [deploy market GitHub action run](<https://github.com/woof-software/comet/actions/runs/13187642351>) and [forum discussion](https://www.comp.xyz/t/gauntlet-base-usds-comet-recommendations/6278).
## cbBTC collateral
Due to the high speed of the market deployment, Gauntlet provided recommendations for cbBTC internally. By the voting start of voting, Gauntlet should be able to update forum the thread with recommendations.
## sUSDS price feed
The sUSDS on Mainnet was a 4626 contract. However, on Base, the sUSDS contract has another contract standard. To speed up the development we decided to use the already deployed price feed of sUSDS/USDS on Base by Spark team. The [price feed](https://basescan.org/address/0x026a5B6114431d8F3eF2fA0E1B2EDdDccA9c540E#readContract) is compatible with our price feed interface and can be re-used. [The audit report of price feed](https://github.com/marsfoundation/xchain-ssr-oracle/blob/master/audits/ChainSecurity_SparkDAO_XChain_SSR_Oracle_audit.pdf).
## Proposal Actions
The first proposal action sets the Comet configuration, deploys a new Comet implementation on Base and sends the encoded 'setFactory', 'setConfiguration' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Base. It also calls 'setRewardConfig' on the Base rewards contract, to set the new Comet’s supply speed to 24 COMP/day and borrow speed to 12 COMP/day.
The second action reduces Compound’s [cDAI](https://etherscan.io/address/0x5d3a536E4D6DbD6114cc1Ead35777bAB948E3643) reserves and transfers it to Timelock, in order to convert it for USDS and then seed the market reserves for the cUSDSv3 Comet.
The third action approves [DaiToUsdsConverterAddress](https://etherscan.io/address/0x3225737a9Bbb6473CB4a45b7244ACa2BeFdB276A) to take Timelock’s DAI and covert it into USDS.
The fourth action converts DAI into USDS so it can be transferred to Base in order to seed the reserves.
The fifth action approves [L1USDSBridge](https://etherscan.io/address/0xA5874756416Fa632257eEA380CAbd2E87cED352A) to take Timelock's USDS.
The sixth action deposits 100K USDS from mainnet to the Base L1USDSBridge contract to bridge to the Comet.
The seventh action updates the ENS TXT record 'v3-official-markets' on 'v3-additional-grants.compound-community-licenses.eth', updating the official markets JSON to include the new Mantle cUSDSv3 market.
# Update USDC, USDT and USDS Comets on Mainnet to support more collaterals
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes to update 3 Comet to a new version, which supports up to 24 collaterals. This proposal takes the governance steps recommended and necessary to update a Compound III USDC, USDT and USDS markets on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario).
Detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/904), [deploy market GitHub action run](<>) and [forum discussion](https://www.comp.xyz/t/increase-amount-of-collaterals-in-comet/5465).
## Proposal Actions
The first action sets the factory for cUSDCv3 to the newly deployed factory.
The second action sets the factory for cUSDSv3 to the newly deployed factory.
The third action sets the factory for cUSDTv3 to the newly deployed factory.
The fourth action sets the extension delegate for cUSDCv3 to the newly deployed contract.
The fifth action sets the extension delegate for cUSDSv3 to the newly deployed contract.
The sixth action sets the extension delegate for cUSDTv3 to the newly deployed contract.
The seventh action deploys and upgrades cUSDCv3 to a new version.
The eighth action deploys and upgrades cUSDSv3 to a new version.
The ninth action deploys and upgrades cUSDTv3 to a new version.
sendMessage(address,bytes,uint32)# Alternate Governance track for Market Updates - Optimism
## Proposal summary
DoDAO has been examining various areas where improvements can be made to governance in Compound through tooling or automation. A significant issue raised repeatedly by many members concerns the time and effort required to apply Market Updates.
Currently, approximately 70-90% of the proposals pertain solely to updating market parameters. Gauntlet uses analytics and algorithms to determine new parameters based on current market conditions. These proposals are highly specific and require unique skills for validation. So far, we have seen minimal participation from other community members or teams in validating these parameters.
Assuming the total cost of reviewing a proposal (including the effort of all delegates) is $2,000 per proposal, we are spending upwards of $300,000 per year on a process that currently acts more as a friction layer without much safeguard, as these market update proposals are rarely reviewed thoroughly.
This not only slows down the process but also diverts focus from reviewing essential proposals related to new partnerships, the addition of new chains, and the introduction of assets, etc.
We propose a parallel process specifically for market updates that can bypass the normal governance lifecycle. This would enable us, as a Compound community, to move faster and concentrate on the most critical decisions.
This proposal has already been discussed here - https://www.comp.xyz/t/market-updates-alternate-governance-track/5379
The forum post includes two solutions, and OpenZeppelin has provided details and feedback on those solutions.
After discussing with OpenZeppelin, DoDAO and OZ together believe that given the amount of changes, updating the Configurator could be the best solution. OpenZeppelin mentioned a couple of important points in the forum post:
1. Grant the market admin role to an Safe address, which can be maintained by Gauntlet or other community members.
2. Market Updates to the Configurator will go through a timelock, providing sufficient time for the community to review or even block the market updates via this alternate route.
sendMessage(address,bytes,uint32)DoDAO has been examining various areas where improvements can be made to governance in Compound through tooling or automation. A significant issue raised repeatedly by many members concerns the time and effort required to apply Market Updates.
Currently, approximately 70-90% of the proposals pertain solely to updating market parameters. Gauntlet uses analytics and algorithms to determine new parameters based on current market conditions. These proposals are highly specific and require unique skills for validation. So far, we have seen minimal participation from other community members or teams in validating these parameters.
Assuming the total cost of reviewing a proposal (including the effort of all delegates) is $2,000 per proposal, we are spending upwards of $300,000 per year on a process that currently acts more as a friction layer without much safeguard, as these market update proposals are rarely reviewed thoroughly.
This not only slows down the process but also diverts focus from reviewing essential proposals related to new partnerships, the addition of new chains, and the introduction of assets, etc.
We propose a parallel process specifically for market updates that can bypass the normal governance lifecycle. This would enable us, as a Compound community, to move faster and concentrate on the most critical decisions.
This proposal has already been discussed here - https://www.comp.xyz/t/market-updates-alternate-governance-track/5379
The forum post includes two solutions, and OpenZeppelin has provided details and feedback on those solutions.
After discussing with OpenZeppelin, DoDAO and OZ together believe that given the amount of changes, updating the Configurator could be the best solution. OpenZeppelin mentioned a couple of important points in the forum post:
1. Grant the market admin role to an Safe address, which can be maintained by Gauntlet or other community members.
2. Market Updates to the Configurator will go through a timelock, providing sufficient time for the community to review or even block the market updates via this alternate route.
# Add sUSDS as collateral into cUSDSv3 on Mainnet
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes to add sUSDS into cUSDSv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDS market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based on the [recommendations from Gauntlet](https://www.comp.xyz/t/add-collateral-usds-market-on-eth-mainnet/5781/5).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/947) and [forum discussion](https://www.comp.xyz/t/add-collateral-usds-market-on-eth-mainnet/5781).
## Proposal Actions
The first action adds sUSDS asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
# Add sFRAX as collateral into cUSDTv3 on Ethereum
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes to add sFRAX into cUSDTv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDT market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/add-sfrax-as-collateral-to-usdt-markets-on-ethereum-mainnet/5615/3).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/932) and [forum discussion](https://www.comp.xyz/t/add-sfrax-as-collateral-to-usdt-markets-on-ethereum-mainnet/5615).
## Proposal Actions
The first proposal action adds sFRAX asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
# Initialize cUSDEv3 on Mantle
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes deployment of Compound III to Mantle network. This proposal takes the governance steps recommended and necessary to initialize a Compound III USDe market on Mantle; upon execution, cUSDEv3 will be ready for use. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/deploy-compound-iii-on-mantle-network/5774/6).
Further detailed information can be found on the corresponding [pull request](https://github.com/compound-finance/comet/pull/939), [deploy market GitHub action run](https://github.com/woof-software/comet/actions/runs/11485970843/job/31967241848) and [forum discussion](https://www.comp.xyz/t/deploy-compound-iii-on-mantle-network/5774).
## COMP token on Mantle
For creating a COMP token we used the same approach that we used before in the first Optimism USDC deployment. It uses OptimismMintableERC20 standard. The deployment COMP [transaction](https://mantlescan.xyz/address/0x52b7D8851d6CcBC6342ba0855Be65f7B82A3F17f#internaltx). [COMP token on Mantle](https://mantlescan.xyz/address/0x52b7D8851d6CcBC6342ba0855Be65f7B82A3F17f).
## Pause Guardian
We deployed Safe pauseGuardian using [clone-multisig.ts](https://github.com/woof-software/comet/blob/main/scripts/clone-multisig.ts). [Deployment transaction](https://explorer.mantle.xyz/tx/0x3ff939d38b84add47f5bca1bd731d83cc030f8f1de6147d28197361ec2dc5ea9). [Address of pauseGuardian](https://explorer.mantle.xyz/address/0x2127338F0ff71Ecc779dce407D95C7D32f7C5F45)
## Proposal Actions
The first proposal action sets the Comet configuration, deploys a new Comet implementation on Mantle and swaps received USDT for USDe. This sends the encoded 'setConfiguration', 'deployAndUpgradeTo', 'transfer' and 'swap' calls across the bridge to the governance receiver on Mantle. It also calls 'setRewardConfig' on the Mantle rewards contract, to establish Mantle’s bridged version of COMP as the reward token for the deployment and set the initial supply speed to be 4 COMP/day and borrow speed to be 4 COMP/day.
The second action reduces Compound’s [cUSDT](https://etherscan.io/address/0xf650c3d88d12db855b8bf7d11be6c55a4e07dcc9) reserves and transfers it to Timelock, in order to swap it for USDe and then seed the market reserves for the cUSDEv3 Comet.
The third action approves Mantle’s [L1StandardBridge](https://etherscan.io/address/0x95fC37A27a2f68e3A647CDc081F0A89bb47c3012) to take USDT, in order to then swap it for USDe./n/nThe fourth action deposits USDT from mainnet to the Mantle L1StandardBridge contract to bridge to Timelock which will swap it for USDe to seed the reserves.
The fifth action approves Mantle’s [L1StandardBridge](https://etherscan.io/address/0x95fC37A27a2f68e3A647CDc081F0A89bb47c3012) to take Timelock's COMP, in order to seed the rewards contract through the bridge.
The sixth action deposits 3.6K COMP from mainnet to the Mantle L1StandardBridge contract to bridge to CometRewards.
The seventh action updates the ENS TXT record 'v3-official-markets' on 'v3-additional-grants.compound-community-licenses.eth', updating the official markets JSON to include the new Mantle cUSDEv3 market.
# Initialize cUSDSv3 on Ethereum Mainnet
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes the deployment of Compound III to the Mainnet network. This proposal takes the governance steps recommended and necessary to initialize a Compound III USDS market on Mainnet; upon execution, cUSDSv3 will be ready for use. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based off of the [recommendations from Gauntlet](https://www.comp.xyz/t/add-collateral-usds-market-on-eth-mainnet/5781/5).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/942), [deploy market GitHub action run](https://github.com/woof-software/comet/actions/runs/11392132048) and [forum discussion](https://www.comp.xyz/t/add-collateral-usds-market-on-eth-mainnet/5781).
## wstETH price feed
For LSTs, the goal is to use full exchange rate price feeds. Thus, we treat that stETH:ETH is 1:1.
## sUSDS and sUSDe collaterals
Gauntlet suggests having sUDSS and sUSDe collaterals. This proposal does not include them, because the price feed is under the audit. We suggest to start bootstrapping the liquidity without these collaterals and as the price feed is audited, we will add these collaterals. We discussed it with Gauntlet, and we received the approval to have such an approach.
## Proposal Actions
The first proposal action sets the CometFactory for the new Comet instance in the existing Configurator.
The second action configures the Comet instance in the Configurator.
The third action deploys an instance of the newly configured factory and upgrades the Comet instance to use that implementation.
The fourth action configures the existing rewards contract for the newly deployed Comet instance.
The fifth action reduces Compound’s [cDAI](https://etherscan.io/address/0x5d3a536E4D6DbD6114cc1Ead35777bAB948E3643) reserves and transfers it to Timelock, in order to convert it to USDS to then seed the market reserves for the cUSDSv3 Comet.
The sixth action approves DAI to DAI-to-USDS native converter.
The seventh action converts DAI to USDS with 1:1 ratio and transfers USDS to cUSDSv3 Comet.
The eight action updates the ENS TXT record `v3-official-markets` on `v3-additional-grants.compound-community-licenses.eth`, updating the official markets JSON to include the new Ethereum Mainnet cUSDSv3 market.
# Add tBTC as collateral into cUSDCv3 on Mainnet
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes to add tBTC into cUSDCv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III USDC market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the [Comet scenario suite](https://github.com/compound-finance/comet/tree/main/scenario). The new parameters include setting the risk parameters based on the [recommendations from Gauntlet](https://www.comp.xyz/t/add-collateral-tbtc-to-eth-market-on-mainnet/5399/12).
Further detailed information can be found on the corresponding [proposal pull request](https://github.com/compound-finance/comet/pull/935) and [forum discussion](https://www.comp.xyz/t/add-collateral-tbtc-to-eth-market-on-mainnet/5399).
## Proposal Actions
The first action adds tBTC asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
# Update price feed in cWstETHv3 on Ethereum
## Proposal summary
Compound Growth Program [AlphaGrowth] proposes to update wstETH price feed in cWstETHv3 market on Ethereum to constant price feed as it is intended to be.
## Proposal Actions
The first proposal action updates price feed for wstETH.
The second action deploys and upgrades Comet to a new version.