Kinza Finance
Kinza Finance is outside the current firm shelf because the rejected-chain policy applies to it. This is a firm policy decision, not a negative quality rating or a client trade instruction. The facts about how it works, who controls it, how losses can occur, and how users exit remain below.
- Deploys meaningful liquidity on a chain the registry approves
- The BSC verdict changes
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-15.
The research file
Mechanism applicability
Kinza describes a pooled money market: suppliers deposit into contracts for each asset, receive interest-bearing kTokens, and make liquidity available to borrowers who provide excess collateral. Borrowers receive dToken debt, rates change with market utilization, unhealthy accounts can be liquidated, and reserve factors direct part of the interest toward protection from bad debt. These facts establish the lending product surveyed by DefiLlama.
Current observation and perimeter
The DefiLlama protocol API read on 2026-08-15 classified Kinza Finance as Lending and reported approximately $2.90M TVL and $1.38M borrowed across BSC, opBNB, Ethereum and Mantle. About $2.85M, more than 98% of TVL, remained on BSC. Ethereum held only about $0.01M, and the other deployments were similarly de minimis. The registry now covers more than BSC, but the shared v1 rejected-chain review still decides the judgment for the deployment that holds nearly all the capital.
Control and exit applicability
Kinza says each market has LTV, liquidation-threshold, reserve-factor and supply/borrow-cap settings, while future governance can change reserve factors. A supplier can request a full withdrawal, but collateral withdrawals must leave health above one, and recovery depends on enough liquidity remaining unborrowed. Asset isolation limits contagion from volatile collateral. It does not make the BSC-dominant lending claim eligible under the chain policy.
Why the class rule decides
Ethereum, Mantle and opBNB labels do not fix a rejected-chain exposure when more than 98% of current capital remains on BSC and approved-chain liquidity cannot support a meaningful advised allocation. The shared v1 rejected-chain review therefore decides before a credit review of each market. Reopen if BSC is approved or if independently verified liquidity on an approved chain becomes large enough for the proposed sleeve. Then review utilization, collateral and oracle settings, admin controls, incidents, bad debt and stressed withdrawals against named lending alternatives.
Class rule
The rejected chain class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Kinza — protocol and deployment overview · primary · accessed 2026-08-15
Supports: money market, BNB, opBNB, Ethereum, Mantle, live lifecycle - Kinza — lending and borrowing mechanics · primary · accessed 2026-08-15
Supports: supplier pools, kTokens, dTokens, utilization rates, collateralized borrowing - Kinza — risk factors and caps · primary · accessed 2026-08-15
Supports: overcollateralization, LTV, liquidation threshold, health factor, supply and borrow caps - Kinza — withdrawal mechanics · primary · accessed 2026-08-15
Supports: full withdrawal, health factor, collateral constraint, execution - Kinza — bad-debt reserves · primary · accessed 2026-08-15
Supports: bad debt, reserve factor, borrower interest, governance parameters - DefiLlama — Kinza Finance survey record · secondary · accessed 2026-08-15
Supports: current TVL, borrowed amount, current chains, Lending category, survey observation
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 |
|---|---|---|---|
| BNB Smart Chain | Rejected | Issuer can freeze | the validator set concentrates around one company, and the chain has been halted by decision. |
| Ethereum | Approved | No freeze key | No sequencer, no upgrade key, no operator who can be compelled. Rule changes require social consensus. |
| Mantle | Rejected | Issuer can freeze | the team can push instant upgrades; there is no exit window a client could use. |