Blockstream bets 600 Bitcoin by rejecting Liquid hacker’s $50 million bounty demand

Blockstream is refusing to pay the Liquid attacker nearly 600 Bitcoin (roughly $50 million), escalating a dispute over how the crypto industry should reward partial restitution.

The standoff follows an unusual recovery from the Sept. 6 exploit, when a vulnerability allowed the attacker to create about 4,000 unbacked L-BTC and withdraw roughly 3,996 real BTC through SideSwap.

The attacker returned 3,400 BTC after Blockstream patched affected nodes, then demanded a 10% bounty paid from Blockstream’s own funds and warned that holders could otherwise bear a roughly 15% shortfall.

On Sept. 11, Blockstream rejected the demand and said it would pursue the remaining funds through law enforcement, exchanges, service providers, and forensic specialists if they are not voluntarily returned.

The decision has opened a broader argument over whether refusing to compensate an attacker who returned about 85% of the haul strengthens deterrence or gives the next hacker less reason to return anything.

Blockstream's rare recovery turns into a fight over incentives

The return of 3,400 BTC shifted the fight from recovering stolen funds to defining what cooperation after an exploit is worth.

Lorenzo Romagnoli, co-founder of USDT0, said Blockstream had already received an outcome that most hacked crypto protocols could only hope for. He argued that an attacker linked to North Korea or another committed criminal group would have little incentive to voluntarily send back hundreds of millions of dollars.

Romagnoli said:

“Blockstream is already in the 1% of the 1% of luckiest hacked protocols on the planet.”

He said Blockstream retains every right to identify and prosecute the attacker, but warned that refusing a substantial bounty could change future hackers' calculations. A grey-hat attacker weighing whether to return stolen funds may see little upside in cooperation if restitution brings the same pursuit as keeping the entire haul.

That argument collides with Blockstream’s concern that paying would create a different incentive: allowing an attacker to exploit open-source infrastructure, seize user assets and then establish the price for returning them.

Blockstream said it would not establish a precedent in which developers of open-source software could be forced to pay a demand that “far exceeds their economic participation.” It also rejected the attacker’s white-hat characterization and urged the party to “return the Bitcoin.”

Samson Mow, a former Blockstream chief strategy officer and chief executive of Bitcoin company Jan3, also challenged the economics behind the attacker’s demand.

The attacker had criticized Blockstream for allegedly spending too little to protect roughly $5 billion in assets issued across Liquid. Mow said that figure combines L-BTC, Tether, and real-world assets that belong to different issuers and holders, making the network’s total asset value an inappropriate basis for determining a bounty.

He said:

“Bounty amounts cannot be calculated based on the network’s overall total value. Regardless of how the rest is negotiated, all users’ assets must be returned in full.”

The circumstances preceding the withdrawal have also complicated the attacker’s white-hat claim. SideSwap said the party spent hours rehearsing the transaction pattern before creating the unbacked L-BTC, with 70 similar transactions preceding the successful mint.

The wallet used to initiate the attack had received funding that traced through a cross-chain bridge to Tornado Cash. In view of this, SideSwap called the event a “deliberate and prepared attack,” while adding that:

“We stand with Blockstream. The bitcoin left the Liquid reserve through our peg-out service and we have given Blockstream everything we have to help trace and recover it. Our fee on it is already returned. Return the Bitcoin.”

The last 600 BTC may be more useful unspent

With the bounty rejected, the remaining 598.5 BTC can continue putting pressure on Liquid even if the coins never move.

Bitcoin researcher Alex Waltz questioned whether the attacker genuinely expects to spend the coins. According to him, the wallet is closely watched, and moving the BTC through exchanges, custodians, or other identifiable services could provide investigators with additional leads.

That creates another possible motive for keeping the funds.

Waltz said the attacker effectively faced two choices after returning most of the haul: return everything and hope Blockstream provides a generous reward, or retain a portion that may be difficult to spend but can continue inflicting an economic cost on Liquid.

He added:

“If the hackers are somewhat well off, and had a good reason to hate Blockstream/Liquid, it seems the only way they can ‘monetize’ this situation is to keep the 600 BTC.”

He also raised the possibility that investigators could eventually obtain clues from artificial intelligence services used by the attacker if models were accessed through identifiable API accounts, though no evidence has emerged publicly showing that such services were used.

The economic pressure is already visible on Liquid.

SideSwap said on Sept. 10 that 4,205 L-BTC remained in circulation while the federation reserve held 3,597 BTC, leaving about 85% reserve coverage after the returned bitcoin was added back. Liquid has resumed producing blocks and SideSwap markets have reopened, but peg-ins and peg-outs remain disabled while the federation completes its security review.

Blockstream Chief Executive Adam Back said the L-BTC-to-BTC peg will ultimately be covered one-for-one and urged holders not to sell at a discount. Blockstream has yet to detail how it will finance the roughly 600-BTC gap if the attacker refuses to return the funds, or when it will resume full redemptions.

Meanwhile, SideSwap has said it will keep its peg service offline until the federation introduces a new security architecture and will disclose the changes before reopening it. Blockstream’s alternative path now depends on tracing the remaining BTC and identifying whoever controls it.

Until either the coins return or the reserve hole is filled from elsewhere, Liquid’s markets can trade again while its core promise of converting L-BTC back into Bitcoin remains suspended.