STRATO

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

STRATO CDP is deployed only on BlockApps’ proprietary STRATO mainnet. STRATO uses identity-gated transactions and a permissioned PBFT validator set whose validator-governance contract can add or remove validators and administrators. No approved-chain deployment is evidenced, so the version-1 rejected-chain dossier decides regardless of the approximately $16.65M observed on 2026-08-15.

Kill criteria: the events that revoke this verdict
• STRATO passes the adviser chain review or the exact CDP deploys on an approved chain
• The named deployment then supplies verified contracts, authority and validator maps, collateral and oracle controls, liquidation history, incidents and proposed-size exit evidence

The research file

Mechanism and chain applicability

The tracked STRATO CDP record is confined to the STRATO mainnet rather than an adviser-reviewed public chain. BlockApps documents STRATO as an EVM-compatible network with verified identities and two node roles, validator and non-validator. Transactions require cryptographic identity verification, while the validator subset orders blocks through PBFT. That proprietary settlement perimeter directly meets the shared v1 rejected-chain dossier.

Current observation and lifecycle

The DefiLlama protocol API read on 2026-08-15 reported approximately $16.65M for STRATO CDP, entirely on Strato. BlockApps continues to publish mainnet node, API, consensus and network-deployment documentation. Those observations support an active chain and coverage record, but do not establish an approved-chain deployment or complete the chain-level legal, custody, operational and incident review required for client capital.

Authority and finality applicability

STRATO documents PBFT finality among a permissioned set of trusted validator identities. A validator-governance contract manages validator and validator-administrator additions and removals, and network setup requires validator certificates. Those controls create chain-specific liveness, membership, identity-provider and administrator dependencies that cannot be underwritten from the CDP TVL figure or ordinary EVM compatibility.

Why the class rule decides

The product cannot be separated from STRATO consensus, verified identity and validator governance because every collateral, debt and exit transaction settles there. The shared v1 rejected-chain dossier therefore controls before CDP collateralization or liquidity analysis. Reopen only after STRATO passes the adviser’s chain review or the exact product deploys on an approved chain, followed by product contracts, authorities, collateral, oracle, liquidation, incident and proposed-size exit review.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• BlockApps — STRATO developer documentation · primary · accessed 2026-08-15
  Supports: STRATO mainnet, EVM compatibility, current lifecycle, developer documentation
• BlockApps — STRATO PBFT consensus and validator governance · primary · accessed 2026-08-15
  Supports: PBFT, permissioned validators, validator governance contract, validator administrators, two-thirds threshold
• BlockApps — STRATO network concepts · primary · accessed 2026-08-15
  Supports: validator nodes, non-validator nodes, PBFT, signed transactions, identity
• BlockApps — STRATO network setup · primary · accessed 2026-08-15
  Supports: mainnet node, validator certificate, network deployment, validator identity
• BlockApps — STRATO API identity verification · primary · accessed 2026-08-15
  Supports: identity verification, OAuth, transaction access, API
• DefiLlama — STRATO CDP survey record · secondary · accessed 2026-08-15
  Supports: current TVL, Strato-only perimeter, CDP category, survey observation

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.