KVORUM
compoundSource: Compound governor oz · #551

Rewards Contract Top-Up for Arbitrum, Base, and Unichain

executedMar 14, 2026, 11:03 AM UTCby680x683a…6c02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Gauntlet proposes topping up COMP rewards contracts on Arbitrum (784 COMP), Base (828 COMP), and Unichain (352 COMP) to ensure sufficient incentives remain available for user claims following recent L2 incentive emission cuts that altered claiming behavior.

Type
treasury allocation

Key changes

  • Transfer 784 COMP to Arbitrum CometRewards contract(medium)
  • Transfer 828 COMP to Base CometRewards contract(medium)
  • Transfer 352 COMP to Unichain CometRewards contract(medium)
  • Bridge COMP from mainnet to L2 networks via designated bridge contracts(medium)

Notable concerns

  • Proposal is a reactive measure to address claimed rewards depletion caused by prior incentive cuts, indicating potential ongoing pressure on reward budgets
Contracts0x6d903f6003cca6255D85CcA4D3B5E5146dC339250x88730d254A2f7e6AC8388c3198aFd694bA9f7fae0x123964802e6ABabBE1Bc9547D72Ef1B69B00A6b10x6f7D514bbD4aFf3BcD1140B7344b32f063dEe486
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

192 words

Rewards Contract Top-Up for Arbitrum, Base, and Unichain

Simple Summary

Gauntlet recommends adding additional COMP to the Compound v3 rewards contracts on Arbitrum, Base, and Unichain to ensure sufficient incentives are available to claim following recent changes to the L2 incentive cuts.

ChainRecommended Reward Top-up (COMP)
Arbitrum784
Base828
Unichain352

Motivation

Proposal 547, which has cut incentive emissions on L2 markets, has altered user claiming behaviour. As a result, a significant portion of the COMP previously held in the CometRewards contracts on several L2 networks has been claimed by users.

To ensure that rewards remain claimable and that the incentive claiming process continues to operate smoothly, Gauntlet recommends topping up the rewards contracts with additional COMP.

Further analysis and discussion can be found here: https://www.comp.xyz/t/gauntlet-rewards-contract-top-up-for-arbitrum-base-and-unichain-2026-02-10/7621

Specification

This proposal transfers COMP to the CometRewards contracts on the following networks:

  • Arbitrum: 784 COMP
  • Base: 828 COMP
  • Unichain: 352 COMP

These funds will be used exclusively to replenish the reward contracts from which users can claim COMP incentives.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

9 total
#0_grantComp(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_grantComp(address,uint256)
Arguments
{
  "amount": "784000000000000000000",
  "recipient": "0x6d903f6003cca6255D85CcA4D3B5E5146dC33925"
}
Calldata
#1approve(address,uint256)chain 0x1
Target
0xc00e…6888
Value
0 wei
Function
approve(address,uint256)
Arguments
{
  "amount": "784000000000000000000",
  "address": "0xa3A7B6F88361F48403514059F1F16C8E78d60EeC"
}
Calldata
#2outboundTransferCustomRefund(address,address,address,uint256,uint256,uint256,bytes)chain 0x1
Target
0x72ce…31ef
Value
826820000000000 wei
Function
outboundTransferCustomRefund(address,address,address,uint256,uint256,uint256,bytes)
Arguments
{
  "_to": "0x88730d254A2f7e6AC8388c3198aFd694bA9f7fae",
  "_data": "0x000000000000000000000000000000000000000000000000000260477678e40000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000",
  "_token": "0xc00e94Cb662C3520282E6f5717214004A7f26888",
  "_amount": "784000000000000000000",
  "_maxGas": "316014",
  "_refundTo": "0x3fB4d38ea7EC20D91917c09591490Eeda38Cf88A",
  "_gasPriceBid": "500000000"
}
Calldata
#3_grantComp(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_grantComp(address,uint256)
Arguments
{
  "amount": "828000000000000000000",
  "recipient": "0x6d903f6003cca6255D85CcA4D3B5E5146dC33925"
}
Calldata
#4approve(address,uint256)chain 0x1
Target
0xc00e…6888
Value
0 wei
Function
approve(address,uint256)
Arguments
{
  "amount": "828000000000000000000",
  "address": "0x3154Cf16ccdb4C6d922629664174b904d80F2C35"
}
Calldata
#5depositERC20To(address,address,address,uint256,uint32,bytes)chain 0x1
Target
0x3154…2c35
Value
0 wei
Function
depositERC20To(address,address,address,uint256,uint32,bytes)
Arguments
{
  "_to": "0x123964802e6ABabBE1Bc9547D72Ef1B69B00A6b1",
  "_amount": "828000000000000000000",
  "_l1Token": "0xc00e94Cb662C3520282E6f5717214004A7f26888",
  "_l2Token": "0x9e1028F5F1D5eDE59748FFceE5532509976840E0",
  "_extraData": "0x",
  "_minGasLimit": "200000"
}
Calldata
#6_grantComp(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_grantComp(address,uint256)
Arguments
{
  "amount": "352000000000000000000",
  "recipient": "0x6d903f6003cca6255D85CcA4D3B5E5146dC33925"
}
Calldata
#7approve(address,uint256)chain 0x1
Target
0xc00e…6888
Value
0 wei
Function
approve(address,uint256)
Arguments
{
  "amount": "352000000000000000000",
  "address": "0x81014F44b0a345033bB2b3B21C7a1A308B35fEeA"
}
Calldata
#8bridgeERC20To(address,address,address,uint256,uint32,bytes)chain 0x1
Target
0x8101…feea
Value
0 wei
Function
bridgeERC20To(address,address,address,uint256,uint32,bytes)
Arguments
{
  "_to": "0x6f7D514bbD4aFf3BcD1140B7344b32f063dEe486",
  "_amount": "352000000000000000000",
  "_extraData": "0x",
  "_localToken": "0xc00e94Cb662C3520282E6f5717214004A7f26888",
  "_minGasLimit": "200000",
  "_remoteToken": "0xdf78e4F0A8279942ca68046476919A90f2288656"
}
Calldata

