Problems with Traditional Bridges

Issues with Traditional Bridging Infrastructure

1. Projects must form bridging liquidity pools for the bridge in addition to standard DEX liquidity pools for swapping. This typically requires projects to spend large sums in bridge liquidity.

2. Traditional bridging infrastructure charges a baseline fee of ~$5 - $10 per transaction in addition to a cross-chain fee. If the bridge user is only transacting small amounts, this can be a significant percentage of their transfer. For example, a $50 cross-chain transfer of an altcoin will result in a $5.05 - $10.10 (10% - 20%) cross-chain fees. On ETH, these numbers are much higher.

3. Using traditional bridging infrastructure, the more tokens you bridge, the longer you wait. Bridge users can wait anywhere from minutes to days. If the bridge liquidity becomes too low, users will receive "any-tokens" which act as a placeholder or an "IOU" from the bridge. These tokens are effectively useless.

4. Not Custom - Traditional bridges do not allow projects to customize the bridging infrastructure.

5. Traditional bridging methods only allow the transfer of tokens. While we specialize in tokens, we can also transfer any form of data cross-chain. (NFTs, veNFTs, Notifications, Messages, Signals, etc).

6. Risk: If the traditional bridge is hacked, your tokens will be drained. The bridge liquidity pool is an attack vector for hackers to exploit. And we've seen it be exploited countless times.

Value Provided Via TBaaS Infrastructure

Please note - the below numbered list corresponds to solving the problems in the above numbered list:

1. TBaaS does NOT require bridging liquidity pools. Projects no longer need to shell out vast amounts of bridge liquidity per chain.

2. TBaaS does not charge a baseline fee. Users who wish to transact small amounts can now do so without paying large percentages in fees.

3. TBaaS is instant. Since we do not use bridging liquidity pools, we can send bridge tokens as fast as the blockchains will allow.

4. TBaaS was designed to be turn-key, you sign up and it works from day one. However, it was built to be customized by developers. The code we provide our clients is very small. Developers are encouraged to add in additional features to their TBaaS custom bridge. These additional features could allow our clients to provide additional revenue streams for their project.

5. TBaaS can transfer any form of data.

6. TBaaS avoids this attack vector completely. Since we do not have bridge liquidity pools, liquidity draining attacks on our bridge is impossible. Further, due to our service being Trustless, even if CryptoLink is hacked, our clients will NEVER lose any funds. (We use a double verification method where we NEVER have access to our clients' keys.)