Cabal Desk
Search
Incidents No. 000198

SKYDAO Discovers Expensive Difference Between 'Smart' Chain & Actual Smart

The figure is $183K on BNB Chain. The listing is the whole record.

Illustration: SKYDAO Discovers Expensive Difference Between 'Smart' Chain & Actual Smart

SKYDAO lost $183,000 on BNB Smart Chain on September 30, 2026, the date on the record[1][2][3]. The page files the method as a swap logic flaw[4].

The target is a DeFi protocol, and its code is written in Solidity[5][6]. That figure stands alone, with no attacker wallet and no transaction hash named[2][3]. A holder has nothing to check against the approval list on BNB Smart Chain[3].

What to do: the record names no contract, no pool and no approval[4]. Nothing can be revoked on its word alone[4].

Who gains, who loses

$183K recorded on BNB Smart Chain SKYDAO holders and anyone in the pair carry the loss; no attacker wallet is named on the record
Filed as a swap logic flaw in a Solidity DeFi protocol the faulty pricing sits in the swap, not in a key or a signature, so no approval is the named entry point

Receipts

[1]

The SKYDAO incident was recorded as occurring on September 30, 2026.

“DeFiLlama records the SKYDAO incident on September 30, 2026.”

[2]

The reported loss in the SKYDAO incident was $183K.

“The reported loss is $183K.”

[3]

The affected chain was BNB Smart Chain, identified on the report as BSC.

“The listed chains are bsc.”

[4]

The incident was classified as a swap logic flaw.

“DeFiLlama labels the technique as Swap Logic Flaw.”

[5]

The affected system was classified as a DeFi protocol.

“Protocol Type DeFi Protocol”

[6]

The protocol was implemented in Solidity.

“Implementation language Solidity”

Cabal Desk is reporting, written with AI under human oversight. Every bracketed number opens its receipt: the source, the quoted span, the hash. Headlines and characterisations are commentary; the sourced facts are the receipts. Not investment advice. Corrections log. Editorial & legal.