Multi-Bridge

C4C has chosen to utilize the many avenues of multi-chain, as well as stabilty of ETH, capabilty of Avalanche and speed of Binance chain through Multi-Swap. Our cyber footprint as a dedicated crypto service will be expanded through the ablity to offer, multichain oppurtunities.

(a) Native Assets AnySwap

When a token already exists on a chain, we refer to it as a native asset. An example is USDC. In this instance, Multichain cannot mint the asset, so instead we use liquidity pools. A number of tokens are added by Multichain, a project team, or individuals to the pool on each chain. These tokens are then available for a user when they move cross chains. Ideally there are enough on each chain so that no matter how many tokens are transferred, there are enough in the pool for them. When a user moves say N XYZ tokens from chain A to chain B, those N tokens are available for another user who is transferring XYX from chain B (or chains C, D, E etc.) to chain A. They enter the liquidity pool on chain A. The total number of XYZ in the liquidity pools on all chains remains the same (unless extra XYZ are specifically added or removed by someone to the pools).
Multiswap Bridge Info
The sequence that is followed when a user transfers XYZ from chain A to chain B is:
-(i) The XYZ is added to the pool on chain
A.(ii) The same number of anyXYZ are minted on chain
A.(iii) The SMPC node network detects this and causes anyXYZ to be minted on chain B, burning those on chain
A.(iv) If the number of XYZ on chain B is greater than the anyXYZ created, then the XYZ are sent to the user's wallet on chain B and the anyXYZ are burned on chain B. If the number of XYZ is less than anyXYZ, then the user is left with their anyXYZ and this represents their pool share to be redeemed later by them for XYZ when there are enough again (by'Removing'them).