Hello Defiers! This week’s interview is with the CTO of Ren Project, one of the teams at the forefront in the effort to bridge different blockchains, and bring Bitcoin to decentralized finance in a trustless way. Loong Wang says RenVm is only a few weeks away from going live, and once it does, it will strengthen DeFi by adding different types of collateral and boosting liquidity. It will also open up a new investment option, as anyone will be able to run a node on the network and collect fees.

Ethereum creator Vitalik Buterin just yesterday tweeted, “it's embarrassing that we still can't easily move between the two largest crypto ecosystems trustlessly.” Ren is one of the teams trying to fix that.

Key things we talked about:

How RenVM started and what it actually is

What will blockchain interoperability look like for users, and what will devs have to do to get it on their dapps

Requirements and incentives to run a node on the Ren network

Main known risks of RenVM

Plans to transition to more decentralized governance

Funding and monetization

Competitors and whether blockchain bridges is a winner take-all market

This interview has been edited for brevity and I’ve bolded my favorite quotes.

You’re signed up to the free version of The Defiant, so you’ll get only part of the interview. Subscribe now for complete access. Click here to pay with DAI at 70 Dai per annual subscription ($100/yr normal price).

📢 Help me scale up The Defiant team by donating to my Gitcoin Grant! Just 1 Dai goes a long way :) Thanks to contributors so far: @cstoraker, @robertpragai, @stone441, @scott-l-e-w-i-s, @nodar, @gliinbox, @ecruz01, @gwintery.

Loong Wang: I'm a computer scientist by trade and education. I had been working in a startup with Tai, the CEO of Ren, I think since 2014, 2015. We got along really well and decided to branch off and do our own thing. We started a development studio and we worked together for a long time on that. And then we took a little break. I went to go teach at the university and finished my thesis. What I was studying at the time was distributed systems and I was focusing on the academics behind distributed systems and how computers work when they're trying to communicate with each other in a global network, specifically in the context of things like supercomputers, which are actually just distributed systems.

This obviously relates to blockchain, but at the time I wasn't particularly interested in it. One of my mates was, and he was big on Ethereum and telling me to buy it way back when. But then Tai got into it and he co-founded Virtual Capital. And then he approached me and wanted to do some work in the space and he'd found sort of a niche in the dark pool space within crypto. And it was a perfect alignment of a good business opportunity and my technical expertise so we kicked it off and we got into it like that. For me it was quite serendipitous that the industry took off because it was a perfect place for me to apply my academic knowledge.

Loong Wang. Image source: Twitter

Dark Pool Beginnings

CR: Tell me about how Ren protocols started. What was the original idea behind it?

LW: So originally, in 2017, we sought out to build a decentralized dark pool. A dark pool is basically just an exchange where the order book is hidden. And so we spent a year building that and we got into production. But the thing that really became apparent when we released it was that the reason you want to use a dark pool is for large liquidity movements and a lot of the liquidity was in chains that weren't actually on Ethereum. So ETH had a lot of liquidity, but it was predominantly Bitcoin and USDT. So we would had to leverage things like atomic swaps, and they're just too painful, they're too clunky, they have too many problems. And so we kind of turned around to say, well, we need to solve this interoperability problem before large liquidity is actually truly accessible in this space.

CR: Did you think of just building a dark pool on Bitcoin?

LW: If we started building a dark pool on just Bitcoin, then we only have the Bitcoin assets, and there's nothing to trade against. You're always going to need some form of interoperability when Bitcoin is involved because Bitcoin doesn't have any programmability.

Interoperability Definition

CR: Can you give me your definition of interoperability? I get what it is on a basic level, but I want to understand what exactly you mean when you say that word.

LW: Sure. I guess the way that I like to think about it is at the user level, so forgetting about the low level technical information because the problem you're really trying to solve is the user's problems. For me interoperability is can a user interact with my system without compromising on all the good stuff about blockchain. So it's still trustless, it's still decentralized, it's still permissionless, it's secure, all these kinds of good things about blockchain. Can they interact with my system and use any chain they want to use? Even more importantly, can they not even know what chain they're necessarily using? Can they just come to my application and say, I want to trade Bitcoin, I want to Zcash, I want to trade ETH, I don't even care what blockchain is being used. It's not even noticeable because the user doesn't really care. If you can achieve that, it means you have achieved quite a high standard of technical interoperability to make that possible.

CR: How has that main goal progressed until today? How close are you to reaching that level of usability?

