🌉 Development - Brewlabs Bridge
The Brewlabs Bridge dAPP acts as a cross-network "unibridge" for token transfers between blockchains.
Current networks accommodated within the Brewlabs Bridge include:
- Binance Smart Chain
- Kucoin Chain
- Polygon (Matic)
Each token that exists in cryptocurrency is deployed on a native blockchain, for example Ethereum, Polygon or Binance Smart Chain. Tokens that are deployed on native blockchains cannot swap (trade) with tokens or currencies that have been deployed on other native blockchains. This means that if a token is deployed on Ethereum (ERC20) it cannot swap through a decentralised exchange (DEX) with a token on the Binance Smart Chain (BEP20).
If the community behind a project that was deployed on BEP20 (Binance Smart Chain) would like to open the same project on ERC20 (Ethereum), the community would need to explore a cross-chain bridge to allow people on both ERC20 and BEP20 to swap for the project token.
The Brewlabs Bridge has been developed with proprietary code logic allowing the smart contract behind the bridge to provide a number outcomes when a wallet is using the bridge. Our smart contract will bank tokens within the contract, and each time a wallet uses the bridge, the contract will query if it can use the banked tokens OR is required to mint a pegged wrapped token. The bridge will also accept liquidity from tokens to contribute to their bridging token balance. By banking tokens within the Brewlabs Bridge, tokens are removed from circulating supply until called upon by a bridging transaction.
To use the bridge you can access it here.
If your token is not visible on the Brewlabs Bridge that means that your token contract has not been integrated into the Brewlabs Bridge. To integrate your currency please direct your community and project leaders to the Brewlabs Services Hub.