anguss

RenBridge: What a Bitcoin DeFi Round Trip Required

Before its 2022 sunset, RenBridge could take a holder from native BTC into DeFi and back only if the holder completed the bridge, application, and redemption steps while the service was functioning. Minting renBTC completed the entry, not the round trip. The original RenVM service was sunset in 2022, so this describes a historical workflow.

How Did RenBridge Turn BTC Into renBTC?

The RenBridge BTC-to-renBTC path required a Bitcoin wallet with spendable BTC, a compatible wallet on a supported destination chain, and funds for that chain’s transaction fees. For the holder, RenBridge supplied the entry and exit operations around a separate DeFi position. On Ethereum, the destination wallet needed ETH for gas: receiving renBTC did not fund the transactions needed to use it.

For entry, the holder sent native BTC to a deposit address controlled through RenVM. RenVM waited for Bitcoin confirmations before the holder submitted a mint transaction with the destination wallet. Ren’s historical interface guidance treated those as separate stages. A confirmed BTC deposit meant RenVM had received the coins; it did not mean renBTC had appeared in the wallet. The holder still had to sign and fund the host-chain mint transaction.

Once that transaction succeeded, renBTC represented the deposited BTC on the destination chain and could be used by applications that accepted it. Entry involved a Bitcoin network fee, a bridge charge, a wait for Bitcoin settlement, and a host-chain transaction fee. The time and cost depended on network conditions and the bridge’s terms at the time.

What Happened After renBTC Reached the Wallet?

The holder had to enter and later leave a DeFi position through the application itself. Lending or providing liquidity could require a token approval followed by a deposit transaction, each funded on the host chain. In return, the application might record a claim or issue a position token rather than leave renBTC freely available in the wallet. Its withdrawal rules determined when that claim could become renBTC again.

Consider two holders with the same BTC deposit, destination wallet, gas funds, and functioning bridge. Both mint renBTC and place it in an application. One can withdraw their position immediately; the other has a position whose withdrawal is temporarily locked. Only the first can make renBTC available for redemption at that point. The difference is the application’s withdrawal condition, even though both bridge entries succeeded. Application fees, execution delays, and losses can also change the quantity returned. A successful mint therefore says nothing by itself about immediate withdrawal or the amount of renBTC eventually available.

How Did renBTC Return to Native BTC?

The holder first needed renBTC in their destination wallet, plus a Bitcoin address to receive the released coins. Historically, they submitted a host-chain burn transaction and a release request. Burning removed the renBTC from circulation; RenVM then had to process that burn and release the corresponding BTC to the named Bitcoin address. A burn confirmation on the host chain and receipt of BTC on Bitcoin were separate completion points.

Exit required host-chain gas, bridge and Bitcoin transaction charges, and time for the burn and BTC payment to settle. It also depended on the burn-and-release infrastructure still operating. Holding renBTC, even outside an application, did not guarantee a future route back to native BTC once that infrastructure ceased operating.

A verified restoration of minting and BTC redemption, with usable host-chain contracts, would justify revisiting this historical conclusion. It would make a new round trip possible to assess; the application’s withdrawal terms and each chain’s fees would still decide whether a particular holder could complete it.