RenBridge | Documentation
Last updated
Last updated
Welcome to the official RenBridge Docs. This guide provides all necessary information on how RenBridge works, how to use it, and how developers and users can interact with the protocol in a secure and decentralized way.
is a decentralized protocol that enables the transfer of native crypto assets (such as BTC, ZEC, DOGE, and LTC) to and from EVM-compatible blockchains like Ethereum, BNB Chain, Arbitrum, and Polygon.
It is powered by RenVM, a virtual machine that uses multi-party computation (MPC) and threshold signature schemes to lock assets on source chains and mint 1:1 representations on destination chains without relying on centralized custody.
RenVM – A decentralized network of nodes (Darknodes) responsible for validating and executing cross-chain transfers.
renAssets – Tokenized versions of native assets (e.g., renBTC, renZEC) minted on EVM chains.
Darknodes – Validator nodes that collectively manage the MPC signing process and secure RenVM operations.
Gateway contracts – Smart contracts on destination chains that handle minting and burning of renAssets.
As of 2025, RenBridge supports:
Bitcoin (BTC)
Zcash (ZEC)
Dogecoin (DOGE)
Litecoin (LTC)
Bitcoin Cash (BCH)
RenBridge is compatible with:
Ethereum
BNB Chain
Polygon
Arbitrum
Avalanche (C-Chain)
More chains may be added through community governance.
Lock – Users send native assets to a RenVM-generated gateway address on the source chain.
Mint – After sufficient confirmations, RenVM mints a 1:1 renAsset on the target EVM chain.
Use – Users can interact with DeFi protocols using renAssets.
Burn – When finished, users can burn the renAsset to initiate a release of the original asset.
Release – RenVM unlocks and sends the native asset back to the user’s original wallet.
Connect your wallet (MetaMask, WalletConnect, etc.)
Choose the source asset and destination chain.
Send your asset to the generated deposit address.
Wait for confirmation.
Receive the wrapped asset (renBTC, renDOGE, etc.)
(Optional) Use DeFi apps or burn the asset later to withdraw to the native chain.
RenVM uses threshold signature cryptography to ensure assets are controlled by the network, not individuals.
Each transaction requires multiple Darknodes to validate and sign.
All operations are non-custodial and transparent, with public audit logs available.
Users can participate in securing RenVM by running a Darknode.
Requirements:
Bond a specified amount of REN tokens
Maintain 24/7 uptime
Participate in MPC signing
Earn a share of protocol fees
SDKs and API documentation
Smart contract interfaces (Solidity)
Integration templates (Node.js, Python)
RenBridge follows a decentralized governance model. Community proposals and upgrades to RenVM are submitted and voted on by REN token holders.
Q: Is RenBridge custodial? No. RenBridge is fully non-custodial. Users retain ownership of assets during and after bridging.
Q: Is KYC required? No. RenBridge is permissionless. Anyone can use it.
Q: How long does bridging take? Usually between 3–6 minutes, depending on the source chain's block time.
Q: Can I use renAssets in DeFi? Yes. renBTC, renZEC, etc. are ERC-20 tokens usable in most DeFi protocols.
Q: Are there bridging fees? Yes, RenVM charges a small fee per transaction in addition to network gas costs.
Community forum: Coming soon
Discord & Telegram: Managed by contributors (check site footer)
Need help integrating or have technical questions? Reach out via GitHub Issues or open a support thread in the community.
Welcome to
For setup instructions, refer to the .
Getting Started
Create your first site
Basics
Learn the basics of GitBook
Publish your docs
Share your docs online
