• © Goverland Inc. 2026
  • v1.0.1
  • Privacy Policy
  • Terms of Use
Aave DAOAave DAOby0xB48fC9a691D1f97296c306351a34C7d3777407060xB48f…0706

[Temp Check] GHO Bounty for Integration Issue Detection

Voting ended about 2 years agoSucceeded

title: "[Temp Check] GHO Bounty for Integration Issue Detection" author: "AaveCo" discussions: "https://governance.aave.com/t/temp-check-gho-bounty-for-integration-issue-detection/15296"

Simple Summary

This TEMP CHECK proposes a bounty to a community member of 50,000 GHO for coming forward and reporting an incident.

Motivation

Bounty of 50,000 GHO for notifying the Aave team of an issue which as a precaution triggered the pausing of the GHO market.

This proposal is to acknowledge and appreciate the collaboration and diligence demonstrated by the individual who initially brought attention to an issue on the frontend. Their efforts ultimately led to the discovery of the underlying problem. Their proactive involvement, although not a direct report, was instrumental in bringing this matter to our attention. Subsequently, with their assistance and the ongoing cooperation of BGD Labs and Certora, we were able to pinpoint and, effectively, resolve the root issue.

In recognition of their valuable contribution to the protocol’s security and stability, we recommend that the DAO consider awarding a bounty of 50,000 GHO to this individual. It is worth noting that while their input may not align precisely with the conventional definition of a vulnerability report, their insights were of paramount importance in instigating an internal investigation.

Specification

This TEMP CHECK executes a single transfer of 50,000 GHO to receiver address

Next Steps

If Snapshot is successful then move to AIP

References

  • Discussion: Governance Thread

Copyright

Copyright and related rights waived via CC0.

Off-Chain Vote

YAE
477.22K AAVE100%
ABSTAIN
8.19 AAVE0%
NAY
0.79 AAVE0%
Quorum:149%
Download mobile app to vote

Discussion

Aave DAO[Temp Check] GHO Bounty for Integration Issue Detection

Timeline

Nov 07, 2023Proposal created
Nov 08, 2023Proposal vote started
Nov 11, 2023Proposal vote ended
Nov 11, 2023Proposal updated