Ren (RenVM)
About
Ren is a decentralized, permissionless interoperability protocol that enables the movement of value between blockchains. Powered by a network of Darknodes running secure multi-party computation (RZL MPC), it acts as a trustless custodian: users lock assets (e.g. BTC) on their origin chain and mint 1:1 pegged representations (e.g. renBTC) on destination chains such as Ethereum, Solana, or Polygon. The protocol targets developers and DeFi applications seeking native cross-chain asset composability without relying on centralized intermediaries.
Where Does Yield Come From?
Ren earns yield from fees charged when users move assets between blockchains. These fees go to Darknode operators — people who run special network computers and have locked up (bonded) 100,000 REN tokens to prove they will behave honestly.
There are three types of fees:
- Minting fee (0.1% at launch) — charged when a user locks an asset like BTC on its original chain and creates a 1:1 version (renBTC) on another chain like Ethereum.
- Burning fee (also 0.1% at launch) — charged when a user destroys (burns) the wrapped version to get the original asset back.
- Continuous fee (set to 0% by default) — a tiny, ongoing charge that could be turned on, slowly reducing how much of the underlying asset a pegged token can claim over time.
Fees are always paid in the asset being moved — BTC fees for Bitcoin transactions, ETH fees for Ethereum transactions, and so on. This keeps the rewards diverse. Small costs for using the underlying blockchain (like Bitcoin miner fees) are passed through without any extra charge from Ren.
To keep the network secure, Darknodes vote to adjust fees so that the total value of bonded REN tokens is always at least three times larger than the value of all locked assets. This rule means attacking the network would never be profitable, and it uses a long-term earnings model rather than a simple price check.
REN tokens have only one job: bonding. This creates a helpful cycle: more people using Ren → more fees earned → REN becomes more valuable → the network can safely hold more locked assets — all without needing to force-sell or liquidate anyone.
Persons
Taiyang Zhang
Co-founder
Loong
Co-founder
Audits
| Audit / Date | Findings | Verdict |
|---|---|---|
ChainSecurity25-11-2019 |
| ChainSecurity found three High and four Medium issues in Ren's smart contracts; all were fixed or addressed before deployment, and the auditor stated no further concerns, indicating the contracts were safe for release at the time of the audit. |
| The audit found no critical or high open issues; one low-severity risk (proposer DoS) was accepted as inherent to PBFT-based consensus. All other findings were remediated during the engagement, but the report notes that consensus algorithms are inherently complex and additional latent issues may exist. | |
Consensys Diligence17-04-202013-05-2020 |
| This cryptographic design review found no exploitable vulnerabilities in the RenVM whitepaper's mathematical protocol, but flagged significant documentation gaps (unset parameters, vague adversarial models, and unclear novelty) that must be resolved before secure implementation. The protocol's safety depends entirely on how faithfully these unspecified details are later implemented in code. |
Trail of Bits03-08-2020 - 17-08-2020 |
| The implementation generally complies with the RenVM protocol specification, and none of the reported issues were deemed immediately exploitable, but Ren should address the high-severity index-zero check and act on the informational hardening recommendations to strengthen overall system assurance. |
Legal
Legal form
Not disclosed on official sources
Registration jurisdiction
Not explicitly disclosed; the forum Terms of Service (forum.renproject.io/tos) select Singapore as governing law and dispute venue, but do not state a place of incorporation or registration.
Status and notes
The forum Terms of Service (last updated July 12, 2018) refer to the operator as "Ren" (described as "the company that runs the forum"), with contact at [email protected] and disputes governed by Singapore law. No imprint, formal legal entity name (e.g., foundation, Ltd., AG), or registration number is disclosed on any first-party source (main site renproject.io is offline; no terms/privacy/imprint pages exist in Wayback archives). The GitHub organization and wiki also contain no legal entity information.