🔐 Security & Audits
Underlying Protocol Risks

Underlying Protocol Risk

AggreLend is built to be conservative and transparent: it is a lend-only router that moves your deposit among vetted venues when there is a clear, durable benefit. That design reduces surface area and avoids liquidation paths—but in a composable ecosystem, outcomes still depend on the continued safe operation of the underlying venues where funds are actually earning.

What We Control

  • The AggreLend program (audits, transaction-context guards, upgrade discipline).
  • Which venue families are enabled, and the curation standards we apply (audits, KYB, operational history).
  • Clear presentation of effective APY and live visibility into where balances are currently allocated.

What We Don’t Control

  • Internal solvency, oracle choices, utilization dynamics, reward schedules, caps/pauses, or parameter changes at the underlying venues.
  • External events that impact a venue’s operations.

AggreLend integrates venues that publish audits and maintain credible operational practices, and we can down-weight, pause, or remove an integration if signals fall below our bar. Nevertheless, if a venue suffers an issue, exposure at that venue can affect routed deposits proportional to allocation and time parked there. This is the trade-off of permissionless composability—so we keep our selection strict and our visibility high.

⚠️

You can always see where your balance is deployed in the app, and via our API. If routing changes, the interface reflects it promptly so you remain informed.

Audit Hubs You Can Review

Bottom Line

We reduce risk by keeping the core small, choosing lend-only integrations, and enforcing strong transaction guards. The remaining risk is the visible, auditable risk of the venues where funds earn—so we link their materials, monitor conditions, and route with reliability in mind.