When building a Dapp on a chain like BSC, you’re traditionally limited to an addressable market of users who hold assets in a BSC wallet, on BSC . This is true despite the fact that most Dapps (like a DEX or a game) are agnostic to the chain they’re built on, meaning that a user interested in an application would likely use it independent of the chain it was built on if they could. Enabling cross chain deposits lets users’ with assets on a single chain use Dapps regardless of what chain they are built on. For example, a BSC Dapp limited to BSC based deposits is chasing a piece of a TAM of $4.6B, if that developer enabled cross chain deposits across the entire EVM ecosystem, that total addressable TVL balloons to $39B.
There’s no reason not to expand the addressable market of users for a Dapp when your goal is to grow. So, let’s dive right in.
Wormhole is a cross chain messaging protocol that makes it simple to build apps and functionality between different on chain environments. See wormhole.com for examples of Dapps that use WH to go cross chain today.
There are different ways to use Wormhole ranging in complexity and functionality. In 3 lines of code, Wormhole Connect lets user swap native or wrapped assets across any chain. On the other side of the spectrum, Wormhole core message passing lets you pass data and call any function across chains via a direct integration with the core Wormhole contracts.
Today, we’re going to use the Wormhole Typescript SDK, and enable cross chain deposits without writing any smart contract code.
Assuming you haven’t yet begun build your application start here to setup your environment.