Host 2 Host is Live

This post was originally published on RenVM

We are very excited to announce Host 2 Host is now live on Mainnet!

Host 2 Host allows RenVM to support and bridge almost any asset on any blockchain. A few examples of the token types and possibilities Host 2 Host provides:

Simply put, this opens up a new world for RenVM and its addressable market.

First Host 2 Host Cohort | New RenVM Assets

The first cohort of assets that RenVM supports is as follows (in alphabetical order):

Native Blockchain Assets

biswap

ERC-20 Tokens

These ERC20 and native chain assets now have wrapped counterparts on all blockchains RenVM supports (e.g. $renMIM on Binance Smart Chain, Polygon, Fantom, Avalanche, Arbitrum, and Solana). Token contracts for all assets on all blockchains that RenVM supports can be found below 👇

https://renproject.github.io/ren-client-docs/contracts/deployments/

Try out moving these assets on our RenJS V3 Demo! 👇
*This is for DEMO and testing purposes only! Don’t expect it to work as a real dApp (again it is a demo) and please do not move large amounts of funds.

Adding Tokens RenVM | Whitelisting via Governance

New token additions will be dictated by community governance. There is a formal whitelisting process that can be found below 👇

RenJS v3 is live | Start Building Cross-Chain dApps!

With the advent of Host 2 Host asset support, the Ren Core Dev team needed to completely overhaul RenJS, the Javascript library that allows third-parties and dApps to interact with, and use RenVM. These changes are significant and have been the biggest update to RenJS to date, making it a far more resilient and usable SDK for the ever-expanding cross-chain DeFi world.

1) Streamlined Addition of New Blockchains
RenJS v1 and v2 relied heavily on Ethereum libraries and types, meaning that a) developers had to import these large libraries even if they were just using other chains (e.g. Bitcoin to Solana) and b) making new chains like Solana much more involved and cumbersome to build with. RenJS v3 has been refactored to no longer rely on these libraries outside of its own Ethereum library. This will significantly speed up adding support for new chains in the future.

2) Updated Interface
Updated interface to match RenVM’s path towards being able to move any value between any chain. This also applies to submitting/waiting for transactions — making it easier for developers to add new chains.

3) Support for Custom Instances
Improve support for using custom and/or local RenVM instances or chain instances.

4) Improved Security
Reduce dependencies to minimize dependency vulnerabilities/attacks.

These improvements will greatly expand RenJS’s ability to serve the DeFi ecosystem and enhance cross-chain composability, so start building 👇

https://renproject.github.io/ren-client-docs/ren-js/ren-js-v3

If you have any questions while building join our RenJS Discord channel here.

Looking forward & next steps | In order of priority

Today marks the release of the Mainnet contracts — there is still plenty to do and the fruits of H2H will take time to bear fruit, so please be patient. With that said, our next steps are outlined below:

We are very excited to finally release Host 2 Host but again, have plenty of work ahead of us, so get involved in the community via Discord and help RenVM become THE universal Bridge for DeFi.

Onwards and upwards,
— Ren Community

About Ren

Ren is an open protocol that enables the movement of value between blockchains.

Website | Docs | Discord | Announcements | Twitter | Reddit | Github

Leave a Comment