Why Was RenBridge Discontinued: The Funding Link That Ended RenVM 1.0
Why was RenBridge discontinued? Alameda’s collapse with FTX cut RenVM’s funding, forcing the team to sunset version 1.0 and end redemptions for users.
By Crypto Docket Newsroom#3399b44 min read

After a transfer stopped being possible, the key answer was that RenBridge’s funder, Alameda Research, collapsed with FTX in November 2022, leaving the team without the money to keep RenVM 1.0 running. The service was wound down in December; the team’s announced plan for Ren 2.0 did not keep the old bridge open.
Why was RenBridge discontinued after Alameda and FTX collapsed?
RenBridge was discontinued because its operating funding depended on Alameda Research, which entered Chapter 11 with FTX in November 2022. The shutdown followed a funding crisis, not an announced bridge exploit.
Alameda had acquired Ren in February 2021. That tied the project’s finances and development to one corporate backer. When Alameda and FTX filed for bankruptcy protection, the money Ren relied on became inaccessible. The team said it lacked funding to continue operating the first version of its network.
The sequence matters: bankruptcy did not instantly make every bridge transfer fail. Instead, it removed the financial support behind continued maintenance. Ren announced a move toward Ren 2.0, but that future plan did not guarantee that assets created by the first version could move safely into the new system. So the team set a shutdown timetable and urged users to redeem their wrapped assets while the original network still worked.
RenBridge connected blockchains by locking an asset on its original chain and issuing a representation on another. RenVM coordinated the transfer using distributed nodes called Darknodes. That let users bring Bitcoin into DeFi as renBTC, a token usable in Ethereum-based applications.
Say you held Bitcoin and wanted to use it in a DeFi application that accepted renBTC. You sent BTC into the bridge’s process; RenVM’s nodes secured the underlying asset and enabled renBTC to be minted on the destination chain. You could then use that token in supported DeFi applications. To return to Bitcoin, you burned the renBTC, and the corresponding BTC was released on Bitcoin’s chain. The burn-and-release step is why keeping the old network operating mattered: without it, holders could be left with a token they could no longer redeem through the bridge.
For more background on the cross-chain service and what its shutdown meant for users, RenBridge context is available at renbridge.net. The central point is that the bridge’s distributed custody model could keep transfers from relying on one custodian, but it could not pay for its own maintenance when its corporate funder failed.
What happened to renBTC holders when the network shut down?
RenVM 1.0 users were asked to burn renBTC and bridge back to BTC before the December 2022 cutoff. After the deadline, redemption through that version ended, so a remaining renBTC balance could no longer count on the old network to release its underlying Bitcoin.
This was the practical cost of the shutdown. Before the cutoff, the route still had an operating network to process a burn and release BTC. After the cutoff, the connection between the wrapped token and the redemption process was gone. Ren 2.0 was a proposed successor, but compatibility with assets from version 1.0 was not assured; waiting for the successor was therefore not equivalent to redeeming in time.
The episode exposes a trade-off in bridge design. Distributed nodes can spread custody and transaction work across operators, reducing reliance on a single entity to hold and move assets. But the network still needs people and money to maintain its software, coordinate upgrades, and communicate changes. In this case, custody was distributed while funding and development depended on one company. That mismatch left users exposed to a corporate failure even without a bridge breach.
Other bridge designs may use different mixes of validators, custodians, and funding sources. The useful questions are who can authorize or process a redemption, who pays for ongoing development, and what happens to existing wrapped assets if the team stops operating. More decentralised custody alone does not answer those questions.
Related questions
What happened to REN token after the shutdown?
The shutdown ended the RenVM 1.0 bridge and its redemption route; it did not itself convert REN token holdings into Bitcoin or renBTC. The service’s closure and the value of a token traded on crypto markets are separate matters.
Was RenBridge hacked?
The shutdown was announced as a funding problem after Alameda’s collapse, not as a hack. The lesson is that a bridge can face a serious failure mode even when the trigger is outside its transaction security: distributed custody did not remove dependence on a single funder.