[Gauntlet] Rewards Contract Top-Up for BASE, Ethereum, and Arbitrum (05/27/24)
01Summary
Gauntlet proposes adding COMP tokens to reward contracts across three chains: 28,000 COMP on Ethereum, 3,600 COMP on Base, and 2,250 COMP on Arbitrum. The proposal executes token grants and cross-chain transfers to fund these reward pools.
- Type
- treasury allocation
Key changes
- Grant 28,000 COMP to Ethereum reward contract(high)
- Transfer 3,600 COMP to Base reward contract via bridge(medium)
- Transfer 2,250 COMP to Arbitrum reward contract via bridge(medium)
Notable concerns
- Cross-chain bridge transfers introduce execution risk across multiple chains
- Gauntlet services are subject to their terms of service
Generated by Kvorum
02Description
[Gauntlet] Rewards Contract Top-Up for BASE, Ethereum, and Arbitrum (05/27/24)
Simple Summary
Gauntlet recommends adding COMP to the reward contracts of Base, Ethereum, and Arbitrum:
| Chain | Reward Amount |
|---|---|
| Ethereum | 28,000 |
| Base | 3,600 |
| Arbitrum | 2,250 |
For more details, see the full forum post here.
<sub> 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. </sub>
03Mismatch analysis
The proposal claims three COMP top-ups: 28,000 to Ethereum, 3,600 to Base, and 2,250 to Arbitrum. The decoded actions show exactly these amounts: action 0 grants 28,000 COMP (28000e18) on Ethereum; actions 1-3 grant 3,600 COMP (3600e18) and bridge it to Base via approve + depositERC20To; actions 4-6 grant 2,250 COMP (2250e18) and bridge it to Arbitrum via approve + outboundTransferCustomRefund. All numeric values match after unit conversion (18-decimal COMP). The bridging steps (approve, depositERC20To, outboundTransferCustomRefund) and the small ETH value in action 6 for L2 gas are standard mechanical steps required to move COMP cross-chain and are reasonably omitted from a high-level summary — this is legitimate summarization, not a hidden action. No target, value, or directional mismatches were found. Overall the description accurately reflects the on-chain actions.
Generated by Kvorum
04Actions
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _grantComp(address,uint256)
- Arguments
{ "0": "0x1B0e765F6224C21223AeA2af16c1C46E38885a40", "1": "28000000000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _grantComp(address,uint256)
- Arguments
{ "0": "0x6d903f6003cca6255D85CcA4D3B5E5146dC33925", "1": "3600000000000000000000" }- Calldata
- Target
- 0xc00e…6888
- Value
- 0 wei
- Function
- approve(address,uint256)
- Arguments
{ "0": "0x3154Cf16ccdb4C6d922629664174b904d80F2C35", "1": "3600000000000000000000" }- Calldata
- Target
- 0x3154…2c35
- Value
- 0 wei
- Function
- depositERC20To(address,address,address,uint256,uint32,bytes)
- Arguments
{ "0": "0xc00e94Cb662C3520282E6f5717214004A7f26888", "1": "0x9e1028F5F1D5eDE59748FFceE5532509976840E0", "2": "0x123964802e6ABabBE1Bc9547D72Ef1B69B00A6b1", "3": "3600000000000000000000", "4": "200000", "5": "0x" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _grantComp(address,uint256)
- Arguments
{ "0": "0x6d903f6003cca6255D85CcA4D3B5E5146dC33925", "1": "2250000000000000000000" }- Calldata
- Target
- 0xc00e…6888
- Value
- 0 wei
- Function
- approve(address,uint256)
- Arguments
{ "0": "0xa3A7B6F88361F48403514059F1F16C8E78d60EeC", "1": "2250000000000000000000" }- Calldata
- Target
- 0x72ce…31ef
- Value
- 851426000000000 wei
- Function
- outboundTransferCustomRefund(address,address,address,uint256,uint256,uint256,bytes)
- Arguments
{ "0": "0xc00e94Cb662C3520282E6f5717214004A7f26888", "1": "0x3fB4d38ea7EC20D91917c09591490Eeda38Cf88A", "2": "0x88730d254A2f7e6AC8388c3198aFd694bA9f7fae", "3": "2250000000000000000000", "4": "365232", "5": "500000000", "6": "0x000000000000000000000000000000000000000000000000000260477678e40000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- [Gauntlet] Rewards Contract Top-Up for BASE, Ethereum, and Arbitrum (05/24/24) ↗discourse · high confidence
Arguments for
- Three chains (Ethereum, Base, Arbitrum) face imminent reward contract depletion within 70-75 days and require top-up to maintain distributions for another 3 months.— Gauntlet
Arguments against
None surfaced.
Notable participants
- GauntletProposer recommending COMP rewards contract top-ups for three chains based on runway analysis.
Generated by Kvorum
08Similar proposals
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for BASE, Ethereum, and Arbitrum (06/03/24)100%
- compounddefeated[Gauntlet] Rewards Contract Top-Up for Ethereum and Base (11/26/24)94%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Ethereum, Arbitrum, Base and Optimism (4/18/25)92%
- compoundcanceled[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain91%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain91%
- compoundexecuted[Gauntlet] - Rewards Top Up for Ethereum, Base and Optimism (10/3/25)91%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain90%
- compoundcanceled[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain90%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arbitrum and Unichain89%
- compoundexecuted[Gauntlet] Rewards Contract Top-Up for Arbitrum, Base, and Optimism (8/7/25)88%