• © Goverland Inc. 2026
  • v1.0.3
  • Privacy Policy
  • Terms of Use
FraxFraxby0xc3d6f21c79C2567A1858d8b93a4EDBD9dB399d9dnader

FIP 78 - Annual Security Budget Allocation

Voting ended over 3 years agoSucceeded

Authors Frax Core Team

Summary

Allocate 1.2m FRAX to the core treasury for use on quarterly security audits.

Background and Motivation

FRAX has had impeccable security to date in its 17 months being live. We have had 0 critical vulnerabilities where the protocol or any user has lost funds to a vulnerability/bug. This is because the core team takes security extremely seriously and has recurring audits scheduled with some of the top firms in the industry such as Trail of Bits. All of the protocol audits are published in our documentation as they become available: https://docs.frax.finance/other/audits

These audits typically take 2-4 weeks depending on amount of engineers involved and go through protocol code extensively. We would like to allocate 1.2m FRAX to pay for annual security budget and recurring, quarterly audits by top firms. It is likely that the total amount will not be used over 12 months which will roll over to the next 12 month period. In the event that the budget is used in under 12 months due to the size of FRAX's core protocol contracts+code, we will propose a new budget allocation so that governance must approve it.

Seeing as how security and top audits are one of, if not most, important aspects of building a reputable and great defi protocol, we assume this will be an easy pass. For comparison, this is the annual budget for all security related audits+expenses which is less than ~5 days of protocol revenue. This small expenditure is one of the most important expenses of any defi project.

PROPOSAL

For: Approve 1.2m FRAX to core treasury for security audits+pentesting

Against: Do nothing

Off-Chain Vote

For
34.66M FXS100%
Against
8.13K FXS0%
Quorum:483%
Download mobile app to vote

Discussion

FraxFIP 78 - Annual Security Budget Allocation

Timeline

Jun 13, 2022Proposal created
Jun 13, 2022Proposal vote started
Jun 18, 2022Proposal vote ended
Nov 21, 2025Proposal updated