Governance exploit pauses Beanstalk — Stablecoin Event

Identity and classification

Overview

Date, taxonomy, impact, recovery, mechanism, confidence, and evidence remain separate.

Date	2022-04-17
Public event category	Security and chain incident
Canonical event subtype	Protocol Exploit
Structured detail kind	Security Incident
Stablecoin subjects	Bean
Organization subjects	Beanstalk
Impact	Critical
Effect on stablecoin lifecycle	Restricted or impaired
Canonical status-effect value	Impaired Context
Recovery or reversal	Not applicable
Recovery date	Not Applicable
Cause or mechanism	A governance exploit caused major non-Bean asset losses and paused Beanstalk.
Structured detail coverage	Structured fields available below
Record confidence	High

Date: 2022-04-17
Public category: Security and chain incident
Canonical subtype: Protocol Exploit
Structured detail kind: Security Incident
Impact: Critical
Status effect: Restricted or impaired
Recovery: Not applicable
Recovery date: Not yet recorded
Cause or mechanism: A governance exploit caused major non-Bean asset losses and paused Beanstalk.
Record confidence: High

Affected records

Stablecoin and organization subjects remain separate record groups.

Stablecoin subject

Open the stablecoin dossier for current state, organizations, deployments, evidence, and unknowns.

Organization subject

Open the organization record for roles, relationships, events, evidence, and unknowns.

Typed record

Event-type-specific facts remain visible with explicit value states.

Structured event detail

Security-incident detail — Summary	A governance exploit caused major non-Bean asset losses and paused Beanstalk.
Security-incident detail — Status	Recovered After Replant
Security-incident detail — Loss or exposure	Official Beanstalk documentation describes approximately 77 million dollars in non-Bean assets affected. (approximate)
Security-incident detail — Resolution date	2022-08-06

Security-incident detail — Summary: A governance exploit caused major non-Bean asset losses and paused Beanstalk.
Security-incident detail — Status: Recovered After Replant
Security-incident detail — Loss or exposure: Official Beanstalk documentation describes approximately 77 million dollars in non-Bean assets affected. (approximate)
Security-incident detail — Resolution date: 2022-08-06

Provenance

Source identity, publisher, publication date, reliability, archive, and relation count remain separate.

3 source identities · 3 evidence relations
Source	Publisher	Source category	Provenance	Primary or secondary	Supported claims	Archive	Reliability
Beanstalk disclosures Published Not yet recorded	Beanstalk	Official documentation or product page Canonical: Official Documentation	Subject-controlled source	Primary source	Launch Date, Security Incident, Governance, Token Lineage, Current Chain, Launch Exploit Governance and Token Lineage	Archive index or wildcard	High
Beanstalk Barn and Replant timeline Published Not yet recorded	Beanstalk	Official documentation or product page Canonical: Official Documentation	Subject-controlled source	Primary source	Security Incident, Pause, Recapitalization, Relaunch, Exploit Pause Barn Raise Replant and Recapitalization	Archive index or wildcard	High
Beanstalk governance Published Not yet recorded	Beanstalk	Official documentation or product page Canonical: Official Documentation	Subject-controlled source	Primary source	Governance, Control, Pause, Upgrade, Post Exploit Governance and Pause Control	Archive index or wildcard	High

Maintenance

Use the documented correction path and methodology.