The Ledger
Aave community proposes study of temporary borrowing controls
An independent community initiative proposes a feasibility study of temporary controls to limit new borrowing during external security incidents. It does not seek immediate protocol changes and asks the community to assess whether a study should be funded or conducted.

A feasibility study, not a protocol change
An independent community initiative proposes that Aave assess a new layer of controls for limiting risk during external security incidents. The “AAVE SECURITY SHIELD” document was posted by bubacarrhaidara on Nov. 9 as a preliminary concept, before a possible ARFC.
The initial request is for the community to consider funding or conducting a feasibility study with defined goals, deliverables, owners and budget. The initiative does not seek immediate changes to the protocol; it asks whether temporary limits on new credit exposure could give Aave more time to assess a threat and respond.
Three controls under consideration
The document describes two kinds of external risk. An attack on another protocol could undermine the backing, liquidity or recoverability of an asset accepted as collateral, while an attacker might try to deposit assets linked to a theft and borrow other assets against them. The proposal treats collateral solvency and the provenance of funds as different issues, saying they should not automatically receive the same response.
The study would examine three main approaches: delaying the point at which selected new collateral can support borrowing, making borrowing capacity available gradually, and capping how quickly new debt can accumulate during a defined time window. The proposal does not set a formula or rate for gradual capacity, and says a 24-hour delay could be tested in simulations but is not a universal requirement.
For borrowing limits, the document suggests assessing caps by collateral asset, borrowed asset or market, as well as different time windows and combinations with existing borrow and draw caps. Limits based only on an individual wallet could be insufficient if activity is spread across multiple wallets, so the study should prioritize aggregate exposure controls, the document says.
Response rules and user protections
The initiative also proposes evaluating a staged “Security Response” system: observation of an unconfirmed signal, precaution when relevant evidence emerges, emergency restrictions when an incident is confirmed and exposure is material, and gradual removal of restrictions during recovery. An alert from a single private analytics provider should not automatically trigger restrictions, the initiative says.
Any measures would be assessed against the quality of evidence, the incident’s scope, potential economic exposure and the possibility of using existing controls. The proposal says it is not seeking powers to confiscate assets, transfer user funds to third parties or selectively block withdrawals based only on links between addresses. It also rejects universal personal identification requirements.
For users with existing loans, the document says the design should, where technically safe, preserve debt repayment, liquidations and collateral contributions that reduce position risk. It also calls for assessing effects on reserve utilization and interest rates, rather than assuming that restricting new activity has no impact on existing users.
Scope, costs and next steps
The proposed study would inventory current controls across Aave versions and markets, identify gaps, compare the three options, and run retrospective and hypothetical incident scenarios. It would also examine evasion, liquidity and user impacts, coverage mechanisms, legal and governance questions, costs, and whether to continue, revise or abandon the work.
The proposal sets no definitive budget, saying one would depend on technical scope and verifiable estimates. Approval of a study would not automatically approve development or deployment, the proposal says; a pilot would be considered only if study results justified it. If the work shows sufficient improvement, the suggested path proceeds through research, technical design, prototyping, audits, a limited pilot and community review before any formal implementation proposal.
Sources
- Original source Aave Governance Forum governance.aave.com