In this blog post, we’re going to dig into the easiest ways for developers to bring BTC, BCH, and ZEC to Ethereum. For the purposes of the post, we will discuss BTC, but the process is identical for all other assets supported by RenVM.

While any DeFi project can use BTC by simply adding renBTC as another ERC20 to their stack, we believe that true interoperability is when users can interact with different dapps on different blockchains without needing to think about interoperability at all: no wrapping, no unwrapping, no waiting for confirmations, and no paying for gas.

If users are selling BTC on a DEX, it shouldn’t matter where the DEX is deployed. Users should only have to make a BTC transaction. Everything else should be taken care of.

To that end, the Ren team has developed GatewayJS, Confirmation-as-a-Service (CaaS), and Gas-as-a-Service (GaaS), allowing developers to quickly and easily create a native cross-chain experience. Together, these tools allow developers to create a user-experience that has the minimum amount of friction possible.