cryptonews24

RenBridge Transfer Types Explained: Three Routes, Three Records

A past RenBridge transfer fits one of three types: lock-and-mint from a native chain to a host chain, burn-and-release back to the native chain, or burn-and-mint between host chains. The direction determines which records should exist.

  • Lock-and-mint: native BTC enters RenVM custody; renBTC is minted on a host chain.
  • Burn-and-release: host-chain renBTC is burned; BTC is sent to a specified Bitcoin address.
  • Burn-and-mint: renBTC is burned on one host chain and minted on another.

A RenBridge history can span several chains because each route starts with a different asset state. RenBridge moved supported assets between chains; that context explains why a renBTC history might contain a Bitcoin deposit, a host-chain burn, or both.

RenBridge Transfer Types and Their Records

The three transfer types are distinguished by where the asset starts and where its representation ends. RenVM, the network of Darknodes behind the bridge, had to recognize a sufficiently confirmed input before authorizing the output. For a host-chain mint, that authorization was a signature submitted in the destination transaction. A Bitcoin release instead ended with a signed Bitcoin transaction. Those output records show whether the requested movement completed.

Lock-and-mint

Lock-and-mint took a native asset into RenVM custody and created its representation on a host chain. For BTC to Ethereum, the sender first needed a gateway address generated for that transfer and a destination capable of receiving renBTC. The Bitcoin transaction paid BTC to the gateway address. After the required Bitcoin confirmations, RenVM supplied a minting signature; an Ethereum transaction used it to mint renBTC. A gateway deposit alone therefore identifies the input, while the Ethereum mint establishes the completed output.

Take an illustrative wallet that held BTC before the transfer. Afterward, it holds renBTC on Ethereum, while the corresponding BTC remains in RenVM custody. The asset represented is still Bitcoin, but the wallet now holds a token usable on the host chain. This type helps classify a record with a Bitcoin gateway payment followed by a host-chain mint.

Burn-and-release

Burn-and-release returned a represented asset from a host chain to its native chain. The holder first needed renBTC available to burn and a Bitcoin receiving address. An Ethereum burn recorded the amount and destination address; RenVM observed the confirmed burn, and Darknodes signed a transaction releasing BTC from custody. The Ethereum burn and Bitcoin payment are separate records, so a burn alone does not show that the recipient received BTC.

In the reverse of the illustrative case, the wallet’s renBTC balance falls and BTC reaches the named Bitcoin address. The representation is extinguished, while the underlying asset remains BTC. This type fits a host-chain burn paired with a native-chain release, even when the original lock-and-mint happened much earlier.

Burn-and-mint

Burn-and-mint moved a represented asset between two host chains. A holder could burn renBTC on Ethereum, specify a Polygon destination, then use RenVM’s signature to mint renBTC on Polygon. The required input was a confirmed Ethereum burn; the completed output was the Polygon mint. The holder needed a valid destination on that supported host chain, but no new Bitcoin gateway deposit.

In an illustrative before-and-after record, renBTC leaves the Ethereum wallet and appears in the Polygon wallet. The Bitcoin backing stays in RenVM custody throughout. Bitcoin is never a transaction leg of this host-to-host move, so no Bitcoin confirmation wait applies. The relevant waits concern the source host-chain burn, RenVM authorization, and destination host-chain mint. An older Bitcoin deposit may explain where the renBTC originally came from; it is not part of this transfer. The same reasoning applies when examining a supported host chain such as Solana: identify the actual burn and mint chains.

All three routes depended on RenVM’s signatures. The Ren Project’s November 2022 sunset announcement specified the scope and sequence for Ren 1.0: disable new minting, leave burns available temporarily, then shut down the network. The original RenBridge service was discontinued, so these types describe historical transfers, not routes available through that service today.

Which assets did RenBridge support?

RenBridge supported selected native assets and their representations, with BTC and renBTC providing the clearest example here. Historical deployments also included representations of assets such as Bitcoin Cash and Zcash. To classify a particular record, identify the asset and the chains supported at that time; the transfer type follows the direction, not the token name alone.

Who paid gas on each side?

The party submitting a host-chain burn or mint paid that chain’s transaction gas, whether it was the holder or a relayer. A BTC gateway deposit required a Bitcoin network transaction; a BTC release required a Bitcoin network transaction too. In a host-to-host burn-and-mint, the source burn and destination mint incurred their respective host-chain costs. Gas payments can help locate transaction submitters, but the burn, mint, deposit, and release records determine the type.

Where do RenBridge transfers show on explorers?

A RenBridge transfer leaves records on its input and output chains, connected by the RenVM transaction. Lock-and-mint shows a Bitcoin gateway deposit and host-chain mint. Burn-and-release shows a host-chain burn and Bitcoin payment. Burn-and-mint shows burns and mints on two host chains, such as Ethereum and Polygon. Start with the known transaction hash, then look for the corresponding output rather than treating one chain’s record as the entire transfer.

Classify the past transfer by its two ends: native to host, host to native, or host to host. That direction tells you where completion should be recorded and, for host-to-host moves, why a Bitcoin confirmation is absent.