LW: I would say we've achieved it, which is really quite an amazing accomplishment by the team. We're a few weeks away from mainnet at most. And at this stage, the functionality that RenVM is able to achieve is pretty much what I just described there. We actually have example applications where you can go to Uniswap and you can buy ETH for Bitcoin on Uniswap. You can do that with just one Bitcoin transaction. You don't even need to make an ETH transaction. You don't even need to have a MetaMask. You don't need an ETH wallet. You just have to have an address that you want to get your ETH at and then you make a single Bitcoin transaction. And there it is. There's no middlemen in that process whatsoever, which embodies this idea of the user being able to interact with any chain, with any application without actually necessarily caring about what's happening under the hood.

What Actually is RenVM

CR: That's amazing. So can you backtrack a little bit and explain exactly what you built? When you say RenVM or Ren Protocol, what actually is it?

LW: RenVM is a network of thousands of machines and anyone can run one of these machines and these machines collectively and collaboratively watch what other chains are doing and can exert actions on those chains as well. And that's basically at the core and it's designed in such a way that they can't exert actions on other chains unless the whole network is in consensus that that's what it should be doing. For all intents and purposes, it's kind of locked up there and then RenVM says, now we're going to exert an action on Ethereum which reflects whatever action it was that you wanted to take. You can trust this interoperability bridge will work and will work correctly as long as the threshold of adversaries that's trying to attack RenVM is below the standard one-third threshold that most blockchains exhibit.

CR: And this network of computers executing these actions for users, is this its own blockchain?

LW: So you can think of it as its own blockchain. It doesn't have a lot of the features that normal blockchains have because it doesn't need them. It uses the same underlying technology that blockchain uses to get the network to come to consensus and to do it in such a way that you can resist adversaries who are trying to behave maliciously.

Dark Nodes Incentives

CR: What kind of incentives do the nodes or I don't know how you call them, the computers of this network, have to make sure that these actions are executed correctly?

LW: We call them dark nodes because they're nodes but they're in the dark about the whole thing. They can't actually see what's going on. But the incentives for them are that they get a small percentage of the liquidity that moves through. So when you move one Bitcoin from Bitcoin to Ethereum and back again to do a trade, the dark nodes get a little cut of that.

CR: Got it. And so who are these dark nodes? Can anyone join and get some of these liquidity fees?

LW: Yup, that's exactly right. Anyone can spin up a dark node. The only restriction is that you have to have a bond. And this is where the REN token comes in. To run a dark node you have to have a 100,000 REN bond. And that's to prevent an adversary coming in and just turning on a thousand machines, 10,000 machines or what have you. But it also sort of bonds the nodes to behave well. If they misbehave and they try to attack the system, then they lose that bond. So there's this strong economic disincentive to misbehave.

CR: That's interesting. So it's kind of like a staking model.

LW: It's similar to a staking model except that the machines, they have to actively work. So it's not quite staking because you don't just passively stake REN and earn rewards. The REN bond is more like a right to work. And then once you've bonded that you have the right to work, but you still have to turn on a machine that will actually actively participate in the network and do work.

Ren Risks

CR: What are the risks? Or at least known risks. For example, recently we've seen all these oracle attacks and I assume that for the system to work correctly, you need to know at what prices to buy tokens. So are faulty prices a risk, for example?

LW: So there's actually no need for an oracle in RenVM. It's oracle-less in that sense. We don't actually have to worry about that. To resist things like, you know, the flash loans attacks that we saw recently against platforms like bZx, it takes several months to register and de-registered in the system. So you can't just sort of quickly borrow some REN, sign up a dark node and try and attack and then give it right back in one one transaction. It takes up to a month to register a node. So you have to bond the node and then wait to be led into the network. And then when you want to leave the network, you have to wait two to three months.

The big risk that users are exposed to is, I like to think about it as compounding risk. So when you're on the Bitcoin blockchain and you're holding BTC, you're exposed to Bitcoin risk, you know that someone might 51% attack the network and that will devalue the network. When you're in Ethereum you're exposed to the same risk. When you've got Bitcoin on Ethereum, you're actually exposed to both risks. And RenVM has its own risks of collusion and attacks to the network, just like any blockchain does. So when you're holding your Bitcoin on Ethereum, you're exposed to Bitcoin risk and you're exposed to RenVM risk and you're exposed to ETH risk. Now in practice, these risks are very low. I don't think we've ever seen 51% attack on Ethereum, for example, or on Bitcoin. The likelihood that something happening is still very low, but still the safest place to keep your Bitcoin is always going to be on Bitcoin. So we don't encourage people to keep the Bitcoin there and just sort of like have it on Ethereum to have it handy.

CR: Have you had an audit?

LW: Yeah, so we are currently underway with our audit. That's basically the only thing that's standing between us and going to main net is getting our audit results back in a few weeks. So it's very hard to give precise estimates because the kind of stuff that we've built has never really been built before. So it's very difficult to know how long an audit will take and what might be found in that audit and therefore how long it will take to fix those bugs. Our priority is safety and security and making sure that this network has no critical issues that can cause a loss of funds or an actual breakage of the network.

