BIP-50 migrates Beanstalk to Arbitrum — Stablecoin Event

Identity and classification

Overview

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

Date	2024-10-01
Public event category	Migration and rebrand
Canonical event subtype	Migration
Structured detail kind	Migration
Stablecoin subjects	Bean
Organization subjects	Beanstalk
Impact	High
Effect on stablecoin lifecycle	Remained active
Canonical status-effect value	Active Version Transition
Recovery or reversal	Not applicable
Recovery date	Not Applicable
Cause or mechanism	BIP-50 moved Beanstalk balances and the current Bean token lineage from Ethereum to Arbitrum One.
Structured detail coverage	Structured fields available below
Record confidence	High

Date: 2024-10-01
Public category: Migration and rebrand
Canonical subtype: Migration
Structured detail kind: Migration
Impact: High
Status effect: Remained active
Recovery: Not applicable
Recovery date: Not yet recorded
Cause or mechanism: BIP-50 moved Beanstalk balances and the current Bean token lineage from Ethereum to Arbitrum One.
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

Migration detail — Summary	BIP-50 moved Beanstalk balances and the current Bean token lineage from Ethereum to Arbitrum One.
Migration detail — Status	Implemented Same Identity New Chain
Migration detail — Resolution date	2024-10-01
Migration detail — Affected deployments	sog_dep_bean_ethereum_batch_r, sog_dep_bean_arbitrum_batch_r
Migration detail — Related organizations	sog_issuer_beanstalk

Migration detail — Summary: BIP-50 moved Beanstalk balances and the current Bean token lineage from Ethereum to Arbitrum One.
Migration detail — Status: Implemented Same Identity New Chain
Migration detail — Resolution date: 2024-10-01
Migration detail — Affected deployments: sog_dep_bean_ethereum_batch_r, sog_dep_bean_arbitrum_batch_r
Migration detail — Related organizations: sog_issuer_beanstalk

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
Migrate Beanstalk balances to Arbitrum Published Not yet recorded	Beanstalk	Official documentation or product page Canonical: Official Documentation	Subject-controlled source	Primary source	Migration, Current Chain, Balance Transition, Token Lineage, Bip50 Ethereum to Arbitrum Migration	Archive index or wildcard	High
BIP-50 migration runbook Published 2024-10-01	Beanstalk Community	Official documentation or product page Canonical: Official Documentation	Subject-controlled source	Primary source	Migration Date, Execution, Contract Lineage, Current Chain, Bip50 Execution Date and Arbitrum Migration	Archive index or wildcard	High

Maintenance

Use the documented correction path and methodology.