[Gauntlet] 2023-08-07: Arbitrum USDC - Reward Updates
01Summary
Gauntlet proposes to reduce daily COMP supply rewards on Arbitrum USDC Comet from 34.73 to 10, saving approximately $542k annually in a comet with low utilization ahead of migration to a new native USDC comet.
- Type
- parameter change
- Funding
- $-542000
Key changes
- Decrease daily COMP supply rewards from 34.73 to 10 via setBaseTrackingSupplySpeed on Arbitrum Configurator(high)
Notable concerns
- Proposal targets deprecated comet being replaced with native USDC comet on Arbitrum
Generated by Kvorum
02Description
[Gauntlet] 2023-08-07: Arbitrum USDC - Reward Updates
Simple Summary
A proposal from Gauntlet to adjust one COMP reward distribution in the Arbitrum USDC comet.
Gauntlet recommends the following change to Arbitrum USDC rewards:
- Decrease daily COMP supply rewards from 34.73 to 10.
For more details, see the full forum post here.
Motivation
Decreasing the daily COMP supply rewards from 34.73 to 10 will result in ~$542k annual savings, in a comet that has low utilization. Compound Labs is working on launching a native USDC comet on Arbitrum, to migrate liquidity from this comet to be deprecated to the new comet.
Full proposal and forum discussion
Specification
The proposal updates the COMP supply rewards on the Arbitrum USDC Comet using the setBaseTrackingSupplySpeed method of the Arbitrum Configurator contract.
By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.network/tos.
03Mismatch analysis
The proposal claims a single change: lower the daily COMP supply reward speed on the Arbitrum USDC Comet from 34.73 to 10 COMP/day via setBaseTrackingSupplySpeed on the Arbitrum Configurator. The single decoded action is a createRetryableTicket call (standard Compound cross-chain governance pattern) whose embedded L2 payload calls setBaseTrackingSupplySpeed on the Configurator (0xb21b06d7...) targeting the Comet at 0xa5edbdd9..., with the argument 115740740740. Converting this using Compound's trackingIndexScale (1e15) gives 115740740740 * 86400 / 1e15 = 10 COMP/day, exactly matching the description's target value. The payload also includes the routine deployAndUpgradeTo(configurator, comet) call that Compound III always bundles to push a configurator change live — this is boilerplate, not a separate substantive action, so its omission from the prose is not a real discrepancy. Addresses used (Configurator, Comet, Arbitrum Inbox/bridge helper) are consistent with known Compound Arbitrum deployment addresses and the specification's stated method. No value, target, or direction mismatches were found.
Discrepancies
- lowomitted in description
The description does not mention the accompanying deployAndUpgradeTo call or the retryable-ticket bridging mechanics, but these are standard, mechanical steps required to apply any Comet configurator change and do not alter the substance of the proposal.
Generated by Kvorum
04Actions
- Target
- 0x4dbd…ab3f
- Value
- 2970535500000000 wei
- Function
- createRetryableTicket(address,uint256,uint256,address,address,uint256,uint256,bytes)
- Arguments
{ "0": "0x42480C37B249e33aABaf4c22B20235656bd38068", "1": "0", "2": "1355210000000000", "3": "0x3fB4d38ea7EC20D91917c09591490Eeda38Cf88A", "4": "0x3fB4d38ea7EC20D91917c09591490Eeda38Cf88A", "5": "3230651", "6": "500000000", "7": "0x000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002600000000000000000000000000000000000000000000000000000000000000002000000000000000000000000b21b06d71c75973babde35b49ffdac3f82ad3775000000000000000000000000d10b40ff1d92e2267d099da3509253d9da4d715e0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000002a73657442617365547261636b696e67537570706c79537065656428616464726573732c75696e743634290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000040000000000000000000000000a5edbdd9646f8dff606d7448e414884c7d905dca0000000000000000000000000000000000000000000000000000001af2af8c840000000000000000000000000000000000000000000000000000000000000040000000000000000000000000b21b06d71c75973babde35b49ffdac3f82ad3775000000000000000000000000a5edbdd9646f8dff606d7448e414884c7d905dca" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- [Gauntlet] Arbitrum USDC - Reward Recommendations ↗discourse · high confidence
Arguments for
- Low USDC utilization (20.2%-36.3%) and negative reserve growth (-31.8% average) justify reducing inefficient incentives.— Gauntlet
- Decreasing rewards from 34.73 to 10 COMP daily saves approximately $542k annually while the deprecated comet will be replaced by a native USDC comet on Arbitrum.— Gauntlet
- Current earn distribution is overly incentivized at 5.27%, losing $760k in annual COMP rewards relative to protocol benefit.— Gauntlet
Arguments against
None surfaced.
Unresolved concerns
- Whether increasing LTV for WETH and WBTC on the current comet would improve competitiveness against AAVE before deprecation.— Michigan_Blockchain
Notable participants
- GauntletProposal author providing market analysis, recommendations, and responses to community questions.
- Michigan_BlockchainCommunity participant raising questions about LTV optimization relative to AAVE's offering.
Generated by Kvorum
08Similar proposals
- compoundexecuted[Gauntlet] Arbitrum v3 USDC Reward Recommendations (2023-09-18)93%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arb and IR Recs for USDT Mainnet and USDC Arbitrum Comets82%
- compoundexecuted[Gauntlet] - Arbitrum USDC - Risk, Incentive, and Interest Rate Curve Recommendations82%
- compoundexecuted[Gauntlet] Arbitrum v3 - Risk Recommendations (2024-04-15)81%
- compoundexecuted[Gauntlet] 2023-11-27: Arbitrum Native USDC - Risk Recommendations80%
- compoundexecuted[Gauntlet] 2024-02-19: BASE v3 & Arbitrum v3 - Risk Recommendations80%
- compoundexecutedRisk Parameter Updates for Polygon Compound v3 USDC (5/9/23)80%
- compoundexecuted[Gauntlet] - Arbitrum USDT Risk and IO Recommendations (2024-08-20)80%
- compoundexecuted[Gauntlet] Arbitrum v3 USDC Native - Risk Recommendations (2023-10-16)79%
- compoundexecuted[Gauntlet] Recommendations for Low Utilization Assets - Arbitrum (2026-01-22)79%