In Governor.sol, we have struct ProposalCore { Timers.BlockNumber voteStart; Timers.BlockNumber voteEnd; bool executed; bool canceled; } which measures the voting period in terms of block number rather than timestamp. I understand that block.timestamp can be chosen to some extent b…

It is better to use block.timestamp. We went with block numbers to remain compatible with the existing Governor ecosystem that had developed around Compound's GovernorBravo. We may consider switching to or adding an option for timestamps later.

Why does `Governol.sol` measure voting period in terms of block number instead of timestamp?

Support Contracts

ernestognw July 17, 2023, 6:38pm 4

I'm closing because the topic is already solved and the follow up discussion about EIP-6372 is in this other thread.

Topic		Replies	Views
Using block.number vs block.timestamp in Governor.sol Contracts	2	879	July 14, 2022
TimeStamp based governance Contracts erc20	5	909	July 18, 2023
Governor Contract on Avalanche Contracts	2	888	December 22, 2021
Block number and timestamp with governor and ivotes Contracts	1	26	April 1, 2025
Changing Block Producing Speed for votingDelay and votingPeriod Smart Contracts erc20	2	530	February 10, 2022

Why does `Governol.sol` measure voting period in terms of block number instead of timestamp?

Related topics