0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

How Does RenVM Work? Darknodes, Shared Keys, and renBTC

0
Posted at

RenVM 1.0 worked by having bonded Darknodes jointly control Bitcoin deposit keys, authorize renBTC mints after confirmed BTC deposits, and sign Bitcoin releases after renBTC was burned.

  • You sent BTC in and received renBTC on Ethereum, minus fees.
  • To get BTC back, you burned renBTC and named a Bitcoin address.
  • Darknodes had to cooperate to sign either side of the transfer.

How Darknodes Controlled the Bitcoin

RenVM 1.0 placed BTC sent to a gateway address under a key controlled jointly by a group of Darknodes. A Darknode was a computer running RenVM software; groups of them, called shards, handled the keys. The gateway address was where you deposited BTC. A separate gateway contract on Ethereum checked the authorization to mint renBTC.

The key was the crucial part. RenVM used RZL MPC, a form of multi-party computation, to generate the private key jointly. Each participating Darknode held a share, while the network could publish the matching public key needed for a Bitcoin address. The full private key was never assembled on one machine, including when the nodes signed a transaction. One Darknode therefore could not take the deposited BTC or authorize a mint by itself.

Signing required enough Darknodes to work with their shares and produce one usable signature. The RZL MPC paper describes distributed key generation and threshold signing without revealing the private key. Its security claim assumes a limit on malicious participants; applying that design to a transfer also depended on the live RenVM network verifying the relevant chain events.

Each Darknode bonded 100,000 REN. Under RenVM’s rules, that bond could be slashed for misbehavior or responsibility for lost assets. It gave an operator capital to lose, alongside the key-sharing rule that required cooperation to move funds. Ren Project’s GitHub documentation describes both the bond and the mint and burn sequence.

What Happened to a 1 BTC Deposit?

A 1 BTC transfer makes the sequence concrete; the amount is illustrative. Before you acted, the BTC was in your Bitcoin wallet and no corresponding renBTC existed for this deposit. You sent the BTC to the gateway address and specified where the renBTC should go on Ethereum. The deposited BTC then sat under the key shared by the Darknodes.

RenVM checked the Bitcoin transaction, its details, and the required confirmations. Once the 1 BTC deposit qualified, the Darknodes used MPC to produce a minting signature. You or an application submitted that signature to the Ethereum gateway contract, which issued renBTC to the chosen address, minus fees. You may remember choosing the destination and seeing the deposit address through RenBridge, the interface for this route.

At that point, the BTC was still on Bitcoin under the gateway key. What changed was your usable asset on Ethereum: you held renBTC representing the deposited BTC after fees. You could then use that token in an Ethereum application, such as a swap or lending contract, without moving the locked BTC out of RenVM’s custody.

For the return trip, you burned renBTC on Ethereum and supplied a receiving Bitcoin address. Burning removed those tokens from circulation. RenVM observed the confirmed burn, and the Darknodes jointly signed a Bitcoin transaction releasing the corresponding BTC to your address, again accounting for fees. The BTC left gateway custody; the burned renBTC could no longer circulate as a claim on it.

Related Questions

What Is a Darknode?

A Darknode was a bonded RenVM operator that helped verify transfers and take part in shared-key signing. Its 100,000 REN bond created a financial stake in following the rules. The signing arrangement also mattered: a node held only a key share, so approving a mint or releasing BTC required cooperation from other Darknodes in its group.

Why Did RenVM Shut Down?

RenVM 1.0 was sunset after Alameda Research, which funded and led its development, entered bankruptcy proceedings with the FTX Group. In its November 2022 announcement, the Ren team said it would disable new mints first and then shut down the 1.0 network. Ren 2.0 was discussed as a successor. The transfer sequence above explains how the earlier system worked, not a current route for depositing or redeeming BTC.

The cycle was lock BTC, mint renBTC, burn renBTC, and release BTC. Darknodes could carry it out because they jointly controlled the signing key without any one node holding it in full—the deciding reason custody was split across the group.

0
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?