[Gauntlet] Rewards Contract Top-Up for Ethereum and Base (11/26/24)
01Summary
Gauntlet recommends adding 11,340 COMP to Ethereum's reward contract and 4,950 COMP to Base's reward contract to extend their runway. Ethereum currently has 75 days of runway remaining and Base has only 19 days remaining at current distribution rates.
- Type
- treasury allocation
Key changes
- Grant 11,340 COMP tokens to Ethereum reward contract (0x1B0e765F6224C21223AeA2af16c1C46E38885a40)(high)
- Grant 4,950 COMP tokens to Base reward contract (0x6d903f6003cca6255D85CcA4D3B5E5146dC33925)(high)
- Bridge 4,950 COMP tokens from Ethereum to Base via cross-chain deposit(medium)
Notable concerns
- Base rewards contract has critically low runway of only 19 days
- Ethereum rewards contract has 75 days of runway remaining, below the timeline of other chains which range from 103-153 days
Generated by Kvorum
02Description
[Gauntlet] Rewards Contract Top-Up for Ethereum and Base (11/26/24)
Simple Summary
Gauntlet recommends adding additional COMP to the reward contracts of Ethereum, Optimism and Arbitrum:
| Chain | Reward Amount |
|---|---|
| Base | 4,950 |
| Ethereum | 11,340 |
Analysis
Below is the projected runway in each chain’s rewards contract.
| Chain | Rewards contract COMP token holdings | Current Daily COMP token reward distributions | Remaining days of runway (not including existing claimable rewards) |
|---|---|---|---|
| Polygon | 3,518 | 23.0 | 153 |
| Optimism | 2,802 | 27.0 | 103 |
| Ethereum | 28,625 | 378.0 | 75 |
| Base | 1,047 | 55.0 | 19 |
| Arbitrum | 15,762 | 130.0 | 121 |
For more details please see the full forum posts below:
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's title and summary table correctly identify Ethereum (11,340 COMP) and Base (4,950 COMP) as the chains receiving top-ups, and the decoded calldata matches these exact amounts: a direct _grantComp of 11,340 COMP for Ethereum (action 0) and a _grantComp of 4,950 COMP (action 1) followed by an approve + depositERC20To bridging sequence (actions 2-3) that routes the same 4,950 COMP amount to Base via the standard bridge — a normal mechanical step for L2 funding that the description reasonably omits as routine implementation detail. However, the first sentence of the Simple Summary incorrectly lists 'Ethereum, Optimism and Arbitrum' as recipients, which contradicts both the table (Base and Ethereum only) and the actual on-chain actions (no Optimism or Arbitrum grants exist). This looks like a copy-paste error from a prior proposal referenced in the forum link, and while it doesn't change what funds actually move, it could confuse a delegate skimming only the summary text. No numeric or target mismatches were found between the table/title and the calldata amounts. Given this is an isolated textual inconsistency rather than a change in fund destination or magnitude, I classify this as a minor discrepancy rather than material or severe.
Discrepancies
- lowextra in description
The opening summary sentence states COMP is being added to reward contracts on 'Ethereum, Optimism and Arbitrum', but neither the accompanying table nor the decoded calldata include any action for Optimism or Arbitrum — only Ethereum and Base receive COMP. This appears to be a copy-paste leftover from a prior, similarly-named proposal and could mislead a reader skimming only that sentence.
“Gauntlet recommends adding additional COMP to the reward contracts of Ethereum, Optimism and Arbitrum”
Generated by Kvorum
04Actions
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _grantComp(address,uint256)
- Arguments
{ "0": "0x1B0e765F6224C21223AeA2af16c1C46E38885a40", "1": "11340000000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _grantComp(address,uint256)
- Arguments
{ "0": "0x6d903f6003cca6255D85CcA4D3B5E5146dC33925", "1": "4950000000000000000000" }- Calldata
- Target
- 0xc00e…6888
- Value
- 0 wei
- Function
- approve(address,uint256)
- Arguments
{ "0": "0x3154Cf16ccdb4C6d922629664174b904d80F2C35", "1": "4950000000000000000000" }- Calldata
- Target
- 0x3154…2c35
- Value
- 0 wei
- Function
- depositERC20To(address,address,address,uint256,uint32,bytes)
- Arguments
{ "0": "0xc00e94Cb662C3520282E6f5717214004A7f26888", "1": "0x9e1028F5F1D5eDE59748FFceE5532509976840E0", "2": "0x123964802e6ABabBE1Bc9547D72Ef1B69B00A6b1", "3": "4950000000000000000000", "4": "200000", "5": "0x" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Ethereum, Arbitrum, Base and Optimism (4/18/25)98%
- compoundexecuted[Gauntlet] - Rewards Top Up for Ethereum, Base and Optimism (10/3/25)98%
- compounddefeated[Gauntlet] Rewards Contract Top-Up for BASE, Ethereum, and Arbitrum (05/27/24)94%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for BASE, Ethereum, and Arbitrum (06/03/24)94%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arbitrum, Base, and Optimism (8/7/25)94%
- compoundexecuted[Gauntlet] Rewards Contract Top-up for Ethereum88%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain88%
- compoundcanceled[Gauntlet] - Incentive Recommendations and Rewards Top Up (2024-10-887%
- compoundexecuted[Gauntlet] - Incentive Recommendations and Rewards Top Up (2024-10-24)87%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain87%