Multichain (Any Swap) Bridge On Avalanche

    Our goal in creating this dashboard is to familiarize with the multi-chain inter-chain bridge that supports the Avalanche chain and users can transfer their assets, the most important of which are stable coins and wrapped tokens such as WETH and WBTC, from this chain. give to other chains they can also transfer their assets from other chains to the Avalanche network. Volumetric and countable data related to this inter-chain bridge is presented in this dashboard.

    📖 INTRO

    The Multichain platform, or AnySwap, helps you transfer your assets from one blockchain to another. The transfer of liquidity between blockchains and the connection of blockchains with each other is one of the problems that various projects have been trying to solve for a long time. Users use centralized exchanges like Binance to transfer cash between blockchains. A large number of users use centralized exchanges to transfer liquidity between blockchains. But it should be kept in mind that the existence of a centralized exchange for the transfer of cash between two decentralized networks has risks, one of which is endangering the user's privacy, and it can be said that the existence of a centralized entity in this transfer is in conflict with the nature of decentralization. Another risk that users may face is the blocking of assets in a centralized exchange. The Multichain platform can provide this need of users and be an alternative to centralized entities in the transfer of assets between blockchains.This platform supports the Avalanche blockchain network and users can transfer their assets between this network and other networks.

    🔧 METHOD

    The most important table used in this topic is ez_decoded_event_logs. By placing the address of the multichain contract in ORIGIN_TO_ADDRESS and using two key parameters 0x0175b1c4 as an input parameter for ORIGIN_FUNCTION_SIGNATURE and 0xedbdf5e2 as an output parameter for this data and using the ID of different chains extracted from the Chainlist website and the address of the bridged token contracts, We were able to call Volumetric and countable data for this topic. In the volume calculation section, we used the fact_token_transfers table and by joining this table with the dim_contract table, we called the actual volumes of the bridged tokens. The called volume was extracted using the Row_amount parameter.

    db_img