Stablecoin dossierReturn to register
Record sog_st_bean
BEAN/Bean
Also recorded as BEAN, Beanstalk Bean
- Lifecycle
- Active
- Issuance
- Protocol-based
- Reference target
- US dollar
- Primary organization
- BeanstalkNo additional recorded relationship
- Launch
- 2021-08-06
- Redemption
- Protocol Based
- Backing
- Algorithmic or unbacked
- Stabilization
- Algorithmic supply
- Last review
- 2026-06-29
- Evidence
- 6 source records
Reviewed assessment
Identity and current state
This summary reports reviewed facts and uncertainty. It is not a rating or recommendation.Beanstalk protocol stablecoin first deployed in August 2021, paused after the April 2022 governance exploit, replanted in August 2022, and later migrated from Ethereum to Arbitrum while remaining an active protocol identity.
| Name | Bean |
|---|---|
| Symbol | BEAN |
| Aliases | BEAN, Beanstalk Bean |
| Asset class | Stablecoin |
| Lifecycle status | Active |
| Issuance status | Protocol-based |
| Canonical record ID | sog_st_bean |
| Route slug | beanstalk-bean |
| Record confidence | High |
| Last reviewed | 2026-06-29 |
- Name
- Bean
- Symbol
- BEAN
- Aliases
- BEAN, Beanstalk Bean
- Asset class
- Stablecoin
- Lifecycle status
- Active
- Issuance status
- Protocol-based
- Canonical record ID
sog_st_bean- Route slug
beanstalk-bean- Record confidence
- High
- Last reviewed
- 2026-06-29
Record coverage
| Section | Entries |
|---|---|
| Organizations | 1 |
| Sources | 6 |
| Reserve reports | 1 |
| Reserve components | 1 |
| Model-history events | 2 |
| Regulatory notes | 0 |
| Deployments | 2 |
| Issuer-control actions | 0 |
| Open questions | 5 |
| Events | 4 |
Primary display is a navigation and summary choice only. It does not replace other organizations or imply sole legal responsibility, operational control, reserve custody, or historical continuity.
- Governance
- DAO Governed
- Primary display organization
- Beanstalk
- Primary display role
- Protocol operator
- Display selection mode
- Deterministic Policy
- Current relationships
- 1
- Ended relationships
- 0
- Unknown relationship state
- 0
- Freeze capability
- 0 recorded yes · 0 recorded no · 2 not recorded
- Blacklist capability
- 0 recorded yes · 0 recorded no · 2 not recorded
- Deployment control-event references
- 0
- Observed issuer-control events
- 0
- Relationship coverage
- 1 recorded relationship
| Organization | Organization category | Regulatory character | Jurisdiction | Role | Display priority | From | Until | Relationship status |
|---|---|---|---|---|---|---|---|---|
| Beanstalk | Protocol or software system | Protocol or decentralized system | Decentralized / protocol governance | Protocol operator | Primary display | 2021-08-06 | Not yet recorded | Active relationship |
Protocol or software system
Primary displayBeanstalk
- Functional role
- Protocol operator
- Relationship status
- Active relationship
- Regulatory character
- Protocol or decentralized system
- Jurisdiction
- Decentralized / protocol governance
- From
- 2021-08-06
- Until
- Not recorded
Mechanism
How the asset works
Reference, backing, stabilization, exit, valuation, and yield remain separate facts.- Reference target
- US dollar
- Reference kind
- Fiat
- Comparison category
- US dollar
- Target value
- Not yet recorded
- Reference methodology
- Bean targets one U.S. dollar through decentralized credit, supply, liquidity, and incentive mechanics.
- Public backing model
- Algorithmic or unbacked
- Canonical backing types
- Unbacked
- Reserve component categories
- Other
- Primary stabilization mechanism
- Algorithmic supply
- Recorded model description
- Credit Based Algorithmic Protocol
- Redemption / exit model
- Protocol Based
- Valuation source
- Public information is incomplete
- Yield / rebase profile
- None recorded
- Classification notes
- Active credit-based algorithmic stablecoin on Arbitrum with no conventional reserve backing.
Reserve and redemption
Reserve and redemption
Recorded components, disclosures, reports, and redemption conditions remain explicit.Reserve components
- No conventional reserve asset; credit and incentive mechanismOther · Component row documents the non-reserve design rather than asserting collateral.
| Disclosure status | No Traditional Reserve By Design |
|---|---|
| Backing types | Unbacked |
| Summary | Bean uses credit, supply, liquidity, and incentive mechanics rather than conventional reserve assets. |
| As of | 2026-06-29 |
| Profile confidence | High |
- Disclosure status
- No Traditional Reserve By Design
- Backing types
- Unbacked
- Summary
- Bean uses credit, supply, liquidity, and incentive mechanics rather than conventional reserve assets.
- As of
- 2026-06-29
- Profile confidence
- High
| Current status | Protocol Based |
|---|---|
| Settlement asset | Market liquidity and protocol functions; no direct fiat issuer claim |
| Eligible parties | Public protocol users and market participants using supported interfaces. |
| Retail access | Public Protocol or Market Based |
| Institutional access | Public Protocol or Market Based |
| Minimum amount | Protocol and market transaction dependent. |
| Fee | Market, protocol, and network costs may apply. |
| Settlement time | Arbitrum transaction, protocol state, and liquidity dependent. |
| Regional limits | Application, wallet, network, governance, and applicable restrictions may apply. |
- Current status
- Protocol Based
- Settlement asset
- Market liquidity and protocol functions; no direct fiat issuer claim
- Eligible parties
- Public protocol users and market participants using supported interfaces.
- Retail access
- Public Protocol or Market Based
- Institutional access
- Public Protocol or Market Based
- Minimum amount
- Protocol and market transaction dependent.
- Fee
- Market, protocol, and network costs may apply.
- Settlement time
- Arbitrum transaction, protocol state, and liquidity dependent.
- Regional limits
- Application, wallet, network, governance, and applicable restrictions may apply.
| Date | Publisher | Type | Assets covered | Record confidence |
|---|---|---|---|---|
| Not yet recorded | Beanstalk | Protocol Design Context | Other | High |
Beanstalk
Not yet recorded- Type
- Protocol Design Context
- Assets covered
- Other
- Record confidence
- High
Deployments and legal context
Deployments and legal context
Network state, contract identity, legal notices, and value states remain separate.| Network | Network record state | Standard | Public deployment category | Canonical deployment type | Operational state | Recorded status | Change or proposal state | Canonicality | Canonicality record state | Verification state | Contract identity state | Contract or identifier | Freeze | Blacklist | Control events | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Ethereum | Specific network recorded | ERC-20 | Historical or legacy deployment | Historical Protocol Native Token | Terminated | Terminated | No separate change state recorded | Legacy deployment | Canonicality recorded | Source-linked record; identifier not recorded | Identifier not recorded | Identifier not recorded | Not yet recorded | Not yet recorded | 0 | Historical Ethereum Bean lineage, including the replanted token, was superseded by the BIP-50 Arbitrum migration. |
| Arbitrum One | Specific network recorded | ERC-20 | Protocol-native or protocol-supported deployment | Protocol Native Token | Active | Active | No separate change state recorded | Native deployment | Canonicality recorded | Source-linked record; identifier not recorded | Identifier not recorded | Identifier not recorded | Not yet recorded | Not yet recorded | 0 | Current Bean identity on Arbitrum after BIP-50; exact contract inventory is retained as an open item. |
| Date | Title | Authority / publisher | Type | Summary |
|---|---|---|---|---|
| No regulatory notes have been added yet. | ||||
No regulatory notes have been added yet.
Evidence
Evidence
Publisher, provenance, supported claims, archive state, reliability, and publication date remain separate.| 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 |
| How Beanstalk works Published Not yet recorded | Beanstalk | Official documentation or product page Canonical: Official Documentation | Subject-controlled source | Primary source | Stabilization, Credit Mechanics, Supply, Liquidity, Recapitalization, Credit Supply Demand and Stabilization Mechanics | 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 |
| 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 |
Known unknowns
Known unknowns and coverage
Missing or disputed facts remain visible instead of being converted into certainty.| Topic | What remains unclear | Value state | Priority | Last checked |
|---|---|---|---|---|
| Current Recapitalization State | The current Fertilizer, Unripe asset, recapitalization, and remaining liability state is not fully normalized. | Unknown after review | High | 2026-06-29 |
| Complete Ethereum and Arbitrum Contract Lineage | The complete old Bean, replanted Bean, BIP-50 migration, and current Arbitrum contract inventory remains incomplete. | Unknown after review | High | 2026-06-29 |
| Current Governance and Multisig Boundary | The current DAO, community multisig, emergency pause, upgrade, and future governance-removal boundaries remain under review. | Unknown after review | Medium | 2026-06-29 |
| Current Supply Liquidity and Peg Depth | Current Bean supply, liquidity distribution, peg depth, and market-support state remain unresolved. | Unknown after review | Medium | 2026-06-29 |
| Residual Ethereum Balances and Migration Completion | Residual Ethereum balances, manual migration completion, obsolete-token holdings, and contract-account exceptions remain incomplete. | Unknown after review | Medium | 2026-06-29 |
Current Recapitalization State
The current Fertilizer, Unripe asset, recapitalization, and remaining liability state is not fully normalized.
- Value state
- Unknown after review
- Priority
- High
- Last checked
- 2026-06-29
Complete Ethereum and Arbitrum Contract Lineage
The complete old Bean, replanted Bean, BIP-50 migration, and current Arbitrum contract inventory remains incomplete.
- Value state
- Unknown after review
- Priority
- High
- Last checked
- 2026-06-29
Current Governance and Multisig Boundary
The current DAO, community multisig, emergency pause, upgrade, and future governance-removal boundaries remain under review.
- Value state
- Unknown after review
- Priority
- Medium
- Last checked
- 2026-06-29
Current Supply Liquidity and Peg Depth
Current Bean supply, liquidity distribution, peg depth, and market-support state remain unresolved.
- Value state
- Unknown after review
- Priority
- Medium
- Last checked
- 2026-06-29
Residual Ethereum Balances and Migration Completion
Residual Ethereum balances, manual migration completion, obsolete-token holdings, and contract-account exceptions remain incomplete.
- Value state
- Unknown after review
- Priority
- Medium
- Last checked
- 2026-06-29
Lifecycle
History
Current classification remains separate from dated changes and incidents.Model and lifecycle changes
- Beanstalk Replant restores operationGovernance Change
- BIP-50 migrates Beanstalk to ArbitrumMigration
| Date | Event | Category | Subtype | Status effect | Recovery |
|---|---|---|---|---|---|
| 2021-08-06 | Beanstalk deploys Bean | Launch and introduction | Launch | Remained active | Not applicable |
| 2022-04-17 | Governance exploit pauses Beanstalk | Security and chain incident | Protocol Exploit | Restricted or impaired | Not applicable |
| 2022-08-06 | Beanstalk Replant restores operation | Governance and protocol change | Protocol Upgrade | Remained active | Not applicable |
| 2024-10-01 | BIP-50 migrates Beanstalk to Arbitrum | Migration and rebrand | Migration | Remained active | Not applicable |
Related records and corrections
Corrections and further reading
Open connected records, methodology, machine-readable data, or report a correction.- All stablecoinsCompare this record with the rest of the archive.
- BeanstalkDecentralized / protocol governance
- Event registry4 connected events recorded.
- MethodologyRead classification, evidence, and value-state rules.
- CorrectionsReport a source, relationship, or record problem.
- Data manifestInspect the machine-readable public layer.