aare.finance

Architecture

No bridges.

Bridges are the leading cause of loss in DeFi. aare removes them entirely by running natively on Layer 1. This is not a design trade-off — it is the design.

Why bridges fail

Message-passing bugs

Cross-chain protocols rely on messages being correctly verified at the destination. A single parsing error in that logic can allow an attacker to mint unbacked tokens.

Bridge admin key risk

Most bridges are controlled by a multi-sig. If those keys are compromised, all bridged funds are at risk simultaneously — not just a single protocol.

Oracle timing on cross-chain

Price oracles must be consistent across chains. A delayed or spoofed oracle on the destination chain can allow undercollateralized borrows before the price is corrected.

Reorg asymmetry

A chain reorg on the source chain can leave the bridge in an inconsistent state — funds locked on one side with no corresponding position on the other.

The L1-native alternative

aare deploys a complete lending protocol on a single L1. Collateral, debt, liquidations, and oracle reads all happen in one atomic transaction on one chain. There is no cross-chain message to intercept, delay, or spoof.

See the security model

How the L1-native design affects the threat model.

Security overview →