Eleven Signatures. $320 Million Gone.

Nearly every bitcoin in Liquid’s federation wallet left through a peg-out the network says was unauthorised. The party controlling 3,998.5 BTC calls itself “whitehats”. The funds have not been returned, the root cause has not been disclosed, and Liquid remains effectively paused.

7 September 2026 | Developing story

What has been confirmed

On 6 September, Liquid acknowledged a security incident involving roughly 4,000 BTC, valued at about $320 million. Its official status page says exchanges were told to suspend LBTC deposits and withdrawals, public bridge nodes were disabled and no new transactions could be submitted. In Liquid’s own words, the sidechain is “effectively paused”.

The same statement contains the most important unresolved contradiction: the withdrawal used the SideSwap Peg-out Authorization Key, or PAK, but Liquid says that key was not compromised. No root cause has yet been published.

This was not a hack of Bitcoin. Bitcoin processed a valid transaction signed by the keys controlling Liquid’s federation wallet. The failure occurred in the system that decided this peg-out should be signed.

What the chain actually shows

The figures circulating online refer to different stages of the same path.

At 14:06 UTC, Liquid transaction ce4cae…e988f2 was confirmed with six confidential inputs and an explicit peg-out of 3,996.01834922 LBTC.

Twenty-two minutes later, Bitcoin transaction 8db751…a7b140 paid exactly 3,996.01834922 BTC from the federation wallet to an intermediate address. That output was immediately forwarded, less fees, to another address.

The controller then combined it with approximately 2.4975 BTC from an earlier linked payment. The resulting transaction c103de…e69a19 created one output of 3,998.49748445 BTC and embedded the message:

“we are whitehats. contact us on chain”

That is why some reports say 3,996 BTC, others say 3,998.5 BTC and Liquid rounds the incident to 4,000 BTC. The abnormal federation payout was 3,996.01834922 BTC. The self-declared whitehat address consolidated 3,998.49748445 BTC.

At publication, the core 3,998.5 BTC output remained unspent at the holding address. It has since received dust and unsolicited messages, which should not be mistaken for movement by the holder.

The withdrawal was signed, not forced

Liquid’s technical documentation says federation watchmen secure the bitcoin backing LBTC and require a greater-than-two-thirds threshold to spend it. The abnormal Bitcoin transaction used 83 federation-wallet inputs. Each input’s witness contains eleven signatures plus the federation spending script.

In plain English, one stolen key did not empty the wallet. The federation’s signing threshold approved the mainchain transaction because the peg-out had already passed the checks presented to it.

Those checks are supposed to include a second barrier. Under Liquid’s published peg-out design, LBTC is burned on the sidechain and the corresponding BTC can only be sent to an address authorised by a registered PAK. Liquid says the SideSwap PAK route was used, while also saying neither that key nor any other key was compromised.

That leaves two broad possibilities. Either the system accepted false data as a valid authorised peg-out, or a legitimate authorised route was induced to process value it should never have processed. Liquid has not yet disclosed which control failed.

Claims that an Elements or LBTC “inflation bug” created unbacked coins are already being repeated as fact. They may prove correct, but the public evidence does not yet establish that conclusion. The visible Liquid transaction contains an explicit 3,996 BTC peg-out, but its six inputs are confidential. An explorer cannot reveal their asset types or values, and there is no official post-mortem, patch or reproducible explanation yet.

“Whitehat” is a claim, not a status

There are reasons not to assume an immediate theft. The coins have remained together, they have not been mixed or sent to exchanges, and the holder openly invited contact on-chain.

There are also reasons not to grant the label too quickly. The withdrawal was not publicly authorised, approximately 95% of the reported reserve was placed under outside control, the actors remain unidentified and not one of the core 3,998.5 BTC has yet been returned. Until the holder reaches an agreement and returns control of the funds, “whitehat” describes only what the holder called itself.

Blockstream has now broadcast a more serious on-chain response than the first public email request. A new transaction to the holding address carries an encrypted message addressed to the key behind that Bitcoin address, together with a detached PGP signature.

The Nexus independently checked that signature against the security key currently published on Blockstream’s own domain. It verifies correctly. That authenticates the encrypted ciphertext as a Blockstream security message. It does not reveal the private contents, prove the holder’s identity or show that a return agreement exists.

What the pause reveals

Liquid’s statement says USDT, DePix and tokenised real-world assets were not involved in the withdrawal. That is narrower than saying their users are unaffected. If bridge nodes are disabled and the sidechain cannot accept new transactions, every wallet and asset on it faces an availability problem.

The incident also exposes Liquid’s actual trust boundary. LBTC is marketed as bitcoin backed one-for-one on the mainchain, but ordinary users cannot independently redeem it. Liquid’s own peg-out guidance says direct peg-outs are restricted to federation members. Users therefore depend on the federation to preserve the collateral, validate withdrawals and keep the network operating.

Speed and confidentiality do not remove that dependency. They move it into a federation, a whitelist and an automated signing system. On 6 September, that control structure approved an unauthorised withdrawal and then stopped the network around it.

What Liquid must answer before restarting

• What was the exact root cause, and which Elements or Liquid versions were affected?
• How was the SideSwap PAK route used if the key itself was not compromised?
• Were unbacked LBTC created? If not, whose valid LBTC funded the burn?
• Why did the watchmen’s validation system approve the peg-out and produce the required eleven signatures?
• What is the precise collateral position for legitimate LBTC holders now?
• Will recovery require a rollback, balance correction, capital injection or negotiated return of the bitcoin?
• Who authorised the pause, and what verifiable conditions must be met before transactions resume?
• Will Blockstream and the federation publish a complete technical post-mortem and an independently reviewable fix?

The Nexus verdict

This is a genuine and severe Liquid security failure. It is not merely a suspicious wallet movement, but it is also not evidence that Bitcoin itself was broken. Bitcoin enforced the federation’s signatures exactly as designed.

The unresolved failure sits inside Liquid’s peg and authorisation path. A transaction the operators say was unauthorised passed the sidechain’s checks, reached the federation’s signing threshold and removed almost all of the wallet’s reported bitcoin reserve. The network then had to be stopped.

The fact that the funds remain visible and apparently untouched leaves room for a whitehat resolution. It does not erase the failure. Even if every satoshi is returned, Liquid still has to explain how its safeguards authorised the withdrawal, prove the remaining LBTC is fully backed and show why the same path cannot be used again.

---

Veritya Thalassa

Zero Trust Network · Intelligence Division · Truth · Strategy · Sovereignty