Refresh Polygon COMP
01Summary
Proposal to bridge 12,500 COMP tokens to Polygon to replenish and sustain rewards for the cUSDCv3 market for approximately one additional year following its successful launch.
- Type
- treasury allocation
Key changes
- Approve transfer of 12,500 COMP tokens to the Polygon bridge contract(high)
- Transfer 12,500 COMP across the bridge to the Polygon rewards contract to sustain current reward speeds(high)
Generated by Kvorum
02Description
Refresh Polygon COMP
Explanation
Since the launch of cUSDCv3 on Polygon mainnet a month ago, the market has grown steadily and proven to be in good order. The initial seeding of rewards only provisioned enough for a few months, as a conservative starting point. Now is a good time to renew the COMP rewards going to the market.
This proposal bridges an additional 12,500 COMP to sustain the current rewards speeds of the market for an additional year (approximately).
Proposal
The proposal itself is to be made from this pull request.
The first action approves the transfer of COMP by the Polygon bridge contract.
The second action triggers the transfer across the bridge to the rewards contract.
03Mismatch analysis
The description states two straightforward steps: (1) approve the Polygon bridge to move COMP, and (2) execute the bridge transfer of 12,500 COMP to the rewards contract. The decoded calldata matches this exactly: action 0 is an ERC20 approve() call on the COMP token contract granting allowance of 12,500 COMP (12500000000000000000000 in base units, consistent with 18 decimals) to the bridge's predicate/manager address, and action 1 is a depositFor() call on the known Polygon RootChainManagerProxy address, passing the COMP token as rootToken and an encoded amount whose magnitude (verified via hex-to-decimal conversion) is consistent with 12,500 COMP. No unrelated recipients, no unexpected amounts, and no additional undisclosed actions are present. The target addresses correspond to the COMP token and the Polygon PoS bridge, matching the proposal's stated intent to bridge COMP to Polygon for reward continuation. No value, target, or scope mismatches were found. . . .
Generated by Kvorum
04Actions
- Target
- 0xc00e…6888
- Value
- 0 wei
- Function
- approve(address,uint256)
- Arguments
{ "0": "0x40ec5B33f54e0E8A33A975908C5BA1c14e5BbbDf", "1": "12500000000000000000000" }- Calldata
- Target
- 0xa0c6…7c77
- Value
- 0 wei
- Function
- depositFor(address,address,bytes)
- Arguments
{ "0": "0x45939657d1CA34A8FA39A924B71D28Fe8431e581", "1": "0xc00e94Cb662C3520282E6f5717214004A7f26888", "2": "0x0000000000000000000000000000000000000000000002a5a058fc295ed00000" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- compoundexecutedRefresh Polygon COMP97%
- compoundexecutedCOMP Distribution Patch69%
- compoundexecutedDistribute COMP to Users68%
- compoundexecutedSplit COMP rewards distribution and bug fixes67%
- compoundexecutedInitialize Compound III COMP Distribution67%
- compoundexecutedAdd COMP Support67%
- compoundexecutedCOMP Speed Recalibration65%
- compoundexecutedFix COMP Accrual Bug65%
- compoundexecutedCOMP Rewards Adjustments - Kickstart Rewards: Step One64%
- compounddefeatedCOMP Rewards Adjustments - Kickstart Rewards: Step Two64%