K613
K613 is an Aave-v3-compatible overcollateralized lending market on Monad with eleven documented reserves, configurable caps, liquidation parameters and emissions. The 2026-08-16 survey measured about $0.037M supplied, only 0.037% of the size floor; separately reported borrowing is not exit capacity. K613 is below that floor, so the version-1 dossier does not open an individual review of reserves, oracles, governance or liquidations until it clears the floor.
- TVL sustained above the retired TVL threshold for 30 days
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-16.
The research file
Mechanism applicability
K613 runs an Aave-v3-compatible pooled money market on Monad. Its market configuration lists eleven reserves with supply and borrow caps, utilization-based interest curves, collateral LTVs and liquidation thresholds. Suppliers receive interest-bearing claims. Withdrawals depend on the underlying cash left after borrower use, while collateralized borrowers face health-factor liquidation.
Control, loss and exit applicability
The published configuration uses the Aave ACLManager and ConfigEngine to list assets, change caps, collateral and rate parameters, configure eMode and freeze or pause reserves. The runbook calls for moving deployer roles to multisigs, but a full review must verify that change on-chain. Exit depends on available reserve liquidity, sound oracles, Monad settlement, asset quality and the configured admin controls.
Current observation and perimeter
The DefiLlama API read on 2026-08-16 classified K613 as Lending and reported approximately $0.037M supplied, all on Monad. A separate approximately $0.065M borrowed suffix is not added to supplied TVL. Current GitHub activity and the Monad-mainnet configuration show an active lifecycle, but the survey lists no audit record.
Why the materiality dossier decides
Supplied TVL is approximately 0.037% of the size floor, so an advised allocation would be large against measured cash capacity despite the familiar upstream code. Do not open the individual review until supplied TVL stays above the size floor for 30 days. Then verify deployed addresses and roles, every reserve and oracle, cap and eMode changes, audit and incident history, bad debt and proposed-size withdrawals.
Research status
This is a capacity-unproven record for K613, not a quality rejection or approval. Reported TVL says how big the venue is, not what the client owns, who can change the rules, or how a position exits at a proposed size. The individual review opens when the protocol clears the size floor.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- K613 — official GitHub organization · primary · accessed 2026-08-16
Supports: current project lifecycle, official repositories, interface and protocol identity - K613 — Monad market configuration · primary · accessed 2026-08-16
Supports: Monad mainnet, eleven reserves, caps and interest curves, liquidation parameters, eMode, admin lifecycle - K613 — protocol repository · primary · accessed 2026-08-16
Supports: Aave v3 origin fork, pool contracts, protocol source - K613 — user interface repository · primary · accessed 2026-08-16
Supports: supply and borrow interface, current application development, Aave interface lineage - K613 — protocol-owned survey adapter · primary · accessed 2026-08-16
Supports: adapter ownership, supplied and borrowed accounting, Monad deployment - DefiLlama — K613 survey record · secondary · accessed 2026-08-16
Supports: current supplied TVL, borrowed separation, Monad perimeter, Lending category, audit count
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Monad | Approved with limits | Governed, no freeze | the L1 has a public validator path, but its short production record, single initial client lineage, and Foundation-directed delegation keep stake and operations concentrated. |