Origin Sonic
Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.
Origin Sonic (OS) is a Sonic liquid-staking receipt now in an approved wind-down, not a growth-stage LST screened only for size. Origin governance approved stopping new activity, unstaking the S backing OS, preserving redemption and claim paths, and giving users at least two months of in-app exit support once exit flows were live. The current adapter still measures about $139,330 in the Sonic vault, so active coverage must remain until residual OS liabilities, unstaked S and user claims are demonstrably extinguished. Rejected with no allocation; the broken product-doc URL is replaced by current governance, vote, contract and survey evidence.
- Within 30 days, publishes a dated block-level reconciliation of OS and wOS supply, vault and ARM assets, validator unstaking, unclaimed balances and user claim instructions
- OS and wOS supply, pending unstaking, unclaimed balances and uncovered liabilities each equal zero, or liquid reserves cover 100% of every remaining claim at the reconciled block
- The live coverage feed confirms zero remaining protocol balance before archive treatment is considered
The research file
Product identity and approved disposition
Origin launched OS in January 2025 as an S-backed liquid-staking token on Sonic, with OS and wrapped wOS contracts and a planned AMO for peg liquidity. On June 18, 2026, an official proposal concluded the products no longer cleared business, liquidity, revenue, risk and maintenance thresholds. Snapshot closed on June 27 with 18,632,310 votes for wind-down and none against or abstaining. The operative lifecycle is therefore exit-only.
Wind-down mechanics and authority
The approved plan stops integrations, liquidity campaigns and business development; unstakes OS backing; keeps redemption and claim paths available; pauses new OS ARM deposits; unwinds lending exposure; and returns ARM assets pro rata in S. Origin may remove product pages after a two-month UI-support window and move remaining claims to documentation or direct contracts. Governance and operators therefore control timing of unstaking, asset availability, notices and interface support during the unwind.
Residual accounting and exit evidence
DefiLlama reported $139,330 on Sonic on 2026-08-16. Its adapter reads every asset and checkBalance result held by vault 0xa3c0eCA00D2B76b4d1F170b0AB3FdeA16C180186; this is residual vault asset value, not proof that every OS or wOS holder can redeem immediately. The public file does not yet reconcile outstanding OS and wOS supply, pending validator unstakes, vault assets, ARM claims and unclaimed user balances at one block. Because adapter TVL counts assets rather than liabilities, a falling balance could reflect successful redemptions, asset removal, price decline or an accounting gap. It cannot by itself prove that the remaining receipt supply is fully backed or that every holder has received S. Final evidence must pair asset balances with token supply and claims.
Incident, chain and comparison review
No exploit is cited as the reason for closure; the disclosed reasons are economic, risk and operating thresholds. Nonetheless every residual claim depends on Sonic contracts, validators, unstaking and Origin-controlled wind-down execution. Unlike a live reviewed LST accepting new deposits, OS has no defensible allocation case while operations cease. The correct comparison is cash returned from an orderly liquidation, not headline LST APY.
Measurable closure criterion
Keep this active rejected version-1 memo until a dated final reconciliation proves OS and wOS supply, vault and ARM assets, pending unstakes and user claims are all zero or fully reserved, and the last holder retains documented contract-level claim instructions. Only after the live coverage feed also disappears may archive treatment be considered; a lower TVL or removed UI is not evidence of completed redemption.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Origin Governance — OS and OS ARM wind-down plan · primary · accessed 2026-08-16
Supports: stop new activity, unstake backing, redemption and claims, ARM unwind, two-month UI support - Origin Snapshot — approved wind-down vote · primary · accessed 2026-08-16
Supports: closed vote, 18,632,310 for, zero against, approved lifecycle - Origin — OS launch and contract identity · primary · accessed 2026-08-16
Supports: Sonic LST, OS and wOS contracts, staking backing, AMO plan - SonicScan — Origin Sonic vault · primary · accessed 2026-08-16
Supports: deployed Sonic vault, residual onchain lifecycle, contract activity - DefiLlama adapter — Origin Sonic vault accounting · secondary · accessed 2026-08-16
Supports: vault address, asset discovery, checkBalance accounting, Sonic-only adapter - DefiLlama — Origin Sonic residual survey record · secondary · accessed 2026-08-16
Supports: $139,330 TVL, Sonic perimeter, Liquid Staking category, active coverage obligation
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.
| Chain | Verdict | Grade | Control constraint |
|---|