Affluent

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

Affluent is an asset-management and lending protocol on TON, delivered mostly through Telegram-based apps that abstract the underlying positions. The 2026-08-15 endpoint reported about $2.43M on TON, while current primary materials describe expert-managed vaults and a Sentora path whose manager bridges queued USDT into whitelisted Euler and Morpho vaults on Ethereum. Because managers can allocate, rebalance and use leverage after deposit, the v1 delegated-allocation dossier controls regardless of current size; TON and cross-chain settlement remain additional hurdles.

Kill criteria: the events that revoke this verdict
• A named vault publishes and enforces an immutable adviser-compatible asset, market, chain and leverage allowlist with caps, no manager substitution, and continuously verifiable positions, debt, roles and realized losses
• Demonstrates a proposed-size stressed withdrawal through every required reserve, manager action, bridge, destination vault and queue within a documented maximum

The research file

Applicability to the surveyed record

Affluent documents permissionless TON lending markets and expert-managed strategy vaults whose code-enforced rules allocate deposits among approved lending, RWA, DeFi, and CeDeFi strategies. Telegram and Wallet interfaces abstract those positions, while vault-share holders delegate allocation, leverage, and rebalancing to a manager within owner and guardian constraints.

Current observation and lifecycle

The DefiLlama protocol API read on 2026-08-15 classified Affluent as Lending, reported only TON, and showed approximately $2.43M TVL with $0.55M borrowed. Current Affluent materials describe a 2026 transition toward cross-chain yield: the TON-side Sentora vault queues USDT while a manager bridges and deploys it into whitelisted Euler and Morpho vaults on Ethereum. The tracked protocol remains far below $100M.

Control and exit applicability

Vault owners appoint managers and guardians and set fees, assets, lending pools, exposure caps, oracle configuration, and upgrades, with timelocks on specified changes. Exit is vault-specific: ordinary withdrawals can depend on reserved liquidity, high utilization, or rebalancing; the cross-chain Sentora vault batches deposits and processes a withdrawal queue weekly, adding manager execution, bridge, destination-vault, and settlement dependencies.

Why the class rule decides

The shared v1 delegated-allocation dossier controls because the holder cannot pin an aggregate Affluent position to today’s approved markets, weights, leverage or chain route while managers rebalance within owner-defined limits. TON disposition and bridge dependencies add constraints but do not cure the delegated mandate. Reopen only for a named vault with an immutable adviser-compatible market, asset, chain and leverage allowlist and caps, no manager substitution, continuously verifiable positions and roles, and a proposed-size stressed withdrawal through every required bridge and queue.

Sources

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

• Affluent Docs — protocol overview · primary · accessed 2026-08-15
  Supports: TON asset management, managed vaults, lending markets, non-custodial design, Telegram interface
• Affluent Docs — strategy-vault roles · primary · accessed 2026-08-15
  Supports: owner, manager, guardian, timelocks, fees, asset caps, pool authorization
• Affluent — vault withdrawal workflow · primary · accessed 2026-08-15
  Supports: TON Wallet, vault deposit, instant withdrawal, reserve-dependent settlement, 24-hour withdrawal
• Affluent — current Sentora lifecycle announcement · primary · accessed 2026-08-15
  Supports: 2026 V3, Sentora vault, Ethereum deployment, Euler and Morpho, weekly withdrawal queue, manager responsibilities
• DefiLlama — Affluent survey record · secondary · accessed 2026-08-15
  Supports: current TVL, borrowed amount, TON perimeter, Lending category

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.