/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Jump and Oasis recovering ~120K stolen ether demonstrates how multisig-controlled upgradeable smart contracts undermine trustlessness and censorship-resistance

Molly White

Context & Ripple Effects

Two years after a 2022 Wormhole exploit drained ~120,000 ether, the money is back: Oasis complied with a UK high court order by upgrading a DeFi contract under its control, letting Jump sweep the stolen funds out. The episode works as the inverse of Parity's 2017 wallet freeze — same lesson about admin keys over deployed code, but this time used for restitution rather than producing losses.

What makes it analytically important is not the recovery itself but the mechanism: multisig-controlled upgradeability meant a handful of keyholders could redirect contract logic at a court's request, which is precisely the trust assumption 'trustless' DeFi claims to have removed.

First-order effects

  • The hacker loses the ~120K ether ($140M), and Jump closes out its exposure from the Wormhole exploit without any on-chain compromise of the attacker's keys — the contract upgrade did the work instead.
  • Oasis's compliance shows that operators holding upgrade authority over deployed contracts can be legally compelled to repurpose it, converting their admin keys into an enforcement tool.

Second-order effects

  • Courts now have a demonstrated playbook — order the operator, force the upgrade, drain the funds — which lowers the cost of future recovery attempts against any protocol whose contracts are upgradeable behind a multisig.
  • DeFi users and auditors are forced to price upgradeable contracts differently: the presence of admin keys is no longer a theoretical centralization footnote but a proven seizure vector, pressuring protocols toward immutability or explicit disclosure.

Third-order effects

  • If the pattern holds, the industry splits structurally between immutable 'censorship-resistant' deployments and governed, upgradeable ones whose effective jurisdiction is wherever their operators sit — with capital and litigation migrating accordingly.
  • The gap between DeFi's trustlessness marketing and its operational reality widens into a legitimacy problem: either recovery-by-design becomes a stated feature courts can invoke, or the 'trustless' label stops being credible for anything upgradeable.

The trend: Court-directed smart-contract upgrades are turning DeFi's upgradeability from a security liability into an enforcement surface, forcing the industry to choose openly between censorship-resistance and recoverability.

Discussion

  • @danyork@mastodon.social Dan York on mastodon
    Another fascinating and brilliant post from @molly0xfff about the reality of #centralization within “DeFi” and how for convenience, immutable actions have become mutable.  A key quote for me: …
  • @profjaparker Jonathan A. Parker on x
    DeFi in many places is converging to a costly, slow, unsafe, centralized, and definitely dodgy version of traditional finance... https://twitter.com/... https://twitter.com/...
  • @blockworksres @blockworksres on x
    2/ We published a free report on Blockworks Research that details exactly how the counter exploit was facilitated. This report includes links to all addresses and transactions mentioned below. The rest of this thread hits the highlights 👇 https://www.blockworksresearch.com/ ...
  • @tayvano_ Tay on x
    Here's the key pieces about the actions with regards to the “sender” (aka Jump) and the “multisig” (aka Oasis) https://www.blockworksresearch.com/ ... https://twitter.com/...
  • @tayvano_ Tay on x
    It looks like in both these cases the contracts were upgraded / funds moved by the parties from whom the funds were originally stolen from. It was almost certainly Jump + Whitehats who actually did the thing This post by @smyyguy is fantastic https://www.blockworksresearch.com/ .…
  • @tayvano_ Tay on x
    And here's the key pieces about the system design that allowed the Oasis 4-of-12 multisig to be used to be able to take action on behalf of an independent entity's vault https://www.blockworksresearch.com/ ... https://twitter.com/...
  • @molly0xfff Molly White on x
    I run into this a lot in crypto. People decide to use a blockchain and incur huge speed/$/scalability costs, then themselves undermine all the things the blockchain is supposed to do, ending up with a version of existing products that's just slow, expensive, and doesn't scale. ht…
  • @molly0xfff Molly White on x
    Grab your machete because we're getting into the weeds. The “counter-hack” by Jump Crypto and Oasis just provided a remarkable demonstration of the centralization of defi. Read more: https://newsletter.mollywhite.net/ ...