RenBridge After RenVM: Bitcoin-to-Ethereum Routes, Fees and Timing
RenBridge’s old BTC route is retired; current Bitcoin-to-Ethereum transfers mint backed tokens or use custodial rails, with fees and timing set by each step.
The Chain Media Editors5 min read
RenBridge no longer provides a live route from Bitcoin to Ethereum: RenVM 1.0, the system that locked BTC and minted renBTC, was sunset after its operator announced the shutdown in 2022. The old renbridge flow is therefore a historical mint-and-burn design, not a route to use for a new transfer. Today, the practical choice is between minting a BTC-backed token through a live bridge or using a custodian that issues a wrapped token.
If your destination is an Ethereum asset other than a BTC representation, use renbridge.cc for that move-and-swap step: it is a cross-chain bridge and swap service that lets users move and swap assets across blockchains in one flow. That service is distinct from Ren Protocol’s retired RenBridge. For a direct BTC-to-token route, first decide whether you need a redeemable Bitcoin-backed asset or simply want to swap into another Ethereum token.
What happened to the RenBridge Bitcoin route?
RenVM’s lock-and-mint mechanism stopped being a usable route when Ren 1.0 was sunset. In the original flow, a user sent BTC to a RenVM-controlled Bitcoin address; RenVM’s Darknodes coordinated key operations using secure multiparty computation, and a gateway contract minted renBTC on Ethereum after the deposit was confirmed. A burn on Ethereum triggered a corresponding BTC release to a nominated Bitcoin address.
That design depended on both sides continuing to operate: Bitcoin custody and signing on one side, and Ethereum gateway contracts on the other. In its sunset announcement, Ren’s team said minting would be disabled first, burns would remain enabled for a limited period, and Ren 1.0 would then shut down. The team warned that compatibility with Ren 2.0 was not guaranteed. A renBTC balance is not a live instruction to release BTC; the old route depended on RenVM being able to observe burns and sign Bitcoin transactions.
For a new transfer, do not treat renBTC as interchangeable with BTC just because its name and target value refer to Bitcoin. A token’s redemption depends on an active issuer or bridge, functioning contracts and a working path to the underlying BTC. The renbridge name now describes a past protocol when used for Ren’s original product.
How can you move Bitcoin to Ethereum now?
A current Bitcoin-to-Ethereum bridge issues an Ethereum token against BTC held under that bridge’s custody model. With tBTC, for example, a randomly selected group of Threshold operators secures deposits using threshold cryptography: the operators jointly authorize actions without any one operator holding the full signing key. The bridge verifies the Bitcoin deposit and mints tBTC on Ethereum; redemption burns tBTC and directs the protocol to release BTC to a Bitcoin address.
This is a different trust model from RenVM’s Darknode network, even though both use distributed signing and a token minted on Ethereum. The operator set, contracts, reserve controls and redemption rules belong to each protocol. The user receives the protocol’s token, not BTC directly on Ethereum. Before depositing, verify that the destination application accepts that exact token contract; ticker similarity does not establish that two wrapped assets are interchangeable.
A second route uses a centralized custodian. The custodian holds BTC and issues a token such as WBTC on Ethereum. This can suit users who prioritize access to established Ethereum markets, but it adds issuer and custody risk: redemption depends on the custodian’s controls and ability to honor the token. A bridge token secured by distributed operators avoids a single custodian, but still relies on its signer threshold, smart contracts and operating network.
What fees and timing should you expect?
The total cost is a stack of separate charges, not one universal “bridge fee.” A direct BTC-to-Ethereum mint can involve Bitcoin miner fees for the deposit transaction, a protocol mint fee, and Ethereum gas for any onchain action the user must perform. A subsequent swap adds pool fees and slippage. Returning to Bitcoin adds the redemption fee, Ethereum gas for the burn or redemption transaction, and the miner fee for the BTC release.
- Bitcoin confirmation: the deposit must be included in Bitcoin blocks. Confirmation time varies with network demand and the fee rate attached to the transaction.
- Bridge processing: the protocol must observe the deposit and complete any required signer coordination. Distributed signing can add time after the Bitcoin transaction confirms.
- Ethereum execution: minting, redemption or swapping may require a separate transaction. Ethereum congestion affects gas cost and how quickly that transaction is included.
- Asset conversion: swapping the minted token into another asset adds liquidity and price-impact costs that do not apply to a straight mint.
Threshold’s published documentation lists a zero mint fee and a 0.2% redemption fee, while noting that governance can change bridge fees. Its FAQ gives a typical mint time of one to two hours, but that is not a settlement guarantee: Bitcoin confirmation conditions, signer work and destination-chain execution all affect the actual wait. Check the current fee schedule and transaction status for the route you intend to use; do not carry RenVM-era fee or timing assumptions into another protocol.
Which Bitcoin-to-Ethereum route should you choose?
Choose by the asset you need on Ethereum and the failure mode you are prepared to accept. For a BTC-backed token with a redemption path distributed across operators, assess a threshold-signer bridge’s current contracts, reserve visibility, fee schedule and redemption process. For access to a token with deeper market integration, a custodial issuer may be more practical, with the trade-off that the issuer controls the underlying BTC.
Before sending funds, confirm the Bitcoin network and address format, the Ethereum destination address, the exact token contract and whether the receiving application supports it. Keep the deposit transaction ID and any bridge receipt needed to track or recover a pending transfer. The central lesson from RenBridge is operational: a wrapped token’s value depends on a functioning redemption mechanism. Compare the live mechanism and its costs today, rather than relying on a familiar name or a quoted one-to-one value.