KVORUM
compoundSource: Compound governor alpha · #41

Legacy market migration: WBTC

executedMar 17, 2021, 02:24 PM UTCby540x54a3…e189

01Summary

AISummary by Kvorumclaude-haiku-4-5

Migrate the WBTC market from legacy immutable cToken contracts to the latest upgradable cToken contracts. This enables new features like supply caps and protocol liquidation fees while reducing technical debt. The new cWBTC contract will run in parallel with the old one, with users incentivized to migrate over time.

Type
protocol addition

Key changes

  • Support new cWBTC contract (0xccF4429DB6322D5C611ee964527D42E5d685DD6a) in the protocol(high)
  • Set collateral factor for new cWBTC to 65% to match legacy market(high)
  • Set reserve factor for new cWBTC to 20%(medium)
  • Transfer COMP distribution from legacy WBTC market (0xC11b1268C1A384e55C48c2391d8d480264A3A7F4) to new cWBTC market with updated speed of 10750000000000000(high)
  • New cWBTC uses modern interest rate model with 80% utilization inflection point and 40% maximum interest rate(medium)

Notable concerns

  • Two WBTC markets will run in parallel, requiring user migration over time
  • Legacy market will eventually need to be deprecated when sufficiently small
Contracts0x3d9819210a31b4961b30ef54be2aed79b9c9cd3b0xccF4429DB6322D5C611ee964527D42E5d685DD6a0xC11b1268C1A384e55C48c2391d8d480264A3A7F4
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

273 words

Legacy market migration: WBTC

This proposal begins the migration of legacy cToken contracts to the latest cToken contracts used by the protocol, starting with the WBTC market.

The next-generation cTokens have two years of development & feature advantages over their immutable counterparts. Standardizing the protocol to use the latest cTokens will reduce "tech debt" and allow us to roll out new features to all markets.

WBTC was chosen as the first market to upgrade because of its recent proposal, which highlighted the need to be able to de-risk the market with new features (like supply caps, and protocol liquidation fees). After this migration, the community can proceed with upgrading BAT, ZRX, USDC, and finally ETH.

Upgrade Process

A new WBTC cToken has been deployed, using the latest upgradable cToken contract and implementation. This proposal supports the new market, then switches the COMP Distribution from the prior market, to the new market. The market then inherits a 65% Collateral Factor, to match the legacy market.

The new WBTC cToken uses a modern interest rate model, that governance can update the parameters for. Initially, the parameters are set to an inflection point at 80% utilization, and a maximum interest rate of 40%, which resembles the legacy market.

The two WBTC markets will run in parallel, with users incentivized (but not required) to begin using the new contracts. When the legacy market is small enough, it can be deprectated like SAI and REP.

Contracts

The new cWBTC contract, and its implementation, rely on existing cToken contracts; no code was modified for this proposal, though new contracts were deployed, and peer reviewed.

Discussion: comp.xyz

03Mismatch analysis

AIMismatch analysis by Kvorumclaude-sonnet-5
Minor discrepancy

I compared each decoded action against the specific claims in the proposal description. Action 0 (_supportMarket) matches the description's claim of 'supporting' the new market. Actions 3 and 4 together implement the described 'switch' of COMP distribution from the legacy market (speed set to 0) to the new market (speed set to a positive value) — this is faithfully summarized even though it required two separate calldata actions. Action 1 sets the collateral factor to exactly 65% (650000000000000000 in 18-decimal fixed point), matching the description's claim precisely. The description also mentions an interest rate model with an 80% utilization kink and 40% max rate, but no governance action here configures that — this is expected, since interest rate model parameters are typically set via a separate interest rate model contract deployed independently of this governance proposal, not through Comptroller/cToken calls, so this is not treated as a discrepancy. The one omission is action 2, which sets a 20% reserve factor on the new cWBTC token — a real, functionally significant parameter that the description does not mention at all. This is a legitimate parameter-setting action not covered by the narrative, but 20% is a routine/typical reserve factor for Compound markets and doesn't contradict the market's described purpose, so I classify it as a low-severity omission rather than a higher-severity mismatch. Overall, the actions are highly consistent with the stated intent, with one minor undisclosed parameter.

