# \[ARFC\] Continuous Security Proposal Aave \<\> Certora **URL:** \ **Category:** Governance\ **Created:** [December 1, 2023, 6:44pm UTC](https://governance.aave.com/t/arfc-continuous-security-proposal-aave-certora/15732 "2023-12-01T18:44:29Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![TokenLogic](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/tokenlogic/32/8248_2.png) [@TokenLogic](https://governance.aave.com/u/TokenLogic)\ **Post date:** [December 3, 2023, 9:40pm UTC](https://governance.aave.com/t/arfc-continuous-security-proposal-aave-certora/15732/6 "2023-12-03T21:40:25Z")
Hi @Shelly, It appears that this proposal does not comply with the ARFC proposal format and should be reworked to reflect the correct template. The details regarding the correct format can be found [here](https://governance.aave.com/t/arfc-arfc-and-temp-check-framework/13828). The most recent [ACI](https://governance.aave.com/t/arfc-aci-phase-ii/15138) or [Chaos Labs](https://governance.aave.com/t/arfc-chaos-labs-aave-risk-management-renewal/15234) proposal can be used as a guide. Requesting AAVE as payment is a hard “No” for us. Please do amend the proposal to remove AAVE and replace it with GHO as payment. Ideally, all or at least \>50% of the funding should be nominated in GHO. Outside of this, requesting USDC should state which Aave deployment this will be drawn from, v2 (aUSDC) or v3 (aEthUSDC), otherwise, it is hard to budget without such details. > [@MCERFSR](#): > > We think that getting a portion in AAVE best aligns Certora with the protocol’s success. This is applicable to all Service Providers, with Chaos Labs, Gauntlet, ACI, Karpatkey, and TokenLogic not receiving payment for services rendered in AAVE, it is a moot point. Certora should not receive AAVE. --- _[View the full topic](https://governance.aave.com/t/arfc-continuous-security-proposal-aave-certora/15732)._