How do DAOs know the exact start/end time of on-chain proposals when it goes by block number vs timestamp? Is it just an estimate like (# of blocks * 12s block time) or am I missing something?

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

I think under PoS the block times are constant, no?

Dev at ethOS, a mobile OS that is crypto native- nf.td/markus, Technology brother

I thought there could be slight variations with a 12s target. Found this chart - more consistent than I expected https://ycharts.com/indicators/ethereum_average_block_time 

In the span of a few day voting period this tiny variation doesn't really matter. I wonder how accurate the estimates were pre-merge though haha

@tim would love to hear your thoughts on the best way to estimate the time of a future block

Actually it isn't insignificant! Take a week-long voting period: 

12.00 second blocks * 50400 blocks = 7 days
12.06 second blocks * 50400 blocks = 7.035 days

That's a ~50 minute difference!

They aren’t variation: it’s just that if a validator is offline when they need to propose a block, it is skipped and the next one comes 12s later (so 24s between two blocks). Happens 1% of the time or less in practice, but it does impact things on longer timescales!