shield Business Logic Flaw · $13K loss

$13K drained from sDAO in a business logic flaw (November 2022)

On November 2022, – sDAO was exploited in a business logic flaw, resulting in approximately $13K in losses. That makes the – sDAO exploit the 368th largest DeFi incident out of 690 documented in our archive.

Attack Mechanics: How the – sDAO Business Logic Flaw Played Out

Exploit Class Applied to – sDAO

The – sDAO incident on November 21, 2022 is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share. In the full archive, – sDAO is 1 of 144 documented business logic flaw incidents.

– sDAO in Context

At $13K, the – sDAO exploit is a minor (<$1M) event compared to the largest same-class incident in our archive — – EulerFinance (2023) at $200M.

Prior Business Logic Flaw Before – sDAO

The nearest business logic flaw incident before – sDAO was BDEX, 16 days earlier on November 5, 2022. The same exploit class surfaced again within the business logic flaw attack surface.

Impact & Recovery for – sDAO

– sDAO Loss Figure

The – sDAO exploit caused $13,000 in losses — a minor (<$1M) incident and the 44th largest of 129 documented in 2022.

Where – sDAO Sits Among Business Logic Flaw Attacks

Ranked by loss size, – sDAO is the 82nd largest of 144 business logic flaw incidents documented. That puts the – sDAO loss below the class average of $6.08M.

Timeline Since the – sDAO Incident

The – sDAO exploit occurred 3.4 years ago (1,240 days). The contract, its fork-block, and the attack transaction remain on-chain and forensically reproducible.

Primary Reference for – sDAO

Public post-mortem / on-chain analysis for the – sDAO incident: view source.

FAQ

How much did – sDAO lose?

The – sDAO exploit in November 2022 resulted in $13,000 in losses — the 44th largest of 129 DeFi incidents that year.

When did the – sDAO hack happen?

The – sDAO exploit was recorded on November 21, 2022 — 1,240 days ago.

What type of exploit hit – sDAO?

The – sDAO incident is classified as a Business Logic Flaw. A business-logic bug in the contract — such as an incorrect formula or missing state update — lets the attacker withdraw more than their share.

How common is the Business Logic Flaw pattern seen at – sDAO?

Our archive contains 144 documented business logic flaw incidents. The – sDAO incident is one of them.

How does – sDAO compare to the largest Business Logic Flaw attack?

The largest business logic flaw incident in our archive is – EulerFinance (2023) at $200M. The – sDAO loss is $13K.

What is the significance of the 'Lachesis' consensus algorithm in Fantom's performance?

Lachesis enables faster consensus without the energy-intensive processes typical of PoW or round-based PoS schemes.

How do cryptocurrency forks compare to corporate spin-offs?

Similar to corporate spin-offs, cryptocurrency forks can potentially create wealth by allowing assets to be more precisely valued based on specific features or community preferences.