Ren (formerly Republic Protocol) has been a staple of our altcoin portfolio since inception of the Mountains and Valleys strategy. At the time of writing, the price of $REN is on a run and important parts of the project made it to mainnet. A good time to explain our continued fascination with this project.
On a quest to make the project’s promises more tangible, Ren have changed their promotional narrative over time (but not so much the project’s inner workings). The current narrative: trustless cross-chain value transfer and liquidity, is a good starting point to explain what Ren does and why the blockchain space needs it.
How to Bring Bitcoin To Ethereum
Over the past 12 months, we’ve seen a tremendous rise in liquidity on decentralized exchanges (DEXes), and the most active DEXes are on the most liquid chain, Ethereum. This poses a major challenge: only ETH and Ethereum based tokens can immediately be traded on Ethereum based DEXes. What if I want to hold part of my portfolio in BTC or even ZEC, but trade on Ethereum? How do we bring value on other chains to Ethereum?
The Custodial Approach
Somebody, let’s call him Carli Custodian, decides to offer a “Bitcoin on Ethereum” service that works in a very simple way: you send Carli some Bitcoins. Carli will keep those for you, and will in turn send a Bitcoin backed token called ccBTC to your Ethereum wallet. You can then freely use your ccBTC on Ethereum, even send it to somebody else. If you want your native Bitcoin back, you send Carli some ccBTC. Carli burns those and sends the same amount of native Bitcoin to your Bitcoin wallet.
This naïve model isn’t far from reality. Apart from an obviously more complex custody system, custodial Bitcoin tokens like WBTC work in exactly this way. While easy to implement, this model breaks the core promise of the blockchain: trustless and permissionless value transfer. No matter how refined the custody system, Carli can run with your native Bitcoins, rendering ccBTC worthless. Or Carli could, to the same effect, start issuing “unbacked” ccBTC tokens in great numbers. We could catch Carli by looking at his BTC holdings and the amount of ccBTC issued. But at that point in time, it would already be too late.
The Debt Based Approach
Another way to bring Bitcoin to Ethereum is to recreate it on Ethereum via debt. Somebody deposits a certain amount of ETH, or of an Ethereum based token into a smart contract vault. This in turn allows him to “mint” a certain amount of Ethereum based Bitcoin. A smart contract system, in constellation with the open market, ensures that any Bitcoin minted in this way remains pegged to the price of native Bitcoin. The system also makes sure that the vaults used as a basis for the minting process remain adequately collateralized. Synthetix works a bit like this.
The debt based approach brings back the advantages of blockchain tech: it is trust- and permissionless. But it comes at the price of quite a bit of complexity. It is also not very capital efficient, as it typically requires about 150% of the value issued to be locked in a vault somewhere.
The Multichain Approach
This approach comes closest to what Ren does, but it is not the same. To transfer value between multiple chains, an additional blockchain can be established that — via its nodes — tracks value on all involved chains and issues or redeems tokens as necessary. This is, grossly simplified, what Cosmos offers. The multichain approach is promising, as it allows much more than “just” value transfer. It is also complex to establish as it requires the creation of an entire ecosystem around the intermediate chain. Just like the crosschain approach, the multichain approach requires its own solution to lock value on one chain and issue it on another.
The Crosschain Approach
What if we could lock up Bitcoin on the native chain, then issue it on Ethereum, all in a trustless and permissionless fashion? That is exactly one of the use cases of Ren.
To transfer Bitcoin, we need a private key. Ren allows a decentralized network of computers to generate and store a private key, but prevents that malicious actors can assemble that key and run with the associated coins. The process necessary to achieve this is called secure multiparty computation (sMPC). sMPC enables a group of nodes to jointly execute calculations on a set of data, without revealing the inputs or outputs, while also remaining certain of the dependability of the result. It can do this even in the presence of malicious or unreliable actors. sMPC has been under research since the 70s of the last century, but its application to blockchain tech poses additional challenges like fault tolerance, the necessity to reach consensus among network participants, or the detection and elimination of bad actors. Ren established a network of nodes, called Darknodes, that solves these problems and that can form the basis for various sMPC applications — like bridging Bitcoin to Ethereum.
So, how does Ren bring Bitcoin to Ethereum? In the simplest possible way: a user initiates the transaction by telling the Ren network that he needs a Bitcoin deposit address. The network generates the private key for that address, without ever revealing it to any of the participants. It then sends a public address corresponding to that key to the user. The user deposits Bitcoin to this address. The Ren network detects the deposit. It waits for a certain number of confirmations, then issues the appropriate amount of renBTC tokens on Ethereum. The opposite way works too: renBTC tokens get burned, the Ren network sends native BTC to the user who initiated the transaction. This all works in a secure, permission- and trustless environment. Nobody can ever run with the deposited BTC. Nobody can issue more renBTC that have been deposited. Nobody can stop these transfers from happening.
Anybody can test out the process of bringing Bitcoin to Ethereum on https://wbtc.cafe/. wbtc.cafe trustlessly transfers Bitcoin to Ethereum and then converts it to, somewhat ironically, trusted but well established WBTC tokens on the open market. Alternatively, renBTC can also be used directly on Ethereum, cutting out any trusted 3rd party.
Other Applications
Trustless and permissionless cross-chain value transfer is an obvious and very present use case for the system that Ren offers. However, blockchain based sMPC is by far not limited to a single use case. On the contrary, blockchain based sMPC is the missing link to make public blockchains useful. Especially in business, the cases where every in- and output to a transaction should be world-readable, are rare. For individuals, the “all public” approach raises substantial privacy concerns. sMPC systems solve this by allowing for dependable, but secret storage and computation, while preserving the core promises of the blockchain based approach. This gives Ren potential far beyond cross-chain value transfer.
Ren is not the only project offering sMPC on the blockchain. Other projects include Keep, Enigma, and iExec. Among those projects, Ren seems to have progressed the most, both in terms of development of the core protocol, and in terms of nascent developer adoption.
Network and Token Economics
As mentioned above, Ren runs its own network of nodes called Darknodes. Fees reward Darknodes for their computation work and for the storage they provide. Each Darknode requires a deposit of 100’000 $REN as a bond to keep the node honest.
If Ren turns out to be a success, running Ren Darknodes could yield exceptional rewards, even for crypto standards. Estimates based on the assumption that Ren will not only be responsible for cross-chain value transfer, but will also be able to capture a part of the decentralized crypto trading volume, range from 62 to 300K US$ of revenue per Darknode per year in 2022, dependent on the emerging fee structure and market capture. Since REN is required as a deposit to run a Darknode, this gives the REN token an exceptional outlook on a high timeframe.
The REN network has been released to the public. Any person holding 100’000 REN can join it, provided that she is willing to maintain the necessary technical infrastructure to run a Darknode.
In our tests, operating a REN Darknode was very easy. Likely the easiest node setup we ever tested.
Conclusion
The Ren project offers exceptional fundamentals and has shown an outstanding quality of delivery since its ICO back in early 2018. From a fundamental perspective, this is one of the most exciting projects to come out of the 2017 ICO craze. It checks all the necessary boxes for a possible long-term success:
- competent team
- high quality of delivery both in code and project communication
- strong product with highly plausible product market fit
- working product is available and testable publicly, generating relevant turnover
- strong blockchain use case
- strong token value link, token mechanics and monetary policy
- fair valuation (relative to ICO), with lots of growth potential for the token price
Like with any early stage project, all these positives do come with the big caveat of “if it works out”. Various associated risks:
- impossibility to solve the chicken and egg problem of bootstrapping liquidity
- centralized team that could run out of funds before the project sees success
- centralized starting point makes the project vulnerable to regulatory action
- token-value-link could be forced to break, e.g. competition could force the Darknodes to run at or near profitability, instead of running at the extrapolated wild profitability
- network could be forced into centralization or a permissioned model, e.g. via a buyout of the company
- team could fail to generate relevant traction in the market, e.g. due to a strongly technical orientation
- on a shorter timeframe, the retail market could fail to recognize the value of the project due to its B2B/professional nature
Over the past months, Ren continued to establish itself as a project and remains one of the most valid bets on the success of “DeFi” as an array of blockchain based products with real adoption, and as a marketing based meme. Our very positive assessment of this project remains unchanged.
Sources
- https://renproject.io/
- https://github.com/renproject/ren/wiki
- https://medium.com/renproject
- https://www.reddit.com/r/RenProject/comments/etf8le/renvm_ama_answers
Cover image by Sarah Meyer.