KVORUM
compoundSource: Compound governor oz · #469

Add rsETH as collateral into cUSDCv3 on Mainnet

executedAug 18, 2025, 08:42 PM UTCby890x89f2…e8db

01Summary

AISummary by Kvorumclaude-haiku-4-5

Proposal to add rsETH as collateral to Compound III's cUSDCv3 market on Ethereum mainnet, including deployment of an updated Comet contract version with risk parameters recommended by Gauntlet.

Type
protocol addition

Key changes

  • Add rsETH (0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7) as collateral asset to cUSDCv3 with configured risk parameters including loan-to-value ratios (85%, 90%, 95%) and liquidation threshold (150%)(high)
  • Deploy and upgrade Comet to new version with updated market configurations(high)

Notable concerns

  • Proposal references external Gauntlet recommendations and simulations that should be independently verified
  • Market readiness confirmed through Comet scenario suite simulations
Contracts0xc3d688B66703497DAA19211EEdff47f25384cdc30x316f9708bb98af7da9c68c1c3b5e79039cd336e30x1ec63b5883c3481134fd50d5daebc83ecd2e8779
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

109 words

Add rsETH as collateral into cUSDCv3 on Mainnet

Proposal summary

WOOF! proposes to add rsETH 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. The new parameters include setting the risk parameters based on the recommendations from Gauntlet.

Further detailed information can be found on the corresponding proposal pull request and forum discussion.

Proposal Actions

The first action adds rsETH asset as collateral with corresponding configurations.

The second action deploys and upgrades Comet to a new version.

03Mismatch analysis

AIMismatch analysis by Kvorumclaude-sonnet-5
Consistent

The description states two actions: (1) adding rsETH as collateral with configuration parameters, and (2) deploying and upgrading Comet to a new version. The decoded calldata contains exactly two actions matching this: an addAsset call configuring rsETH as collateral on the same cUSDCv3 Comet proxy, followed by a deployAndUpgradeTo call on the same Comet proxy via the Configurator. Both actions target the correct, consistent contract addresses (Configurator and Comet proxy), and the number/order of actions matches the description's 'Proposal Actions' section. The description does not make specific numeric claims (e.g., exact collateral factors or supply cap) that could be checked against calldata values, only referencing Gauntlet's recommendations generically, so there is no verifiable value mismatch. No omitted, extra, or misdirected actions are present. This is a standard, well-formed Compound market collateral-onboarding proposal with no red flags.

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

2 total
#0addAsset(address,(address,address,uint8,uint64,uint64,uint64,uint128))chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
addAsset(address,(address,address,uint8,uint64,uint64,uint64,uint128))
Arguments
{
  "cometProxy": "0xc3d688B66703497DAA19211EEdff47f25384cdc3",
  "assetConfig": [
    "0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7",
    "0x92014e7f331dFaB2848A5872AA8b2E7b6f3cE8B4",
    "18",
    "850000000000000000",
    "900000000000000000",
    "950000000000000000",
    "1500000000000000000000"
  ]
}
Calldata
#1deployAndUpgradeTo(address,address)chain 0x1
Target
0x1ec6…8779
Value
0 wei
Function
deployAndUpgradeTo(address,address)
Arguments
{
  "cometProxy": "0xc3d688B66703497DAA19211EEdff47f25384cdc3",
  "configuratorProxy": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3"
}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

AIForum synthesis by Kvorumclaude-sonnet-5
sentiment · favorablethread · constructive

Arguments for

  • Kelp DAO requested listing rsETH/wrsETH on Compound markets including the Unichain WETH market, citing existing listings across other Compound deployments and growing liquidity/demand.— whyshock
  • Gauntlet provided formal risk parameter recommendations (CF 90%, LF 93%, LP 4%, supply cap 1,000 rsETH) for onboarding rsETH to the Unichain WETH comet, aligning them with rsETH's mainnet parameters.— Gauntlet
  • WOOF! executed the technical implementation (PRs, tests, simulations, deployment artifacts) confirming the market's readiness for adding rsETH as collateral.— dmitriywoofsoftware
  • Gauntlet noted that liquidity for rsETH on Unichain (via Uniswap V4 pool, ~$14.81M TVL) was sufficient to support the recommended conservative supply cap.— Gauntlet

Arguments against

None surfaced.

Unresolved concerns

  • Gauntlet flagged that the rsETH/ETH pool on Unichain had been supported by UNI incentives that ended, and observed TVL volatility afterward, raising questions about sustained liquidity.— Gauntlet
  • A community member questioned the legitimacy of the on-chain proposal because it was created by an address not associated with a known entity or past governance history.— she256

Notable participants

  • AlphaGrowthOriginal proposer who initiated the broader proposal to launch the Unichain WETH market and listed candidate collateral assets including rsETH.
  • GauntletRisk manager who provided detailed parameter recommendations for the WETH comet, WBTC/UNI/ezETH/wstETH/weETH assets, and later specifically for rsETH on both Unichain and Mainnet markets.
  • dmitriywoofsoftwareWOOF! team member who executed and documented the technical deployment, PRs, and on-chain proposal details for the WETH market and rsETH additions.
  • whyshockKelp DAO representative who requested the listing of rsETH/wrsETH on Compound markets, including Unichain.
  • she256Community member who raised a due-diligence concern about the proposer wallet's identity.
  • PashaClarified that the proposing wallet was a legitimately whitelisted WOOF! wallet, resolving the identity concern.
Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