Elevated risk — novel Liquidity Hook architecture with limited oracle redundancy and a severe TVL collapse from peak (~95%), combined with pre-token governance, leaves the protocol in a fragile operational state.
Risk Breakdown
Top Risks
Liquidity Hook architecture introduces external smart contract risk: third-party hook contracts (e.g., DEX loop hooks for MerchantMoe, Agni, Ethena) interact directly with user positions in INIT's core, and a buggy or malicious hook could drain positions — 'Official Partner' status requires an audit but permissionless hook submissions have lower scrutiny.
Oracle infrastructure is under-redundant: API3 is the primary price source with Pyth listed as 'coming soon,' and when oracle sources deviate beyond thresholds, INIT pauses all protocol actions rather than falling back to a secondary price — creating a hard dependency on a single active feed.
Severe TVL collapse since mid-2024 peak ($45M → $2.25M, ~95% decline) suggests the hook-based liquidity flywheel has not self-reinforced; the Blast chain deployment is effectively dormant ($93K TVL), and development activity appears sparse since late 2024.
Pre-token status means no protocol-owned governance or formal risk committee: parameter changes require manual operator action with limited on-chain accountability, introducing key-person risk for oracle threshold and debt ceiling adjustments.
Frequently Asked Questions
Is INIT Capital safe to use?
What are the main risks of using INIT Capital?
What is INIT Capital's risk score breakdown?
How does INIT Capital compare to other Lending protocols?
Has INIT Capital ever been hacked or exploited?
Get risk alerts before it's too late
Weekly grade changes, downgrade alerts, and new protocol risk findings. Free.