Overview
Risks
How much debt can be issued against SYRUPUSDC as collateral across lending protocols.
Maximum possible exposure to SYRUPUSDC
$99.5m
$37.4m (max additional borrows against SYRUPUSDC) + $62.1m (bad debt if SYRUPUSDC was hacked now)
Aave V3
$19.88m at-risk exposure = -- bad debt if hacked + $19.88m additional borrowable against SYRUPUSDC
Morpho V1
$69.2m at-risk exposure = $59.85m bad debt if hacked + $9.35m additional borrowable against SYRUPUSDC
Fluid
$5.09m at-risk exposure = $28,155.54 bad debt if hacked + $5.06m additional borrowable against SYRUPUSDC
Euler V2
$5.34m at-risk exposure = $2.22m bad debt if hacked + $3.12m additional borrowable against SYRUPUSDC
Methodology and limitations
Showing collateral exposure for SYRUPUSDC on onchain. Max Borrowable uses the backend's liquidity-bounded borrow-capacity metric (`collateralMaxBorrowUsdLiquidity`) for the maximum additional USD debt that can be issued against the asset right now. Bad Debt at $0 is the minimum known bad debt if the collateral asset price goes to zero; null rows are excluded from this total rather than treated as zero, so totals may remain lower bounds.
- These metrics describe lending exposure only and are not a full protocol risk rating.
- This view does not include multisigs, timelocks, audits, oracle incidents, listing discussions, curator reports, or protocol backstops.
- Chain-specific drilldown is exact only when the token resolves to a concrete chain:address.
- Bad debt at $0 is a lower bound when some contributing markets return null for zero-price bad debt; null rows are excluded instead of being treated as zero.
Show exposure details
Each row is one protocol-chain exposure for SYRUPUSDC as collateral. Bad debt at $0 totals remain lower bounds when a row is marked partial.
Token Usage
An is required to view token usage.
Liquidations
An is required to view token liquidations.
Yields
Tracking 6 pools, average APY 4.03%
Borrow
Showing 10 of 26 routes