OpenZeppelin/openzeppelin-contracts

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

Open

#6,431 opened on Mar 23, 2026

View on GitHub
 (4 comments) (0 reactions) (1 assignee)JavaScript (11,560 forks)batch import
good first issue

Repository metrics

Stars
 (23,941 stars)
PR merge metrics
 (Avg merge 42d 15h) (16 merged PRs in 30d)

Description

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

Contributor guide

Research direction
Inspect the ` propose` function in GovernorTimelockCompound.sol and add a check to detect duplicate actions before proposal submission.
Tech stack
javascript
Domain
blockchain
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitSolidity
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75