Getting Bitcoin on Dapps

CR: For Dapps to integrate to this network, what do they need to do? And what would it look like for the end user?

LW: From the Dapps perspective when the Bitcoin arrives on Ethereum, it arrives as an ERC20. Almost every Dapp or DeFi protocol supports ERC20s. They don't typically have to do anything to support having Bitcoin on Ethereum because it is just an ERC20.But what you can do and what we've done with Uniswap —and this is the great thing about DeFi and permissionless networks is that you can build stuff on other people's protocols and no one could stop you–– is we have a little adapter that sits at the front of Uniswap and it sort of talks to RenVM in RenVM's language and then gets the Bitcoin as an ERC20 and then sends it off to Uniswap and then Uniswap sends it back to whatever the counterpart of the trade was, and then they adaptor can send that back to you. This adaptive contract in the middle, they worry about the translation between those two languages, if you want.

From the Dapp developers perspective, all they have to do is write this little adaptive contract. And these adaptive contracts are very thin. They're a couple of lines of code and then attach a little widget to their front end. And this will handle all of that translation between the different languages between different blockchains. And so a user can come up and just see a Bitcoin deposit address and they just send their Bitcoin to that address, like a normal Bitcoin transaction. And then that will initiate whatever action it was that they were trying to take. So it's very easy.

Adoption Efforts

CR: You mentioned RenVM provides tools for developers to build these integrations. What else are you currently working on to gain adoption?



LW: So we've built a bunch of developer tools and we're still building them an, constantly getting feedback and improving these dev tools. And these dev tools make it as easy as possible for Dapp developers to integrate their applications. So the Ren Alliance is the main way that we're tackling adoption. It's a consortium of, I think at the moment we've announced 38 projects and we've got a bunch of other ones that are going to be announced in the second round. These are all projects that are committed to helping secure network and helping to use the network and the liquidity that that is going to be accessible. So obviously you gain access to Bitcoin and there's a ton of liquidity there. With these projects we help them do co-marketing. We help with any development needs that they have to get integrated if they have any problems. And so that's how we're tackling it. We don't want to build our own dapps. We don't want to compete with any of these systems. We just want to be a tool to empower them to be better basically.

Plans for Decentralized Governance

CR: I wanted to ask you about governance. You have the REN token and so many projects in the space are launching their own token-based governance processes. Are you thinking about doing the same? And, and also what is the level of control that the team has over the project?

LW: Governance is a really interesting question. And it's actually the next major thing we're thinking about in terms of adding to the protocol. So when we launch, it's actually really important to us that we maintain a level of central control of the governance because if there are bugs or if there are things that need to be changed, it's very important that we can react and respond to that quickly and effectively. So while the network is in its very early days and it's sort of bootstrapping and getting out there, we will maintain a governance alongside members of the Ren Alliance, who will opt in to helping us with that governance.

But we haven't decided on a specific model yet. There are some particular features that I find interesting in governance that we're thinking about getting into our system. So there's things like inflation to incentivize participation. Things like quadratic voting to try and resist big whales coming in and owning the vote. Delayed voting or time-bonded voting so your bond gets more powerful the longer you're willing to bond your voting tokens for. And all of this is stuff that we're looking at and trying to understand how it's going to work in the context of RenVM. But at the end of the day, what we will do is make the governance of the system completely open to participation by REN holders. We don't want to maintain governance over the system for any longer than we absolutely have to and we want to get that out to the community as quickly as possible.

[ … ]

Paid subscribers have access to the full interview, including sections on:

Ren’s funding and monetization strategy

View on competitors

Interoperability impact to DeFi

Subscribe now so you don’t miss any of The Defiant content. Subscribers reading this post: Head to posts marked with the little lock to see the full content.

The Defiant is a daily newsletter focusing on decentralized finance, a new financial system that’s being built on top of open blockchains. The space is evolving at breakneck speed and revolutionizing tech and money. Sign up to learn more and keep up on the latest, most interesting developments. Subscribers get full access at $10/month or $100/year, while free signups get only part of the content.

Click here to pay with DAI.There’s a limited amount of OG Memberships at 70 Dai per annual subscription ($100/yr normal price).

About the author: I’m Camila Russo, a financial journalist writing a book on Ethereum with Harper Collins. (Pre-order The Infinite Machine here). I was previously at Bloomberg News in New York, Madrid and Buenos Aires covering markets. I’ve extensively covered crypto and finance, and now I’m diving into DeFi, the intersection of the two.