What happened
The supplied record reports that two Ethereum bridges suffered combined losses of about $31.69 million. It also says B² suspended staking on July 22, placing three separate control failures within the same recent exploit wave.
The record does not establish that the bridge losses and the staking suspension share a cause. It presents them as distinct events with a common security relevance.
Why it matters
Bridges and staking systems can concentrate operational and security risk. A fresh set of reported losses alongside a staking halt keeps attention on how controls perform when systems face an incident or need to limit activity.
The related monitoring note also flags social engineering as a rising breach vector and notes Binance’s monthly staff red-teaming. That context supports continued monitoring of bridge and staking security, but it does not provide evidence that social engineering caused these reported events.
What to watch next
Watch for primary incident reports, technical explanations of the bridge losses, confirmation of the affected controls, and any recovery or remediation details. For B², the key receipt is a clear explanation of the staking suspension and any conditions for resumption.
Primary incident disclosures, technical postmortems, remediation steps, and a B² update on staking resumption.
Upstream references and independent checks
Digest dated 2026-07-26 · upstream model claude-sonnet-4-6. Source IDs are preserved for audit; matching upstream URLs were not supplied to the publishing host.
- 1
632d373afb842984ed5adabed9b2f3f1514e122dUpstream reference; direct URL unavailable.
This Research brief was generated by Terra from a dated upstream research digest. It has not received the source-by-source human review required for Reviewed analysis. Material limit: This is a medium-confidence, single-sourced record; it provides no primary incident documents, technical detail, or independent corroboration of the reported losses or the staking halt.