Venus Flux

Venus Flux is a BNB Chain lending product whose unified liquidity layer accepts supplier deposits and supports borrowing across its markets. The 2026-08-15 survey showed about $3.10M supplied and $1.88M borrowed, but size is contextual rather than decisive. Every position and exit settles on BSC, whose chain verdict is rejected, so the version-1 rejected-chain dossier controls before market-level underwriting.

Review triggers: events that reopen the verdict
• The same lending product sustains meaningful, independently verifiable liquidity on an approved chain
• 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

Applicability to the shared dossier

The live Venus Flux product describes a unified liquidity layer in which users supply assets for interest and borrowers draw against the same venue. Its live dashboard is identified by chain ID 56 and the survey reports only the Binance/BNB Chain perimeter. Deposits, interest accrual, borrowing, liquidations and withdrawals therefore depend on BSC settlement, matching the rejected-chain dossier directly.

Current observation and perimeter

Observed 2026-08-15: the protocol page and chain-56 dashboard remained live. DefiLlama reported approximately $3.10M of TVL and $1.88M borrowed, with no deployment outside Binance/BNB Chain. Those figures establish the current product perimeter; they do not substitute a residual size test for the more fundamental chain exclusion.

Control, loss and exit applicability

Venus states that Flux uses an automated debt ceiling: withdrawals increase the ceiling each block along a smoothing curve to limit abrupt liquidity movement. A supplier exit therefore depends on available market liquidity and this on-chain control, and the product warns that loss can be complete. These are material lending risks, but all are realized through the excluded settlement venue and do not overcome the chain gate.

Why the class rule decides

The chain registry rejects BSC and Venus Flux currently has no independently verifiable approved-chain instance of the same lending product. The shared version-1 rejected-chain dossier therefore decides without implying that Flux failed an individual credit, code or governance review. Reopen if BSC becomes approved or the same product establishes meaningful liquidity on an approved chain, then perform full market-level underwriting.

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.

• Venus Flux — lending product, liquidity and risk disclosures · primary · accessed 2026-08-15
  Supports: unified liquidity layer, supplier yield, automated debt ceiling, loss risk
• Venus Flux — live BNB Chain dashboard · primary · accessed 2026-08-15
  Supports: chain ID 56, live product perimeter
• Venus governance — Venus Flux product operations · primary · accessed 2026-08-15
  Supports: Venus suite product, Flux operations
• DefiLlama — Venus Flux survey record · secondary · accessed 2026-08-15
  Supports: current TVL, borrowed amount, chain coverage

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.