Throughout the process of building and launching CUB on the Binance Smart Chain, we realized that one of the most demanded apps is a permissionless asset bridge from ETH to BSC.
As of now, there are few ways to bridge ERC20 assets to BEP20 assets. A lot of dev activity and capital has migrated to the Binance Smart Chain. This is not to say that ETH is any less valuable, only that BSC provides a much more user and developer-friendly playground for DeFi applications that require a significant number of transactions (i.e. the Cub Finance DeFi app).
As of now (July 8th, 2021), LeoBridge allows for ERC20->BEP20 cross-chain swaps.
ERC20->BEP20 is just the beginning of what we can do with LeoBridge. One of the core values of LeoFinance and Cub Finance is interoperability.
We want to serve as a bridge to all major blockchain protocols and allow our users to seamlessly access the top dApps and cryptocurrencies in this space now and in the future.
We believe that ERC20 -> BEP20 is a killer feature due to the current status of trying to swap funds from Ethereum to Binance Smart Chain but we also believe that this is just a glimpse of the future of cross-chain swapping.
The future of LeoBridge is in seamless cross-chain swaps and interactions with all major blockchains and cryptocurrencies. Every swap will bring in the 0.25% swap fee and burn both CUB and bLEO.
Phase 1: ERC20 -> BEP20 token swaps
Phase 2: BSC -> Polygon token swaps (In Progress)
Phase 3: Polygon -> BSC token swaps
Phase 4: BEP20 -> ERC20 token swaps
Phase 5: HIVE -> BEP20 token swaps
Phase 6: HIVE -> Polygon token swaps
After nearly 2 months of development, we're excited to finally launch LeoBridge - our solution to permissionless cross-chain token swaps. LeoBridge will continue to scale with swap caps as liquidity and usage deepens.
Getting LeoBridge to the form you see today took several iterations both on the frontend and backend. The original idea was to integrate a simple swap UI into the existing Cub Finance app but that idea was scrapped mid development.
After going back to the drawing board a few times, the Uniswap UI was chosen and forked to create the UI you see today. LeoBridge is now a standalone application, although inherently tied to the Cub Finance platform through menu links, branding and swap fees.
As we move into LeoBridge Phase 2 and beyond, you'll see this UI change drastically to handle more blockchain asset conversions while maintaining a clean and simple UX.
LeoFinance has a unique tokenomic structure. We have 3 tokens that represent LEO:
Native LEO (Hive Blockchain)
Wrapped LEO (Ethereum Blockchain)
BEP20 LEO (Binance Smart Chain)
Polygon LEO (In Progress)
Wraps can be performed instantaneously for minimal fees across these 3 versions of LEO. This allows our users to do some interesting things like participate in ETH-based applications and seamlessly unwrap assets onto the Hive blockchain and then rewrap LEO onto the Binance Smart Chain to participate in Cub Finance or other BSC dApps.
Utilizing this tri-token economy, LeoBridge allows users to swap any ERC20 token into any BEP20 token using smart contracts that interact with wLEO (ERC20) -> LEO (Hive) -> bLEO (BEP20).
LeoBridge offers a seamless way to convert ERC20 assets into BEP20 assets. It's the most unique cross-chain bridge setup we've seen.
Users simply enter an ERC20 input on the LeoBridge UI
Enter a BEP20 output
BSC receiving address
The UI shows approximate send / receive amounts after slippage and swap fees are calculated.
Like any other DeFi app, a token approval TX is required before any swaps can occur for a specific ERC20 asset. Once approved, the UI allows the user to swap that token into any desired BEP20 output.
Once the user clicks swap, they're prompted to send their ERC20 asset. From there, LeoBridge smart contracts handle the rest until it delivers the BEP20 asset to the user's wallet.
On the backend, LeoBridge follows a process that looks like this:
ERC20 Input -> wLEO -> LEO -> bLEO -> BEP20 Output
From the User's perspective, this is a simple swap page like any other AMM. On the backend, LeoBridge is handling the swap by:
Taking the ERC20 Input
Swapping it for wLEO
Unwrapping wLEO into native LEO
Rewrapping LEO into bLEO
Swapping bLEO for the chosen BEP20 Output
LeoBridge will calculate slippage / fees for this cross-chain swap. The Binance Smart Chain side of this mechanism is much cheaper relative to the Ethereum side of the swap mechanism. Depending on the time of day, gas fees on Ethereum can be relatively expensive.
LeoBridge doesn't side step these gas fees. Instead, it offers a way to seamlessly get assets from ERC20 to BEP20. For many users, this may be the last ETH gas fee they ever pay as moving assets to BSC and remaining there for the forseeable future makes the most sense.
Outside of slippage and gas fees, LeoBridge takes a 0.25% swap fee. This swap fee is sent to the Cub treasury and 100% of the fee is utilized to buy/burn CUB and bLEO using the same structure as Cub Finance vault revenue.
80% of the swap fee burns CUB
20% of the swap fee burns bLEO
At launch, we enabled a $3,000 swap cap. We will regularly raise the cap to allow for larger and larger swaps as the bridge matures and wLEO and bLEO gain more liquidity pool depth.
LeoBridge is an incredibly long-term project. Our intention is to service ERC20 -> BEP20 swaps now and continually add new protocol support for other blockchains in the future. A multi-phase launch with continuous swap cap raises is our path to achieving this over the coming weeks and months.
In phase 1 and 2 of LeoBridge, 2 liquidity pools make bridge TXs possible:
As of launch, wLEO-ETH has $1.6M in total liquidity and bLEO-BNB has $1.5M in total liquidity.
All swaps through LeoBridge are handled via the wLEO and bLEO liquidity pools. When an ERC20 is swapped for a BEP20, it is first swapped into wLEO, unwrapped and rewrapped into bLEO. That bLEO is then immediately swapped for the chosen BEP20 output.
In the user's eyes, they never really owned LEO through the life of the bridge trade. They are not exposed to the price movement since the bridge TX immediately unwraps and rewraps their swap value and converts it into the BEP20 output.
LeoBridge slippage is based on the depth of liquidity in each side of the bridge pool. The ETH side and BSC side have almost identical liquidity right now and allow for mid-sized swaps with low slippage.
We believe that the maturity of LeoBridge will coincide with the rapid increase in depth seen on the wLEO and bLEO liquidity pools. In order for LeoBridge to be viable in the long-run for large Bridge TXs, we need to see the $ value of liquidity pool depth increase drastically. This happens when:
More assets (wLEO & ETH, bLEO & BNB) are added to the liquidity pools
The value of assets in the liquidity pools increase
There is an inherently positive feedback loop for LeoBridge and the liquidity pools on either side of the bridge: as assets are converted, trading volume occurs on both sides of the bridge. This trading volume increases LP rewards via normal LP swap fees. This attracts more liquidity which increases the swap cap and allows for more/larger Bridge TXs.
Bridge TXs also generate Bridge fees which are used to buy/burn CUB and LEO, creating inherent demand and value for LEO as the Bridge gains adoption. In other popular DeFi projects, deterministic value is used to describe built-in value mechanisms that can be used to determine a base value for an asset. We believe a similar phenomenon will take place as LeoBridge gains adoption and expands to support a multitude of popular blockchain protocols.