Thursday, September 17, 2026

Latest Posts

Splash patch leaves OADA liquidity problem unresolved

Three days after Splash’s Cardano-based ADA/OADA StableSwap pool was drained, OADA holders still faced a problem that corrected code alone could not solve: the pool had lost the ADA that provided their meaningful route out of the token.

Splash’s incident report said one actor used two transactions on Sept. 13 to remove 2,434,648 ADA and 1,988,222 OADA. After subtracting the attacker’s 9,870 ADA deposit, but before network fees, the ADA drain was 2,424,778.

Related Reading

515M NIGHT bridge exploit rocks Cardano but ADA jumps 8% anyway after landmark hard fork

Why a code patch is not a liquidity fix

The pool’s validator calculated a “tradable” reserve by subtracting accrued protocol fees from its real balances. According to Splash, it did not require that reserve to remain positive, bounded fee changes only from below and did not enforce the direction of a swap.

Read More:  Bitcoin futures carry tops Treasury yield in matched CME check

Those missing checks allowed the validator to accept a transaction after the tradable ADA reserve had turned negative. Splash said a reserve-domain check or a two-sided fee bound would have stopped the reconstructed attack.

Either fix would close the documented exploit path. Neither would return the ADA that had already left the pool. Immediately after the drain, the pool held 10 ADA and about 1.44 million OADA, while its tradable ADA reserve was negative and its LP token balance was unchanged.

The balance-sheet damage matters because Splash’s Sept. 13 snapshot said OADA had no protocol-level redemption. Other OADA venues in the report were close to empty at that time, with the listed pools holding only single- or double-digit ADA balances.