Discrepancies

  • lowomitted in description

    The calldata includes an explicit _setReserveFactor call (action 2) setting the new cWBTC market's reserve factor to 20%. The description discusses collateral factor and interest rate model parameters in detail but never mentions the reserve factor being configured, even though it is a materially relevant economic parameter for the new market.

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

04Actions

5 total
#0_supportMarket(address)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_supportMarket(address)
Arguments
{
  "0": "0xccF4429DB6322D5C611ee964527D42E5d685DD6a"
}
Calldata
#1_setCollateralFactor(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_setCollateralFactor(address,uint256)
Arguments
{
  "0": "0xccF4429DB6322D5C611ee964527D42E5d685DD6a",
  "1": "650000000000000000"
}
Calldata
#2_setReserveFactor(uint256)chain 0x1
Target
0xccf4…dd6a
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "200000000000000000"
}
Calldata
#3_setCompSpeed(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_setCompSpeed(address,uint256)
Arguments
{
  "0": "0xccF4429DB6322D5C611ee964527D42E5d685DD6a",
  "1": "10750000000000000"
}
Calldata
#4_setCompSpeed(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_setCompSpeed(address,uint256)
Arguments
{
  "0": "0xC11b1268C1A384e55C48c2391d8d480264A3A7F4",
  "1": "0"
}
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 · mixedthread · constructive

Arguments for

  • Legacy immutable cToken contracts cannot support new risk-management and recovery features, so migrating to an upgradeable implementation is overdue and beneficial.— blck, massnomis, dvf
  • The new JumpRateModelV2 interest rate model is a clear improvement over the old linear model for WBTC.— dvf, massnomis
  • The migration also fixes the known recursive/in-kind liquidation issue affecting older markets.— blck, mistertom
  • The deployed contracts (cWBTC, implementation, interest rate model) were independently reviewed and confirmed to match expected parameters, supporting confidence in the technical execution.— arr00
  • Since both old and new markets will coexist for a while, users can migrate at their own pace without being forced immediately.— arr00, Sirokko

Arguments against

  • Upgradeable contracts sacrifice the value of immutability, removing guarantees that protocol rules can't be changed by governance later.— Sirokko
  • Starting the legacy migration process with a large market like WBTC rather than a smaller one like BAT or ZRX is risky and not ideal.— akirillo, arr00
  • L2 scaling solutions might arrive soon and could reduce the gas costs of migration, making immediate migration premature.— dabar90, Sirokko

Unresolved concerns

  • Without a migrator contract, users must pay multiple gas fees (redeem, approve, mint) or repay loans entirely to move positions, which is costly and burdensome.— suspect78, brad5155, joshua
  • Switching COMP distribution to the new market immediately advantages technically sophisticated users who can migrate quickly, disadvantaging others before a migrator exists.— akirillo, suspect78
  • There is no clear plan or timeline for a community- or Compound-funded gas subsidy/migrator to ease the transition.— tatsuzou12, phoenix, arr00
  • Lack of clear communication/documentation about the migration process and its implications for users has caused confusion.— brad5155, tatsuzou12
  • Long delay before any community-built migrator appeared, and its legitimacy/security was not officially vetted by the core team.— 3.1415r, mistertom

Notable participants

  • blckOriginal proposer who described the migration plan, new contract features, and answered technical questions.
  • arr00Verified deployed contracts, discussed COMP distribution timing, and advocated for a subsidized migrator before forcing migration.
  • akirilloRaised concerns about migration order (starting with a large market) and fairness of immediate COMP distribution switch.
  • SirokkoProvided philosophical pushback on upgradeability and practical guidance on migration timing for different user types.
  • suspect78Raised early concerns about gas costs and migration logistics for borrowers and suppliers.
  • brad5155Repeatedly questioned the purpose and cost of migration, highlighting user confusion.
  • tatsuzou12Argued Compound should cover gas fees since the change originates from protocol-side decisions.
  • mistertomAsked about liquidation fixes and later shared information about a community-built migrator.
  • dvfSupported the proposal while suggesting further research into optimal interest rate parameters.
  • massnomisExpressed early support for moving away from legacy contracts while requesting more IRM justification.
Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