Bridge entity
Ren Protocol
Ren Protocol operated RenVM and RenBridge as cross-chain infrastructure for native assets including Bitcoin. The reviewed Ren 1.0 lineage ended after Alameda-related funding stopped in late 2022, while Ren 2.0 remained announced but not verified as a public mainnet successor.
deprecatedreviewedcurrent
Bridge facts
- Canonical name
- Ren Protocol
- Type
- Interoperability Protocol
- Status
- Deprecated
- Confidence
- High
- Primary chains
- Bitcoin, Ethereum, BNB Chain, Polygon, Avalanche, Solana, Unknown
- Primary assets
- renBTC, BTC, Unknown
- Operator
- Ren Foundation and Ren community
- Ecosystem
- Ren
- Launch date
- 2020-05-27
- End date
- 2022-12
- Terminal reason
- Ren 1.0 entered a planned sunset after Alameda-related funding ended; the reviewed current site still describes Ren 2.0 as coming soon.
- Last reviewed
- 2026-06-18
- Last verified
- 2026-06-18
Incident cases
No linked incident cases.
Incident records will appear here after canonical JSON data is merged.
Evidence records
- RenVM Mainnet ReleaseRen Protocol · Tier 1 · 2020-05-27
- Introducing RenBridge 3.0Ren Protocol · Tier 1 · 2022-06-08
- Introducing Ren 2.0Ren Protocol · Tier 1 · 2022-08-10
- Moving on from AlamedaRen Protocol · Tier 1 · 2022-11-18
- Moving on from Alameda - Ren 1.0 transition detailsRen Protocol · Tier 1 · 2022-11-18
- Ren FoundationRen Foundation · Tier 1 · 2026-06-18
- renproject GitHub organizationRen project · Tier 1 · 2026-06-18
Official URL status
Official URL recorded as live: https://renprotocol.org/Independent incident archive
Help maintain bridge history
Support incident linkage, lifecycle updates, evidence preservation, broken-link replacement, and corrections.
Record maintenance
Report a correction
Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.