OpenZeppelin/openzeppelin-contracts

Prevent proposals with duplicate actions from being submitted in `GovernorTimelockCompound`

Open

#6,431 创建于 2026年3月23日

在 GitHub 查看
 (3 评论) (0 反应) (1 负责人)JavaScript (23,941 star) (11,560 fork)batch import
good first issue

描述

It is a know issue in Compound Governance that proposal queueing will fail if it contains 2 (or more) actions that have the same target, value, and calldata. While this can be circumvented by adding extra (useless) bytes at the end of the calldata to create unicity, it is possible to create such a proposal and not realised if will never be executable after the voting ends.

We should modify the behavior of _propose in GovernorTimelockCompound to reject proposals that have duplicated actions

贡献者指南

技术栈
无
领域
blockchainsecurity
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Solidity basicsOpenZeppelin ContractsCompound governance pattern
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Examine the GovernorTimelockCompound contract (likely in contracts/governance/extensions/GovernorTimelockCompound.sol). The propose function should be modified to check for duplicate actions before adding them. Duplicate actions are defined as having the same target, value, and calldata. Consult the OpenZeppelin governance documentation and existing tests for guidance.