Upshift

Upshift is rejected under the shared class rule, not because of an allegation that Upshift is unsafe. It issues vault shares while professional curators run changing DeFi strategies and, for some designs, CeFi or cross-chain strategies through infrastructure bound by set policies. 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 judgment 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.

Review triggers: events that reopen the 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

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 and class applicability

Upshift supports single-asset ERC-4626 and multi-asset vaults that give depositors receipt tokens. Its documentation says professional curators actively run lending, liquidity provision, staking, basis, real-world-asset and other strategies, sometimes across several protocols and chains. Because the curator can change those exposures after deposit, the product falls directly within the delegated-allocation class, not the below-materiality class.

Control and operating evidence

Upshift describes two ways to carry out transactions: August smart-contract subaccounts with strategist roles and whitelisted integrations, and Fordefi MPC workspaces with transaction policies that require approvals. It says funds cannot go to arbitrary external addresses through the August path. It also provides configurable buffers and NAV-change limits, applies a 24-hour timelock to critical settings, and gives a multisig emergency powers. These limits matter, but partners, curators and administrators still choose the permitted set of venues and strategies.

Security, accounting and exit evidence

The published interface includes operator, settlement-account, issuance-limit, NAV-sync, timelock and redemption-processing functions. These show significant accounting and operating powers that must be identified for each deployment. A holder requests redemption, burns shares and waits until a claimable epoch. Settlement therefore depends on the configured buffer, the unwinding of strategies and accurate NAV, and a multisig may pause withdrawals in an emergency. The reviewed sources do not provide one complete audit and incident record across all vaults, so no claim of a clean record across the platform is made.

Why the delegated-allocation rule decides

Upshift’s policy engine can reduce unauthorized transfers while still letting an approved curator change underlying venues and weights. Some documented designs also add bridges, MPC custody or CeFi positions and chain dependencies that a platform-level label cannot accept. Review can reopen only for a named vault with an immutable or client-specific allowlist and caps limited to approved venues and chains, plus holdings, authorities, NAV, losses and stressed redemption liquidity that can be checked at all times.

Class rule

The delegated allocation 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.

• 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-09-15
  Supports: non-custodial controls, liquidity buffer, NAV constraint, timelock, multisig pause
• Upshift Docs — multi-asset custody and execution · primary · accessed 2026-09-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-09-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 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.