RenBridge minted renBTC by deriving a Bitcoin gateway address from the destination parameters, confirming the BTC deposit, obtaining RenVM’s signature, and submitting that signature to an Ethereum Gateway contract for the recipient.
The original network is discontinued, so this sequence describes a historical mint rather than a live procedure.
A Bitcoin deposit needed a separate Ethereum mint transaction
The RenBridge mint completed only when the Gateway contract verified RenVM’s signature on Ethereum.
Each stage below shows what to record and where a mint could stall. For more on the RenBridge mint question, renbridge.net covers the cross-chain crypto bridge.
- Choose the amount and destination. A developer needed RenJS, BTC to send, and an Ethereum wallet funded for gas. Set BTC as the asset, specify the recipient wallet or contract, and retain the nonce and any payload. The actual deposit and mint fee determined the token amount.
- Derive and save the gateway address. RenJS generated the Bitcoin address from a hash bound to the destination, nonce, and payload. Those inputs committed the deposit to a particular recipient and call. Say the recipient changed afterward: the new parameters would derive a different address, while BTC sat at the original one. The deposit could only be minted with the exact parameters that produced its address. Save the parameters with the address; losing the nonce could prevent recovery. Ren’s parameter documentation explains this binding.
- Send BTC to that address. Record the Bitcoin transaction ID and the output paying the saved address. A deposit below the applicable mint fee would leave no positive renBTC amount to mint.
- Wait for confirmations. Track the Bitcoin output until it reached RenVM’s threshold. A visible deposit was not eligible for signing before that point. RenJS exposed it as an input transaction to await.
- Obtain the RenVM signature. Submit the confirmed deposit to RenVM and wait for the Darknodes’ threshold signature. The signature authorized a mint for the original parameters; it did not execute an Ethereum transaction. Ren’s transaction model separates the Bitcoin input, RenVM processing, and Ethereum output.
- Submit the mint on Ethereum. RenJS could submit the output transaction, or an integration could pass the payload hash, nonce hash, amount, and signature to the Gateway contract. Its mint function verified RenVM’s signature before minting renBTC. Without a gas-funded submission, BTC stayed locked and no token reached the recipient.
- Verify the result. Compare the Ethereum receipt with the recipient’s renBTC balance. Before minting, BTC was locked and the wallet lacked the new tokens; afterward, BTC remained locked and the wallet held renBTC after fees because the Gateway accepted the signature.
Related questions explain the reverse flow and the SDK
Burn and release moved value back to Bitcoin, while RenJS coordinated both directions.
How did the RenBridge burn and release flow work?
RenBridge’s burn and release flow began with an Ethereum transaction that burned renBTC. RenVM observed the burn and arranged a Bitcoin release to the specified address.
What was RenJS?
RenJS was the developer SDK for creating gateways and tracking input, RenVM, and output transactions. For research now, reconstruct the saved parameters and compare the Bitcoin deposit, RenVM response, and Ethereum receipt to find the failed stage.