Skip to the article
Blockheight

Crypto markets, protocols, policy

Why Did My renBTC Mint Need a Darknode Signature?

Why did a renBTC mint need a Darknode signature instead of a custodian? RenVM's nodes jointly authorized the mint, and the gateway contract checked their shared key.

The Blockheight Editors··2 min read

Why Did My renBTC Mint Need a Darknode Signature?

RenVM’s Darknodes jointly authorized each renBTC mint; no company held the Bitcoin and approved it. Your mint needed their threshold signature because the Ethereum gateway contract trusted RenVM’s public key.

  • You sent 0.1 BTC to a gateway address; Darknodes waited for confirmations, then signed.
  • The gateway contract checked the signature against one stored RenVM public key and minted renBTC.
  • Each Darknode bonded 100,000 REN, making dishonest signing costly.

What happened to your 0.1 BTC?

After your deposit reached the gateway address and had enough confirmations, RenVM’s Darknodes produced a threshold signature authorizing the mint. The signature represented their joint approval: no individual node or company acted as the custodian’s substitute.

The Ethereum gateway contract checked one stored RenVM public key. It did not need to know which Darknodes took part or how many signed; it verified that the signature matched the key it trusted, then minted renBTC.

That design kept the mint check simple on Ethereum, while shifting trust to RenVM’s shared signing process. The gateway’s check established that RenVM had authorized the mint; the bonded REN gave Darknode operators a financial cost for signing dishonestly.

How did that differ from WBTC?

WBTC uses a named custodian: a merchant requests a mint, and BitGo processes the request and authorizes WBTC issuance. In RenVM’s model, a threshold of Darknodes signed instead of one custodian approving the deposit.

So the trade-off was where the mint depended on trust. WBTC depended on its custodian’s handling and approval; renBTC depended on RenVM’s nodes producing a valid shared signature and the gateway contract checking it. The 100,000 REN bond per Darknode made dishonest signing costly, but the authorization still relied on RenVM’s key and signing process.

Before acting on an old mint, check whether the BTC is already represented on Ethereum or needs redeeming: RenBridge users can review how to redeem renBTC for Bitcoin before sending funds. The mint flow explains the original authorization; redemption is a separate step.

Related stories