What happened.
Fogo, a layer-1 network, halted its mainnet after an attacker reportedly received 400M FOGO. The supplied record describes the amount as about 10% of circulating supply, roughly 4% of genesis supply, and about $3M at the time. This is a network-integrity incident on a fresh network.
Why it matters.
A forced mainnet halt is a high-severity event because it shifts attention from normal network operation to the conditions for a restart and any remediation. The record places the event alongside other recent security and transparency stress across protocols, exchanges, and apps, rather than treating it as an isolated venue-specific issue.
What to watch next.
The next useful receipt is Fogo’s restart terms and its remediation and disclosure. Those details would clarify how the network addresses the reported transfer and what safeguards or process changes, if any, follow. The supplied record also flags MANTRA/Cosmos remediation and disclosure as a related cross-chain and validator-level risk to monitor.
Watch for Fogo’s published restart terms, remediation, and disclosure.
Upstream references and independent checks
Digest dated 2026-08-30 · upstream model claude-sonnet-4-6. Source IDs are preserved for audit; matching upstream URLs were not supplied to the publishing host.
- 1
fb258c905970a1126126f1167519f635c26ded37Upstream 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 brief relies on a single supplied source record with medium confidence; the record does not provide underlying technical details, restart terms, or independent confirmation beyond the reported incident.