[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain
01Summary
Gauntlet proposes adding 1,408 COMP tokens total to reward contracts: 1,012 COMP to Base and 396 COMP to Unichain. The proposal transfers COMP from the treasury, approves it for bridge contracts, and deposits/bridges the funds to the respective networks' reward contracts.
- Type
- treasury allocation
Key changes
- Grant 1,408 COMP from treasury to Gauntlet recipient address(medium)
- Transfer 1,012 COMP to Base reward contract via bridge(high)
- Transfer 396 COMP to Unichain reward contract via bridge(high)
Notable concerns
- Proposal description mentions Base and Unichain but title references Arbitrum; decoded actions confirm Base and Unichain as actual targets
Generated by Kvorum
02Description
[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain
Simple Summary
Gauntlet recommends adding additional COMP to the Base and Unichain reward contracts.
- Base: 1012 COMP
- Unichain: 396 COMP
Motivation
Full proposal and forum discussions can be found in the following post.
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
03Mismatch analysis
I compared the two COMP amounts and destination chains stated in the Simple Summary (Base: 1012 COMP, Unichain: 396 COMP) against the five decoded actions. Action 0 grants 1408 COMP (exactly the sum of 1012+396) from the Comptroller. Actions 1-2 approve and deposit 1012 COMP through what is clearly a Base bridge pattern (depositERC20To with L1/L2 token pair and 200000 gas limit), matching the Base figure in the body. Actions 3-4 approve and bridge 396 COMP through a separate bridge contract (bridgeERC20To), matching the Unichain figure. All amounts and the underlying mechanics align with the body text, so the substantive on-chain execution is consistent with what the proposal describes. However, the proposal's title says 'Arbitrum and Unichain' while the body and calldata both clearly concern 'Base and Unichain' — there is no Arbitrum action anywhere in the calldata. This is an internal inconsistency in the description itself (title vs. body) rather than a mismatch between the body's stated intent and the calldata, but it could mislead a delegate skimming only the title. Because the body correctly identifies the real recipients and the amounts match precisely, I rate this a minor discrepancy rather than material or severe, with high confidence given the numbers are exact and easy to verify.
Discrepancies
- mediummisleading phrasing
The proposal title references 'Arbitrum' as one of the destination chains, but the Simple Summary and all decoded on-chain actions (approve/deposit/bridge calls) target Base and Unichain only — there is no Arbitrum-related action in the calldata. This appears to be a copy-paste/title error rather than an intentional redirection, since the body text and amounts (1012 COMP to Base, 396 COMP to Unichain) match the calldata exactly.
“[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain”
Generated by Kvorum
04Actions
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _grantComp(address,uint256)
- Arguments
{ "amount": "1408000000000000000000", "recipient": "0x6d903f6003cca6255D85CcA4D3B5E5146dC33925" }- Calldata
- Target
- 0xc00e…6888
- Value
- 0 wei
- Function
- approve(address,uint256)
- Arguments
{ "amount": "1012000000000000000000", "address": "0x3154Cf16ccdb4C6d922629664174b904d80F2C35" }- Calldata
- Target
- 0x3154…2c35
- Value
- 0 wei
- Function
- depositERC20To(address,address,address,uint256,uint32,bytes)
- Arguments
{ "_to": "0x123964802e6ABabBE1Bc9547D72Ef1B69B00A6b1", "_amount": "1012000000000000000000", "_l1Token": "0xc00e94Cb662C3520282E6f5717214004A7f26888", "_l2Token": "0x9e1028F5F1D5eDE59748FFceE5532509976840E0", "_extraData": "0x", "_minGasLimit": "200000" }- Calldata
- Target
- 0xc00e…6888
- Value
- 0 wei
- Function
- approve(address,uint256)
- Arguments
{ "amount": "396000000000000000000", "address": "0x81014F44b0a345033bB2b3B21C7a1A308B35fEeA" }- Calldata
- Target
- 0x8101…feea
- Value
- 0 wei
- Function
- bridgeERC20To(address,address,address,uint256,uint32,bytes)
- Arguments
{ "_to": "0x6f7D514bbD4aFf3BcD1140B7344b32f063dEe486", "_amount": "396000000000000000000", "_extraData": "0x", "_localToken": "0xc00e94Cb662C3520282E6f5717214004A7f26888", "_minGasLimit": "200000", "_remoteToken": "0xdf78e4F0A8279942ca68046476919A90f2288656" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- [Gauntlet] Rewards Contract Top-Up for Base and Unichain ↗discourse · high confidence
Arguments for
None surfaced.
Arguments against
None surfaced.
Notable participants
- GauntletProposer presenting data on reward contract depletion and recommending top-ups for Base and Unichain.
Generated by Kvorum
08Similar proposals
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain98%
- compoundcanceled[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain98%
- compoundcanceled[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain97%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain96%
- compounddefeated[Gauntlet] Rewards Contract Top-Up for BASE, Ethereum, and Arbitrum (05/27/24)91%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for BASE, Ethereum, and Arbitrum (06/03/24)91%
- compounddefeated[Gauntlet] Rewards Contract Top-Up for Ethereum and Base (11/26/24)88%
- compoundexecutedRewards Contract Top-Up for Arbitrum, Base, and Unichain88%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Ethereum, Arbitrum, Base and Optimism (4/18/25)87%
- compoundexecuted[Gauntlet] Rewards Contract Top-up for Ethereum87%