05Tally

Summed from votes

Voters22
VP participating609.9K
Outcome (current)For
Current support100%

06Voters

22 total
Filter:
VoterChoice% of totalRationale
3F0x3fb1…4c8aFor104.8K17.18%—8mo ago
660x66cd…65f9For80K13.12%—8mo ago
050x0579…ca09For60K9.84%—8mo ago
170x1729…b879For60K9.84%—8mo ago
B70xb792…89d7For60K9.84%—8mo ago
B90xb933…8dd1For60K9.84%—8mo ago
070x0703…961bFor51.7K8.48%—8mo ago
2B0x2b38…bf33For50.3K8.24%—8mo ago
4F0x4f89…fd3cFor50K8.20%—8mo ago
130x13bd…8548For30K4.92%—8mo ago
4D0x4d74…5896For2.7K0.44%—8mo ago
1F0x1f3d…0591For440.70.07%—8mo ago
C50xc554…7759For11.20.00%—8mo ago
8B0x8bb9…ccc2For1.10.00%—8mo ago
010x0151…c3b9For1.10.00%—8mo ago
9F0x9f77…2768For0.90.00%—8mo ago
2F0x2f2f…f78aFor0.50.00%—8mo ago
070x0751…5295For0.10.00%—8mo ago
3E0x3e6c…e384Abstain0.10.00%—8mo ago
250x252b…c23aFor0.10.00%—8mo ago
940x940a…15e7For0.10.00%—8mo ago
D80xd8de…ae41For0.10.00%—8mo ago
Showing 22

07Forum

AIForum synthesis by Kvorumclaude-haiku-4-5
sentiment · favorablethread · constructive

Arguments for

  • Reward contracts on Arbitrum, Base, and Unichain have insufficient runway (12-14 days) and require top-ups to continue distributing promised incentives.— Gauntlet

Arguments against

None surfaced.

Unresolved concerns

  • Whether the top-up was still needed after Gauntlet's subsequent incentives optimization recommendations and the passage of Proposal 547.— allthecolors
  • Timeline and process for replenishing COMP on Unichain when users encountered insufficient funds in the claim contract.— aa2a

Notable participants

  • GauntletProposer and primary technical authority providing runway analysis and recommendations for reward contract top-ups.
  • allthecolorsCommunity member who questioned whether the proposal remained necessary given subsequent recommendations.
  • LP17Community member inquiring about future COMP reward distribution plans on Base and OP.
  • aa2aUser reporting a real claim contract insufficiency issue on Unichain requiring a top-up.
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