The getDebugInfo function uses the current quorum requirement instead of the historical value at proposal creation time, leading to incorrect reporting of required votes for past proposals.
In Governance::getDebugInfo, the quorum requirement is fetched using the quorum() function which calculates based on the current total voting power and quorum numerator:
This is problematic because:
The total voting power can change over time as veRAAC tokens are locked/unlocked
The quorum numerator can be modified by the owner via setParameter()
Historical proposals should reference the quorum requirement at their creation time
The getDebugInfo function will return incorrect quorum requirements for historical proposals if:
The total voting power has changed since proposal creation
The quorum numerator was modified by governance
While this does not affect on-chain functionality or proposal execution, it provides misleading data for:
Off-chain analytics and reporting
User interfaces showing proposal status
Historical proposal auditing
Store quorum requirement at proposal creation
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.