Difference between RenBridge and RenVM: app versus network
RenBridge was the web app for requesting cross-chain transfers; RenVM was the Darknode network that held the underlying assets and signed the messages…
The Crypto Front Page Desk4 min read

RenBridge was the web app for requesting cross-chain transfers; RenVM was the Darknode network that held the underlying assets and signed the messages needed to mint or release them.
A 1 BTC deposit shows where each layer acted
Consider a user moving 1 BTC from Bitcoin into renBTC on Ethereum. The bridge app assembled the transfer request and, through RenJS, generated a gateway address for the deposit. That address was tied to the intended destination, so the request had to be in place before the user sent BTC. Generating the address did not itself move or custody the coin.
The user then sent BTC to that address on Bitcoin. For someone tracing this transfer, RenBridge identifies the application that prepared the request and displayed its progress; the Bitcoin deposit and Ethereum mint identify the transactions to examine. The app’s status was a view of the process, not the record that made the transfer valid.
RenVM’s Darknodes observed the Bitcoin deposit. They jointly controlled the keys associated with assets held by the network through secure multiparty computation, a method that lets nodes cooperate on key operations without one operator holding the complete key. Once the deposit met the network’s requirements, RenVM produced a signature authorizing the corresponding mint. Custody and signing belonged to RenVM, regardless of which app had initiated the request.
The user submitted the mint transaction on Ethereum. There, a gateway contract verified RenVM’s signature before minting renBTC, the token representing the deposited BTC on that chain. The contract supplied the on-chain verification step; it did not take its authority from the bridge app’s displayed status. Ren’s contract reference assigns signature verification and minting to the MintGateway contract.
Those stages give a practical way to attribute a past transfer. The Bitcoin transaction establishes the deposit. RenVM’s signature connects an accepted deposit to the requested mint. The Ethereum transaction and gateway contract event establish whether renBTC was minted. A request shown in an app is not, by itself, evidence that all three stages completed. The relevant chain transactions remain inspectable after the app that presented them stops operating.
The same division explains why the bridge app was only one route into RenVM. Developers could use RenJS, the SDK for interacting with RenVM, to build another app that requested a gateway and handled the resulting transactions. Ren’s RenJS tutorial walks through an app that mints BTC on Ethereum. A transfer made through such an app still depended on the same network signature and host-chain contract, so app branding alone cannot identify who held the BTC.
Availability follows the dependency in the other direction. If the web app alone had stopped while RenVM continued operating, an app using RenJS could still have reached the network. Once RenVM stopped providing custody and signatures, no interface could complete a new transfer that required them. The original bridge service has been discontinued; a visible interface should therefore not be taken as evidence that its underlying transfer service operates.
Related
Is REN the same as RenVM?
REN is the protocol token; RenVM was the network that processed cross-chain transfers. Darknode operators bonded REN to register nodes, but sending REN was not the step that minted renBTC from a Bitcoin deposit. For transfer attribution, the token explains a node operator’s bond, while RenVM identifies the network responsible for custody and signing.
Who ran the Darknodes?
Darknodes were run by operators who registered nodes and provided the computing resources used by RenVM. Their joint key operations made network custody and signing possible. Ren’s Darknode documentation describes the operator role and registration bond. The bridge app’s user did not become a Darknode operator by requesting a transfer.
- The app prepared the request and showed progress; RenVM held assets and signed.
- Gateway contracts verified RenVM signatures before minting renBTC.
- Trace a transfer through its Bitcoin deposit and Ethereum mint, whichever app initiated it.