Solana The governance vote-counting vulnerability was fixed before the SGP-0002 vote and did not change the proposal's outcome
BIBIBI
AT A GLANCE
The vote-counting vulnerability in Solana's governance program svmgov was fixed before SGP-0002 the vote, and reports stated that it did not change the proposal outcome.
Article
Security firm:Solana Governance vulnerability caused vote-counting discrepancy; fixed with no impact SGP-0002 According to
BlockBeats,October 20, blockchain security research firm Asymmetric Research disclosed that Solana's on-chain governance program svmgov previously had a vulnerability: when validators did not participate in voting, independent votes submitted in advance by their delegators might not have been included in the final result.
The vulnerability was July 10 reported to Solana Foundation and the mainnet fix was completed on August 3, prior to August 24's governance vote. Based on on-chain data, Asymmetric Research estimated that, had the vulnerability not been fixed, support for the proposal intended to accelerate SOL's inflation decline SGP-0002 could have fallen from the actual 67.00%to 66.65%, below the 66.67%approval threshold. The vulnerability was fixed before the vote and did not actually change the proposal's outcome.
Original link https://m.theblockbeats.info/flash/372664
Key points
01
Asymmetric Research disclosed that Solana's on-chain governance program svmgov previously had a vulnerability.
02
When validators did not participate in voting, independent votes submitted in advance by their delegators might not have been included in the final result.
03
The vulnerability was July 10 reported to Solana Foundation, and the mainnet fix was completed on August 3.
04
The fix preceded August 24 the governance vote.
05
Based on on-chain data, Asymmetric Research estimated that, had the vulnerability not been fixed,SGP-0002 proposal support could have fallen from the actual 67.00%to 66.65%, below the 66.67%approval threshold.
06
SGP-0002 Intended to accelerate SOL's inflation decline.
07
Reports indicated that the vulnerability did not actually change SGP-0002 the outcome.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
Under certain circumstances, this vulnerability could omit delegates' independent votes, causing a skew in governance voting ratios. The estimates in the report show that, if it had not been fixed,SGP-0002 the approval rate might have been slightly below the passage threshold; however, the vulnerability was fixed before that vote, so the report considers the actual outcome unchanged.
Why it matters to readers
The governance vote-counting program determines whether a proposal can pass. Even a small change in the ratio may alter the outcome when it is close to the threshold; the vulnerability described in this report was fixed in advance.
Beginners should distinguish between the “hypothetical outcome the vulnerability could have caused” and the “actual voting outcome”: 66.65%is an estimate for the unpatched scenario, while the actual approval rate was 67.00%。
Risks and unknowns
The materials do not include the original Asymmetric Research report or on-chain data, so the estimates cannot be independently verified.
The materials do not state whether the vulnerability affected any other governance votes.
The materials do not provide the scope of the fix, technical details, or independent audit results.
Related Developments
Loading event timeline…
Related concepts
validators
This term is not in the glossary yet. Browse related concepts in the glossary.
