feat(web): DAO governance schedule - voting + queue duration, per-proposal countdown#69
Merged
Merged
Conversation
…posal countdown Surface the proposal lifecycle timing, read live from each governor so the two chains show their real (and currently different) settings. - dao-overview now returns a schedule: votingDelay + votingPeriod (blocks -> seconds via measured block time: Ethereum ~12s, LightChain ~6s) + the timelock minDelay + proposalThreshold. The treasury bar renders it as "1 day delay -> 7 days voting -> 2 days timelock queue" plus the proposing threshold. Computed per chain, not hard-coded. - Fact-checked against the contracts: the Ethereum DAO is now 7d voting + 2d queue (the change from 14d that governance voted in); the LightChain native governor is still 14d (that param change has not been applied there yet). - Per-proposal countdown: the API returns the current head block and the expanded card shows "Voting ends in ~X" for active proposals (or "opens in" for pending). - Quorum stat gains a tooltip explaining the % in absolute terms (e.g. the For+Abstain wei needed for the vote to be valid). humanizeDuration extracted to dao-math and unit-tested (+5 tests).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the proposal lifecycle timing you asked for (voting days + queue), read live per governor.
Fact-check result
Both governors count in blocks (CLOCK_MODE=blocknumber); I measured the real block times (Ethereum ~12s, LightChain ~6s) to convert:
So the 7 days + 2 days queue change is live on the Ethereum DAO (where the proposals + that vote live), exactly as recalled (down from 14). The LightChain native governor is still 14 days - that parameter change hasn't been applied there yet. The UI computes this per-tab from the chain, so it shows 7d on Ethereum and honestly 14d on LightChain.
What's added
schedule(votingDelay + votingPeriod in seconds, timelock minDelay, proposalThreshold). The treasury bar renders "1 day delay → 7 days voting → 2 days timelock queue" + the proposing threshold.Verification
tscclean,next buildclean, ESLint clean, 478/478 tests pass (+5 forhumanizeDuration). Verified live: overview returns 7d (ETH) / 14d (LC), proposals returnsheadBlock.