Upshift

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

Upshift issues vault shares while professional curators execute changing DeFi and, for some designs, CeFi or cross-chain strategies through policy-constrained infrastructure. The DefiLlama API read on 2026-08-15 reported about $345M across twelve nonzero chains, so the former $55M below-materiality classification was false. The correct v1 disposition is delegated allocation: whitelists, buffers, timelocks and transaction policies constrain a curator, but they do not give this advisory program control over future underlying venues, strategy weights or every accepted chain. Rejected under the shared class rule, not on an allegation that Upshift is unsafe.

Kill criteria: the events that revoke this verdict
• A named vault enforces an immutable or client-specific allowlist and caps limited to approved protocols and chains
• That vault publishes continuous holdings, authority, NAV, realized-loss and executable stressed-redemption evidence

The research file

Mechanism and class applicability

Upshift supports single-asset ERC-4626 and multi-asset vaults whose depositors receive receipt tokens. Its documentation says professional curators actively execute lending, liquidity provision, staking, basis, real-world-asset and other strategies, potentially across multiple protocols and chains. Because the curator can change those exposures after deposit, the product directly meets the delegated-allocation dossier rather than the below-materiality class.

Control and operating evidence

Upshift describes two execution paths: August smart-contract subaccounts with strategist roles and whitelisted integrations, and Fordefi MPC workspaces whose transaction policies require approvals. It says funds cannot be sent to arbitrary external addresses in the August path, provides configurable buffers and NAV-change limits, applies a 24-hour timelock to critical settings, and gives a multisig emergency powers. These are meaningful constraints, but partners, curators and administrators still determine the permitted universe and strategy.

Security, accounting and exit evidence

The published interface includes operator, settlement-account, issuance-limit, NAV-sync, timelock and redemption-processing functions, showing material accounting and operational authority that must be mapped per deployment. A holder requests redemption, burns shares and waits until a claimable epoch; settlement therefore depends on the configured buffer, strategy unwind and accurate NAV, and a multisig may pause withdrawals in an emergency. The reviewed sources do not provide a single complete cross-vault audit and incident ledger, so no platform-wide clean-record claim is made.

Why the delegated-allocation rule decides

Upshift’s policy engine can reduce unauthorized transfers while still permitting an approved curator to alter underlying venues and weights. Some documented designs also introduce bridges, MPC custody or CeFi positions and chain dependencies that cannot be accepted through a platform-level label. Review can reopen only for a named vault with an immutable or client-specific allowlist and caps restricted to approved venues and chains, plus continuously verifiable holdings, authorities, NAV, losses and stressed redemption liquidity.

Sources

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

• Upshift Docs — platform and strategy scope · primary · accessed 2026-08-15
  Supports: curated vaults, DeFi and CeFi strategies, multi-protocol allocation, August subaccounts
• Upshift Docs — product and curator FAQ · primary · accessed 2026-08-15
  Supports: professional curator, yield sources, whitelisted protocols, receipt tokens
• Upshift Docs — risk-management framework · primary · accessed 2026-08-15
  Supports: non-custodial controls, liquidity buffer, NAV constraint, timelock, multisig pause
• Upshift Docs — multi-asset custody and execution · primary · accessed 2026-08-15
  Supports: August subaccount, Fordefi MPC, strategist role, whitelists, bridge modules, NAV responsibility
• Upshift Docs — vault contract interface · primary · accessed 2026-08-15
  Supports: redemption request, claimable epoch, operator authority, settlement account, NAV sync
• Upshift Docs — deployed Upshift Lend contracts · primary · accessed 2026-08-15
  Supports: deployed proxies, vault owner, operator, proxy admin, timelocked calls
• DefiLlama — Upshift survey record, read 2026-08-15 · secondary · accessed 2026-08-15
  Supports: current TVL, chain distribution, allocator category, survey perimeter

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.